Securities trading system with identity authentication and securities trading method with identity authentication

Biometric authentication and FIDO integration at trade execution points in securities trading systems address the vulnerability of existing systems by ensuring user verification at critical moments, enhancing security and preventing fraudulent transactions.

WO2026235156A1PCT designated stage Publication Date: 2026-11-12MATSUNAGA CHIKARA
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/JP2026/017443
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-08-20
Filing Date
2026-05-06
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

Existing securities trading systems lack robust security measures during the execution of trades, as user authentication is only required at login, leaving them vulnerable to fraudulent transactions once the user is logged in.

Method used

Implementing biometric authentication using facial images or fingerprint images at the moment of trade execution, coupled with FIDO authentication, to ensure user identity verification at critical points of the trading process.

Benefits of technology

Enhances security by requiring user authentication at the time of trade execution, preventing fraudulent activities and ensuring the legitimacy of transactions through automatic facial image capture and FIDO authentication, thus providing high security with minimal user inconvenience.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure JP2026017443_12112026_PF_FP_ABST
    Figure JP2026017443_12112026_PF_FP_ABST
Patent Text Reader

Abstract

[Problem] To achieve both a high level of security and immediacy in a securities trading system. [Solution] Provided is a securities trading service involving identity authentication processing, by using an object for securities trading data input / output or a securities trading application in which an open authentication code for identity authentication and a trade execution close authentication code for identity authentication are set for each user. Identity authentication processing is executed by a trade-start identity authentication processing module 210 for executing identity authentication processing at the start of a trade and by a data input / output processing module 310. When a securities trade execution instruction is received, image capture of a user's face image by a camera is linked to the securities trade execution instruction by using a module 220 for identity authentication processing at the time of a securities trade execution instruction and a module 330 for linking a securities trade instruction with image capture. Identity authentication is executed by using the module 220 for identity authentication processing at the time of a securities trade execution instruction, and securities trade instruction data is transmitted upon receipt of the authentication result of the identity authentication processing at the time of the securities trade execution instruction.
Need to check novelty before this filing date? Find Prior Art

Description

Securities trading systems and securities trading methods that require identity verification.

[0001] The present invention relates to a securities trading system with user authentication that operates on a computer system, and a method for providing securities trading services with user authentication.

[0002] In the financial instruments trading market, a wide variety of commodities and futures products are traded, including securities, bonds, foreign currencies, and precious metals. In recent years, securities trading has been carried out using digital data on computers and networks, in a world where buy and sell orders intersect and transactions are completed. Cybercrime has become more sophisticated in recent years, and it is believed that criminal groups are deceiving investors through various means to steal user identification IDs and passwords. For example, cybercrimes such as "phishing," which involves luring users to fraudulent sites through emails impersonating securities companies, and "hacking," which involves obtaining information by infecting personal devices with malicious programs, are becoming problematic. Therefore, as a measure to prevent such cybercrimes, so-called two-factor authentication and two-step authentication are attracting attention as effective methods of identity verification. Two-factor authentication and two-step authentication verify the user's identity when logging into a securities trading system by requiring the input of multiple factors or by requiring additional input using a constantly changing "one-time password."

[0003] These two-factor authentication and two-step authentication can be expected to provide a certain improvement in security against cyberattacks, but they are basically set when a user logs in to a securities trading system, and once the user authentication is successful at login and the user is in a state where the service can be enjoyed, user authentication is basically not required thereafter. In other words, once the user authentication is successful only once at the start of service use and the service becomes available, it is merely presumed that the legitimate user has continued to use the service throughout the entire service usage period until the end of subsequent service use. That is, there has been no special security setting for user authentication when executing securities trading such as a "buy order" or "sell order" for securities. In other words, once logged in successfully, most securities trading systems allow trading to be executed simply by pressing an operation button at the time of executing a securities trade such as a "buy order" or "sell order".

[0004] FIG. 23 is a diagram that briefly illustrates the user authentication procedure in a general securities trading system, that is, the operations of launching an application, opening a user account file, then using the trading service of the securities trading system to specify the "issue", "trade type", and "number of traded shares", and pressing the operation buttons for a "buy order" and a "sell order". By way of example, this represents a typical operation example of "buy order" and "sell order" in the prior art securities trading system.

[0005] As shown in FIG. 23(a), the securities trading application 10 is installed on a computer system or a smartphone, and when a user intends to use the securities trading application 10, the securities trading application 10 is started by selecting the icon of the securities trading application 10 displayed on the monitor of the computer system or smartphone with a pointing device such as a mouse, and performing an operation such as double-clicking.

[0006] Furthermore, each user's file 20 is installed on the computer system in the securities trading application 10, and their respective icons are displayed on the monitor. When a user selects the icon of the user authentication file 20 with a pointing device such as a mouse and activates it by double-clicking, as shown in the upper part of Figure 23(b), the user is prompted to enter a password or passkey, user identification ID information from an IC card, or biometric information to perform identity verification. In the case of two-factor authentication or two-step authentication, the user is required to enter multiple factors or a specified code such as a one-time password. If the identity verification is successful, the securities trading application 10 starts up, the user authentication file 20 is loaded, and the user becomes ready to place buy and sell orders using the securities trading application 10, and the data contents are displayed on the monitor.

[0007] Next, as shown in the right-hand diagram of Figure 23(b), the desired number of shares of the desired stock are set using the securities trading application 10. Here, to prevent incorrect input of the stock or the number of shares to be traded, it is possible to have the user individually press a confirmation button or enter code information. Once the input settings for the buy and sell orders are complete, the user selects the operation button labeled "buy order" or "sell order" displayed on the screen of the securities trading application 10 on the monitor and presses it by clicking or tapping, and the securities trading application 10 executes the trade. Generally, the user authentication file 20 is closed by tapping the "close" icon, as shown in the lower part of Figure 23(b). In this way, most securities trading applications 10 do not require the input of a special password or user identification ID information when closing the user authentication file 20, and conventional securities trading applications 10 can simply terminate and close the user authentication file 20.

[0008] In other words, while the authentication process in general securities trading systems requires users to input information for authentication based on various security levels, such as two-factor authentication or two-step authentication, to verify whether the user has legitimate authorization, it is assumed that once authentication is successful during login, the authorized user will continue to use the service correctly for the entire duration of use. In reality, no special security settings are made when placing trade orders or when closing the securities application 10 or user authentication file 20.

[0009] In conventional technology, only Patent No. 6476533 discloses a system that achieves a high level of security by requiring and verifying user authentication at both the time the user authentication file is opened when the service is started and when the user authentication file is closed when the service is finished.

[0010] Figure 24 is a simplified diagram illustrating the user authentication procedure according to Japanese Patent No. 6476533. As shown in Figure 24, application 100-1 includes the application's main function 101, as well as an application file unlocking function 102, an application file editing function 1011, and an application file locking function 103. The application's main function 101 is diverse depending on the service used and is equipped with various functions for providing the service. It is also assumed that the application file editing function 1011 is included and includes general-purpose functions such as data input, data output, and data storage. Here, it is equipped with a function to edit data on the opened user authentication file 110. The content of the data editing is not particularly limited, and various data can be input, rewritten, added, or modified on the user authentication file 110. The application file unlocking function 102 receives an open authentication code input, verifies the authentication of the open authentication code, and if authentication is successful, opens the corresponding user authentication file 110, indicating that user authentication has been successful. The application file locking function 103 receives a close authentication code, verifies the authentication of the close authentication code, and if authentication is successful, it considers the user authentication to be successful, enables editing of the user authentication file 110, confirms the data content, and closes the open user authentication file 110 after a normal termination.

[0011] Thus, only Patent No. 6476533 in Patent Document 1 discloses a system that achieves a high level of security by requiring and verifying user authentication at both times: when opening the user authentication file at the start of service use and when closing the user authentication file at the end of service use.

[0012] Japanese Patent Publication No. 6476533, Japanese Unexamined Patent Publication No. 2009-271581, Japanese Unexamined Patent Publication No. 2021-144598, Japanese Unexamined Patent Publication No. 2022-075773

[0013] Inventor Riki Matsunaga believed that in order to prevent fraudulent transactions by impersonating others after illegally obtaining IDs and passwords through phishing and hacking when using securities trading services such as securities, it is important to perform not only user authentication when logging into the securities trading system, but also when executing trades, in order to improve security and prevent fraudulent use. The technology disclosed in Japanese Patent Publication No. 6476533 is a system that requires the input of a closed authentication code when a securities transaction is executed and completed, and is expected to be effective to a certain extent.

[0014] However, performing identity verification is often inconvenient for users. While it is understood that necessary identity verification procedures should be tolerated to prevent fraudulent use, having to perform identity verification procedures according to the requirements and operating procedures of the service provider application is extremely troublesome.

[0015] Therefore, the present invention aims to provide a system that ensures a high level of security for securities transactions using a securities trading system, such as securities, by requiring user authentication at the time of execution, while also being extremely easy to operate and allowing for the confirmation of securities transaction execution in a short amount of time.

[0016] To achieve the above objectives, the securities trading service provision system with user authentication of the present invention not only authenticates the user's identity when logging into the securities trading application, but also captures the user's biometric information (such as a facial image or fingerprint image) at the critical moment when issuing an order to execute a securities trade, and enhances security by performing user authentication using said biometric information (such as a facial image or fingerprint image). The present invention provides a securities trading service provision system with identity authentication, which provides a securities trading service with identity authentication processing using a securities trading data input / output object or securities trading application to which an open authentication code for identity authentication and a transaction execution closed authentication code for identity authentication are set for each user, and is characterized by comprising: a securities trading start identity authentication processing module that executes identity authentication processing using the user's open authentication code for identity authentication at the start of a securities trade; a data editing processing module that inputs securities trading data to the user transaction data input / output object or the application; a securities trading execution instruction capture image linkage control processing module that controls the linkage between receiving a transaction execution instruction for the securities trade and capturing an image of the user's face or fingerprint; a securities trading execution instruction identity authentication processing module that executes the identity authentication processing using the data obtained from the capture image processing by the securities trading execution instruction capture image linkage control processing module and the transaction execution closed authentication code in conjunction with the transaction execution instruction; and a securities trading execution processing module that transmits the securities trading data to a securities trading network system with the success of the identity authentication processing by the securities trading execution instruction identity authentication processing module as the processing execution condition.

[0017] The term "code" is used for both open authentication codes and closed authentication codes for transaction execution, but here, "code" broadly refers to data that can be matched with input data entered for identity verification, including not only character code information and index information, but also data based on features obtained from biometric image data such as facial images and fingerprint images, and challenge codes in FIDO authentication. An "open authentication code for identity verification" is an authentication code used for identity verification when starting to use the securities trading system, and may be character code information, image data such as facial images and fingerprint images, converted data, or a challenge code in FIDO authentication. Where "facial image" or "facial image data" is used in this specification, it means "biometric image" or "biometric image data," and biometric information includes facial images, fingerprint images, iris images, and voice data. A "closed authentication code for transaction execution" is any authentication code used for identity verification when executing securities or bond transactions using the securities trading system, and may be facial image converted data or a challenge code in FIDO authentication. If user authentication is successful during transaction execution using this transaction execution close authentication code, the entered securities transaction data is transmitted to the securities trading network system. In other words, it is sufficient for the transaction to be executed, and whether or not it includes termination processing of the securities trading client application is optional. The image capture linked to the instruction to execute a securities transaction only needs to be linked to the act of pressing the instruction button labeled "Execute Transaction" that appears on the monitor after entering the details of the securities transaction, or to the act of inputting an instruction by voice, and the camera capture is controlled accordingly. The means for receiving execution instructions may be provided by the user authentication application interface. In conjunction with this action of the user instructing to execute a securities transaction, the user's facial image capture is performed and a facial photograph is taken. This system, in which a facial image is forcibly and automatically taken in conjunction with the instruction to execute a transaction, and the successful authentication using the captured facial image data for matching or FIDO authentication is a condition for executing a securities transaction, is a novel technology and allows for a securities trading service provision system that performs user authentication at the decisive and important moment of transaction execution.

[0018] With the above configuration, not only is the user authentication process at the start of a securities transaction performed automatically, but the process of capturing the user's facial image is also automatically controlled in conjunction with the securities transaction execution instruction. This ensures extremely high security because user authentication is also performed at the time of the securities transaction execution instruction. Furthermore, since the process of capturing the user's facial image is automatically controlled in conjunction with the securities transaction execution instruction, the user does not perform the act of capturing the image at will; it is a mandatory, automatic capture that requires no operation from the user. In addition, the "execution condition" for the securities transaction execution process is the mandatory acquisition of facial image data from the capture of the user's facial image, and the facial image data entered at that time can be treated as evidence data linked to the confirmation of the user's intent.

[0019] Here, the aforementioned securities transaction execution instruction capture image synchronization control processing module can perform multiple roles and functions. First, depending on the system configuration, if an execution instruction is given, the securities transaction execution instruction capture image synchronization control processing module itself can capture a facial image or terminal state and obtain the captured image or feature data to use for user authentication. Second, depending on the system configuration, it can perform trigger control to start FIDO authentication processing. Trigger control is the control that synchronizes the securities transaction execution instruction and FIDO authentication to create a trigger to start FIDO authentication processing. It operates as a control module that synchronizes the securities transaction execution instruction and FIDO authentication processing.

[0020] The aforementioned transaction execution close authentication code is generated by the securities transaction execution instruction user authentication processing module as a code that reflects the securities transaction data content entered by the user, thereby fixing the securities transaction content. The securities transaction execution instruction user authentication processing module is equipped with a securities transaction data content authentication function that, upon receiving a transaction execution instruction for the securities transaction, presents the entered securities transaction data content to the user and allows the user to confirm the securities transaction data content. It is preferable to link the input of the transaction execution close authentication code by the user with the execution of the securities transaction by the user. With the above configuration, performing authentication processing using the transaction execution close authentication code authenticates the code that reflects the securities transaction data content entered by the user, and in other words, it is possible to perform "intention authentication" that the user has "intentionally" approved the transaction content in addition to identity authentication.

[0021] Next, the objects of the user transaction data input / output include either a group of securities transaction data associated with the user's securities trading account or a group of securities transaction data stored in a data storage area associated with the user account, or a combination thereof. The transaction data of a user account may be referred to in various ways, such as files, blocks, pages, and records, but these are all equivalent in this invention.

[0022] Next, there are at least two patterns for the system configuration of the securities trading system of the present invention described above. The first system configuration pattern is one in which a securities trading server, a user terminal which is a securities trading client, and the securities trading network system are connected by a computer network. Multiple securities trading servers may cooperate to form a securities trading network system. In other words, a processing module that performs identity authentication processing is included in the securities trading server. In addition, multiple securities trading servers may cooperate to form a securities trading network system. In this first system configuration pattern, the capture shooting linked control processing module when a securities trading execution instruction is given is implemented in the user terminal, and the identity authentication processing module when a securities trading start is given, the identity authentication processing module when a securities trading execution instruction is given, and the securities trading execution processing module are implemented in the securities trading server.

[0023] Next, the second system configuration pattern is one in which a securities trading server, a user terminal acting as a securities trading client, the securities trading network system, and an authentication server are connected by a computer network. In other words, the authentication server, which is equipped with a processing module that performs user authentication processing, is configured independently of the securities trading server. It is also possible for multiple securities trading servers to cooperate and form a securities trading network system. In this second system configuration pattern, it is sufficient that the capture shooting linked control processing module when a securities trading execution instruction is given is implemented in the user terminal, the user authentication processing module when a securities trading start and the user authentication processing module when a securities trading execution instruction is given are implemented in the authentication server, and the securities trading execution processing module is implemented in the securities trading server. Various configurations of securities trading systems are possible, but a variety of system configurations can be accommodated by using the above two patterns of system configuration as a basis.

[0024] Next, as the identity authentication process in the securities trading system of the present invention described above, a FIDO authentication process compliant with the FIDO standard can be used. In the case of the first system configuration pattern described above, the securities trading server is configured to include a FIDO server compliant with the FIDO standard, and the user terminal is configured to include a FIDO authenticator. In the case of the second system configuration pattern described above, the authentication server is configured to include a FIDO server compliant with the FIDO standard, and the user terminal is configured to include a FIDO authenticator. In either of the above configurations, the identity authentication process at the time of the securities trading execution instruction using the transaction execution close authentication code in the identity authentication processing module at the time of the securities trading execution instruction is a FIDO identity authentication process compliant with the FIDO standard, and the capture shooting linked control processing module at the time of the securities trading execution instruction executes a trigger control to start the FIDO authentication process, synchronizing the transaction execution instruction and the FIDO authentication process. In either of the above configurations, a FIDO identity authentication process compliant with the FIDO standard can be adopted as identity authentication at the start of a securities trade. At the time of this patent application, FIDO2 is the mainstream FIDO standard, but subsequent FIDO standards that will appear in the future may also be included.

[0025] Next, various user terminals can be envisioned in the system configuration, and various FIDO authenticators can also be envisioned depending on the user terminal. The first pattern is one in which the user terminal is a smartphone and the FIDO authenticator is a platform authenticator installed on the smartphone, and the FIDO authentication process by the platform authenticator is performed in conjunction with the operation of the securities transaction execution instruction. In this pattern, the user authentication processing module at the time of securities transaction execution instruction and the capture shooting linked control processing module at the time of securities transaction execution instruction initiate WebAuthn / Passkey authentication via an application or browser on the user terminal, Face ID is activated by the OS during this process, and after successful user verification, a FIDO2 Assertion is generated using the private key. The second pattern is one in which the user terminal is a personal computer and the FIDO authenticator is a trusted platform (TPM) authenticator or an OS-managed platform authenticator installed on the personal computer, and the FIDO authentication process by the platform authenticator is performed in conjunction with the operation of the securities transaction execution instruction. In this pattern, the authenticator within the TPM or under OS management performs user verification through an authentication flow such as the WebAuthn API or Windows Hello for Business, and a FIDO2 Assertion is generated using the private key only if user verification is successful. The third pattern is that the user terminal is a personal computer, and the FIDO authenticator is a USB roaming authenticator connected to the personal computer, and the FIDO authentication process is performed by the USB roaming authenticator in conjunction with the operation of the securities transaction execution instruction. In this pattern, the USB roaming authenticator, which is an external FIDO authenticator connected to the user terminal, performs user verification in response to the authentication request by PIN input, touch operation, or built-in biometric authentication of the authenticator itself, and a FIDO2 Assertion is generated using the private key only if user verification is successful.

[0026] Next, when using FIDO authentication processing in the securities trading system of the present invention described above, a challenge code is used, and there are at least two patterns for the challenge code that becomes the transaction execution close authentication code. The first pattern of the challenge code that becomes the transaction execution close authentication code is a challenge code issued by the FIDO server and is a random number pattern. The second pattern of the challenge code that becomes the transaction execution close authentication code is generated as a challenge code issued by the FIDO server, and this challenge code is generated as a code that reflects the securities trading data content input by the user by the securities trading execution instruction user authentication processing module, so that the securities trading content is fixed on the server side. In particular, it is preferable that the securities trading server is equipped with a hash processing module, and the code that reflects the securities trading data content in the challenge code is obtained by the securities trading server using data using the securities trading data content input by the user via the user terminal, and that the securities trading data content authentication function is provided to present the securities trading data content to the user via the user terminal at the time of receiving the securities trading execution instruction, and to allow the user to confirm the securities trading data content. In the above configuration, the execution conditions for the securities transaction execution instruction personal authentication processing module can be set as the fulfillment of both the successful completion of personal authentication using the transaction execution close authentication code and the successful completion of securities transaction data content authentication.

[0027] Here, the securities transaction data content to be targeted may include, for example, the stock, buy / sell category, quantity, price, order type, account ID, timestamp, and session ID. If a securities transaction data content authentication function is provided that presents the securities transaction data content to the user via the user terminal at the time of receiving the instruction to execute the securities transaction, and allows the user to confirm the securities transaction data content, then the execution conditions of the securities transaction execution instruction time user authentication processing module can be set as the conditions for both the successful completion of user authentication using the transaction execution close authentication code and the successful completion of securities transaction data content authentication. In this way, by using a hash obtained by converting a code that reflects the securities transaction data content, the challenge code used for user authentication using the FIDO server at the time of securities transaction execution instruction (when securities transaction content is confirmed) will reflect the securities transaction data content, the transaction content itself will be included as the target of FIDO signing, and the user will be able to confirm the securities transaction content at the time of securities transaction execution instruction through FIDO signing, and in other words, "intention authentication" can be performed in addition to user authentication, indicating that the user has "intention" to approve the transaction content.

[0028] Next, in the above configuration, it is preferable that the transaction instruction capture shooting linked control process can determine that the user who is the target of the capture shooting and is positioned in front of the camera is a three-dimensional person. In other words, security can be improved by performing liveness verification.

[0029] For user registration data, it is preferable to use data from which features have been extracted using facial image data provided through eKYC, in order to maintain a high level of security. Several types of eKYC (electronic Know Your Customer) are available. For example, some use "digital signature certificates for public personal authentication services (digital signature certificates recorded on My Number cards)," while others use "images of photo identification documents" and "camera-captured images." With the former, the facial image on the My Number card can be captured, and if a My Number card reader is used, public information such as name, address, date of birth, and gender can also be used. With the latter, the facial image from official identification documents such as My Number cards or driver's licenses, as well as images of the applicant taken with a smartphone, can be captured. With the above configuration, the facial image data provided through eKYC can be used as facial image data that has been officially recognized and registered by various governments, thus increasing security. If new users are allowed to register their facial images without proof of identity, it would allow malicious individuals to impersonate others and register their own faces as if they were the actual users. However, by using facial image data provided through eKYC, it is possible to prevent such malicious individuals from interfering.

[0030] Next, in the securities trading system of the present invention described above, it is also preferable that the personal authentication processing module at the time of securities trading commencement instruction or the personal authentication processing module at the time of securities trading execution instruction receives input of information on one other element related to the user, in addition to the user's facial image data obtained from the capture shooting process linked to the reception of the securities trading execution instruction by the capture shooting linked control processing module at the time of securities trading execution instruction, and performs two-factor authentication using the captured facial image data and the information on the other element. With the above configuration, so-called two-factor authentication can be performed in the personal authentication processing at the time of securities trading commencement instruction and the personal authentication processing at the time of securities trading execution instruction, by adding one other element in addition to the captured image, thereby further improving security. For example, it is also preferable that the other element of information be any of the following: the user's public personal number, the PIN set on the user's public personal number card, the user ID number assigned by the document management service provider, the PIN linked to the user ID number, device ID data or GPS location information input via wireless communication from an electronic device or medium held by the user, or liveness information indicating that the user is alive. This information is extremely effective for identity verification, and incorporating it into two-factor authentication is beneficial.

[0031] Next, in the securities trading system of the present invention described above, it is preferable to include a registration data storage unit that stores user registration data for user registration, and a recent user registration data storage unit that stores recent face image data of the user recently captured by the execution instruction capture-linked control processing module, and in the identity authentication processing at the time of execution instruction by the identity authentication processing module at the time of execution instruction, a matching process of three face image data is performed: the user registration data, the recent face image data, and the captured face image data. With the above configuration, in addition to the face image of the execution instructioner and the registered face image forcibly acquired by the capture image, the capture image acquired in the most recent securities trading is also included, and by performing three image matching, it is possible to take into account the changes in the user, who is the execution instructioner, over time, and the accuracy of confirming identity is increased.

[0032] Next, in the securities trading system of the present invention described above, the facial image data refers to data based on feature data extracted from the facial image data. In the above description, the terms "captured facial image of the execution commander" and "registered facial image" are used, but in reality, instead of matching facial image data with each other, it is more common to first extract feature quantities from the facial image data and then match those feature quantities with each other. Similarly, in the securities trading system of the present invention, the process is not necessarily limited to matching facial image data with each other, and it is also preferable to match the feature quantities extracted from each of those facial image data.

[0033] Next, in the securities trading system of the present invention described above, there is also a configuration that includes state transition control to switch between an enabled state and an disabled state of a user account. In the securities trading system of the present invention described above, a user account is provided for each user to manage access to the securities trading data, and an account management unit is provided to manage the user account for each user, and the account management unit has a status management function that manages whether the access to the securities trading data managed by the user account for each user is in an allowed or denied state, and by default the account management unit sets the status of the user account for each user to the denied state uniformly, and if the user's authentication at the start of the securities trading using the open authentication code is successful, the account management unit individually changes the status of the user account to the allowed state, and if the user's authentication at the time of issuing a securities trading execution instruction using the closed authentication code is successful, the account management unit individually changes the status of the user to the denied state after the securities trading execution processing module has executed the contents of the securities trading execution instruction. With the above configuration, the state transition control causes all user accounts to be in the default state of the "denied" status. When user authentication is successful at the start of a securities transaction, the user accounts are individually changed to the "enabled" status. After the securities transaction is executed, when user authentication is successful at the time of the securities transaction execution instruction, all user accounts return to the original default state of the "denied" status. This is an extremely unique state transition control that prevents malicious third parties from interfering.

[0034] Next, the scope of application of the present invention will be described. The securities trading services may include general securities trading services, bond trading services, foreign exchange margin trading services, and the like.

[0035] The securities trading service provision system of the present invention can also be provided as a method for providing securities trading services. Furthermore, the present invention can also be provided as a program for executing the securities trading service provision method.

[0036] This figure shows two patterns of system configuration examples. This figure shows a system configuration example of the securities trading service provision system 1 according to Example 1. This figure shows an overview of the identity authentication process and exchange of securities trading data between the securities trading server and the user terminal in the configuration example of Figure 2. This is a diagram (1) that simply shows the basic data flow in the basic configuration of the securities trading service provision system 1. This is a diagram (2) that simply shows the basic data flow in the basic configuration of the securities trading service provision system 1. This is a diagram (3) that simply shows the basic data flow in the basic configuration of the securities trading service provision system 1. This figure shows a configuration example in which the identity authentication process according to Example 2 is executed by the authentication server 5. This figure shows an overview of the identity authentication process and exchange of securities trading data between the authentication server 5 and the user terminal 3 in the configuration example of Figure 7. This figure shows a configuration example in which the identity authentication process according to Example 3 is executed by the FIDO server 400 of the securities trading server 2. This figure shows an overview of the identity authentication process and exchange of securities trading data in the configuration example of Figure 9. This is a diagram (1) that simply shows the basic data flow in the basic configuration of the securities trading service provision system 1 of Example 3. This is a diagram (part 2) that simply illustrates the basic data flow in the basic configuration of the securities trading service provision system 1 of Example 3. This is a diagram (part 3) that simply illustrates the basic data flow in the basic configuration of the securities trading service provision system 1 of Example 3. This is a diagram showing an example configuration in which the identity authentication process according to Example 4 is executed by the FIDO server 400 of the authentication server 5. This is a diagram showing an overview of the exchange of identity authentication processing and content authentication data for securities trading in the configuration example of Figure 14. This is a diagram (part 1) that simply illustrates the basic data flow in the basic configuration of the securities trading service provision system 1 of Example 4. This is a diagram (part 2) that simply illustrates the basic data flow in the basic configuration of the securities trading service provision system 1 of Example 4. This is a diagram (part 3) that simply illustrates the basic data flow in the basic configuration of the securities trading service provision system 1 of Example 4. This is a diagram with an added configuration for identity authentication using the history information of the user's facial image according to Example 5. This is a diagram showing an overview of identity authentication using the history information of the user's facial image executed in the configuration example of Figure 19.This figure shows a configuration for managing the status of a user account for securities trading using the account management unit 160 according to Example 6. This figure shows an overview of the status control of access to a user account for securities trading performed in the configuration example of Figure 21. This figure shows an overview of the operation of a conventional general application. This figure briefly explains the configuration of an application disclosed in the conventional Japanese Patent Publication No. 6476533.

[0037] The user authentication process is performed using computer resources capable of performing user authentication. However, there are two possible configurations for the authentication server, which is such a resource: one where it is independent of the securities trading server, and another where it is built within the securities trading server. Figure 1(a) is an example of the first pattern of system configuration, simply illustrating a pattern where the authentication processing module that performs user authentication is implemented as part of the securities trading server. Figure 1(b) is an example of the second pattern of system configuration, simply illustrating a pattern where the authentication server that performs user authentication is configured independently of the securities trading server. Below, as Example 1, we will describe an example of the pattern shown in Figure 1(a) where the authentication processing module is implemented within the securities trading server. As Example 2, we will describe an example of a configuration where the authentication server shown in Figure 1(b) is provided independently of the securities trading server. As Example 3, we will describe an example of the pattern shown in Figure 1(b) in which the authentication server performs "FIDO authentication" as the user authentication process. In the following description of the securities trading service provision system of the present invention, we will use "securities trading system" as an example. However, by substituting the products and services handled by the securities trading server, it is possible to apply this invention to other bond trading service provision systems, etc. In this specification, any mention of "facial image data" may be replaced with "feature quantities extracted from facial image data."

[0038] Figure 2 is a diagram showing an example of the system configuration of the securities trading service provision system 1 according to Embodiment 1, and is a diagram showing an example of the implementation of a processing module in the system configuration of Figure 1(a). Figure 3 is a diagram showing an overview of the user authentication process and the exchange of securities trading data between the securities trading server and the user terminal in the example system configuration of the securities trading service provision system 1 of Figure 2. Figures 4 to 6 are diagrams (part 1, part 2, and part 3) that simply show the basic data flow in the basic configuration of the securities trading service provision system 1.

[0039] As shown in Figure 2, the basic configuration of the securities trading service provision system 1 consists of a securities trading server 2, a securities trading user terminal 3, and a securities trading network system 4. The securities trading server 2 is equipped with a securities trading server application 100 and an identity authentication application 200. The securities trading server application 100 consists of a data editing processing module 110, a securities trading execution processing module 120, a securities trading user database 130, and a securities trading data area 140 linked to a user account.

[0040] The data editing processing module 110 inputs securities transaction data entered by the user via the data input / output module 310 of the user terminal 3 into the securities transaction data area 140 in the securities transaction user database 130 of the user application 100. Since a securities transaction data area 140 exists for each user account, input and editing are performed in the securities transaction data area 140 of the user who has completed the identity authentication process and is able to use the securities transaction service. As described later, the securities transaction execution processing module 120 transmits the securities transaction information in the securities transaction data area 140 linked to the user account in the securities transaction user database 130 to the securities transaction network system 4 after the identity authentication is completed when a securities transaction execution instruction is given. The securities transaction user database 130 is a database that stores and manages securities transaction data areas 140 for each of multiple user accounts. The securities transaction data area 140 is a data area 140 that holds securities transaction data assigned to each user account, and it is sufficient if it is linked to a user account, and may be in units such as files, blocks, pages, or database records. The file format and database management method are not limited to any specific type, but they must be compatible with the securities trading user database 130.

[0041] The user authentication application 200 is configured to include a user authentication processing module 210 for when a securities transaction is initiated, a user authentication processing module 220 for when a securities transaction is executed, and a registration authentication code data storage module 230. In this configuration example, the registration authentication code data storage module 230 is located within the user authentication application 200, but it can also be configured to be stored in the user file 140 or on a storage device.

[0042] The Securities Trading Initiation Command User Authentication Processing Module 210 is a module that performs user authentication when a securities trading initiation command is issued. As described above, when the user authentication process at the time of the securities trading initiation command is performed using facial image data, the Securities Trading Initiation Command User Authentication Processing Module 210 performs facial image matching processing using the facial image captured by the Securities Trading Initiation Command Capture Image Linkage Control Processing Module 320 on the user terminal 3 and the registered open authentication code 231 (in this case, the registered facial image) for user authentication at the time of the securities trading initiation command. When the user authentication process at the time of the securities trading initiation command is performed using a password, password matching processing is performed using the password entered via the data input / output module of the user terminal 3 and the registered open authentication code 231 (in this case, the registered password) for user authentication at the time of the securities trading initiation command. Note that when the user authentication process at the time of the securities trading initiation command is performed using a password, the Securities Trading Initiation Command Captured Facial Image Matching Processing Module 211 and the Securities Trading Initiation Command Capture Image Linkage Control Processing Module 320 do not need to be started.

[0043] The Securities Trading Initiation Start-Upon Instruction Face Image Matching Processing Module 211 is a module used when the user authentication process performed at the time of the Securities Trading Initiation Instruction uses features obtained from face image data for matching. In this operation, the Securities Trading Initiation Start-Upon Instruction Capture Image Linkage Control Processing Module 320 of the user terminal 3 performs the matching process using matching data generated using at least a portion of the features obtained from the user's face image data captured in conjunction with the Securities Trading Initiation Instruction. The user registration data used for the user matching process is registered as the registration open authentication code 231 for securities trading initiation instruction user authentication in the registration authentication code data storage module 230, and the matching process between the user registration data and the matching data is performed.

[0044] The captured face image collation processing module 220 at the time of issuing a securities transaction execution instruction is a module that executes personal authentication processing performed when a securities transaction execution instruction is issued. This module executes collation processing using collation data generated by using at least a part of the feature quantity obtained from the user's face image data captured in conjunction with the securities transaction execution instruction by the capture and photographing interlocking control processing module 330 at the time of issuing a securities transaction execution instruction of the user terminal 3. Note that, similarly to the above, the user registration data used for the user's collation process is user registration data generated by using at least a part of the feature amount obtained from the user's face image captured at the time of registration, and is registered as the registered open authentication code 232 for personal authentication at the time of issuing a securities transaction execution instruction in the registration authentication code data storage module 230, and the collation process between the user registration data and the collation data is executed. In this embodiment, the personal authentication process at the time of issuing a securities transaction execution instruction is performed by personal authentication using a face image.

[0045] The registration authentication code data storage module 230 is a storage device that holds and manages, for each user, a registered open authentication code 231 for personal authentication at the time of a securities transaction start instruction, and a registered transaction execution closed authentication code 232 for personal authentication at the time of a securities transaction execution instruction. The registered open authentication code 231 for personal authentication used at the time of issuing a securities transaction start instruction may be a password if the operation uses a password or the like for personal authentication, or face image data or a feature amount extracted from the face image data if the operation uses a face image for personal authentication. In the present invention, the registered transaction execution closed authentication code 232 for personal authentication at the time of issuing a securities transaction execution instruction is based on the premise that personal authentication at the time of issuing an order execution instruction for a securities transaction is performed by capturing a photograph of the user's face image, and since the operation uses the face image for personal authentication, it is face image data or a feature amount extracted from the face image data.

[0046] The user terminal 3 has a securities transaction client application 300 installed therein, and is configured to include a data input / output module 310, a capture and photographing interlocking control processing module 320 at the time of issuing a securities transaction start instruction, and a capture and photographing interlocking control processing module 330 at the time of issuing a securities transaction execution instruction.

[0047] The data input / output module 310 may enable data input and output via an input / output user interface provided to the user. The input securities transaction data is transmitted to and entered into the user file 140 in the securities transaction user database 130 of the user application 100.

[0048] The securities transaction start instruction time capture and photographing interlocking control processing module 320, in the operation where a face image is used for identity authentication at the time of a securities transaction start instruction, interlocks with the user's instruction to start a securities transaction to photograph the user's face image via a photographing means such as a camera. For a smartphone, the equipped camera may be used, and for a personal computer, the installed camera may be used. The face image data captured in an interlocked manner is transmitted to the securities transaction start instruction time identity authentication processing module 210 of the securities transaction server 2.

[0049] The securities transaction execution instruction time capture and photographing interlocking control processing module 330 is capable of assuming multiple roles and functions. First, if there is an execution instruction as required by the system configuration, the securities transaction execution instruction time capture and photographing interlocking control processing module itself captures a face image or terminal state to obtain the captured image or obtain a feature value to link to identity authentication. In the configuration example of this first embodiment, this function is exerted, and in response to a securities transaction execution instruction, the securities transaction execution instruction time capture and photographing interlocking control processing module 330 activates and operates the camera to capture a face image or terminal state, obtain a feature value from the captured image, and link it to identity authentication. For a smartphone, the equipped camera may be used, and for a personal computer, the installed camera may be used. The face image data captured in conjunction with the securities transaction order execution instruction is transmitted to the securities transaction execution instruction time identity authentication processing module 220 of the securities transaction server 2.

[0050] Securities trading network system 4 refers to a network system that handles the target securities and involves multiple securities trading service providers. In this example, since the target is securities trading, in Japan, this could include front-end systems of core systems such as the Tokyo Stock Exchange, Osaka Securities Exchange, and Nagoya Stock Exchange (order systems, execution systems, settlement systems, etc.), back-end systems such as THE STAR, and international systems.

[0051] Figure 3 is a diagram illustrating the general configuration of Figure 2, showing the user authentication process and the exchange of securities trading data between the securities trading server 2 and the user terminal 3. As shown in Figure 3, users of securities trading perform three main processes using the user terminal 3. The first process (securities trading initiation process) is user authentication performed at the start of securities trading. When the user presses the "start trading" button, the securities trading server 2 requests user authentication via the user terminal 3, and the user performs the authentication at the time of the securities trading initiation instruction according to the instructions. If authentication is by password, the user enters the specified password via the input screen. If authentication is by facial image, a facial image is taken in conjunction with the pressing of the "start trading" button, and the facial image data is sent to the securities trading server 2. The securities trading server 2 has the open authentication code (password or facial image data) registered at the time of the securities trading initiation instruction registered, and server authentication is performed. If the user authentication at the time of the trading initiation is successful, securities trading can be started. This corresponds to the completion of user login. The second process (input / editing process) is when the user inputs or edits securities trading information via the user terminal 3. Furthermore, it is preferable for the securities trading server 2 to present the contents of the securities trading data to the user terminal 3. The third process (securities trading execution process) is identity authentication performed when executing a securities trading transaction. When a user who has confirmed the contents of the securities trading transaction presses the instruction button to execute the transaction, a facial image is taken in conjunction with the pressing of the instruction button, and the facial image data is sent to the securities trading server 2. Server authentication is performed, and if identity authentication at the time of transaction execution is successful, the transmission of the securities trading order data is executed. This corresponds to the execution of transmission to the securities trading network 4.

[0052] The data flow of the process described in Figure 3 is summarized below. Figure 4 is a simplified diagram (part 1) showing the basic data flow in the basic configuration of the securities trading service provision system 1 according to Example 1. This corresponds to the securities trading initiation process in Figure 3. Here, an example is shown in which identity authentication processing using a facial image is performed. Required user ID information is input via the data input / output module 310 (step S1), and when the user presses the icon button for the securities trading initiation instruction, the camera is operated by the securities trading initiation instruction capture shooting linked control processing module 320 in conjunction with the instruction, and a facial image of the person giving the instruction is taken (step S2). The order of steps S1 and S2 does not matter. The input facial image data is input to the securities trading initiation instruction captured facial image matching processing module 211 (step S3), and the user ID information is input to the securities trading initiation instruction identity authentication processing module 210 (step S4). The registered open authentication code 231 (user registration data) for authentication when issuing a securities trading commencement instruction, which is linked to the entered user ID information, is compared with the facial image data obtained by the camera (step S5). If the comparison is successful (step S5: YES), the user is authorized to log in to the securities trading client application 300 on the user terminal 3 (step S6).

[0053] Figure 5 is a simplified diagram (part 2) showing the basic data flow in the basic configuration of the securities trading service provision system 1 according to Embodiment 1. This corresponds to the securities trading data input and editing process in Figure 3. The user inputs securities trading data, such as buy and sell orders for securities, via the data input / output module 310 of the user terminal 3 (step S7). The securities trading data is passed via the network to the securities trading server 2 of the securities trading company being used, and the securities trading data is input and edited in the user file 140 assigned to the user in the securities trading user database 130 via the data editing processing module 110 (step S8) (step S9). The user may proceed to the securities trading execution process shown in Figure 5 each time editing is performed, or it is possible to input and edit data for multiple securities at any time. The securities trading execution instruction time authentication processing module 220 presents the input securities trading content to the user terminal 3 (step S10). Here, the securities trading execution instruction time authentication processing module 220 generates information that reflects the securities trading data content, and the securities trading content becomes fixed on the server side.

[0054] Figure 6 is a simplified diagram (part 3) showing the basic data flow in the basic configuration of the securities trading service provision system 1 according to Embodiment 1. This corresponds to the securities trading execution process in Figure 3. When the user confirms the presented securities trading details and presses an icon to instruct the execution of a securities trading transaction, such as "Execute Transaction" (step S11), the securities trading execution instruction capture shooting linked control processing module 330 forcibly and automatically captures the user's face image via the camera in conjunction with the instruction, and acquires face image data at the time of the securities trading execution instruction (step S12). Feature quantities are calculated from this face image data, and matching data including these feature quantities is sent to the user authentication application 200 on the securities trading server 2, where user authentication processing is performed at the time of the securities trading order execution instruction. The data is passed to the Securities Transaction Execution Instruction User Authentication Processing Module 220 (Step S13), and the Securities Transaction Execution Instruction User Captured Face Image Matching Processing Module 221 matches the matching data using the feature quantities of the input face image data with the registered transaction execution close authentication code 232 for user authentication when a securities transaction is executed in the registration authentication code data storage module 230 (here, registration data using the feature quantities of the registered user's face image data) (Step S14). If the matching process is successful (Step S14: YES), the user authentication application 200 notifies the securities transaction server application 100 that user authentication has been successful (Step S15), and the securities transaction execution processing module 120 extracts the securities transaction data set in the user file 140 of the user in the securities transaction user database 130 and transmits the securities transaction data to the securities transaction network system 4 via the network (Step S16). The above is an outline of the flow of securities transaction data processing in the securities transaction system according to the present invention.

[0055] As Example 2, we will describe an example of a configuration in which the authentication server 5 is provided independently of the securities trading server 2, as shown in Figure 1(b). Figure 7 shows an example of a configuration in which the authentication process is performed by the authentication server 5. As shown in Figure 7, the basic configuration of the securities trading service provision system 1 consists of a securities trading server 2, an authentication server 5, a securities trading user terminal 3, and a securities trading network system 4. In the configuration of Example 1, the authentication application 200 and the registration authentication code data storage module 230 were provided within the securities trading server 2, but in the configuration of Example 2, there is an independent authentication server 5, and the authentication application 200 and the registration authentication code data storage module 230 are provided within the authentication server 5. In Example 1, the authentication process was completed on-premises within the securities trading server 2, but in Example 2, the authentication server 5 is accessed via the network to exchange data and perform the authentication process. In other words, the authentication server 5 functions as a so-called RP server that provides authentication services to the securities trading server 2. Aside from that point, the functions of each processing module etc. in each configuration are the same, and a detailed explanation is omitted here.

[0056] Figure 8 is a diagram illustrating the configuration example in Figure 7, showing the general flow of user authentication processing between the authentication server 5 and the user terminal 3, and the exchange of securities trading data between the user terminal 3 and the securities trading server 2. As shown in Figure 8, a user using securities trading performs three main processes using the user terminal 3. The first process (securities trading initiation process) is the user authentication process performed when starting a securities trade. This process can be the same as the first process (securities trading initiation process) shown in Example 1, but differs in that the user authentication process at the start of a securities trade is performed by accessing the authentication server 5, which functions as an RP server, via the network. The second process (input / editing process) is the process in which the user inputs or edits securities trading information to the securities trading server 2 via the user terminal 3, and can be the same as the second process (securities trading initiation process) shown in Example 1. The third process (securities trading execution process) is the user authentication process performed when issuing a securities trading execution instruction. This process can be the same as the third process (securities transaction execution process) shown in Example 1, but in Example 2, the difference is that the authentication process for the user when issuing a securities transaction instruction is performed by accessing the authentication server 5 via the network. The basic data flow in the securities transaction service system 1 configured in Example 2 is the same as in Example 1, except that data is exchanged by accessing the external authentication server 5 via the network. The operation of each processing module in each configuration is the same as in Figures 3 to 5 shown in Example 1, so the explanation here will be omitted.

[0057] As Example 3, we will describe an example in which the securities trading server 2 performs "FIDO authentication" as the user authentication process, specifically from the pattern in Figure 1(a). In other words, the configuration involves the on-premise implementation of the FIDO server 400 to handle the authentication process within the securities trading server 2. We will also describe an example in which a challenge code reflecting the securities trading data content is used as the challenge code during user authentication, which is a hash of a code reflecting the securities trading data content, and "intentional authentication" is also performed to confirm that the user has "intention" to approve the transaction content. Figure 9 is a diagram showing an example configuration in which the FIDO server 400 is implemented on-premise in the securities trading server 2 for user authentication processing. Figure 10 is a diagram showing an overview of the user authentication process and the exchange of securities trading data between the authentication server 5 and FIDO server 400, the securities trading server 2, and the user terminal 3 in the configuration example in Figure 9. Figures 11 to 13 are diagrams (parts 1, 2, and 3) that briefly show the basic data flow in the basic configuration of the securities trading service provision system 1 of this Example 3.

[0058] As shown in Figure 9, the basic configuration of the securities trading service provision system 1 of the "FIDO authentication pattern" in Example 3 consists of a securities trading server 2, a FIDO server 400, a securities trading user terminal 3, and a securities trading network system 4. The securities trading server 2 is equipped with a securities trading server application 100, which, like the configurations of Examples 1 and 2, includes a data editing processing module 110, a securities trading execution processing module 120, and a securities trading database 130. Furthermore, it includes a hash processing module 150, which is an addition compared to the configurations of Examples 1 and 2. The basic functions of the data editing processing module 110, the securities trading execution processing module 120, the securities trading user database 130, and the user file 140 are the same as in Examples 1 and 2, so their explanation is omitted.

[0059] The hash processing module 150 converts input data into a hash code using a hash function. It is added as an optional configuration. Securities transaction data input and edited by the user via the data input / output module 310 of the user terminal 3 is input to the data editing processing module 110 and edited in the user data area 140 linked to the user account in the securities transaction user database. In this embodiment 3, however, in parallel with this, the securities transaction data edited in the user data area 140 (for example, data including stock, buy / sell category, quantity, price, order type, account ID, timestamp, session ID, etc.) is converted into hash data using the hash function of the hash processing module 150 and passed to the FIDO server 400. The FIDO server 400 then generates a challenge code for FIDO authentication processing (a transaction execution close authentication code when a securities transaction execution instruction is given) based on that hash data. In other words, the FIDO server 400 of the securities transaction server 2 in this embodiment 3 converts the securities transaction data input by the user into hash data using the hash processing module 150 and adopts the hash data that reflects the contents of that securities transaction data as the challenge code for FIDO authentication processing. This challenge code becomes the "transaction execution close authentication code when issuing a securities transaction execution instruction." In this embodiment 3, the securities transaction server 2 can also perform user authentication using the FIDO server 400 when starting a securities transaction (when logging in), but the challenge code used at that time may be a randomly generated number. On the other hand, user authentication using the FIDO server 400 is performed when issuing a securities transaction execution instruction (when confirming the securities transaction details), and while it is also possible to use a randomly generated number as the challenge code, here we will use an example of operation in which a challenge code reflecting the securities transaction data content described above is adopted.By using a challenge code that reflects the securities transaction data content as the challenge code for user authentication using the FIDO server 400 when issuing a securities transaction execution instruction (when the securities transaction details are finalized), the transaction details are included in the FIDO signature target. Through FIDO signing, the user can confirm the securities transaction details when issuing a securities transaction execution instruction, and in other words, in addition to user authentication, "intention authentication" can also be performed, indicating that the user has "intentionally" approved the transaction details. The securities transaction data content can include, as described above, the stock, buy / sell category, quantity, price, order type, account ID, timestamp, session ID, etc.

[0060] Next, the securities trading server 2 is equipped with an identity authentication application 200 and has a configuration comprising an identity authentication processing module 210 for when a securities trading start instruction is given, an identity authentication processing module 220 for when a securities trading execution instruction is given, and a FIDO server 400. The securities trading server 2 has a FIDO server 400 and a FIDO authentication processing module 410 that manages the open authentication code 231 for when a securities trading start is given and the transaction execution close authentication code 232 for when a securities trading execution instruction is given. The FIDO authentication challenge code used when a securities trading start instruction is given corresponds to the registered open authentication code 231 for identity authentication when a securities trading start instruction is given, as described in Example 1 and Example 2, and is assigned the same code number. The flow of the FIDO identity authentication process will be described later. The FIDO authentication challenge code used when a securities trading execution instruction is given corresponds to the transaction execution close authentication code 232 for identity authentication when a securities trading execution instruction is given, as described in Example 1 and Example 2, and is assigned the same code number. The flow of the FIDO identity authentication process will be described later. As described above, the open authentication code 231 at the start of a securities transaction may be a random number arbitrarily generated by the FIDO authentication processing module 410 at the start of a securities transaction. However, the transaction execution close authentication code 232 at the time of issuing a securities transaction execution instruction is an example in which the FIDO authentication processing module 410 uses hash data that reflects the contents of the securities transaction data generated by the hash processing module 150 as a challenge code.

[0061] The securities trading commencement instruction user authentication processing module 210 controls the user authentication process performed when a securities trading commencement instruction is given. Here, FIDO user authentication processing using the FIDO server 400 is executed. Since it is FIDO user authentication processing, user authentication is performed in cooperation with the FIDO authenticator 350 inside the user terminal 3.

[0062] The securities transaction execution instruction time authentication processing module 220 performs the authentication process performed when a securities transaction order is issued. In this case, FIDO authentication processing is performed using the FIDO server 400. Since it is FIDO authentication processing, authentication is performed in cooperation with the FIDO authenticator 350 in the user terminal 3. In this embodiment 3, the securities transaction execution instruction time authentication processing module 220 has the role of performing trigger control to start the FIDO authentication process and also acts as a control module that synchronizes the securities transaction execution instruction and the FIDO authentication process.

[0063] The FIDO server 400 is a server that performs FIDO user authentication processing in accordance with the FIDO standard. This FIDO server 400 and the FIDO authenticator 350 in the user terminal 3 can be general-purpose devices that comply with the FIDO2 standard. The FIDO authentication processing module 410 holds a public key 411. This public key 411 is a public-key cryptographic key corresponding to the private key 351, which will be described later.

[0064] The user terminal 3 is configured to include a data input / output module 310, a capture shooting linked control processing module 320 when a securities transaction start instruction is given, a capture shooting linked control processing module 330 when a securities transaction execution instruction is given, and a FIDO authenticator 350 within the terminal.

[0065] In Embodiment 3, the securities transaction initiation instruction capture image acquisition linked control processing module 320 and the securities transaction execution instruction capture image acquisition linked control processing module 330 each execute trigger control to start FIDO authentication processing, synchronizing the transaction execution instruction and the FIDO authentication processing. In Embodiments 1 and 2, when a securities transaction initiation instruction was received, image capture processing was executed in conjunction with it. However, in Embodiment 3, trigger control to start FIDO authentication processing is executed, and when a securities transaction execution instruction is received, the linked capture processing of the user's face image or fingerprint image is controlled. This control of the linked face image or fingerprint image capture processing depends on the system configuration of the user terminal 4.

[0066] If user terminal 3 is a smartphone, the FIDO authenticator becomes the platform authenticator installed in the smartphone, and the platform authenticator performs FIDO authentication processing in conjunction with the securities transaction execution instruction. More specifically, the user authentication processing module 220 and the capture shooting linked control processing module 330 at the time of securities transaction execution instruction initiate WebAuthn / Passkey authentication via an application or browser on the user terminal. During this process, Face ID is activated by the OS, and after successful user verification, a FIDO2 assertion is generated using the private key.

[0067] If the user terminal 3 is a personal computer, the FIDO authenticator will be a Trusted Platform (TPM) authenticator installed in the personal computer or a platform authenticator under OS management, and will execute FIDO authentication processing by the platform authenticator in conjunction with the operation of the securities transaction execution instruction. More specifically, the securities transaction execution instruction user authentication processing module 220 and the securities transaction execution instruction capture shooting linked control processing module 330 will perform user verification through an authentication flow such as WebAuthn API or Windows Hello for Business, and a FIDO2 assertion will be generated using the private key only if the user verification is successful.

[0068] In this scenario, the user terminal 3 is a personal computer and the FIDO authenticator is a USB roaming authenticator connected to the personal computer. The FIDO authentication process is performed by the USB roaming authenticator in conjunction with the operation of the securities transaction execution instruction. More specifically, the USB roaming authenticator, which is an external FIDO authenticator connected to the user terminal, performs user verification by PIN input, touch operation, or built-in biometric authentication in response to an authentication request. A FIDO2 assertion is generated using the private key only if user verification is successful.

[0069] Figure 10 is a diagram illustrating the FIDO authentication process and exchange of securities trading data between the securities trading server 2, the FIDO server 400, and the user terminal 3 in the configuration example shown in Figure 9. As shown in Figure 10, a user using securities trading performs three main processes using the user terminal 3. The first process (securities trading initiation process) is the FIDO authentication process performed when securities trading is initiated. When the command button to start trading is pressed, as shown in Figure 10, a facial image is captured by the securities trading initiation instruction capture shooting linked control process, and the FIDO authentication process at the time of securities trading initiation is executed. The securities trading initiation instruction capture shooting linked control processing module 320, the FIDO authenticator 350, and the FIDO server 400 work together to execute the FIDO authentication process at the time of securities trading initiation. The challenge code used here may be a random number challenge code generated by the FIDO server 400. The second process (input / editing process) is when the user inputs or edits securities trading information via the user terminal 3. This process may be the same as in Example 1 and Example 2. The third process (securities transaction execution process) is the FIDO identity authentication process performed when executing a securities transaction. When the command button to execute a transaction is pressed, as shown in Figure 10, a facial image is captured by the capture shooting linked control process at the time of securities transaction execution command, and the FIDO identity authentication process at the time of securities transaction execution command is executed. The terminal's FIDO authenticator 350, the securities transaction execution command identity authentication processing module 220, and the FIDO server 400 work together to execute the FIDO identity authentication process at the time of securities transaction execution command. The challenge code used in the executed FIDO identity authentication process may be a random number, but here, a challenge code based on a hash code that reflects the securities transaction details, called the "transaction execution close authentication code at the time of securities transaction execution command," is used, and identity authentication is performed through verification of the securities transaction details along with identity authentication.

[0070] The following summarizes the data flow of the process described in Figure 10. Figure 11 is a diagram illustrating the FIDO authentication process performed at the start of a securities transaction, which is the first process. As an example, we will explain the case where the user terminal 3 is a smartphone. In order to use "FIDO authentication," it is assumed that the FIDO server 400 in the authentication server 5 holds the public key 411 of the so-called public key cryptography scheme, and the user terminal 3 holds the private key 351. The required user ID information is input via the data input / output module 310, and when the user presses the icon button for instructing to start a securities transaction (step S21), the authentication processing module 210 for instructing to start a securities transaction in the securities transaction server 2 is notified, and the authentication processing for instructing to start a securities transaction initiates (step S22). In this embodiment 3, the FIDO server 400 of the securities transaction server 2 is started and the FIDO authentication process begins. The FIDO server 400 generates a random number to create a "FIDO authentication challenge code." This random number is temporarily held as the "open authentication code 231 for instructing to start a securities transaction." The open authentication code (challenge code) 231 held at the start of securities trading is sent to the user terminal 3 (step S23).

[0071] In parallel with these processes, the following process is also executed. In this process, the securities trading initiation instruction capture-linked control processing module 320 is activated in conjunction with the securities trading initiation instruction, and the platform authenticator performs FIDO authentication processing. Specifically, the securities trading initiation instruction user authentication processing module 210 and the securities trading initiation instruction capture-linked control processing module 320 perform trigger control, and WebAuthn / Passkey authentication is initiated via an application or browser on the user terminal. During this process, the Face ID of the FIDO authenticator 350 is activated by the OS (step S26), and after successful user verification (step S26: Yes), a FIDO2 Assertion is generated using the private key (step S27). This is returned to the FIDO authentication processing module 410 as a signed FIDO authentication challenge code at the start of the securities trading (step S28). The FIDO authentication processing module 410 holds the public key 411 and verifies the signed FIDO authentication challenge code at the start of the securities transaction. It then compares the verified information with the original "FIDO authentication challenge code at the start of the securities transaction" (step S29). If the comparison is successful (step S29: Yes), the FIDO server 400 notifies the securities transaction start authentication processing module 210 that FIDO authentication has been successful (step S30). The securities transaction start authentication processing module 210, upon receiving the notification, notifies the securities transaction server 2 that the authentication process at the start of the securities transaction has been successful (step S32). The data editing processing module 110 then becomes ready to receive securities transaction data via the data input / output module 310 of the user terminal 3. With this, the first process, the authentication process performed at the start of a securities transaction, is completed.

[0072] Next, the process moves to the securities trading data input and editing process. Figure 12 is a simplified diagram (part 2) showing the basic data flow in the basic configuration of the securities trading service provision system 1 according to Embodiment 3. This corresponds to the securities trading data input and editing process in Figure 10. The user inputs securities trading data, such as buy and sell orders for securities, via the data input / output module 310 of the user terminal 3 (step S32). The securities trading data is passed to the securities trading server 2 of the securities trading company (step S33), and the securities trading data is input and edited in the securities trading data area 140 assigned to the user in the securities trading user database 130 via the data editing processing module 110 (step S34). As already mentioned, the securities trading data area 140 can be any input data object linked to the user's securities trading. For example, it can be a group of securities trading data for each user account (the name does not matter, such as trading files or trading records). Here, the securities trading service provision system 1 according to Embodiment 3 performs not only user authentication but also authentication regarding the content of the securities trading data. As the data editing processing module 110 progresses with the input of securities transaction data, it requests the securities transaction execution instruction user authentication processing module 220 to proceed with preparations for executing the securities transaction (step S35).

[0073] The securities transaction execution instruction instruction authentication processing module 220 initiates two processes. The first process involves the hash processing module 150 receiving the securities transaction data (for example, data including stock symbol, buy / sell category, quantity, price, order type, account ID, timestamp, session ID, etc.) that has been input and edited in the securities transaction data area 140, converting it into hash data using a hash function (step S36), and passing it to the FIDO server 400. The FIDO server 400 then generates a challenge code for FIDO authentication processing (transaction execution close authentication code 232 when a securities transaction execution instruction is given) based on this hash data (step S37). In other words, the challenge code based on the hash code that reflects the securities transaction details (data such as stock symbol, buy / sell category, quantity, price, order type, account ID, timestamp, session ID, etc.) becomes the "transaction execution close authentication code 232 when a securities transaction execution instruction is given". In short, the "transaction execution close authentication code 232 when a securities transaction execution instruction is given" is generated as information that reflects the securities transaction data details, and the securities transaction details are fixed on the FIDO server 400 side for verification.

[0074] The second process involves the securities transaction execution instruction user authentication processing module 220 taking in the securities transaction data entered and edited in the securities transaction data area 140 and displaying it on the monitor of the data input / output module 310 of the user terminal 3 (step S38). For example, the securities transaction details such as stock, buy / sell category, quantity, price, order type, account ID, timestamp, and session ID are displayed, and the user can confirm whether they were entered as intended. In other words, a hash code is generated from normalized data identical to the securities transaction details displayed on the user terminal, and this is set as the "transaction execution close authentication code when a securities transaction is executed." At the same time, the same securities transaction details are displayed on the monitor of the data input / output module 310 of the user terminal 3, and the securities transaction data content authentication function allows the user to confirm the securities transaction data details. The content of the user's approval of the displayed content and confirmation of their intention to input it matches the "transaction execution close authentication code when a securities transaction is executed."

[0075] Next, we move on to the securities transaction execution process. Figure 13 is a simplified diagram (part 3) showing the basic data flow in the basic configuration of the securities transaction service provision system 1 according to Embodiment 3. This corresponds to the securities transaction execution process in Figure 10. As shown in the securities transaction data input and editing process in Figure 12 above, when the user operates the user terminal 3 and inputs the securities transaction details into the securities transaction server 2, a FIDO authentication challenge code (transaction execution close authentication code when issuing a securities transaction execution instruction) is generated, and the user can confirm these securities transaction details displayed on the monitor and verify that the securities transaction details are as intended by the user by viewing them on the screen of the user terminal 3.

[0076] When the user confirms the transaction details and presses the icon button for executing a securities transaction (step S39), the securities transaction execution instruction user authentication processing module 220 on the securities transaction server 2 is notified, and the user authentication processing for securities transaction execution instructions is started (step S40). The securities transaction execution instruction user authentication processing module 220 instructs the FIDO authentication processing module 410 on the FIDO server 400 to execute the FIDO user authentication processing for securities transaction execution (step S41). The FIDO server 400 sends the "securities transaction execution closing authentication code 232 for securities transaction execution instructions," which is a challenge code generated in step S37, that is, a challenge code based on a hash code that reflects the transaction details generated by the hash processing module 150, to the FIDO authenticator 350 on the user terminal 3 as a challenge code (step S42). In parallel with these steps, the following steps are also executed. In this step, the securities transaction execution instruction capture shooting linked control processing module 330 is activated in conjunction with the securities transaction execution instruction, and the platform authenticator executes the FIDO authentication processing. The specific process is as follows: Trigger control is performed by the securities transaction execution instruction user authentication processing module 220 and the securities transaction execution instruction capture shooting linked control processing module 330 (step S43), WebAuthn / Passkey authentication is initiated via an application or browser on the user terminal, and in the process, Face ID of the FIDO authenticator 350 is activated by the OS (step S45), and after successful user verification (step S45: Yes), a FIDO2 Assertion is generated using the secret key (step S46).

[0077] The public key 411 is returned to the FIDO authentication processing module 410 as a signed FIDO authentication challenge code at the time of the securities transaction execution instruction (step S47). Since the FIDO authentication processing module 410 holds the public key 411, it verifies the signed FIDO authentication challenge code at the time of the securities transaction execution instruction and compares the verified information with the original "FIDO authentication challenge code at the start of the securities transaction" (step S48). If the verification is successful (Step S48: Yes), the FIDO server 400 notifies the securities transaction execution instruction authentication processing module 220 that FIDO authentication has been successful (Step S49). The securities transaction execution instruction authentication processing module 220, upon receiving the notification, notifies the securities transaction server 2 that the authentication process for the securities transaction execution instruction has been successful (Step S50). The securities transaction execution processing module 120, upon receiving the notification, sends the securities transaction data located in the data area of ​​the corresponding user account from the securities transaction database 130 to the securities transaction network system only if the hash code used for FIDO authentication matches the hash code regenerated from the securities transaction data to be executed (Step S51).

[0078] The above outlines the flow of securities trading data processing in the securities trading system 1 according to Embodiment 3 of the present invention. Furthermore, by using the securities trading system 1 according to Embodiment 3 of the present invention, user authentication is performed, and the securities trading content is fixed on the server side. This content is authenticated by FIDO2 Assertion using the private key on the user terminal 3, and the user can confirm that the securities trading content is as they intended. In other words, since the challenge code that reflects the trading content is the transaction execution close authentication code when issuing a securities trading instruction, user authentication of the securities trading content is also performed.

[0079] As Example 4, we will describe a configuration example using a FIDO server 400 in a system configuration where the authentication process shown in Figure 1(b) is performed by the authentication server 5. As shown in Figure 14, the basic configuration of the securities trading service provision system 1 of the "FIDO authentication pattern" according to Example 4 is a configuration comprising a securities trading server 2, a securities trading user terminal 3, an authentication server 5 equipped with a FIDO server 400, and a securities trading network system 4. The securities trading server 2 has a securities trading server application 100 implemented and is configured to include a data editing processing module 110, a securities trading execution processing module 120, a securities trading user database 130, and a user file 140. The basic functions of each of these modules are the same as in Example 1, so their explanation is omitted here.

[0080] The authentication application 200 of the authentication server 5 is configured to include an authentication processing module 210 for when a securities transaction is initiated and an authentication processing module 220 for when a securities transaction is executed. These may be the same as in Embodiment 3. The authentication server 5 has a FIDO server 400, which is a server that performs FIDO authentication processing in accordance with the FIDO standard. This FIDO server 400 and the FIDO authenticator 350 in the user terminal 3 may be compliant with the FIDO2 standard. The FIDO server 400 has a FIDO authentication processing module 410 which holds a public key 411. This public key 411 is a public-key cryptographic code corresponding to the private key 351 described later. The FIDO server 400 manages the open authentication code 231 when a securities transaction is initiated and the transaction execution close authentication code 232 when a securities transaction is executed. In this embodiment, the case where the user terminal 3 is a personal computer will be explained as an example.

[0081] The open authentication code 231 at the start of securities trading is a FIDO authentication challenge code used when issuing a command to start securities trading. It corresponds to the registered open authentication code 231 for identity verification at the start of securities trading described in Examples 1 and 2, and is assigned the same code number. This "open authentication code 231 at the start of securities trading" is used in the FIDO identity verification process at the start of securities trading (when logging in), and the challenge code used at that time may be a random number arbitrarily generated by the FIDO server 400. The flow of the FIDO identity verification process at the start of securities trading will be described later.

[0082] Next, the securities transaction execution close authentication code 232, which is used when issuing a securities transaction execution instruction, corresponds to the transaction execution close authentication code 232 used for identity verification when issuing a securities transaction execution instruction, as explained in Examples 1 and 2, and is assigned the same code number. The "transaction execution close authentication code 232 when issuing a securities transaction execution instruction" used by the FIDO authentication processing module 410 in Example 4 is used for FIDO identity verification when issuing a securities transaction execution instruction (when the details of the securities transaction are finalized), but as with Example 3, there are multiple patterns for the challenge code used at that time.

[0083] The first challenge code pattern is a random number arbitrarily generated by the FIDO server 400. Since the challenge code itself is merely a random number, the authentication it performs is limited to authenticating the FIDO authenticator 350 within the user terminal 3.

[0084] The second challenge code pattern uses a hash code that reflects the securities transaction data content as the challenge code. In other words, as explained in Example 3, the FIDO authenticator 350 of the user terminal 3 returns a correctly signed challenge code, which is verified by the FIDO server 400's public key and matches with the original challenge code. This allows for "identity authentication" of the owner through device authentication of the user terminal 3. Furthermore, by matching the challenge code, which is a hash code that reflects the securities transaction data content, authentication of the content itself, i.e., the securities transaction data content, can also be performed, i.e., "securities transaction content authentication".

[0085] The user terminal 3 is configured to include a data input / output module 310, a capture image synchronization control processing module 320 for when a securities transaction is initiated, a capture image synchronization control processing module 330 for when a securities transaction is executed, and a FIDO authenticator 350 within the terminal. Of these, the data input / output module 310, the capture image synchronization control processing module 320 for when a securities transaction is initiated, and the capture image synchronization control processing module 330 for when a securities transaction is executed are the same as those described in Example 1 and Example 2, and their description is omitted here.

[0086] Figure 15 is a diagram illustrating the FIDO authentication process and exchange of securities trading data between the securities trading server 2, the user terminal 3, the authentication server 5, and the FIDO server 400 in the configuration example shown in Figure 14. As shown in Figure 15, a user using securities trading performs three main processes using the user terminal 3. The first process (securities trading initiation process) is the FIDO authentication process performed when securities trading is initiated. When the instruction button to initiate securities trading is pressed, as shown in Figure 15, a facial image is captured by the securities trading initiation instruction capture shooting linked control process, and the FIDO authentication process at the time of securities trading initiation is executed. The securities trading initiation instruction capture shooting linked control processing module 320, the FIDO authenticator 350, and the FIDO server 400 work together to execute the FIDO authentication process at the time of securities trading initiation. The second process (input / editing process) is when the user inputs or edits securities trading information via the user terminal 3. This process can be the same as in Examples 1, 2, and 3. The third process (securities transaction execution process) is the FIDO identity authentication process performed when executing a securities transaction. When the command button to execute a transaction is pressed, as shown in Figure 15, a facial image is captured by the securities transaction execution command capture shooting linked control process, and the FIDO identity authentication process for securities transaction execution is executed. The terminal's FIDO authenticator 350, the securities transaction execution command identity authentication processing module 220, and the FIDO server 400 work together to execute the FIDO identity authentication process for securities transaction execution. The challenge code used in the executed FIDO identity authentication process is the "securities transaction execution close authentication code 232," which is a challenge code based on a hash code that reflects the securities transaction details. This performs identity authentication along with verification of the securities transaction details to authenticate the user's intent.

[0087] The data flow of the process described in Figure 15 is summarized below. Figure 16 is a diagram illustrating the FIDO authentication process performed at the start of a securities transaction, which is the first process. In order to use "FIDO authentication," it is assumed that the FIDO server 400 in the authentication server 5 holds the public key 411 of the so-called public key cryptography scheme, and the user terminal 3 holds the private key 351. The required user ID information is input via the data input / output module 310, and when the user presses the icon button for instructing to start a securities transaction (step S60), the authentication processing module 210 for securities transaction start instructions in the securities transaction server 2 is notified, and the authentication processing for securities transaction start instructions is started (step S61). In this embodiment 4, the FIDO server 400 of the authentication server 5 is started and the FIDO authentication process is started. The FIDO server 400 generates a random number to create a "FIDO authentication challenge code." This random number is temporarily stored as the "open authentication code 231 for initiating securities trading," and this stored open authentication code (challenge code) 231 for initiating securities trading is transmitted to the user terminal 3 (step S62).

[0088] In parallel with these processes, the following process is also executed. This process involves the activation of the securities transaction initiation instruction capture image capture linked control processing module 320 in conjunction with the securities transaction initiation instruction (step S63), and the execution of FIDO authentication processing by the platform authenticator (step S64). Specifically, trigger control is performed by the securities transaction execution instruction user authentication processing module 220 and the securities transaction execution instruction capture image capture linked control processing module 330. In this example, the FIDO authenticator is a trusted platform (TPM) authenticator installed in the personal computer or a platform authenticator under OS management. In conjunction with the securities transaction execution instruction operation, the authenticator within the TPM or under OS management performs user verification through an authentication flow such as WebAuthn API or Windows Hello for Business (step S65), and only if user verification is successful (step S65: Yes) is a FIDO2 Assertion generated using the private key. Using the available private key 351, the "FIDO authentication challenge code at the start of securities trading" is signed (step S66), and sent back to the FIDO authentication processing module 410 as the signed FIDO authentication challenge code at the start of securities trading (step S67). Since the FIDO authentication processing module 410 holds the public key 411, it verifies the signed FIDO authentication challenge code at the start of securities trading and compares the verified information with the original "FIDO authentication challenge code at the start of securities trading" (step S68). If the comparison is successful (step S68: Yes), the FIDO server 400 notifies the securities trading start authentication processing module 210 that FIDO authentication has been successful (step S69), and the securities trading start authentication processing module 210, upon receiving the notification, notifies the securities trading server 2 that the securities trading start authentication process has been successful (step S70), and the data editing processing module 110 becomes ready to receive securities trading content data via the data input / output module 310 of the user terminal 3. With the above steps completed, the first process, the identity verification process performed at the start of securities trading, is finished.

[0089] Next, we move on to the securities trading data input and editing process. Figure 17 is a simplified diagram (part 2) showing the basic data flow in the basic configuration of the securities trading service provision system 1 according to Embodiment 4. This corresponds to the securities trading data input and editing process in Figure 16. The user inputs securities trading data, such as buy and sell orders for securities, via the data input / output module 310 of the user terminal 3 (step S71). The securities trading data is passed to the securities trading server 2 of the securities trading company (step S72), and the securities trading data is input and edited in the securities trading data area 140 assigned to the user in the securities trading user database 130 via the data editing processing module 110 (step S73). As already mentioned, the securities trading data area 140 can be any input data object linked to the user's securities trading. For example, it can be a group of securities trading data for each user account (the name does not matter, such as trading file or trading record). Here, the securities trading service provision system 1 according to Embodiment 4 performs not only user authentication but also authentication regarding the content of the securities trading data. As the data editing processing module 110 progresses with the input of securities transaction data, it requests the securities transaction execution instruction user authentication processing module 220 to proceed with preparations for executing the securities transaction (step S74).

[0090] The securities transaction execution instruction instruction authentication processing module 220 initiates two processes. The first process involves the hash processing module 150 receiving the securities transaction data entered into the securities transaction data area 140 and editing it, converting it into hash data using a hash function (step S75), and passing it to the FIDO server 400. The FIDO server 400 then generates a challenge code for FIDO authentication processing (transaction execution close authentication code 232 when a securities transaction execution instruction is given) based on this hash data (step S76). In other words, the challenge code based on the hash code that reflects the securities transaction details (data such as stock, buy / sell category, quantity, price, order type, account ID, timestamp, and session ID) becomes the "transaction execution close authentication code 232 when a securities transaction execution instruction is given". In short, the "transaction execution close authentication code 232 when a securities transaction execution instruction is given" is generated as information that reflects the securities transaction data details, and the securities transaction details are fixed on the FIDO server 400 side for verification.

[0091] The second process involves taking in the securities transaction data (for example, data including stock symbol, buy / sell category, quantity, price, order type, account ID, timestamp, session ID, etc.) that has been entered and edited in the securities transaction data area 140 and displaying it on the monitor of the data input / output module 310 of the user terminal 3 (step S77). For example, the securities transaction details such as stock symbol, buy / sell category, quantity, price, order type, account ID, timestamp, and session ID are displayed, and the user can confirm whether they were entered as intended. In other words, a hash code is generated from normalized data identical to the securities transaction details displayed on the user terminal, and this is set as the "transaction execution close authentication code when issuing a securities transaction execution instruction." At the same time, the same securities transaction details are displayed on the monitor of the data input / output module 310 of the user terminal 3, and the user's confirmation of their approval and input of the displayed content matches the "transaction execution close authentication code when issuing a securities transaction execution instruction."

[0092] Next, we move on to the securities transaction execution process. Figure 18 is a simplified diagram (part 3) showing the basic data flow in the basic configuration of the securities transaction service provision system 1 according to Example 4. This corresponds to the securities transaction execution process in Figure 15. As shown in the securities transaction data input and editing process in Figure 17 above, when the user operates the user terminal 3 and inputs the securities transaction details into the securities transaction server 2, a FIDO authentication challenge code (transaction execution close authentication code when issuing a securities transaction execution instruction) is generated, and the user can confirm the securities transaction details displayed on the monitor and verify that the securities transaction details are as intended.

[0093] When the user confirms the securities transaction details and presses the icon button to instruct the execution of the securities transaction (step S78), the authentication server 5's securities transaction execution instruction user authentication processing module 220 is notified, and the user authentication processing for the securities transaction execution instruction is started (step S79). The securities transaction execution instruction user authentication processing module 220 instructs the FIDO server 400's FIDO authentication processing module 410 to execute the FIDO user authentication processing for the securities transaction execution (step S80). The FIDO server 400 sends the "securities transaction execution closing authentication code 232," which is a challenge code based on the hash code that reflects the transaction details generated by the hash processing module 150 in step S76, to the FIDO authenticator 350 of the user terminal 3 as a challenge code (step S81).

[0094] In parallel with these processes, the following process is also executed. The securities transaction execution instruction triggers the capture image capture linked control processing module 330 (step S82), and the platform authenticator performs FIDO authentication processing. Specifically, the securities transaction execution instruction user authentication processing module 220 and the securities transaction execution instruction capture image capture linked control processing module 330 perform trigger control (step S82), the authenticator within the TPM or under OS management performs user verification through an authentication flow such as WebAuthn API or Windows Hello for Business (step S83), and only if user verification is successful (step S83: Yes) does a FIDO2 Assertion generate using the private key (step S84). In other words, the private key 351 is used to sign the "FIDO authentication challenge code at the time of the securities transaction execution instruction" (step S84), and it is sent back to the FIDO authentication processing module 410 as the signed FIDO authentication challenge code at the time of the securities transaction execution instruction (step S85). Since the FIDO authentication processing module 410 holds the public key 411, it verifies the signed FIDO authentication challenge code at the time of the securities transaction execution instruction and compares the verified information with the original "FIDO authentication challenge code at the start of the securities transaction" (step S86). If the comparison is successful (step S86: Yes), the FIDO server 400 notifies the securities transaction execution instruction authentication processing module 220 that FIDO authentication has been successful (step S87). The securities transaction execution instruction authentication processing module 220, upon receiving the notification, notifies the securities transaction server 2 that the authentication process at the time of the securities transaction execution instruction has been successful (step S88). The securities transaction execution processing module 120, upon receiving the notification, sends the securities transaction data in the data area of ​​the corresponding user account from the securities transaction database 130 to the securities transaction network system only if the hash code used for FIDO authentication matches the hash code regenerated from the securities transaction data to be executed (step S89).

[0095] The above outlines the flow of securities trading data processing in the securities trading system 1 according to Embodiment 4 of the present invention. Furthermore, by using the securities trading system 1 according to Embodiment 3 of the present invention, identity verification is performed, and it is also confirmed that the securities trading content is as the user intended. Since the challenge code is the transaction execution close authentication code at the time of issuing a securities trading instruction, identity verification of the securities trading content is also performed.

[0096] As Example 5, we will describe an example in which a history of the user's facial images is saved, and identity verification is performed between the historical data of these facial images as part of identity verification.Here, we will describe the configuration described in Example 4, with the addition of a configuration that performs identity verification between the historical data of facial images.However, it is also possible to add a configuration to control the state transition of the active / inactive state of the securities trading user account in each of the configurations of Example 1, Example 2, and Example 3.Note that the same components as those described in Example 1 to Example 4 will not be explained.

[0097] Figure 19 shows the configuration of Figure 14 described in Example 4, with the addition of a configuration for user authentication using the user's facial image history information. Figure 20 is a schematic diagram showing the user authentication using the user's facial image history information performed in the configuration example of Figure 19. Here, it is explained that the user authentication using facial image history information is completed within the user terminal 3.

[0098] As shown in Figure 19, the user terminal 3 is equipped with an image history matching processing module 360, which includes a user registration data storage unit 361 (face image history data storage area). The image history matching processing module 360 ​​has a user registration data storage processing function, an execution command capture shooting linked control processing function, and an execution command identity authentication processing function. Although the FIDO2 standard may not store face images acquired for FIDO2 authentication and used for local biometric authentication processing, in this embodiment 5, the face image that is automatically and automatically captured by the execution command capture shooting linked control processing module 330 in the user terminal 3 is used for face image history matching processing separately from the identity authentication processing of the FIDO2 standard, and is not captured separately. The user registration data storage processing function stores the face image data acquired from the user at the time of user registration as user registration data in the user registration data storage unit 361. Furthermore, the recent facial image data saving processing function saves the most recent facial image data of the person who issued the trading order, which was captured by the execution order capture shooting linked control processing module 330 during the most recent securities transaction, to the user registration data storage unit 361. In addition, the execution order identity authentication processing function saves the facial image of the person who issued the trading order, which was captured by the execution order identity authentication processing module 330 during the identity authentication process for the securities transaction currently being executed, to the user registration data storage unit 361.

[0099] Here, the image history matching processing module 360 ​​performs a matching process between the user registration data, the most recent face image data, and the currently running face image data to perform the identity authentication process.

[0100] Figure 20 is a simplified diagram illustrating the concept of the three-party matching process performed by the image history matching processing module 360. Figure 20(a) shows how, when the face image data currently being executed is captured by the execution instruction capture shooting linked control processing module 330 and input to the image history matching processing module 360 ​​as the captured face image data A currently being executed, matching is performed between the most recent face image data B input in the most recent transaction and the user registration data R registered at the time of registration. Since the capture times of the data from these three parties are different, the images will not be perfectly identical, but identity authentication can be performed with a predetermined accuracy rate by comparing the feature quantities extracted from the images.

[0101] Figure 20(b) shows how the execution instruction authentication processing module 330, currently executing, replaces the face image of the execution instructioner captured by image capture with the most recent face image data. In this way, it is not necessary to retain all previously input face image data, and it is replaced with the most recent face image data. Note that this does not preclude the use of multiple face images, such as the most recent (one time ago) face image, and even the face image from two times ago. However, since using all past history face images would place a heavy system load, it is better to limit it to a finite number of times.

[0102] As Example 6, an account management unit is provided to manage the status of whether access to securities trading data managed by each user's user account is permitted or denied, and status management is performed for each user account.Here, we will describe the configuration described in Example 5, with the addition of an account management unit to manage whether the user account for securities trading is permitted or denied, but it is also possible to add an account management unit to the configurations of Example 1, Example 2, Example 3, and Example 4.

[0103] Figure 21 shows a configuration in which, in addition to the configuration of Figure 19 described in Example 5, the status of whether access to a user account for securities trading is permitted or denied is managed using the account management unit 160. In the description of this Example 6, the same components as those described in Examples 1 to 5 will not be explained. Figure 22 shows an overview of the status control of whether access to a user account for securities trading is permitted or denied, as executed in the configuration example of Figure 21.

[0104] As shown in Figure 21, the securities trading server 2 is equipped with an account management module 160. In conventional technology, it is generally the case that all user accounts of users who do not pose any particular problems are enabled. For example, unless a user is on a blacklist or is subject to some kind of sanction, a normal user account is enabled, and as a result, access is permitted for those who have passed authentication. The inventor, Riki Matsunaga, realized that having user accounts always enabled (i.e., access permitted status) even when a user is not conducting securities trading actually leads to security vulnerabilities. He conceived of the idea that security vulnerabilities could be minimized by making it the default state for user accounts to be disabled (i.e., access denied status) when a user is not conducting securities trading.

[0105] The account management module 160 shown in Figure 21 has a status management function that manages whether access to securities trading data managed by each user's user account is permitted or denied. By default, the account management unit 160 uniformly sets the status of each user's user account to the denied status. If the user's authentication is successful when starting a securities transaction, the account management unit 160 individually changes the status of the user account to the permitted status. Furthermore, if the user's authentication is successful when issuing a securities transaction execution instruction using the user's closed authentication code, the securities transaction execution processing module 120 executes the contents of the execution instruction, and then the account management unit 160 individually changes the status of the user account to the denied status. Note that although Figure 21 shows that the data area for each user's securities trading data linked to the user account is managed in the securities trading user database, this can be applied even if the management format of the data area for each user's securities trading data linked to the user account by the securities trading server 2 is not a database format.

[0106] Here, there are two possible patterns for the status management function that manages whether the account management unit 160's access to securities trading data is permitted or denied. Figure 22 is a simplified diagram showing how the status management function executed by the account management module 160 manages whether a user account's access to securities trading data is permitted or denied. Figure 22(a) shows the first pattern of the status management function. The first status management function changes the status of the user account individually to permitted status if the user's authentication at the start of a securities transaction using the user's open authentication code is successful, and then maintains that permitted status. In this first pattern, if the user's authentication at the time of issuing a securities transaction execution instruction using the user's closed authentication code is successful, the execution processing module 120 executes the contents of the execution instruction, and then the account management unit 160 individually changes the status of the user account that was maintained as permitted back to denied status.

[0107] Figure 22(b) shows a second pattern of the status management function. The second status management function provides even stricter status management than the first pattern. If user authentication is successful when starting a securities transaction using the user's open authentication code, the status of the user account is individually changed to an permitted status. However, access is only permitted for the time required for user A to log in to their account after starting the securities transaction. Once the user account is identified, the account management module 160 immediately denies access to the securities transaction data associated with that user account. Note that since the data editing processing module 110 is operating effectively, users can input securities transaction data, and it only needs to be temporarily held. If user authentication is successful when issuing a securities transaction execution instruction using the user's closed authentication code, the account management module 160 changes the status to a permitted status, allowing access to the securities transaction data associated with the user account, and the securities transaction data is reflected. After that, the execution processing module 120 executes the contents of the execution instruction to the securities transaction network system 4, and then the account management unit 160 controls the user account to individually return its permitted status to a denied status. In this way, by establishing an account management unit 160 and managing the status of each user account, it becomes extremely difficult to control intrusions by malicious actors, thereby improving security in securities trading.

[0108] This invention is suitable as a securities trading service provision system for the securities trading field, particularly for applications requiring immediacy and high security.

[0109] 1. Securities trading service provision system 2. Securities trading server 3. User terminal 4. Securities trading network system 5. Authentication server 100. Securities trading server application 200. User authentication application 300. Securities trading client application 400. FIDO server

Claims

1. A securities trading system that provides securities trading services involving identity verification processing using a securities trading data input / output object or securities trading application for which an open authentication code for identity verification and a transaction execution closed authentication code for identity verification are set for each user, comprising: a securities trading start-time identity verification processing module that executes identity verification processing using the open authentication code for identity verification of the user at the start of a securities trade; a data editing processing module that inputs securities trading data into the user transaction data input / output object or the application; a securities trading execution instruction capture image linkage control processing module that controls the linkage between receiving a transaction execution instruction for the securities trade and capturing an image of the user's face or fingerprint; a securities trading execution instruction identity verification processing module that executes the identity verification processing using the data obtained from the capture image processing by the securities trading execution instruction capture image linkage control processing module and the transaction execution closed authentication code in conjunction with the transaction execution instruction; and a securities trading execution processing module that transmits the securities trading data to a securities trading network system with the success of the identity verification processing by the securities trading execution instruction identity verification processing module as the processing execution condition.

2. The securities trading system according to claim 1, wherein the transaction execution close authentication code is generated by the securities trading execution instruction user authentication processing module as a code that reflects the securities trading data content entered by the user, thereby fixing the securities trading content, and the securities trading execution instruction user authentication processing module includes a securities trading data content authentication function that, upon receiving a transaction execution instruction for the securities trading, presents the entered securities trading data content to the user and allows the user to confirm the securities trading data content, and links the input of the transaction execution close authentication code from the user with the user's execution of the securities trading.

3. The securities trading system according to claim 1 or 2, wherein the object of input / output of user transaction data includes either a group of securities transaction data associated with the user's securities trading account or a group of securities transaction data stored in a data storage area associated with the user account, or a combination thereof.

4. A securities trading service provision system according to claim 2, wherein a securities trading server, a user terminal which is a securities trading client, and the securities trading network system are connected by a computer network, the capture shooting linked control processing module when a securities trading execution instruction is given is implemented in the user terminal, and the user authentication processing module when a securities trading is started, the user authentication processing module when a securities trading execution instruction is given, and the securities trading execution processing module are implemented in the securities trading server.

5. A securities trading service provision system according to claim 2, wherein a securities trading server, a user terminal which is a securities trading client, the securities trading network system, and an authentication server are connected by a computer network, the capture shooting linked control processing module when a securities trading execution instruction is given is implemented in the user terminal, the personal authentication processing module when a securities trading start and the personal authentication processing module when a securities trading execution instruction is given are implemented in the authentication server, and the securities trading execution processing module is implemented in the securities trading server.

6. The securities trading service provision system according to claim 4, characterized in that the securities trading server is configured to include a FIDO server compliant with the FIDO standard, the user terminal is configured to include a FIDO authenticator, the authentication process at the time of the securities trading execution instruction using the transaction execution close authentication code in the securities trading execution instruction instruction time authentication processing module is a FIDO authentication process compliant with the FIDO standard, and the securities trading execution instruction time capture shooting linked control processing module executes control of a trigger to start the FIDO authentication process by synchronizing the transaction execution instruction and FIDO authentication, thereby synchronizing the transaction execution instruction and the FIDO authentication process.

7. The securities trading service provision system according to claim 5, characterized in that the authentication server is configured to include a FIDO server compliant with the FIDO standard, the user terminal is configured to include a FIDO authenticator, the authentication process at the time of the securities trading execution instruction using the transaction execution close authentication code in the securities trading execution instruction instruction time user authentication processing module is a FIDO authentication process compliant with the FIDO standard, and the securities trading execution instruction time capture shooting linked control processing module executes control of a trigger to start the FIDO authentication process by synchronizing the transaction execution instruction and FIDO authentication, thereby synchronizing the transaction execution instruction and the FIDO authentication process.

8. The securities trading service provision system according to claim 4, characterized in that the authentication server is configured to include a FIDO server compliant with the FIDO standard, the user terminal is configured to include a FIDO authenticator, the authentication process at the time of the securities trading initiation instruction using the open authentication code in the securities trading initiation instruction instruction module is a FIDO authentication process compliant with the FIDO standard, and the securities trading execution instruction capture shooting linked control processing module executes control of a trigger to start the FIDO authentication process by synchronizing the transaction execution instruction and FIDO authentication, thereby synchronizing the securities trading initiation instruction and the FIDO authentication process.

9. The securities trading service provision system according to claim 5, characterized in that the authentication server is configured to include a FIDO server compliant with the FIDO standard, the user terminal is configured to include a FIDO authenticator, the authentication process at the time of the securities trading initiation instruction using the open authentication code in the securities trading initiation instruction instruction module is a FIDO authentication process compliant with the FIDO standard, and the securities trading execution instruction capture shooting linked control processing module synchronizes the transaction execution instruction and FIDO authentication to control a trigger that starts the FIDO authentication process, thereby synchronizing the securities trading initiation instruction and the FIDO authentication process.

10. A securities trading service provision system according to any one of claims 6 to 9, wherein the user terminal is a smartphone, the FIDO authenticator is a platform authenticator installed in the smartphone, and the platform authenticator performs FIDO authentication processing in conjunction with the operation of the securities trading execution instruction.

11. A securities trading service provision system according to any one of claims 6 to 9, wherein the user terminal is a personal computer, the FIDO authenticator is a trusted platform authenticator or an OS-managed platform authenticator installed on the personal computer, and the platform authenticator performs FIDO authentication processing in conjunction with the operation of the securities trading execution instruction.

12. A securities trading service provision system according to any one of claims 6 to 9, wherein the user terminal is a personal computer, the FIDO authenticator is a USB roaming authenticator connected to the personal computer, and the FIDO authentication process by the USB roaming authenticator is performed in conjunction with the operation of the securities trading execution instruction.

13. The securities trading service provision system according to any one of 6 to 9, characterized in that the transaction execution close authentication code is a challenge code issued by the FIDO server and is a random number.

14. The securities trading service provision system according to any one of 6 to 9, characterized in that the transaction execution close authentication code is generated as a challenge code issued by the FIDO server, and the challenge code is generated as a code that reflects the securities trading data content entered by the user by the securities trading execution instruction user authentication processing module, thereby fixing the securities trading content.

15. The securities trading server is equipped with a hashing module, the code in the challenge code that reflects the securities trading data content is obtained by the securities trading server using data entered by the user via the user terminal and converted by the hashing module, the system is equipped with a securities trading data content authentication function that presents the securities trading data content to the user via the user terminal and allows the user to confirm the securities trading data content when a securities trading execution instruction is received, and the execution conditions for the securities trading execution instruction time user authentication processing module are that both the successful completion of user authentication by the transaction execution close authentication code and the successful completion of securities trading data content authentication are required.

16. The securities trading service provision system according to claim 1, characterized in that the authentication process performed when a trading execution is given in the securities trading execution instruction processing in the securities trading service service provision system 17. The securities trading service provision system according to claim 1, characterized in that the user authentication processing module at the time of start instruction or the user authentication processing module at the time of execution instruction receives input of information on one other element relating to the user, in addition to data based on the user's face image data or fingerprint image data related to the capture shooting process linked to the reception of the securities trading execution instruction by the securities trading execution instruction capture shooting linked control processing module, and performs two-factor authentication using the data based on the captured face image data or fingerprint image data and the information on the other element.

18. The securities trading service provision system according to 16, characterized in that the other one element of information is any of the following: the user's public personal number, the PIN set on the user's public personal number card, the user ID number assigned by the document management service provider, the PIN associated with the user ID number, device ID data or GPS location information entered wirelessly from an electronic device or medium held by the user, or liveness information indicating that the user is alive.

19. A securities trading service provision system with identity authentication processing according to 16, characterized by comprising: a user registration data storage processing module that stores data based on facial image data or fingerprint image data obtained from the user at the time of user registration as registration data in the user registration data storage unit; a recent data storage processing module that stores data based on recent facial image data or recent fingerprint image data of the person who issued the trading order, which was recently captured by the execution instruction capture shooting linked control processing module at the time of the most recent securities trading order, in the identity authentication processing for the securities trading currently being executed, the captured facial image data or captured fingerprint image data of the person who issued the order, which was captured by the execution instruction identity authentication processing module; the user registration data; and the recent facial image data or recent fingerprint image data.

20. A securities trading service provision system that includes an identity authentication process according to any one of 1, 16, 18, or 19, characterized in that the processing using the facial image data or the fingerprint image data is processing using data based on feature quantities extracted from the facial image data or the fingerprint image data.

21. A securities trading service provision system with identity verification processing according to any one of 1 to 10, characterized in that a user account is provided for each user to manage access to the securities trading data, an account management unit is provided to manage the user account for each user, the account management unit has a status management function that manages whether access to the securities trading data managed by the user account for each user is permitted or not, the default setting for the account management unit is to uniformly set the status of the user account for each user to the not permitted status, if the user's initial identity verification using the open authentication code is successful, the account management unit individually changes the status of the user account to the permitted status, and if the user's identity verification at the time of the execution instruction using the closed authentication code is successful, the securities trading execution processing module executes the contents of the execution instruction, and then the account management unit individually changes the status of the user to the not permitted status.

22. A securities trading method that provides securities trading services accompanied by identity verification processing using a securities trading data input / output object or securities trading application for which an open authentication code for identity verification and a transaction execution closed authentication code for identity verification are set for each user, characterized in that: at the start of a securities transaction, identity verification processing is performed using the user's open authentication code for identity verification; securities trading data is input to the user transaction data input / output object or the application; the acceptance of a transaction execution instruction for the securities transaction is linked to the capture of the user's face image or fingerprint image; in conjunction with the transaction execution instruction, identity verification processing is performed using the data obtained as a result of the securities trading execution instruction capture image linkage control processing and the transaction execution closed authentication code; and the success of the identity verification processing at the time of the securities trading instruction is used as the processing execution condition to transmit the securities trading data to a securities trading network system.

23. The method for providing securities trading services according to claim 22, wherein the transaction execution close authentication code is generated as a code that reflects the securities trading data content entered by the user through the identity authentication process at the time of issuing a securities trading instruction, thereby fixing the securities trading content, and in the identity authentication process at the time of issuing a securities trading instruction, when receiving a transaction execution instruction for the securities trading, the entered securities trading data content is presented to the user, the user is asked to confirm the securities trading data content, and the input of the transaction execution close authentication code from the user is linked to the user's execution of the securities trading.