JP7113883B2 - Identity verification system, method and computer program - Google Patents

Description

FIELD OF THE DISCLOSURE The present disclosure relates to an identity authentication system, method, and computer program product. In particular, the present disclosure relates to an identity authentication system, method, and computer program for authenticating the identity of a policyholder when signing an insurance contract for an insurance product sold by a bank.

In December 2007, the ban was fully lifted on the so-called ``bank bancassurance,'' which allows insurance products to be sold over the counters of banks. Since banks have account holders (hereinafter referred to as "account holders") who have a certain amount of assets, by proposing investment products that utilize insurance to account holders, they will revitalize asset management by account holders. can do.

When an account holder actually concludes an insurance contract, a prescribed procedure is carried out between the account holder (contractor) and the insurance company (insurer). At this time, the insurer often verifies the identity of the policyholder. In particular, in order to prevent money laundering, etc., the Act on Prevention of Transfer of Criminal Proceeds requires policyholders to present their identity verification documents (driver's license) to the insurer when concluding certain insurance contracts. It has established.

Under the conventional system, even when a bank sells insurance products, when the insurance contract is concluded, the insurer requires the policyholder to submit identity verification documents, and the policyholder sends the identity verification documents by mail, etc. I sent it to my insurer. Due to such a procedure, there have been cases where the contractor has canceled the contract without concluding the contract, for example, because of the troublesomeness of the procedure and neglecting to submit the identification document.

A computer device according to one embodiment is a computer device that allows an account holder who holds an account with the bank to conclude, as a policyholder, an insurance contract corresponding to an insurance product sold by the bank, wherein the computer The device includes a control device, a storage device, and a communication device, wherein the storage device associates and stores account information and authentication information regarding an account held by an account holder, and the communication device receives authentication information from a client computer. Upon receiving the telegram, the control device authenticates the account holder as the contractor by comparing the information contained in the authentication telegram with the account information and the authentication information stored in the storage device. , the communication device receives from the client computer a selection telegram indicating a selection of an insurance product, and the communication device transmits the selection telegram to a second computer device implemented by an insurer providing the insurance product. and, in response to the transmission of the application message, the communication device receives from the client computer a consent message indicating that the policyholder has agreed to the insurance contract. receive.

In another embodiment, a method is performed by a computer device that causes an account holder having an account with a bank to enter into an insurance contract corresponding to an insurance product sold by the bank as a policyholder. A method, wherein the computer device includes a storage device that associates and stores account information and authentication information related to an account held by an account holder, receiving an authentication message from a client computer; authenticating the account holder as the policyholder by comparing the information stored in the storage device with the account information and the authentication information stored in the storage device; receiving a message; sending an application message including an insurance number corresponding to the selected message to a second computer device implemented by an insurer providing the insurance product; and sending the application message. and correspondingly receiving, from the client computer, a consent telegram indicating that the policyholder has agreed to the insurance contract.

According to the identity authentication system according to the embodiment, it is possible to authenticate a policyholder when concluding an insurance contract without submitting identity verification documents.

1 is a block diagram showing an example of the overall configuration of a personal authentication system according to one embodiment; FIG. 1 is a block diagram illustrating example detailed components of an authentication system according to one embodiment; FIG. FIG. 12 illustrates an example of an account data table, according to one embodiment; FIG. 4 illustrates an example of an authentication screen according to one embodiment; 4 is a flow chart showing an example of processing executed by the personal authentication system according to one embodiment. FIG. 4 illustrates an example of an insurance data table according to one embodiment; FIG. 4 illustrates an example insurance product list, according to one embodiment. FIG. 4 illustrates an example of a contract data table according to one embodiment; FIG. 4 illustrates an example insurance application screen in accordance with one embodiment;

Hereinafter, the personal authentication system 100 according to one embodiment will be described in detail with reference to the attached drawings. The personal authentication system 100 authenticates the policyholder on behalf of the insurer when signing an insurance contract sold by a specific financial institution (bank, securities company, etc.).

<Definition>
As used herein, the term “policyholder” refers to a person who concludes an insurance contract with an insurer. "Account holder" refers to a person who opens an account at a bank, which will be described later, and deposits money into the account. If the account holder concludes an insurance contract for an insurance product sold by a bank, the account holder and the policyholder are the same person. This embodiment describes an example where the account holder and the contractor are the same person, and both terms are used interchangeably below.

As used herein, the term “insurer” refers to a person who is obligated to collect insurance premiums and pay insurance claims when an insured event occurs, based on an insurance contract with a policyholder. Banks can sell insurance products on behalf of insurers. Banks and insurers may have a one-to-one or one-to-many relationship. In other words, a bank, acting as an agent for multiple insurers, can sell multiple insurance products offered by multiple insurers.

<System configuration>
First, with reference to FIG. 1, an example of the overall configuration of the personal authentication system 100 will be described. The personal authentication system 100 includes a server computer 1, server computers 2a, 2b, . A server computer 1, a server computer 2, and a client computer 3 are interconnected via a network 4 (a public network such as the Internet).

The server computer 1 is a computer device (information processing device) that executes main processes according to this embodiment. The server computer 1 is managed by a bank or an entity affiliated/cooperative with the bank to manage/support banking operations. For this reason, the server computer 1 may be implemented in a conventional banking accounting system. In this embodiment, it is assumed that the server computer 1 is implemented by Bank A. Also, the server computer 1 may be implemented by a single computer device, or may be implemented by multiple computer devices.

The server computer 1 implements a database management system (DBMS) and stores account information on accounts (managed by bank A) owned by account holders (contractors). The server computer 1 implements an input/output interface (WEB interface) for providing account information to the account holder, such as referring to the account holder's own account information (balance, etc.). Provide client computer 3 with account information.

The server computer 2 is a computer device (information processing apparatus) that cooperates with the server computer 1 to execute processing according to the present embodiment. The server computer 2 is managed by an insurer or a company affiliated/cooperating with the insurer to manage/support insurance solicitation operations. As such, the server computer 2 may be implemented in a conventionally existing policy administration system of an insurer. Also, the server computer 2 may be implemented by a single computer device or may be implemented by multiple computer devices.

As noted above, banks and insurers may have a one-to-many relationship. In this case, each of the multiple insurers implements the server computer 2 . For example, when a policyholder concludes an insurance contract with insurer a regarding an insurance product provided by insurer a, server computer 1 and server computer 2 implemented by insurer a cooperate. Similarly, when a policyholder concludes an insurance contract with insurer b for an insurance product provided by insurer b, server computer 1 and server computer 2 implemented by insurer b cooperate. The server computer 2 implements a database management system (DBMS) and stores insurer management information relating to insurance contracts concluded by insurers with policyholders.

The client computer 3 is, for example, a computer device (information processing device) used by an account holder (contractor). The client computer 3 displays the above-described input/output interface and receives input from the contractor via the input/output interface. Client computers 3 may be portable computing devices such as smart phones and tablets, laptop computing devices, notebook computing devices, and the like.

Next, with reference to FIG. 2, an example of detailed components of server computer 1 and server computer 2 will be described.

The server computer 1 includes a control device 11, a memory 12, a storage device 13, and a communication device 14, each of which are coupled via a system bus. As shown in FIG. 2, server computer 1 is connected to server computer 2 and client computer 3 .

The control device 11 is also called a processor, and executes control of each component and calculation of data. Further, the control device 11 reads a program stored in the storage device 13 to the memory 12 and executes it for executing various processes according to the present embodiment. Here, the above-mentioned program is a program for implementing part of the functions executed by the personal authentication system 100 and is stored in the storage device 13 of the server computer 1 .

The memory 12 is a volatile data storage device that stores data transmitted from the server computer 2 and the client computer 3, computer-executable instructions, data after arithmetic processing according to the instructions, and the like. The memory 12 may be implemented with RAM (random access memory) (eg, SRAM (static RAM) and DRAM (dynamic RAM)) and the like.

The storage device 13 is a non-volatile data storage device that stores database tables 13a and the like used by the programs and DBMS described above. The storage device 13 may be implemented with a nonvolatile semiconductor memory such as a ROM (Read Only Memory), a magnetic storage device (such as a hard disk drive), an optical disc, or the like. Data such as programs and database tables may be stored in NAS (Network Attached Storage) and/or SAN (Storage Area Network) in addition to or instead of storage device 13 .

Communication device 14 is a network interface that transmits and receives data and control information to and from server computer 2 and client computer 3 over network 4 . This network interface is implemented by, for example, a network card (eg, LAN card) conforming to a protocol such as TCP/IP.

The server computer 2 includes a control device 21, a memory 22, a storage device 23, and a communication device 24, each of which are coupled via a system bus. As shown in FIG. 2, server computer 2 is connected to server computer 1 . The control device 21, memory 22, storage device 23, and communication device 24 function in the same manner as the control device 11, memory 12, storage device 13, and communication device 14 included in the server computer 1, respectively. Description is omitted.

The client computer 3 is a generally used general-purpose computer device, and detailed description of its configuration is omitted. The client computer 3 includes at least a communication device that communicates with the server computer 1, an output device (such as a display) for displaying the input/output interface described above, and an input device (such as a touch panel and mouse) for inputting predetermined information. including. Client computer 3 also optionally includes an imaging device (camera) for photographing an identification document such as a driver's license.

Next, an example of the account data table 300 stored in the database table 13a of the server computer 1 will be described with reference to FIG. Account data table 300 contains account information relating to accounts held by the nominee. The account data table 300 stores a data record (account data record) for each account.

As shown in FIG. 3, the account data table 300 includes data items such as branch number 301, account number 302, account type 303, account holder 304, holder number 305, authentication information 306, name 307, address 308, and Contains date of birth 309 .

Branch number 301 and account number 302 contain information (a combination of branch number and account number) that identifies the account held by the account holder. The combination of branch number and account number serves as information that identifies the account. In this embodiment, the information set in the branch number 301 and the account number 302 identifies the account data record. The account type 303 includes information indicating the corresponding account type (ordinary account, current account, etc.). Account holder 304 contains information indicating the account holder who holds the corresponding account.

The holder number 305 contains an identification number uniquely assigned to the account holder whose account is managed by Bank A (hereinafter referred to as the holder number). The holder number serves as information that identifies the account holder, and if the same person has two accounts at bank A, the holder number 305 of the two corresponding account data records will contain the same holder number. A person number is set. Name 307, address 308, and date of birth 309 each contain information indicating the name, address, and date of birth of the corresponding account holder.

Note that the nominee number is not necessarily assigned to the account holder. Either a branch number and account number combination, or a nominee number may be used to perform identity verification as described below.

The authentication information 306 is used to authenticate the account holder when displaying an account inquiry screen (hereinafter referred to as an account information provision screen) via the input/output interface for providing the account information described above. information (such as passwords).

An account data record is generated, for example, when an account holder opens a corresponding account and sets authentication information to use the account information providing screen. Note that the layout of the data table shown in FIG. 3 is merely an example. Account data table 300 need not include all of the elements shown in FIG. 3, and may include any information not shown in FIG. For example, instead of the layout shown in FIG. 3, account data table 300 may be implemented by a plurality of normalized data tables.

In this embodiment, when an account holder who holds an account at Bank A concludes an insurance contract for an insurance product sold by Bank A, the account holder (contractor) through the account information provision service provided by Bank A authenticate the identity of The account information providing service is an online service that provides account information to the account holder through the input/output interface described above.

An authentication screen is displayed on the output device (display) of the client computer 3 via the input/output interface as the initial screen of the online service described above. FIG. 4 shows an authentication screen 400. As shown in FIG. The authentication screen 400 corresponds to a WEB page generated by the server computer 1 (the WEB page is transmitted from the server computer 1), and accepts input of authentication information and the like from the account holder B. FIG.

As shown in FIG. 4 , the authentication screen 400 includes a branch number input field 401 , an account number input field 402 , a nominee number input field 403 , an authentication information input field 404 and an authentication button 405 . When the account holder uses a combination of the branch number and the account number for personal authentication, the account holder enters the branch number and the account number in the branch number entry field 401 and the account number entry field 402, respectively, and enters the name holder number. , enter the nominee number in the nominee number entry field 403 . Next, when the holder enters authentication information such as a password in the authentication information input field 404 and presses the authentication button 405, the person in question is authenticated.

Next, an example of processing executed by the personal authentication system 100 according to this embodiment will be described with reference to FIG. In this embodiment, account holder B, who has an account at bank A, purchases an insurance product sold by bank A and provided by insurer C, and account holder B acts as policyholder B with insurer C. An example of signing an insurance contract will be explained. When purchasing an insurance product, the account holder B can apply for the insurance product via an input/output interface (account information providing screen) displayed on the output device (display) of the client computer 3 .

First, on the authentication screen 400 displayed on the output device (display) of the client computer 3, when information such as authentication information for authenticating the account holder A is entered, the client computer 3 confirms the entered information. It is transmitted to the server computer as an authentication message (step S501). The authentication screen corresponds to the WEB page transmitted from the server computer 1 as the initial screen of the account information providing screen.

When the communication device 14 of the server computer 1 receives the authentication message, the control device 11 extracts the corresponding account data record from the account data table 300 based on the combination of the branch number and the account number included in the authentication message or the nominee number. (step S502). Next, the control device 11 compares the authentication information set in the authentication information 306 of the account data record with the authentication information included in the authentication message. If the two match, the communication device 14 transmits a response message indicating that the authentication was successful to the client computer 3 (step S503). Account holder B is authenticated by the processing of steps S501 to S503.

When the personal authentication is successful, the client computer 3 transitions from the authentication screen to the account information provision screen (not shown), and the account holder B can check the account information (balance, etc.) on the account information provision screen. . The account information providing screen corresponds to a WEB page generated by the server computer 1 (the WEB page is transmitted from the server computer 1), and receives input from the account holder B such as selection of insurance product. At this time, the control device 11 acquires an insurance data record from the insurance data table 600 (S504). Insurance data table 600 contains insurance information about all or part of the insurance products sold by Bank A.

An example of an insurance data table 600 stored in the database table 13a of the server computer 1 will be described with reference to FIG. The insurance data table 600 stores data records (insurance data records) for each insurance product. As shown in FIG. 6, the insurance data table 600 includes, as data items, an insurance number 601, an insurer number 602, identity verification document submission necessity 603, and explanation necessity 604. FIG.

Insurance number 601 contains information that identifies the insurance product. Insurer number 602 contains information identifying the insurer that provides the corresponding insurance product. Since Bank A may sell multiple insurance products offered by multiple insurers, the insurance product and insurer can be identified by the policy number and the insurer number.

Whether the identity verification document submission requirement 603 specifies that the policyholder presents an identity verification document (driver's license) when the corresponding insurance product concludes an insurance contract under the Act on Prevention of Transfer of Criminal Proceeds. It includes information indicating whether or not (for example, “0: not required” or “1: required”). For example, when "1: required" is set in the identity verification document submission requirement 603, the policyholder must present the identity verification document to the insurer when concluding an insurance contract for the corresponding insurance product. .

The need for explanation 604 indicates that when the corresponding insurance product concludes an insurance contract under the Insurance Business Law, an insurer (including a bank salesperson who sells insurance products, hereinafter referred to as a "salesperson") It includes information indicating whether or not it is prescribed to explain the insurance product to the customer (for example, "0: not required" or "1: required"). For example, when "1: required" is set in the explanation necessity 604, when concluding an insurance contract for the corresponding insurance product, the salesperson needs to explain the insurance product to the policyholder.

Note that the layout of the data table shown in FIG. 6 is merely an example. Insurance data table 600 need not include all of the elements shown in FIG. 6, and may include any information not shown in FIG. For example, instead of the layout shown in FIG. 6, insurance data table 600 may be implemented with multiple normalized data tables.

Returning to the description of FIG. 5, when the insurance contract data record is acquired, the control device 11 generates an insurance product list including the insurance contract data record, and the communication device 14 transmits the insurance product list to the client computer 3 (step S505). ). The insurance product list is displayed on a part of the account information provision screen (or a new screen transitioned from the account information provision screen). The insurance product list corresponds to the WEB page generated by the server computer 1 .

FIG. 7 shows an insurance product list 700 . As shown in FIG. 7, the insurance product list 700 shows an insurance product list 701 corresponding to the insurance data record acquired in step S504, and the policyholder presses any of the corresponding insurance product application buttons 702 to 704. When pressed, it is possible to apply for the corresponding insurance contract.

Insurance 1 displayed in the insurance product list 700 shown in FIG. 7 corresponds to the first insurance data record shown in FIG. not necessary" and whether or not explanation is necessary "0: not necessary"). Similarly, for insurance 2, the second insurance data record shown in FIG. : not required"). Similarly, for insurance 3, the third insurance data record shown in FIG. : required”).

The above means that when the policyholder applies for insurance 1 and 2, there is no need to present identification documents to the insurer, and the salesperson does not need to explain the insurance product to the policyholder. On the other hand, when the policyholder applies for insurance 3, it is necessary to present the identity verification document to the insurer, and the salesperson needs to explain the insurance product to the policyholder.

Insurance 1 is provided by an insurer (referred to as insurer C) corresponding to insurer number "111", and insurance 2 is provided by an insurer corresponding to insurer number "222" (hereinafter referred to as "insurer a ”), and insurance 3 is provided by an insurer corresponding to the insurer number “333” (hereinafter “insurer b”). The insurer C implements a server computer 2 (server computer 2a), and manages insurance contracts for insurance products provided by the insurer through the server computer 2a. Similarly, insurers a and b each implement server computer 2 (server computers 2b and 2c).

For example, when the policyholder applies for insurance 1, when the application button 702 is pressed, the client computer 3 transitions from the screen displaying the insurance product list 700 to the insurance application screen (WEB page) provided by the insurer C. . Similarly, when the policyholder applies for insurance 2 (or insurance 3) and presses the application button 703 (or 704), the client computer 3 displays the insurance product list 700 on the screen for the insurer a ( Alternatively, the screen transitions to an insurance application screen (WEB page) provided by the insurer b).

Transitions from the application buttons 702 to 704 to the corresponding insurance application screens are implemented by hyperlinks embedded in the WEB page of the insurance product list 700 . For example, insurance 1 (insurance number “11111”) is provided by insurer C (insurer number “111”), so apply button 702 may be linked to an insurance application screen provided by insurer C. . That is, an application button for selecting a particular insurance product may be linked to an insurance application screen provided by an insurer that provides the insurance product. That is, insurance products may be linked to a common insurance application screen for each type.

Also, a plurality of insurers may jointly provide an insurance application screen. For example, an insurance application screen for applying for an insurance product sold by multiple insurers that requires the submission of identity verification documents (necessity to submit identity verification documents "1: Required") may be used by multiple insurers. may be provided jointly by In this case, for example, an application button that selects a plurality of insurance products that require submission of identification documents may be linked to a joint insurance application screen. Insurance products may be linked to a common insurance application screen for each type.

Similarly, an insurance application screen for applying for an insurance product that is sold by multiple insurers and that requires an explanation of the insurance product to policyholders (explanation requirement “1: Required”) is provided by multiple insurance companies. May be provided jointly by insurers. In this case, for example, an application button that selects a plurality of insurance products defined to explain the insurance product to the policyholder may be linked to a joint insurance application screen.

In this embodiment, the server computer 1 generates the insurance product list 700 from the insurance data records acquired from the insurance data table 600 (a hyperlink to the insurance application screen corresponding to the insurance product is set). ), instead of acquiring the insurance data record acquired from the insurance data table 600, the insurance product list 700 may be embedded with a hyperlink to the insurance application screen corresponding to the insurance product.

Returning to the description of FIG. 5, when the policyholder presses any of the application buttons 702 to 704 in the insurance product list 700 (in this embodiment, it is assumed that the application button 702 is pressed to apply for insurance 1). , the client computer 3 transmits the selection message to the server computer 1 (step S506). The selection message indicates that the apply button 702 has been pressed (that is, indicates the insurance product selected by policyholder B) and includes at least the policy number corresponding to policy 1 and optionally the insurer number of insurer C. .

Controller 11 of server computer 1 then generates a temporary contract number that includes, for example, a date, a fixed number, a random number, or any combination thereof (step S507). A temporary policy number is a number that is uniquely assigned to each insurance policy that the policyholder enters into with the insurer. As will be described later, when an insurance contract is concluded, the insurer assigns a policy number, and the policy number serves as information that identifies the insurance contract. Until then, the deal is identified by the temporary contract number.

Next, the control device 11 selects the combination of the contractor's branch number and account number or the nominee number included in the account data record acquired in step S502 together with the temporary contract number, and the selection message received in step S506. Based on (insurer C's insurance number), a data record is inserted into the contract data table 800 (step S508). The contract data table 800 contains contract information relating to insurance contracts that Bank A will conclude with policyholders.

An example of the contract data table 800 stored in the database table 13a of the server computer 1 will be described with reference to FIG. The contract data table 800 stores data records (contract data records) for each insurance contract. As shown in FIG. 8, contract data table 800 includes temporary contract number 801, insurance number 802, policy number 803, branch number 804, account number 805, and nominee number 806 as data items.

Temporary contract number 801 contains the temporary contract number generated in step S507. Branch Number 804, Account Number 805, and Nominee Number 806 each include the subscriber's branch number and account number combination, or nominee number, included in the account data record obtained in step S502. Insurance number 802 includes the insurance number corresponding to the selected message received in step S506. The policy number 803 contains an initial value (eg, blank) at the time of step S508.

With the contract data table 800, the server computer 1 (bank A) can manage the insurance contract that the policyholder concludes with the insurer. As will be described later, when a policy number is assigned by the server computer 2 (insurer C), the value included in the policy number 803 includes a value updated by the policy number.

Next, the control device 11 generates an application message, and the communication device 14 transmits the application message to the server computer 2a (step S509). The application message indicates that the policyholder B applies for the selected insurance 1, and at least the name, address, and date of birth of the policyholder included in the account data record obtained in step S502, along with the temporary contract number, and The insurance number corresponding to the selected message received in step S506 is included.

As mentioned above, Bank A may sell insurance products from multiple insurers. For this reason, the server computer 2 is implemented by multiple insurers. The application message has a unified format so that it can be used in common by any of the plurality of server computers 2 . Therefore, the server computer 1 does not need to generate an application message for each server computer 2 .

In step S506, the server computer 1 receives the selection message indicating that the application button 702 has been pressed, so it can recognize that the policyholder has selected the insurance product provided by the insurer C. That is, the destination of the application message can be recognized (information on the server computer 2 (destination information such as IP address is stored in the server computer 1 in association with the insurer number).

Next, the controller 21 of the server computer 2a generates a policy number corresponding to the temporary contract number included in the application message, and generates an insurance application screen (web page) based on the information included in the application message. , the communication device 24 transmits the insurance application screen to the client computer 3 (either directly to the client computer 3 or via the server computer 1) (step S510). The policy number identifies the insurance contract concluded between policyholder B and insurer C. The insurance application screen includes policyholder information including the name of the policyholder included in the application message, the generated policy number, and insurance product information corresponding to the insurance number included in the application message. Also, although not required to be displayed on the insurance application screen, the insurance application screen includes the temporary contract number included in the application message.

Upon receiving the insurance application screen, the client computer 3 transitions from the screen displaying the insurance product list 700 to the insurance application screen 900 (through the hyperlink from the application button 702). FIG. 9 shows an insurance application screen 900 . As shown in FIG. 9 , the insurance application screen 900 includes a policyholder information display field 901 , an insurance contract information display field 902 , a regulation check field 903 , and an input button 904 .

The contractor information display field 901 includes the contractor information described above. The Contractor confirms that this Contractor Information contains his/her correct information. The insurance contract information display column 902 includes the policy number and insurance product information described above. The policyholder confirms whether this insurance product information contains accurate information on the contract content. In the legal regulation check column 903, items such as agreements and the like, which are agreed upon in the corresponding insurance contract under the Insurance Business Law and the like, are checked. When the policyholder presses the input button 803, the client computer 3 considers that the policyholder has agreed to the corresponding insurance contract, and generates an agreement message and transmits it to the server computer 1 (step S511). The consent message indicates that Policyholder B has accepted the insurance policy and includes at least the temporary policy number and the policy number.

When the communication device 14 of the server computer 1 receives the consent message, the control device 11 reads the contract data record (contract data table 800 ) is updated (step S512).

Next, the control device 11 generates a contract conclusion message, and the communication device 14 transmits it to the server computer 2a (step S513). The contract conclusion message indicates that an insurance contract corresponding to insurance 1 has been concluded with policyholder B, and includes at least a policy number. When the communication device 24 of the server computer 2a receives the contract conclusion telegram, it updates data on the corresponding insurance contract managed by the server computer 2a (step S514). Data update means that an insurance contract has been concluded between insurer A and policyholder B, for example, the status of the corresponding insurance contract, which can be identified by the policy number, is set to "1: concluded". to the value that indicates An insurance contract is concluded between the insurer a and the policyholder B for the insurance product sold by the bank A through this process.

The personal authentication system according to this embodiment has been described above. According to this embodiment, the identity of the account holder at Bank A is authenticated on the authentication screen 400, and the information of the account holder held by Bank A (stored in the server computer 1) is used to authenticate the insurer (server). In conjunction with the computer 2), it concludes an insurance contract with the policyholder. With this configuration, at least for insurance products that do not require the policyholder to present identification documents under the Act on Prevention of Transfer of Criminal Proceeds, the identity of the policyholder can be verified by personal authentication at Bank A at the time of contract conclusion. .

In addition, since the temporary contract number is generated by the server computer 1 and the temporary contract number is shared between the server computer 1 and the server computer 2, the information regarding the insurance contract can be synchronized between them.

In the processing described with reference to FIG. 5, when the application button 704 is pressed to apply for insurance 3 (that is, when an insurance product that requires the policyholder to present identification documents is selected), the following such processing is performed.

The insurance application screen sent to the client computer 3 in step S509 includes an identity verification document upload screen. As described above, the application button that selects an insurance product that requires the submission of identification documents links to the insurance application screen corresponding to such insurance product. Therefore, this insurance application screen includes an embedded personal identification document upload screen.

Further, the server computer 1 can determine whether or not the selected insurance product requires the presentation of the identity verification document from the value set in the identity verification document submission necessity 603 of the corresponding insurance data record. can. Therefore, the server computer 1 may request the server computer 2 to include the personal identification document upload screen in the insurance application screen. In addition, depending on the insurance product selected by the policyholder, the server computer 2 determines whether or not the selected insurance product requires the presentation of the identity verification document, and the server computer 2 displays the identity verification document on the insurance application screen. An upload screen may be included.

When the contractor uses the imaging device of the client computer 3 to photograph the identity verification document and uploads the image through the identity verification document upload screen, the identity verification document is shown in the consent message sent to the server computer 2a. Images will be included. In this way, when the insurance product selected by the policyholder requires the presentation of identification documents, an image showing the identification documents is sent to the insurer, so that the insurer can comply with the Act on Prevention of Transfer of Criminal Proceeds. The contractor's identity can be verified in accordance with the procedures set forth below.

Also, in the processing described in FIG. 5, when the application button 704 is pressed to apply for insurance 3 (that is, when an insurance product for which an explanation of the insurance product is specified for the policyholder is selected). , the following process is executed:

The insurance application screen sent to the client computer 3 in step S509 includes a video call activation button. The video call activation button, when pressed by subscriber B, triggers the establishment of an audio-video communication between the client computer 3 and a computer device (not shown) used by the salesperson. Video calling is available, for example, from Zoom Video Communications, Inc. Zoom (registered trademark) provided by Microsoft Corporation and Skype (registered trademark) provided by Microsoft Corporation may be used. As described above, the application button that selects an insurance product that is prescribed to explain the insurance product to the policyholder is linked to the insurance application screen corresponding to such insurance product. Thus, this insurance application screen includes an embedded video call activation button.

Also, the server computer 1 can determine whether or not the selected insurance product requires an explanation by the policyholder from the value set in the explanation necessity 604 of the corresponding insurance data record. Therefore, server computer 1 may request server computer 2 to include a video call activation button in the insurance application screen. In addition, according to the insurance product selected by the policyholder, the server computer 2 determines whether or not the selected insurance product requires an explanation by the policyholder. may be included.

When the policyholder receives an explanation from the salesperson via audio-video communication, a button indicating that the explanation has been received is displayed or activated on the insurance application screen. When the contractor presses the button, the client computer 3 generates an agreement telegram and transmits it to the server computer 2 . In this way, if an insurance product selected by a policyholder requires an explanation by the policyholder, the policyholder can receive explanations from the salesperson via audio-video communication, so that the insurer can: Able to carry out procedures stipulated under the Insurance Business Act, etc.

Note that the hardware components described in the above embodiments are exemplary only, and that other configurations are possible. Also, the order of the processes described in the above embodiment does not necessarily have to be executed in the order described, and may be executed in any order. Moreover, additional steps may be newly added without departing from the basic concept of the invention.

Also, the personal authentication system 100 according to one embodiment of the present invention is implemented by a computer program executed by the server computer 1, but the computer program may be stored in a non-temporary storage medium. Computer programs executed by the server computer 2 and the client computer 3 are similar. Examples of non-transitory storage media include read-only memory (ROM), random access memory (RAM), registers, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disk devices, magneto-optical media, and Including optical media such as CD-ROM discs and Digital Versatile Discs (DVDs).

1 Server Computer 2 Server Computer 2a Server Computer 2b Server Computer 2n Server Computer 3 Client Computer 4 Network 100 Personal Authentication System

Claims (11)

A computer device that allows an account holder who has an account with the bank to conclude an insurance contract corresponding to an insurance product sold by the bank as a policyholder, the computer device comprising a control device, a storage device, and a communication device, the storage device associates and stores account information and authentication information related to the account held by the account holder,
The communication device receives an authentication message from a client computer,
The control device compares the information contained in the authentication message with the account information and the authentication information stored in the storage device to authenticate the account holder as the contractor ,
The communication device receives, from the client computer, a selection message indicating selection of an insurance product,
The communication device provides a second computer device implemented by an insurer that provides the insurance product with an insurance number corresponding to the selected message and an application indicating an application for an insurance contract corresponding to the insurance product. send a message,
In response to the transmission of the application message, the communication device receives, from the client computer, a consent message indicating that the policyholder has agreed to the insurance contract.
A computing device characterized by: 2. The computer device of claim 1, wherein the controller generates a temporary contract number, associates the temporary contract number with the insurance number, and stores the temporary contract number as contract information in the storage device. The temporary contract number is included in the application message,
the consent message includes the policy number corresponding to the temporary contract number and the insurance contract;
The controller updates the contract information corresponding to the temporary contract number based on the policy number.
3. A computer device as recited in claim 2, wherein: 4. A computer device as claimed in any one of claims 1 to 3, wherein the insurance product corresponds to an insurance product that does not require presentation of identification documents by the policyholder. The second computer device includes a plurality of computer devices implemented by a plurality of insurers, and the application message has a common format used in common among the plurality of computer devices. 5. A computing device according to any one of claims 1-4. The communication device transmits an insurance product list for accepting selection of the insurance product to the client computer,
The insurance product list includes a link for transitioning to an insurance application screen provided by an insurer that provides the insurance product when the insurance product is selected,
6. A computer device as claimed in any one of claims 1 to 5, characterized in that: sending an insurance product list for accepting selection of the insurance product to the client computer;
The insurance product list includes a link for transitioning to an insurance application screen provided for each type of insurance product when the insurance product is selected,
6. A computer device as claimed in any one of claims 1 to 5, characterized in that: if the insurance product corresponds to an insurance product that provides for presentation of identification documents by the policyholder, the insurance application screen includes a screen for uploading the identification documents to the second computing device; 8. A computing device according to claim 6 or 7, characterized in that: If the insurance product corresponds to an insurance product that provides a description of the insurance product by a seller of the insurance product, the insurance application screen is a video call with a third computing device used by the seller. 9. A computer device as claimed in any one of claims 6 to 8, comprising a button for activating the . A method executed by a computing device that causes an account holder having an account with the bank to enter into, as a policyholder, an insurance contract corresponding to an insurance product sold by the bank, the computing device comprising: including a storage device that associates and stores account information and authentication information related to the account held by the account holder;
receiving an authentication message from a client computer;
a step of authenticating the account holder as the contractor by comparing the information contained in the authentication message with the account information and the authentication information stored in the storage device;
receiving a selection message indicating a selection of insurance products from the client computer;
sending to a second computer device implemented by an insurer providing said insurance product an application message containing an insurance number corresponding to said selection message and indicating an application for an insurance policy corresponding to said insurance product; When,
a step of receiving, from the client computer, a consent message indicating that the policyholder has agreed to the insurance contract in response to sending the application message;
A method comprising: 11. A computer program product comprising computer-executable instructions, said computer-executable instructions, when executed by a computing device, causing said computing device to perform the method of claim 10.

Images