Financial transaction system with identity authentication and financial transaction method with identity authentication

The financial transaction system addresses the vulnerability of conventional systems by integrating biometric and FIDO authentication to ensure continuous user verification during transaction execution, enhancing security and convenience.

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

Patent Information

Application Number
PCT/JP2026/017444
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

Conventional financial transaction systems lack continuous identity verification during transaction execution, leaving them vulnerable to fraudulent activities despite initial login authentication, and existing solutions like two-factor authentication are inconvenient and not fully effective.

Method used

A financial transaction system that performs user authentication at the start and execution of transactions using biometric data, such as facial images or fingerprints, and integrates FIDO authentication to ensure secure and seamless transaction execution.

Benefits of technology

Enhances security by mandatorily capturing biometric data during transaction execution, providing continuous identity verification and reducing user inconvenience while ensuring high-security financial transactions.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure JP2026017444_12112026_PF_FP_ABST
    Figure JP2026017444_12112026_PF_FP_ABST
Patent Text Reader

Abstract

[Problem] To ensure both high security and immediacy in a financial transaction system.  [Solution] Provided is a financial transaction system for providing a financial transaction service with identity authentication processing by using a financial transaction data input / output object or a financial transaction application in which an open authentication code for identity authentication and a transaction execution closing authentication code for identity authentication are set for each user. Identity authentication processing is executed by: a transaction start time identity authentication processing module 210 for executing identity authentication processing at the transaction start; and a data input / output processing module 310. When a financial transaction execution instruction is received, capturing a facial image of a user with a camera is interlocked by a transaction execution instruction time identity authentication processing module 220 and a transaction instruction image capture interlocking processing module 330. Identity authentication is executed by the transaction execution instruction time identity authentication processing module 220. Financial transaction instruction data is transmitted by receiving the authentication result of the identity authentication processing at the time of financial transaction execution instruction.
Need to check novelty before this filing date? Find Prior Art

Description

Financial transaction systems and financial transaction methods that involve identity verification.

[0001] The present invention relates to a financial transaction system with user authentication that operates on a computer system, and a method for providing financial transactions with user authentication.

[0002] There are many different types of financial instruments that are the subject of financial transactions in the financial instruments trading market. For example, a wide variety of commodities and futures products are traded, such as currencies, foreign currencies, securities, bonds, stocks, derivatives, foreign exchange, and commodities such as gold. In recent years, financial transactions have been executed using digital data on computers and networks, and transactions are completed in a world where receiving and sending money intersect. 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 financial 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 financial trading system by requiring the input of multiple factors or by requiring additional input with a constantly changing "one-time password."

[0003] Two-factor authentication and two-step authentication are expected to provide a certain level of improved security against cyberattacks, but these are basically configured when a user logs in to a financial transaction system. Once the user successfully completes identity authentication at login and becomes eligible to access the services, no further identity authentication is generally required thereafter. In other words, once the identity authentication is successfully completed only once at the start of service usage to enable service access, it is merely presumed that the legitimate individual has been continuously using the service throughout the entire service usage period until the end of the subsequent service usage. For example, there were no special security settings for identity authentication when performing transaction executions such as "sending money" or "receiving money" in currency. That is, once logged in successfully, most financial transaction systems allowed users to simply execute trades by pressing operation buttons when performing financial transactions such as "sending money" and "receiving money".

[0004] FIG. 23 is a diagram that briefly illustrates the identity authentication procedure in a general financial trading system, that is, the operations of launching an application, opening a user account file, and then pressing financial transaction operation buttons such as "send money" and "receive money" using the trading service of the financial transaction system. Although it is one example, it serves as a typical example of operations for "sending money" and "receiving money" in the prior-art financial trading system.

[0005] As shown in FIG. 23(a), the financial trading application 10 is installed on a computer system or a smartphone. When a user intends to use the financial trading application 10, the financial trading application 10 is launched by selecting the icon of the financial 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 to activate it.

[0006] Furthermore, each user file 20 is installed on the computer system in the financial 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 launches 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 financial 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 financial 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 financial transaction details are set using the financial trading application 10. To prevent incorrect input, the user may be required to press a confirmation button or enter code information individually. Once the financial transaction input settings are complete, the user selects and presses the "Send" or "Receive" operation buttons displayed on the financial trading application 10 screen on the monitor by clicking or tapping, and the financial 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 financial trading applications 10 do not require the user to enter a special password or user identification ID information when closing the user authentication file 20, and conventional financial trading applications 10 can simply terminate and close the user authentication file 20.

[0008] In other words, while the authentication procedures in general financial trading systems require the input of authentication information based on various security levels, such as two-factor authentication and two-step authentication, to confirm whether the person attempting to use the system has the legitimate right to use it, the reality is that once authentication is successful during login, it is assumed that the authorized user continues to use the service correctly for the entire duration of use, and no special security settings are actually implemented when placing trade orders or when terminating the financial 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 through identity theft by illegally obtaining IDs and passwords through phishing and hacking when using financial services such as finance, it is important to perform not only user authentication when logging into financial trading systems, but also when executing financial transactions, 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 financial 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 financial transactions using financial transaction systems, such as those in the financial sector, by requiring user authentication even at the time of execution, while also being extremely easy to operate and allowing for the confirmation of financial transaction execution processing in a short amount of time.

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

[0017] The financial transaction system of the present invention covers all types of financial transactions, including a wide variety of items such as cash, foreign currency, securities, bonds, stocks, derivatives, foreign exchange, and commodities such as gold. While the term "code" is used for both open authentication codes and closed authentication codes for transaction execution, it broadly refers to data that can be matched with input data entered for authentication, 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. The "open authentication code for authentication" is an authentication code used for authentication when the financial transaction system is first used, 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. The "transaction execution close authentication code for identity verification" can be any authentication code used for identity verification when executing financial or bond transactions using the financial trading system, and can be facial image conversion data or a challenge code for FIDO authentication. If identity verification is successful when executing a transaction using this transaction execution close authentication code, the entered financial transaction data is sent to the financial 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 financial trading client application is optional. The image capture linked to the instruction to execute a financial transaction can be any image capture that is linked to the act of pressing the instruction button labeled "Execute Transaction" that appears on the monitor after entering the details of the financial transaction, or to the act of inputting an instruction by voice, and controls camera shooting in conjunction with this action of the user instructing to execute a financial transaction.This system, which automatically and forcibly captures a facial image when a transaction is executed, and uses the captured facial image data for matching and FIDO authentication, is a novel technology that makes successful authentication a condition for executing a financial transaction. This allows for the provision of financial transaction services that perform identity verification at the critical and important moment of transaction execution.

[0018] With the above configuration, not only is the user authentication process at the start of a financial transaction performed automatically, but the process of capturing the user's facial image is also automatically controlled in conjunction with the financial transaction execution instruction. This results in extremely high security because user authentication is also performed when the financial transaction execution instruction is given. Furthermore, since the process of capturing the user's facial image is automatically controlled in conjunction with the financial transaction execution instruction, the user does not perform the act of taking the image at will; it is a mandatory, automatic capture that requires no operation from the user. In addition, the "execution condition" for the financial 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 financial transaction execution instruction capture image linkage control processing module can perform multiple roles and functions. First, depending on the system configuration, if an execution instruction is given, the financial transaction execution instruction capture image linkage 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 financial transaction execution instruction user authentication processing module as a code that reflects the financial transaction data content entered by the user, thereby fixing the financial transaction content. The financial transaction execution instruction user authentication processing module is equipped with a financial transaction data content authentication function that, upon receiving a transaction execution instruction for the financial transaction, presents the entered financial transaction data content to the user and allows the user to confirm the financial transaction data content. It is preferable to link the input of the transaction execution close authentication code by the user with the user's execution of the financial transaction. With the above configuration, performing authentication processing using the transaction execution close authentication code authenticates the code that reflects the financial 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 financial transaction data associated with the user account of the user's financial transactions, or a group of financial transaction data stored in the 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 system configurations for the financial transaction system of the present invention described above. The first system configuration pattern is one in which a financial transaction server, a user terminal which is a financial transaction client, and the financial transaction network system are connected by a computer network. Multiple financial transaction servers may cooperate to form a financial transaction network system. In other words, a processing module that performs identity authentication processing is included in the financial transaction server. In addition, multiple financial transaction servers may cooperate to form a financial transaction network system. In this first system configuration pattern, the capture shooting linked control processing module when a financial transaction execution instruction is given is implemented in the user terminal, and the identity authentication processing module when a financial transaction starts, the identity authentication processing module when a financial transaction execution instruction is given, and the financial transaction execution processing module are implemented in the financial transaction server.

[0023] Next, the second system configuration pattern is one in which a financial transaction server, user terminals (which are financial transaction clients), the financial transaction 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 financial transaction server. It is also possible for multiple financial transaction servers to cooperate and form a financial transaction network system. In this second system configuration pattern, it is sufficient that the capture shooting linked control processing module at the time of financial transaction execution instruction is implemented in the user terminal, the user authentication processing module at the start of financial transaction and the user authentication processing module at the time of financial transaction execution instruction are implemented in the authentication server, and the financial transaction execution processing module is implemented in the financial transaction server. While various configurations of financial transaction systems are possible, the above two system configuration patterns serve as a basis for accommodating diverse system configurations. User terminals include smartphones and personal computers carried by users, as well as ATMs and cash dispensers in bank branches, credit cards, and credit card terminals. Cameras are typically implemented in smartphones, and computers also have built-in or external cameras. Furthermore, ATMs, cash dispensers, and credit card terminals are also assumed to be equipped with cameras.

[0024] Next, as the user authentication process in the financial transaction 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 financial transaction 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 user authentication process at the time of the financial transaction execution instruction using the transaction execution close authentication code in the user authentication processing module at the time of the financial transaction execution instruction is a FIDO user authentication process compliant with the FIDO standard, and the capture shooting linked control processing module at the time of the financial transaction 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 user authentication process compliant with the FIDO standard can be adopted as user authentication at the start of a financial transaction. 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 financial transaction execution instruction. In this pattern, the user authentication processing module at the time of financial transaction execution instruction and the capture shooting linked control processing module at the time of financial 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 financial 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 financial 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 financial transaction 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 financial transaction data content input by the user by the user authentication processing module at the time of financial transaction execution instruction, and the financial transaction content is fixed on the server side. In particular, it is preferable that the financial transaction server is equipped with a hash processing module, and the code that reflects the financial transaction data content in the challenge code is obtained by the financial transaction server using data using the financial transaction data content input by the user via the user terminal, and that the financial transaction data content authentication function is provided that presents the financial transaction data content to the user via the user terminal at the time of receiving the transaction execution instruction for the financial transaction, and allows the user to confirm the financial transaction data content. In the above configuration, the execution conditions for the personal authentication processing module at the time of financial transaction execution instruction may be the successful completion of both the personal authentication using the transaction execution close authentication code and the successful completion of the financial transaction data content authentication.

[0027] Here, the financial transaction data content in question includes, for example, a wide variety of financial instruments that are the subject of financial transactions. For example, it may include transaction details related to cash, foreign currency, securities, bonds, stocks, derivatives, foreign exchange, and commodities such as gold. If the system is equipped with a financial transaction data content authentication function that presents the financial transaction data content to the user via the user terminal at the time of receiving the transaction execution instruction for the financial transaction, and allows the user to confirm the financial transaction data content, then the execution conditions for the user authentication processing module at the time of financial transaction execution instruction can be set as the successful completion of both user authentication using the transaction execution close authentication code and the successful completion of the financial transaction data content authentication. In this way, by using a hash created from a code that reflects the content of financial transaction data, the challenge code used for user authentication via the FIDO server when issuing a financial transaction execution instruction (when the financial transaction details are finalized) reflects the content of the financial transaction data. The transaction details themselves are included in the FIDO signature, and the FIDO signature allows the user to confirm the financial transaction details when issuing a financial transaction execution instruction. In other words, it is possible to perform "intention authentication" that the user has "intentionally" approved the transaction details, in addition to user authentication.

[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 financial transaction system of the present invention described above, it is also preferable that the personal authentication processing module at the time of financial transaction initiation instruction or the personal authentication processing module at the time of financial transaction 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 receipt of the transaction execution instruction of the financial transaction by the capture shooting linked control processing module at the time of financial transaction 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 financial transaction initiation instruction and the personal authentication processing at the time of financial transaction execution instruction by adding one other element in addition to the captured image, 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 financial transaction 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 financial transaction is also included, and by performing three image matching, it is possible to take into account the changes in the execution instructioner over time, which is the user, and the accuracy of confirming identity is increased.

[0032] Next, in the financial transaction 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 financial transaction 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 financial transaction 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 financial transaction system of the present invention described above, a user account is provided for each user to manage access to the financial transaction 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 financial transaction 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 financial transaction using the open authentication code is successful, the account management unit changes the status of the user account individually to the allowed state, and if the user's authentication at the time of issuing a financial transaction execution instruction using the closed authentication code is successful, the account management unit changes the status of the user individually to the denied state after the financial transaction execution processing module has executed the contents of the financial transaction execution instruction. With the above configuration, the state transition control causes all user accounts to be in the default "disallowed" status, and upon successful authentication at the start of a financial transaction, the user accounts are individually changed to the "enabled" status. After the financial transaction is executed, subject to successful authentication at the time of the financial transaction execution instruction, the user accounts uniformly return to the original default "disallowed" 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 financial transaction services may include general financial trading services, bond trading services, foreign exchange margin trading services, and the like.

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

[0036] This figure shows two patterns of system configuration examples. This figure shows a system configuration example of the financial transaction service provision system 1 according to Example 1. This figure shows an overview of the user authentication process and financial transaction data exchange between the financial transaction server and the user terminal in the configuration example of Figure 2. This is a diagram (part 1) that simply shows the basic data flow in the basic configuration of the financial transaction service provision system 1. This is a diagram (part 2) that simply shows the basic data flow in the basic configuration of the financial transaction service provision system 1. This is a diagram (part 3) that simply shows the basic data flow in the basic configuration of the financial transaction service provision system 1. This figure shows a configuration example in which the user authentication process according to Example 2 is executed by the authentication server 5. This figure shows an overview of the user authentication process and financial transaction data exchange 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 user authentication process according to Example 3 is executed by the FIDO server 400 of the financial transaction server 2. This figure shows an overview of the user authentication process and financial transaction data exchange in the configuration example of Figure 9. This is a diagram (part 1) that simply shows the basic data flow in the basic configuration of the financial transaction 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 financial transaction 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 financial transaction service provision system 1 of Example 3. This is a diagram showing an example configuration in which the user 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 user authentication process and the exchange of content authentication data for financial transaction details 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 financial transaction 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 financial transaction 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 financial transaction service provision system 1 of Example 4. This is a diagram with an added configuration for user authentication using the history information of the user's facial image according to Example 5. This is a diagram showing an overview of user 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 user accounts for financial transactions using the account management unit 160 according to Example 6. This figure shows an overview of the status control of access to user accounts for financial transactions 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 financial transaction server, and another where it is built within the financial transaction server. Figure 1(a) is an example of the first pattern of system configuration, which simply illustrates a pattern in which the authentication processing module that performs user authentication is implemented as part of the financial transaction server. Figure 1(b) is an example of the second pattern of system configuration, which simply illustrates a pattern in which the authentication server that performs user authentication is configured independently of the financial transaction server. Below, as Example 1, we will describe an example of the pattern shown in Figure 1(a) in which the authentication processing module is implemented within the financial transaction server. As Example 2, we will describe an example of the configuration shown in Figure 1(b) in which the authentication server is provided independently of the financial transaction 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 financial transaction service provision system of the present invention, we will use "financial transaction system" as an example. However, by substituting the products and services handled by the financial transaction server, it is possible to apply this invention to other debt transaction service provision systems, etc. In this specification, "facial image data" may be read as "feature quantities extracted from facial image data." User terminals include smartphones and personal computers carried by users, as well as ATMs and cash dispensers in bank branches, credit cards, and other media and credit card terminals. Cameras are usually implemented in smartphones, and computers also have cameras implemented, either internally or externally. In addition, ATMs, cash dispensers, and credit card terminals are also assumed to have cameras implemented.

[0038] Figure 2 is a diagram showing an example of the system configuration of the financial transaction 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 financial transaction data between the financial transaction server and the user terminal in the system configuration example of the financial transaction 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 financial transaction service provision system 1.

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

[0040] The data editing processing module 110 inputs financial transaction data entered by the user via the data input / output module 310 of the user terminal 3 into the financial transaction data area 140 in the financial transaction user database 130 of the user application 100. Since a financial transaction data area 140 exists for each user account, input and editing are performed in the financial transaction data area 140 of the user who has completed the identity authentication process and is able to use the financial transaction service. As described later, the financial transaction execution processing module 120 transmits the financial transaction information in the financial transaction data area 140 linked to the user account in the financial transaction user database 130 to the financial transaction network system 4 after the identity authentication is completed when a financial transaction execution instruction is given. The financial transaction user database 130 is a database that stores and manages financial transaction data areas 140 for each of multiple user accounts. The financial transaction data area 140 is a data area 140 that holds financial 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 financial transaction user database 130.

[0041] The user authentication application 200 is configured to include a user authentication processing module 210 for when a financial transaction is initiated, a user authentication processing module 220 for when a financial 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 Financial Transaction Initiation Instruction User Authentication Processing Module 210 is a module that performs user authentication when a financial transaction is initiated. As described above, when the user authentication process at the time of the financial transaction initiation instruction is performed using facial image data, the Financial Transaction Initiation Instruction User Authentication Processing Module 210 performs facial image matching using the facial image captured by the Financial Transaction Initiation Instruction 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 financial transaction initiation instruction. When the user authentication process at the time of the financial transaction initiation instruction is performed using a password, 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 financial transaction initiation instruction perform password matching. Note that when the user authentication process at the time of the financial transaction initiation instruction is performed using a password, the Financial Transaction Initiation Instruction Captured Facial Image Matching Processing Module 211 and the Financial Transaction Initiation Instruction Capture Image Linkage Control Processing Module 320 do not need to be started.

[0043] The Financial Transaction Initiation Time Capture Face Image Matching Processing Module 211 is a module used when the user authentication process performed at the time of the Financial Transaction Initiation Instruction uses features obtained from face image data for matching. In this operation, the Financial Transaction Initiation Time 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 Financial Transaction Initiation Instruction. The user registration data used for the user matching process is registered as the Registration Open Authentication Code 231 for user authentication at the time of the Financial Transaction Initiation Instruction 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 a financial transaction execution instruction is a module that executes identity verification processing performed at the time of a financial transaction execution instruction. This module executes collation processing using collation data generated by using at least part of the feature amount obtained from the user's face image data captured in conjunction with the financial transaction execution instruction by the capture photographing interlocking control processing module 330 at the time of the financial transaction execution instruction of the user terminal 3. Note that, similarly to the above, the user registration data used for the user's collation processing is user registration data generated by using at least part of the feature amount obtained from the user's face image captured at the time of registration, which is registered as the registration open authentication code 232 for identity verification at the time of a financial transaction execution instruction in the registration authentication code data storage module 230, and the collation processing between the user registration data and the collation data is executed. Note that, in this embodiment, the identity verification processing at the time of a financial transaction execution instruction performs identity verification 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 registration open authentication code 231 for identity verification at the time of a financial transaction start instruction, and a registration transaction execution closed authentication code 232 for identity verification at the time of a financial transaction execution instruction. The registration open authentication code 231 for identity verification used at the time of a financial transaction start instruction may be a password if the operation uses a password or the like for identity verification, and may be face image data or a feature amount extracted from face image data if the operation uses a face image for identity verification. Regarding the registration transaction execution closed authentication code 232 for identity verification at the time of a financial transaction execution instruction, in the present invention, the identity verification at the time of an order execution instruction for a financial transaction is premised on the capture photographing of the user's face image, and since the operation uses a face image for identity verification, it is face image data or a feature amount extracted from the face image data.

[0046] The user terminal 3 has a financial transaction client application 300 installed, and is configured to include a data input / output module 310, a capture photographing interlock control processing module 320 for when a financial transaction start instruction is issued, and a capture photographing interlock control processing module 330 for when a financial transaction execution instruction is issued. In addition to smartphones and personal computers carried by users as user terminals, the user terminals also include media such as ATMs, cash dispensers, and credit cards located in bank branches, and credit card use terminals. Cameras are usually mounted on smartphones, and computers also have built-in or external cameras mounted thereon. It is also assumed that ATMs, cash dispensers, and credit card use terminals are also equipped with cameras.

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

[0048] The capture photographing interlock control processing module 320 for when a financial transaction start instruction is issued photographs the user's face image by a photographing means such as a camera in conjunction with the user's instruction to start a financial transaction, in the case of an operation using a face image for personal authentication when the financial transaction start instruction is issued. 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 is transmitted to the personal authentication processing module 210 for when a financial transaction start instruction is issued in the financial transaction server 2.

[0049] The financial transaction execution instruction capture image synchronization control processing module 330 can perform multiple roles and functions. First, depending on the system configuration, if an execution instruction is given, the financial 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. In this embodiment 1 configuration example, this function is performed, and upon receiving a financial transaction execution instruction, the financial transaction execution instruction capture image synchronization control processing module 330 activates and operates the camera to capture a facial image or terminal state, obtains feature data from the captured image to use for user authentication. If it is a smartphone, the built-in camera can be used, and if it is a personal computer, the installed camera can be used. The facial image data captured in conjunction with the financial transaction order execution instruction is transmitted to the financial transaction execution instruction user authentication processing module 220 on the financial transaction server 2.

[0050] Financial Transaction Network System 4 refers to a network system that handles the target financial transactions and involves multiple financial transaction service providers. In this example, since the target is financial transactions, in Japan, this could include front-end systems of core systems such as the Tokyo Financial Exchange, Osaka Financial Exchange, and Nagoya Financial 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 above, showing the user authentication process and the exchange of financial transaction data between the financial transaction server 2 and the user terminal 3. As shown in Figure 3, users of financial transactions perform three main processes using the user terminal 3. The first process (financial transaction initiation process) is user authentication performed at the start of a financial transaction. When the user presses the "start transaction" button, the financial transaction server 2 requests user authentication via the user terminal 3, and the user performs the authentication at the time of the financial transaction initiation instruction according to the instructions. If authentication is by password, the user enters the prescribed password via the input screen. If authentication is by facial image, a facial image is taken in conjunction with the pressing of the "start transaction" button, and the facial image data is sent to the financial transaction server 2. The financial transaction server 2 has the registered open authentication code (password or facial image data) at the time of the financial transaction initiation instruction registered, and server authentication is performed. If the user authentication at the time of the transaction initiation is successful, the financial transaction can be started. This corresponds to the completion of user login. The second process (input / editing process) is when the user inputs or edits financial transaction information via the user terminal 3. Furthermore, it is preferable for the financial transaction server 2 to present the contents of the financial transaction data to the user terminal 3. The third process (financial transaction execution process) is user authentication performed when executing a financial transaction. When a user who has confirmed the contents of the financial transaction presses the command button to execute the transaction, a facial image is taken in conjunction with the press of the command button, and the facial image data is sent to the financial transaction server 2. Server authentication is performed, and if user authentication at the time of transaction execution is successful, the financial transaction order data is sent. This corresponds to sending the data to the financial transaction 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 financial transaction service provision system 1 according to Example 1. This corresponds to the financial transaction 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 financial transaction initiation instruction, the camera is operated by the financial transaction 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 captured (step S2). The order of steps S1 and S2 does not matter. The input facial image data is input to the financial transaction initiation instruction captured facial image matching processing module 211 (step S3), and the user ID information is input to the financial transaction initiation instruction identity authentication processing module 210 (step S4). The registered open authentication code 231 (user registration data) for user authentication at the time of initiating a financial transaction, 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 financial transaction 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 financial transaction service provision system 1 according to Embodiment 1. This corresponds to the financial transaction data input and editing process in Figure 3. The user inputs financial transaction data, such as sending or receiving money, via the data input / output module 310 of the user terminal 3 (step S7). The financial transaction data is passed via the network to the financial transaction server 2 of the financial transaction company being used, and the financial transaction data is input and edited in the user file 140 assigned to the user in the financial transaction user database 130 via the data editing processing module 110 (step S8) (step S9). The user may proceed to the financial transaction 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 personal authentication processing module 220 at the time of financial transaction execution instruction presents the input financial transaction content to the user terminal 3 (step S10). Here, the personal authentication processing module 220 at the time of financial transaction execution instruction generates information that reflects the financial transaction data content, and the financial transaction 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 financial transaction service provision system 1 according to Embodiment 1. This corresponds to the financial transaction execution process in Figure 3. When the user confirms the presented financial transaction details and presses an icon to instruct the execution of the financial transaction, such as "Execute Transaction" (step S11), the financial transaction 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 financial transaction 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 financial transaction server 2, where user authentication processing is performed at the time of the financial transaction order execution instruction. The data is passed to the user authentication processing module 220 when a financial transaction execution instruction is given (step S13). The user authentication processing module 221 when a financial transaction execution instruction is given captures a facial image and matches the matching data using the feature quantities of the input facial image data with the registered transaction execution close authentication code 232 for user authentication when a financial transaction execution instruction is given in the registered authentication code data storage module 230 (in this case, registration data using the feature quantities of the registered user's facial image data) (step S14). If the matching is successful as a result of the matching process (step S14: YES), the user authentication application 200 notifies the financial transaction server application 100 that user authentication has been successful (step S15). The user authentication processing module 120 then extracts the financial transaction data set in the user file 140 of the user in the financial transaction user database 130 and transmits the financial transaction data to the financial transaction network system 4 via the network (step S16). The above is an outline of the flow of financial transaction data processing in the financial 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 financial transaction 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 financial transaction service provision system 1 consists of a financial transaction server 2, an authentication server 5, a financial transaction user terminal 3, and a financial transaction 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 financial transaction 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 financial transaction 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 financial transaction 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 financial transaction data between the user terminal 3 and the financial transaction server 2. As shown in Figure 8, a user using financial transactions performs three main processes using the user terminal 3. The first process (financial transaction initiation process) is the user authentication process performed when initiating a financial transaction. This process can be the same as the first process (financial transaction initiation process) shown in Example 1, but differs in that the user authentication process at the start of a financial transaction 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 financial transaction information to the financial transaction server 2 via the user terminal 3, and can be the same as the second process (financial transaction initiation process) shown in Example 1. The third process (financial transaction execution process) is the user authentication process performed when issuing a financial transaction execution instruction. This process can be the same as the third process (financial transaction execution process) shown in Example 1, but in Example 2, the difference is that the authentication process for the user when issuing a financial transaction instruction is performed by accessing the authentication server 5 via the network. The basic data flow in the financial 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 financial transaction server 2 performs "FIDO authentication" as the user authentication process, specifically from the pattern in Figure 1(a). In other words, the FIDO server 400 is implemented on-premises to handle the authentication process within the financial transaction server 2. We will also describe an example in which a challenge code reflecting the content of the financial transaction data is used as the challenge code during user authentication, which is a hash of a code that reflects the content of the financial transaction data, and "intentional authentication" is also performed to show 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-premises in the financial transaction server 2 for user authentication processing. Figure 10 is a diagram showing an overview of the user authentication process and the exchange of financial transaction data between the authentication server 5 and FIDO server 400, the financial transaction server 2, and the user terminal 3 in the configuration example in Figure 9. Figures 11 to 13 are diagrams (part 1, part 2, and part 3) that briefly show the basic data flow in the basic configuration of the financial transaction service provision system 1 of this Example 3.

[0058] As shown in Figure 9, the basic configuration of the financial transaction service provision system 1 of the "FIDO authentication pattern" in Example 3 is a configuration comprising a financial transaction server 2, a FIDO server 400, a financial transaction user terminal 3, and a financial transaction network system 4. The financial transaction server 2 is equipped with a financial transaction server application 100, which, like the configurations of Examples 1 and 2, includes a data editing processing module 110, a financial transaction execution processing module 120, and a financial transaction database 130. Furthermore, compared to the configurations of Examples 1 and 2, it is configured to include a hash processing module 150. The basic functions of the data editing processing module 110, the financial transaction execution processing module 120, the financial transaction 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. Financial 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 financial transaction user database. In this embodiment 3, in parallel with this, the financial 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 financial transaction execution instruction is given) based on that hash data. In other words, the FIDO server 400 of the financial transaction server 2 in this embodiment 3 converts the financial transaction data input by the user into hash data using the hash processing module 150 and adopts the one that reflects the content of that financial transaction data as the challenge code for FIDO authentication processing. This challenge code becomes the "transaction execution close authentication code when a financial transaction execution instruction is given." In this embodiment 3, the financial transaction server 2 can also perform user authentication using the FIDO server 400 when a financial transaction is initiated (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 a financial transaction execution instruction is given (when the financial transaction details are finalized), 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 that reflects the financial transaction data content described above is adopted.By using a challenge code that reflects the financial transaction data content as the challenge code for user authentication using the FIDO server 400 when issuing a financial transaction execution instruction (when the financial transaction details are finalized), the transaction details are included in the FIDO signature target. Through FIDO signing, the user can confirm the financial transaction details when issuing a financial 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 financial transaction data content can include, as described above, the security, buy / sell category, quantity, price, order type, account ID, timestamp, session ID, etc.

[0060] Next, the financial transaction server 2 is equipped with an identity authentication application 200 and has a configuration comprising an identity authentication processing module 210 for when a financial transaction is initiated, an identity authentication processing module 220 for when a financial transaction is executed, and a FIDO server 400. The financial transaction server 2 has a FIDO server 400 and a FIDO authentication processing module 410 that manages the open authentication code 231 for when a financial transaction is initiated and the transaction execution close authentication code 232 for when a financial transaction is executed. The FIDO authentication challenge code used when a financial transaction is initiated corresponds to the registered open authentication code 231 for identity authentication when a financial transaction is initiated, 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 financial transaction is executed corresponds to the transaction execution close authentication code 232 for identity authentication when a financial transaction is executed, 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 financial transaction may be a random number arbitrarily generated by the FIDO authentication processing module 410 at the start of the financial transaction. However, the transaction execution close authentication code 232 at the time of issuing a financial transaction execution instruction is an example in which the FIDO authentication processing module 410 uses hash data that reflects the contents of the financial transaction data generated by the hash processing module 150 as a challenge code.

[0061] The financial transaction initiation instruction user authentication processing module 210 controls the user authentication process performed when a financial transaction initiation 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 financial transaction execution instruction time authentication processing module 220 performs authentication processing when an order execution instruction for a financial transaction is given. In this case, FIDO authentication processing using the FIDO server 400 is performed. Since it is FIDO authentication processing, authentication is performed in cooperation with the FIDO authenticator 350 inside the user terminal 3. In this embodiment 3, the financial transaction execution instruction time authentication processing module 220 has the role of performing trigger control to start the FIDO authentication processing, and also acts as a control module that synchronizes the financial transaction execution instruction and the FIDO authentication processing.

[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 image capture linked control processing module 320 for when a financial transaction is initiated, a capture image capture linked control processing module 330 for when a financial transaction is executed, and a FIDO authenticator 350 inside the terminal. Generally, a FIDO authenticator performs so-called "terminal authentication" to confirm that the user terminal is owned by the legitimate owner, but here it is also assumed that the user terminal 3 is an ATM or a credit card reader. In this case, the cash card or credit card is an IC card, and a FIDO authenticator 350 compliant with the FIDO standard is installed in the IC chip, and by inserting the card into the ATM or credit card reader, the ATM or credit card reader temporarily becomes a terminal used by the user and becomes a device including the FIDO authenticator 350.

[0065] In Embodiment 3, the financial transaction initiation instruction capture image acquisition linked control processing module 320 and the financial 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 financial 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 transaction execution instruction for a financial transaction 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 financial transaction execution instruction. More specifically, the user authentication processing module 220 and the capture shooting linked control processing module 330 at the time of financial 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 financial transaction execution instruction. More specifically, the user authentication processing module 220 and the capture shooting linked control processing module 330 for financial transaction execution instructions 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 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 a financial 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 the exchange of financial transaction data between the financial transaction 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 financial transactions performs three main processes using the user terminal 3. The first process (financial transaction initiation process) is the FIDO authentication process performed when a financial transaction is initiated. When the user presses the transaction initiation button, as shown in Figure 10, a facial image is captured by the financial transaction initiation instruction capture shooting linked control process, and the FIDO authentication process at the time of financial transaction initiation is executed. The financial transaction 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 financial transaction 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 financial transaction information via the user terminal 3. This process may be the same as in Example 1 and Example 2. The third process (financial transaction execution process) is the FIDO authentication process performed when a financial transaction is executed. When the transaction execution instruction button is pressed, as shown in Figure 10, a facial image is captured by the financial transaction execution instruction capture shooting linked control process, and the FIDO authentication process for the financial transaction execution instruction is executed. The terminal's FIDO authenticator 350, the financial transaction execution instruction authentication processing module 220, and the FIDO server 400 work together to execute the FIDO authentication process for the financial transaction execution instruction. The challenge code used in the executed FIDO authentication process may be a random number, but here, a challenge code based on a hash code that reflects the financial transaction content, called the "transaction execution close authentication code for the financial transaction execution instruction," is used, and authentication of the user's intent is performed through verification of the financial transaction content along with user 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 financial 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 financial transaction (step S21), the financial transaction start instruction authentication processing module 210 in the financial transaction server 2 is notified, and the financial transaction start instruction authentication processing is started (step S22). In this embodiment 3, the FIDO server 400 of the financial transaction server 2 is started and the FIDO authentication process is started. The FIDO server 400 generates a random number and creates a "FIDO authentication challenge code." This random number is temporarily held as the "financial transaction start instruction open authentication code 231." The open authentication code (challenge code) 231 held at the start of a financial transaction 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 financial transaction initiation instruction capture-linked control processing module 320 is activated in conjunction with the financial transaction initiation instruction, and the platform authenticator performs FIDO authentication processing. Specifically, the financial transaction initiation instruction user authentication processing module 210 and the financial transaction initiation instruction capture-linked control processing module 320 perform trigger control, initiating WebAuthn / Passkey authentication via an application or browser on the user terminal. During this process, the OS activates Face ID on the FIDO authenticator 350 (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 financial transaction (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 financial transaction. It then compares the verified information with the original "FIDO authentication challenge code at the start of the financial transaction" (step S29). If the comparison is successful (step S29: Yes), the FIDO server 400 notifies the financial transaction start-of-person authentication processing module 210 that FIDO authentication has been successful (step S30). The financial transaction start-of-person authentication processing module 210, upon receiving the notification, notifies the financial transaction server 2 that the authentication process at the start of the financial transaction has been successful (step S32). The data editing processing module 110 then becomes ready to receive financial transaction data via the user terminal 3's data input / output module 310. This completes the first process, the authentication process performed at the start of a financial transaction.

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

[0073] The user authentication processing module 220 initiates two processes when a financial transaction execution instruction is given. The first process involves the hash processing module 150 receiving the financial 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 financial 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 financial 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 financial 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 financial transaction execution instruction is given". In short, the "transaction execution close authentication code 232 when a financial transaction execution instruction is given" is generated as information that reflects the financial transaction data details, and the financial transaction details are fixed on the FIDO server 400 side for verification.

[0074] The second process involves the financial transaction execution instruction user authentication processing module 220 taking in the financial transaction data entered and edited in the financial transaction data area 140 and displaying it on the monitor of the user terminal 3's data input / output module 310 (step S38). For example, the financial transaction details such as the security, 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 financial transaction details displayed on the user terminal, and this is set as the "transaction execution close authentication code at the time of financial transaction execution instruction." At the same time, the same financial transaction details are displayed on the monitor of the user terminal 3's data input / output module 310, and the financial transaction data content authentication function allows the user to confirm the financial transaction data details. The user's approval of the displayed content and confirmation of their intention to input it are matched with the "transaction execution close authentication code at the time of financial transaction execution instruction."

[0075] Next, we move on to the financial transaction execution process. Figure 13 is a simplified diagram (part 3) showing the basic data flow in the basic configuration of the financial transaction service provision system 1 according to Example 3. This corresponds to the financial transaction execution process in Figure 10. As shown in the financial transaction data input and editing process in Figure 12 above, when the user operates the user terminal 3 and inputs the financial transaction details into the financial transaction server 2, a FIDO authentication challenge code (transaction execution close authentication code when a financial transaction execution instruction is given) is generated, and the user can confirm these financial transaction details displayed on the monitor and verify that the financial 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 financial transaction (step S39), the user authentication processing module 220 on the financial transaction server 2 is notified, and the user authentication processing for the financial transaction execution instruction is started (step S40). The user authentication processing module 220 on the financial transaction execution instruction instructs the FIDO authentication processing module 410 on the FIDO server 400 to execute the FIDO user authentication processing for the financial transaction execution (step S41). The FIDO server 400 sends the "transaction execution close authentication code 232 for financial transaction execution instruction," 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 capture shooting linked control processing module 330 on the financial transaction execution instruction is activated in conjunction with the financial transaction execution instruction, and the platform authenticator executes the FIDO authentication processing. The specific process is as follows: trigger control is performed by the financial transaction execution instruction user authentication processing module 220 and the financial 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, Face ID of the FIDO authenticator 350 is activated by the OS during this process (step S45), and after successful user verification (step S45: Yes), a FIDO2 Assertion is generated using the secret key (step S46).

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

[0078] The above outlines the flow of financial transaction data processing in the financial transaction system 1 according to Embodiment 3 of the present invention. Furthermore, by using the financial transaction system 1 according to Embodiment 3 of the present invention, user authentication is performed, and the financial transaction details are fixed on the server side. These details are authenticated by FIDO2 Assertion using the private key on the user terminal 3, and the user can confirm that the financial transaction details are as they intended. In other words, since the challenge code reflecting the transaction details is the transaction execution close authentication code when a financial transaction execution instruction is given, user authentication of the financial transaction details 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 financial transaction service provision system 1 of the "FIDO authentication pattern" according to Example 4 is a configuration comprising a financial transaction server 2, a financial transaction user terminal 3, an authentication server 5 equipped with a FIDO server 400, and a financial transaction network system 4. The financial transaction server 2 has a financial transaction server application 100 implemented and is configured to include a data editing processing module 110, a financial transaction execution processing module 120, a financial transaction 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 financial transaction is initiated and an authentication processing module 220 for when a financial transaction is executed. These may be the same as in Embodiment 3. The authentication server 5 has a FIDO server 400 built on it, 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 financial transaction is initiated and the transaction execution close authentication code 232 when a financial transaction execution is instructed. In this embodiment, the case where the user terminal 3 is a personal computer will be explained as an example.

[0081] The financial transaction initiation open authentication code 231 is a FIDO authentication challenge code used when a financial transaction initiation instruction is given. It corresponds to the registered open authentication code 231 used for user authentication when a financial transaction initiation instruction is given, as described in Examples 1 and 2, and is assigned the same code number. This "financial transaction initiation open authentication code 231" is used in the FIDO user authentication process when a financial transaction is initiated (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 user authentication process when a financial transaction initiation instruction is given will be described later.

[0082] Next, the financial transaction execution close authentication code 232, which is used when issuing a financial transaction execution instruction, corresponds to the transaction execution close authentication code 232 used for identity verification when issuing a financial 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 financial transaction execution instruction" used by the FIDO authentication processing module 410 in Example 4 is used for FIDO identity verification when issuing a financial transaction execution instruction (when the financial transaction details are finalized), and 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 content of the financial transaction data 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 using its 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 content of the financial transaction data, authentication of the content itself, i.e., "financial transaction content authentication," can also be performed.

[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 financial transaction is initiated, a capture image synchronization control processing module 330 for when a financial 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 financial transaction is initiated, and the capture image synchronization control processing module 330 for when a financial 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 the exchange of financial transaction data between the financial transaction 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 financial transactions performs three main processes using the user terminal 3. The first process (financial transaction initiation process) is the FIDO authentication process performed when initiating a financial transaction. When the instruction button to start a financial transaction is pressed, as shown in Figure 15, a facial image is captured by the financial transaction initiation instruction capture shooting linked control process, and the FIDO authentication process at the time of financial transaction initiation is executed. The financial transaction 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 financial transaction initiation. The second process (input / editing process) is when the user inputs or edits financial transaction information via the user terminal 3. This process can be the same as in Examples 1, 2, and 3. The third process (financial transaction execution process) is the FIDO authentication process performed when a financial transaction is executed. When the transaction execution instruction button is pressed, as shown in Figure 15, a facial image is captured by the financial transaction execution instruction capture shooting linked control process, and the FIDO authentication process for the financial transaction execution instruction is executed. The terminal's FIDO authenticator 350, the financial transaction execution instruction authentication processing module 220, and the FIDO server 400 work together to execute the FIDO authentication process for the financial transaction execution instruction. The challenge code used in the executed FIDO authentication process is the "financial transaction execution closing authentication code 232," which is a challenge code based on a hash code that reflects the financial transaction details. This performs authentication of the user's intent through verification of the financial transaction details along with user authentication.

[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 financial transaction, which is the first process. 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 financial transaction (step S60), the financial transaction start instruction authentication processing module 210 in the financial transaction server 2 is notified, and the authentication processing for the financial transaction start instruction 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 "Financial Transaction Initiation Open Authentication Code 231," and this stored Financial Transaction Initiation Open Authentication Code (Challenge Code) 231 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 financial transaction initiation instruction capture synchronization control processing module 320 in conjunction with the financial 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 financial transaction execution instruction user authentication processing module 220 and the financial transaction execution instruction capture synchronization 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 operation of the financial transaction execution instruction, 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 a financial transaction" 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 a financial transaction (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 a financial transaction and compares the verified information with the original "FIDO authentication challenge code at the start of a financial transaction" (step S68). If the comparison is successful (step S68: Yes), the FIDO server 400 notifies the financial transaction start authentication processing module 210 that FIDO authentication has been successful (step S69), and the financial transaction start authentication processing module 210, upon receiving the notification, notifies the financial transaction server 2 that the authentication process at the start of a financial transaction has been successful (step S70), and the data editing processing module 110 becomes ready to receive financial transaction content data via the user terminal 3's data input / output module 310. With the above steps completed, the first process, the identity verification process performed at the start of a financial transaction, is finished.

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

[0090] The user authentication processing module 220 initiates two processes when a financial transaction execution instruction is given. The first process involves the hash processing module 150 receiving the financial transaction data entered into the financial 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 financial transaction execution instruction is given) based on this hash data (step S76). In other words, the challenge code based on a hash code that reflects the financial transaction details (data such as security, buy / sell category, quantity, price, order type, account ID, timestamp, and session ID) becomes the "transaction execution close authentication code 232 when a financial transaction execution instruction is given". In short, the "transaction execution close authentication code 232 when a financial transaction execution instruction is given" is generated as information that reflects the financial transaction data details, and the financial transaction details are fixed on the FIDO server 400 side for verification.

[0091] The second process involves taking in the financial 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 into and edited in the financial 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 financial 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 financial transaction details displayed on the user terminal, and this is set as the "transaction execution close authentication code when a financial transaction is executed." At the same time, the same financial 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 a financial transaction is executed."

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

[0093] When the user confirms the financial transaction details and presses the icon button to instruct the execution of the financial transaction (step S78), the authentication server 5's financial transaction execution instruction user authentication processing module 220 is notified, and the user authentication processing for the financial transaction execution instruction is started (step S79). The financial 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 financial transaction execution (step S80). The FIDO server 400 sends the "financial 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 on the user terminal 3 as a challenge code (step S81).

[0094] In parallel with these processes, the following process is also executed. The financial 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 financial transaction execution instruction user authentication processing module 220 and the financial 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 financial 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 financial transaction execution instruction (step S85). The FIDO authentication processing module 410 holds the public key 411 and verifies the signed FIDO authentication challenge code at the time of the financial transaction execution instruction. It then compares the verified information with the original "FIDO authentication challenge code at the start of the financial transaction" (step S86). If the comparison is successful (step S86: Yes), the FIDO server 400 notifies the financial transaction execution instruction user authentication processing module 220 that FIDO authentication has been successful (step S87). The financial transaction execution instruction user authentication processing module 220, upon receiving the notification, notifies the financial transaction server 2 that the user authentication process at the time of the financial transaction execution instruction has been successful (step S88). The financial transaction execution processing module 120, upon receiving the notification, sends the financial transaction data located in the data area of ​​the corresponding user account from the financial transaction database 130 to the financial transaction network system only if the hash code used for FIDO authentication matches the hash code regenerated from the financial transaction data to be executed (step S89).

[0095] The above outlines the flow of financial transaction data processing in the financial transaction system 1 according to Embodiment 4 of the present invention. Furthermore, by using the financial transaction system 1 according to Embodiment 3 of the present invention, user authentication is performed, and it is also confirmed that the user has confirmed that the financial transaction content is as they intended. Since the challenge code is the transaction execution close authentication code at the time of financial transaction execution instruction, user authentication of the financial transaction 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 user account for financial transactions 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 described.

[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 transaction execution commander, which was captured by the execution command capture shooting linked control processing module 330 during the most recent financial transaction, to the user registration data storage unit 361. In addition, the execution command identity authentication processing function saves the facial image of the execution commander, which was captured by the execution command identity authentication processing module 330 during the identity authentication process for the financial 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 access to financial transaction data managed by each user's user account, determining whether it is permitted or denied. Status management is performed for each user account. Here, we describe the configuration described in Example 5, with the addition of an account management unit to manage the status of user accounts for financial transactions, 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 the user account for financial transactions 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 the user account for financial transactions is permitted or denied, as executed in the configuration example of Figure 21.

[0104] As shown in Figure 21, the financial transaction 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., permission granted status) even when a user is not conducting financial transactions 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 financial transactions.

[0105] The account management module 160 shown in Figure 21 has a status management function that manages whether access to financial transaction 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 user authentication is successful when a user starts a financial transaction, the account management unit 160 individually changes the status of the user account to the permitted status. Furthermore, if user authentication is successful when a user issues a financial transaction execution instruction using a closed authentication code, the financial 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 financial transaction data linked to the user account is managed in the financial transaction user database, this can be applied even if the management format of the data area for each user's financial transaction data linked to the user account by the financial transaction 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 financial transaction 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 financial transaction 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 financial 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 financial 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 initiating a financial 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's account login process to initiate the financial transaction. Once the user account is identified, the account management module 160 immediately denies access to the financial transaction data associated with the user account. Note that since the data editing processing module 110 is operational, users can input financial transaction data, and it only needs to be temporarily held. If user authentication is successful when issuing a financial transaction execution instruction using the user's closed authentication code, the account management module 160 changes the status to a permitted status, granting access to the financial transaction data associated with the user account, and the financial transaction data is reflected. Subsequently, after the execution processing module 120 executes the contents of the execution instruction to the financial transaction network system 4, the account management unit 160 controls the user account to individually revert the permitted status back 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 financial transactions.

[0108] This invention is suitable as a financial transaction service provision system applicable to the financial transaction field, particularly the financial transaction field, where immediacy and high security are required.

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

Claims

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

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

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

4. (Financial Transaction Server) The financial transaction service provision system according to claim 2, wherein the financial transaction server, the user terminal which is a financial transaction client, and the financial transaction network system are connected by a computer network, the capture shooting linked control processing module when a financial transaction execution instruction is given is implemented in the user terminal, and the user authentication processing module when a financial transaction starts, the user authentication processing module when a financial transaction execution instruction is given, and the financial transaction execution processing module are implemented in the financial transaction server.

5. The financial transaction service provision system according to claim 2, wherein the financial transaction server, the user terminal which is a financial transaction client, the financial transaction network system, and the authentication server are connected by a computer network, the capture shooting linked control processing module when a financial transaction execution instruction is given is implemented in the user terminal, the user authentication processing module when a financial transaction starts and the user authentication processing module when a financial transaction execution instruction is given are implemented in the authentication server, and the financial transaction execution processing module is implemented in the financial transaction server.

6. The financial transaction service provision system according to claim 4, characterized in that the financial transaction server is configured to include a FIDO server compliant with the FIDO standard, the user terminal is configured to include a FIDO authenticator, the user authentication process at the time of the financial transaction execution instruction using the transaction execution close authentication code in the user authentication processing module at the time of the financial transaction execution instruction is a FIDO user authentication process compliant with the FIDO standard, and the securities transaction 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 transaction execution instruction and the FIDO authentication process.

7. The financial transaction 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 financial transaction execution instruction using the transaction execution close authentication code in the financial transaction execution instruction time user authentication processing module is a FIDO authentication process compliant with the FIDO standard, and the securities transaction 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 financial transaction 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 user authentication process at the time of the financial transaction initiation instruction using the open authentication code in the user authentication processing module is a FIDO user authentication process compliant with the FIDO standard, and the securities transaction 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 transaction initiation instruction of the financial transaction with the FIDO authentication process.

9. The financial transaction 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 user authentication process at the time of the financial transaction initiation instruction using the open authentication code in the user authentication processing module at the time of the financial transaction initiation instruction is a FIDO user authentication process compliant with the FIDO standard, and the securities transaction 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 transaction initiation instruction of the financial transaction with the FIDO authentication process.

10. A financial transaction 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 financial transaction execution instruction.

11. A financial transaction 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 in the personal computer, and the platform authenticator performs FIDO authentication processing in conjunction with the operation of the financial transaction execution instruction.

12. A financial transaction service provision system according to any one of claims 6 to 9, wherein the user terminal is an ATM or a credit card acceptance machine, the FIDO authenticator is a platform authenticator mounted on the IC chip of a card medium used in the ATM or the credit card acceptance machine, and the platform authenticator performs FIDO authentication processing in conjunction with the operation of the financial transaction execution instruction.

13. A financial transaction 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 is performed by the USB roaming authenticator in conjunction with the operation of the financial transaction execution instruction.

14. The financial transaction 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.

15. The financial transaction 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 financial transaction data content entered by the user by the financial transaction execution instruction user authentication processing module, thereby fixing the financial transaction content.

16. The financial transaction service provision system according to 15, characterized in that the financial transaction server is equipped with a hashing module, the code reflecting the financial transaction data content in the challenge code is obtained by the financial transaction server using data entered by the user via the user terminal and converted by the hashing module, the financial transaction data content authentication function presents the financial transaction data content to the user via the user terminal and allows the user to confirm the financial transaction data content when a transaction execution instruction for the financial transaction is received, and the execution conditions for the user authentication processing module at the time of financial transaction execution instruction are the establishment of user authentication by the transaction execution close authentication code and the establishment of financial transaction data content authentication.

17. The financial transaction service provision system according to claim 1, characterized in that the authentication process performed when a transaction is executed in the financial transaction execution instruction processing in the financial transaction authentication process in the financial transaction authentication process in the financial transaction authentication process in the financial transaction authentication process in the financial transaction authentication process in the financial transaction authentication process in the financial transaction authentication process in the financial transaction authentication process in the financial transaction authentication process in the financial transaction authentication process in the financial transaction authentication process in the financial transaction authentication process in the financial transaction authentication process in the financial transaction authentication process in the financial transaction authentication process in the financial transaction authentication process in the financial transaction authentication process in the financial transaction authentication process in the financial transaction authentication process in the financial transaction authentication process in the financial transaction authentication process in the financial transaction authentication process in the financial transaction authentication process in the financial transaction authentication process in the financial transaction authentication process in the financial transaction authentication process in the financial transaction authentication process in the financial transaction execution instruction instruction instruction module 18. The financial transaction 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 receipt of the transaction execution instruction of the financial transaction by the financial transaction 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.

19. The financial transaction service provision system according to 17, characterized in that the other one element of information is any of the following: the user's public individual number, the PIN set on the user's public individual 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.

20. A financial transaction service provision system with identity authentication processing according to 16, 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 the most recent facial image data or fingerprint image data of the transaction execution instructioner, which was most recently captured by the execution instruction capture shooting linked control processing module at the time of the most recent financial transaction, in the identity authentication processing for the financial transaction currently being executed, the image history matching processing module that performs a matching process between three parties: data based on the captured facial image data or fingerprint image data of the execution instructioner captured by the execution instruction identity authentication processing module, the user registration data, and the most recent facial image data or the most recent fingerprint image data.

21. A financial transaction service provision system that includes an identity authentication process according to any one of 1, 17, 19, or 20, 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.

22. A financial transaction service provision system with user authentication 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 financial transaction 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 financial transaction data managed by the user account for each user is permitted or not, the default setting for the user account for each user in the account management unit is uniformly set to the not permitted status, if the user's initial authentication 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 authentication at the time of the execution instruction using the closed authentication code is successful, the financial transaction 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.

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

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