JP2022089438A - Identity authentication system, method, and computer program - Google Patents

Abstract

To let an account holder who holds an account at a bank conclude, as a policyholder, an insurance contract corresponding to an insurance product sold by the bank.SOLUTION: A computer device receives an authentication message from a client computer, authenticates an account holder as a policyholder by comparing information contained in the authentication message with account information and authentication information stored in a storage device, receives a selection message indicating selection of an insurance product from the client computer, and transmits an application message containing an insurance number corresponding to the selection message to a second computer device implemented by an insurer who provides the insurance product. A communication device receives a consent message indicating that the policyholder has agreed to an insurance contract from the client computer in response to the transmission of the application message.SELECTED DRAWING: Figure 5

Description

This disclosure relates to personal authentication systems, methods, and computer programs. In particular, the disclosure relates to identity verification systems, methods, and computer programs that authenticate policyholders when concluding insurance contracts for insurance products sold by banks.

In December 2007, the so-called "bank window sales," which allows insurance products to be sold at bank counters, was completely lifted. Since banks have account holders with certain assets (hereinafter referred to as "account holders"), by proposing investment products that utilize insurance to the account holders, asset management by the account holders is activated. can do.

When the account holder actually concludes an insurance contract, a predetermined procedure is performed between the account holder (contractor) and the insurance company (insurer). At this time, the insurer often confirms the identity of the policyholder. In particular, in order to prevent money laundering, the Act on Prevention of Transfer of Criminal Proceeds requires that the policyholder be presented with an identity verification document (driver's license) when concluding a certain insurance contract. It has established.

Under the conventional system, even if a bank sells insurance products, the insurer requires the policyholder to submit identity verification documents when concluding an insurance contract, and the policyholder sends the identity verification documents by mail, etc. It was sent to the insurer. Due to such a procedure, the contractor may be canceled without concluding the contract due to neglecting to submit the identity verification document due to the troublesomeness of the procedure.

A computer device according to an embodiment is a computer device that allows an account holder who holds an account at the bank to conclude an insurance contract corresponding to an insurance product sold by the bank as a policyholder. The device includes a control device, a storage device, and a communication device, in which the storage device stores account information and authentication information related to the account held by the account holder in association with each other, and the communication device authenticates from a client computer. Upon receiving the message, the control device authenticates 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. , The communication device receives a selection message indicating selection of an insurance product from the client computer, and the communication device sends the selection message to a second computer device implemented by an insurer who provides the insurance product. In response to the transmission of the application message including the insurance number corresponding to the above and the transmission of the application message, the communication device receives the consent message indicating that the policyholder has agreed to the insurance contract from the client computer. To receive.

Further, the method according to another embodiment is executed by a computer device that causes an account holder who holds an account at the bank to conclude an insurance contract corresponding to an insurance product sold by the bank as a policyholder. The computer device includes a storage device that stores account information and authentication information related to an account held by the account holder in association with each other, and includes a step of receiving an authentication message from a client computer and the authentication message. The step of authenticating the account holder as the policyholder by comparing the information stored in the storage device with the account information and the authentication information, and selection indicating selection of insurance products from the client computer. The step of receiving the message, the step of transmitting the application message including the insurance number corresponding to the selected message to the second computer device implemented by the insurer who provides the insurance product, and the step of transmitting the application message. Correspondingly, the step of receiving a consent message indicating that the policyholder has agreed to the insurance contract is included from the client computer.

According to the identity verification system according to the embodiment, the policyholder can be authenticated when concluding an insurance contract without submitting an identity verification document.

It is a block diagram which shows the example of the whole structure of the person authentication system according to one Embodiment. It is a block diagram which shows the example of the detailed component of the person authentication system according to one Embodiment. It is a figure which shows the example of the account data table according to one Embodiment. It is a figure which shows the example of the authentication screen according to one Embodiment. It is a flowchart which shows the example of the process which the person authentication system executes according to one Embodiment. It is a figure which shows the example of the insurance data table according to one Embodiment. It is a figure which shows the example of the insurance product list according to one Embodiment. It is a figure which shows the example of the contract data table according to one Embodiment. It is a figure which shows the example of the insurance application screen according to one Embodiment.

Hereinafter, the personal authentication system 100 according to the embodiment will be described in detail with reference to the attached drawings. The identity verification system 100 authenticates the identity of the policyholder on behalf of the insurer when concluding 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. The "account holder" refers to a person who opens an account at a bank described later and makes a deposit in the account. When 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. In this embodiment, an example in which the account holder and the contractor are the same person will be described, and in the following, both terms are used interchangeably.

As used herein, the term "insurer" refers to a person who is obliged to collect insurance premiums and pay insurance claims in the event of an insurance accident, based on the insurance contract with the policyholder. Banks may sell insurance products on behalf of the insurer. Banks and insurers may have a one-to-one or one-to-many relationship. That is, a bank can sell a plurality of insurance products provided by a plurality of insurers on behalf of a plurality of insurers.

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

The server computer 1 is a computer device (information processing device) that executes the main processing according to the present embodiment. The server computer 1 is managed by a bank or a business operator affiliated with / cooperative with the bank to manage / support the banking business. For this reason, the server computer 1 may be implemented in a conventional bank accounting system. In this embodiment, the server computer 1 is implemented by the bank A. Further, the server computer 1 may be implemented by a single computer device, or may be implemented by a plurality of computer devices.

The server computer 1 implements a database management system (DBMS) and stores account information about an account (managed by bank A) held by an account holder (contractor). The server computer 1 implements an input / output interface (WEB interface) for providing account information to the account holder, such as the account holder referring to his / her own account information (balance, etc.), via the input / output interface. The account information is provided to the client computer 3.

The server computer 2 is a computer device (information processing device) that executes the processing according to the present embodiment in cooperation with the server computer 1. The server computer 2 is managed by an insurer or a business operator affiliated with / cooperative with an insurer in order to manage / support insurance solicitation operations and the like. Therefore, the server computer 2 may be implemented in the existing insurance contract management system of the insurer. Further, the server computer 2 may be implemented by a single computer device or may be implemented by a plurality of computer devices.

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

The client computer 3 is, for example, a computer device (information processing device) used by the account holder (contractor). The client computer 3 displays the above-mentioned input / output interface and accepts input from the contractor via the input / output interface. The client computer 3 may be a portable computer device such as a smartphone or tablet, a laptop computer device, a notebook computer device, or the like.

Next, with reference to FIG. 2, examples of the server computer 1 and the detailed components of the 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, and each element thereof is connected via a system bus. As shown in FIG. 2, the server computer 1 is connected to the server computer 2 and the client computer 3.

The control device 11 is also referred to as a processor, and controls each of the above components and executes data calculation. Further, the control device 11 reads the program stored in the storage device 13 into the memory 12 and executes the program for executing the various processes according to the present embodiment. Here, the above-mentioned program is a program for implementing a 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, and data after arithmetic processing by the instructions. The memory 12 may be implemented by a RAM (random access memory) (for example, a SRAM (static RAM) and a DRAM (dynamic RAM)).

The storage device 13 is a non-volatile data storage device that stores the database table 13a and the like used by the above-mentioned program and DBMS. The storage device 13 may be mounted on a non-volatile semiconductor memory such as a ROM (read-only memory), a magnetic storage device (hard disk drive or the like), an optical disk, 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 the storage device 13.

The communication device 14 is a network interface for transmitting and receiving data and control information between the server computer 2 and the client computer 3 through the network 4. This network interface is implemented by, for example, a network card (for example, a LAN card) that conforms 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, and each element thereof is connected via a system bus. As shown in FIG. 2, the server computer 2 is connected to the server computer 1. Since the control device 21, the memory 22, the storage device 23, and the communication device 24 function similarly to the control device 11, the memory 12, the storage device 13, and the communication device 14 included in the server computer 1, their details are detailed. The explanation is omitted.

The client computer 3 is a general-purpose computer device that is generally used, and a detailed description of the configuration thereof will be omitted. The client computer 3 is at least a communication device that communicates with the server computer 1, an output device (display, etc.) for displaying the above-mentioned input / output interface, and an input device (touch panel, mouse, etc.) for inputting predetermined information. including. Further, the client computer 3 includes an image pickup device (camera) that arbitrarily captures an identity verification 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. The account data table 300 contains account information about the account held by the holder. 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 has branch number 301, account number 302, account type 303, account holder 304, holder number 305, authentication information 306, name 307, address 308, and data items. Includes date of birth 309.

The branch number 301 and the account number 302 include information (a combination of the branch number and the account number) that identifies the account held by the account holder. The combination of the branch number and the account number serves as information for identifying the account. In this embodiment, the account data record is identified by the information set in the branch number 301 and the account number 302. The account type 303 includes information indicating the type of the corresponding account (usually, for the time being, etc.). The account holder 304 contains information indicating the account holder who holds the corresponding account.

The holder number 305 includes an identification number (hereinafter referred to as a holder number) uniquely assigned to the account holder whose account is managed by the bank A. The holder number serves as information for identifying the account holder, and if the same person has two accounts in bank A, the holder number 305 of the corresponding two account data records has the same name. The 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.

The holder number is not always assigned to the account holder. Either a combination of a branch number and an account number, or a holder number may be used to perform personal authentication described later.

The authentication information 306 is used to authenticate the identity of the account holder when displaying an account inquiry screen or the like (hereinafter referred to as an account information provision screen) via the input / output interface for providing the above-mentioned account information. Information (password, etc.) is included.

The account data record is generated, for example, when the account holder opens the corresponding account and sets the authentication information to use the account information providing screen. The layout of the data table shown in FIG. 3 is merely an example. The account data table 300 does not have to 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, the account data table 300 may be implemented by a plurality of normalized data tables.

In the present 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 providing service provided by bank A. Authenticate your identity. The account information providing service is an online service that provides account information to the account holder through the above-mentioned input / output interface.

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

As shown in FIG. 4, the authentication screen 400 includes a branch number input field 401, an account number input field 402, a holder 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 to perform identity verification, the account holder inputs the branch number and the account number in the branch number input field 401 and the account number input field 402, respectively, and the holder number. When using, enter the holder number in the holder number input field 403. Next, when the holder inputs authentication information such as a password in the authentication information input field 404 and presses the authentication button 405, the holder is authenticated.

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

First, when information such as authentication information for performing personal authentication of the account holder A is input on the authentication screen 400 displayed on the output device (display) of the client computer 3, the client computer 3 inputs the input 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 receives 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 holder 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 they match, the communication device 14 transmits a response message indicating that the authentication was successful to the client computer 3 (step S503). By the processing of steps S501 to S503, the identity of the account holder B is authenticated.

If the identity 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 confirm the account information (balance, etc.) on the account information provision screen. .. The account information provision screen corresponds to the WEB page generated by the server computer 1 (the WEB page is transmitted from the server computer 1), and receives input such as selection of insurance products from the account holder B. At this time, the control device 11 acquires the insurance data record from the insurance data table 600 (S504). The insurance data table 600 contains insurance information about all or part of the insurance products sold by Bank A.

An example of the 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 a data record (insurance data record) for each insurance product. As shown in FIG. 6, the insurance data table 600 includes insurance number 601 and insurer number 602, identity verification document submission necessity 603, and explanation necessity 604 as data items.

The insurance number 601 contains information that identifies the insurance product. The insurer number 602 contains information that identifies the insurer who provides the corresponding insurance product. Since Bank A may sell a plurality of insurance products provided by a plurality of insurers, the insurance products and the insurer can be identified by the insurance number and the insurer number.

Whether it is necessary to submit identity verification documents 603 does the corresponding insurance product stipulate that the policyholder presents identity verification documents (driver's license) when concluding an insurance contract under the Act on Prevention of Transfer of Criminal Proceeds? Includes information indicating whether or not (for example, "0: unnecessary" or "1: required"). For example, if "1: Required" is set in 603 for whether or not to submit identity verification documents, the policyholder must present the identity verification documents to the insurer when concluding an insurance contract for the corresponding insurance product. ..

Explanation Necessity 604 is a contract with an insurer (including a salesperson of a bank that sells insurance products, hereinafter referred to as "salesperson") when the corresponding insurance product concludes an insurance contract under the Insurance Business Law. Includes information (eg, "0: unnecessary" or "1: required") indicating whether or not it is stipulated to explain the insurance product to the person. 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.

The layout of the data table shown in FIG. 6 is merely an example. The insurance data table 600 does not have to 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, the insurance data table 600 may be implemented by a plurality of 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 the insurance product list 700. As shown in FIG. 7, the insurance product list 700 shows the 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, the corresponding insurance contract can be applied for.

The insurance 1 displayed in the insurance product list 700 shown in FIG. 7 is the first insurance data record (insurance number “11111”, insurer number “111”, identity verification document submission necessity “0:” shown in FIG. Corresponds to "unnecessary" and "0: unnecessary"). Similarly, the insurance 2 has a second insurance data record (insurance number “22222”, insurer number “222”, identity verification document submission necessity “0: unnecessary”, and explanation necessity “0” shown in FIG. : Not required "). Similarly, the insurance 3 has a third insurance data record (insurance number "33333", insurer number "333", identity verification document submission necessity "1: required", and explanation necessity "1" shown in FIG. : Required ").

The above means that if the policyholder applies for insurance 1 and 2, it is not necessary to present the identity verification document 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.

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

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), when the application button 703 (or 704) is pressed, the client computer 3 displays the insurance product list 700 from the screen of the insurer a (or insurance 3). Alternatively, the screen transitions to the insurance application screen (WEB page) provided by the insurer b).

The transition from the application buttons 702 to 704 to the corresponding insurance application screens is implemented by the hyperlink embedded in the WEB page of the insurance product list 700. For example, since insurance 1 (insurance number "11111") is provided by insurer C (insurer number "111"), the application button 702 may be linked to the insurance application screen provided by insurer C. .. That is, the application button for selecting a specific insurance product may be linked to the insurance application screen provided by the insurer who provides the insurance product. That is, the insurance product may be linked to a common insurance application screen for each type.

In addition, a plurality of insurers may jointly provide an insurance application screen. For example, multiple insurers have an insurance application screen for applying for an insurance product (necessity of submitting identity verification documents "1: required") that is sold by multiple insurers and is required to submit identity verification documents. May be jointly provided by. In this case, for example, an application button for selecting a plurality of insurance products for which identity verification documents are to be submitted may be linked to a joint insurance application screen. Insurance products may be linked to a common insurance application screen for each type.

Similarly, there are multiple insurance application screens for applying for insurance products sold by multiple insurers that are required to explain insurance products to policyholders (explanation required or not "1: required"). It may be jointly provided by the insurer. In this case, for example, an application button for selecting a plurality of insurance products that are defined to explain the insurance product to the policyholder may be linked to a joint insurance application screen.

In the present embodiment, the server computer 1 generates the insurance product list 700 from the insurance data record acquired from the insurance data table 600 (a hyperlink to the insurance application screen corresponding to the insurance product is set). ), A hyperlink to the insurance application screen corresponding to the insurance product may be embedded in the insurance product list 700 without acquiring the insurance data record acquired from the insurance data table 600.

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

Next, the control device 11 of the server computer 1 generates a temporary contract number including, for example, a date, a fixed number, a random number, or a combination thereof (step S507). The temporary contract number is a number uniquely assigned to each insurance contract that the policyholder will conclude with the insurer. As will be described later, when an insurance contract is concluded, the insurer assigns a securities number, and the securities number serves as information for identifying the insurance contract. Up to, the matter is identified by the temporary contract number.

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

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 a data record (contract data record) for each insurance contract. As shown in FIG. 8, the contract data table 800 includes temporary contract number 801 and insurance number 802, securities number 803, branch number 804, account number 805, and holder number 806 as data items.

The temporary contract number 801 includes the temporary contract number generated in step S507. The branch number 804, the account number 805, and the holder number 806 each include a combination of the contractor's branch number and the account number, or the holder number included in the account data record acquired in step S502. The insurance number 802 includes the insurance number corresponding to the selected telegram received in step S506. The security number 803 includes an initial value (for example, a blank) at the time of step S508.

The contract data table 800 allows the server computer 1 (bank A) to manage the insurance contract that the policyholder will conclude with the insurer. As will be described later, the value included in the securities number 803 will include the value updated by the securities number when the securities number is assigned by the server computer 2 (insurer C).

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 is applying for insurance 1 selected, at least along with the temporary contract number, the contractor's name, address, and date of birth included in the account data record obtained in step S502. 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 a plurality of 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 corresponding to each of the server computers 2.

In step S506, since the server computer 1 has received the selection message indicating that the application button 702 has been pressed, it can be recognized 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 of the server computer 2 (the destination information such as the IP address is stored in the server computer 1 in association with the insurer number).

Next, the control device 21 of the server computer 2a generates a securities 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 (directly to the client computer 3 or via the server computer 1) (step S510). The securities number identifies the insurance contract entered into 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 securities number, and insurance product information corresponding to the insurance number included in the application message. Further, although it is not necessary to be displayed on the insurance application screen, the insurance application screen includes a 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 the 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 legal 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 or her accurate information. The insurance contract information display field 902 includes the above-mentioned securities number and insurance product information. The policyholder confirms that this insurance product information contains accurate information on the contract details. The legal and regulatory check column 903 confirms matters such as contracts and other matters agreed upon in the corresponding insurance contract under the Insurance Business Law. When the policyholder presses the input button 803, the client computer 3 generates a consent message and sends it to the server computer 1 (step S511), assuming that the contractor has agreed to the corresponding insurance contract. The consent message indicates that policyholder B has accepted the insurance contract and includes at least a temporary contract number and a securities number.

When the communication device 14 of the server computer 1 receives the consent message, the control device 11 receives the contract data record (contract data table 800) corresponding to the temporary contract number (value included in the temporary contract number 801) included in the consent message. ), The value included in the security number 803 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 securities number. When the communication device 24 of the server computer 2a receives the contract conclusion message, the data about the corresponding insurance contract managed by the server computer 2a is updated (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 securities number, is "1: concluded". Update to the value indicating. By this process, an insurance contract is concluded between the insurer a and the policyholder B for the insurance product sold by the bank A.

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

Further, 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, information on the insurance contract can be synchronized between the two.

In the process described with reference to FIG. 5, when the application button 704 is pressed to apply for insurance 3 (that is, when the insurance product for which the policyholder is required to present the identity verification document is selected), the following Such processing is executed.

The insurance application screen transmitted to the client computer 3 in step S509 includes an identity verification document upload screen. As mentioned above, the application button for selecting an insurance product for which identity verification documents are required to be submitted is linked to the insurance application screen corresponding to such insurance product. Therefore, this insurance application screen includes an embedded identity verification 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 identity verification document upload screen in the insurance application screen. Further, according to 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. You may include the upload screen.

When the contractor takes a picture of the identity verification document using the image pickup device of the client computer 3 and uploads the image via the identity verification document upload screen, the identity verification document is shown in the consent message sent to the server computer 2a. The image will be included. In this way, if the insurance product selected by the policyholder requires the presentation of an identity verification document, an image showing the identity verification document will be sent to the insurer so that the insurer can comply with the Act on Prevention of Transfer of Criminal Proceeds. The identity of the contractor can be confirmed by the procedure specified below.

Further, in the process described with reference to FIG. 5, when the application button 704 is pressed to apply for insurance 3 (that is, when an insurance product for which it is stipulated to explain the insurance product to the policyholder is selected). , The following processing is executed.

The insurance application screen transmitted to the client computer 3 in step S509 includes a video call activation button. When pressed by the contractor B, the video call activation button triggers the establishment of audio-video communication between the client computer 3 and a computer device (not shown) used by the salesperson. Video calls can be made, for example, from Zoom Video Communications, Inc. Zoom® provided by Microsoft and Skype® provided by Microsoft Corporation may be used. As mentioned above, the application button for selecting an insurance product that is defined to explain the insurance product to the policyholder is linked to the insurance application screen corresponding to such insurance product. Therefore, this insurance application screen includes an embedded video call activation button.

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

When the policyholder receives an explanation from the salesperson via voice-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 a consent message and sends it to the server computer 2. In this way, if the insurance product selected by the policyholder requires explanation by the policyholder, the policyholder can receive an explanation from the salesperson via voice-video communication, so that the insurer can. You can follow the procedures stipulated under the Insurance Business Law.

It should be noted that the hardware components described in the above embodiments are only exemplary and other configurations are possible. Further, 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. In addition, additional steps may be added without departing from the basic concepts of the invention.

Further, the personal authentication system 100 according to the embodiment of the present invention is implemented by a computer program executed by the server computer 1, and the computer program may be stored in a non-temporary storage medium. The same applies to the computer programs executed by the server computer 2 and the client computer 3. Examples of non-temporary 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, optomagnetic media, and Includes optical media such as CD-ROM discs and digital multipurpose 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 holds an account at the bank to conclude an insurance contract corresponding to an insurance product sold by the bank as a policyholder, wherein the computer device is a control device, a storage device, or the like. And a communication device, the storage device associates and stores account information and authentication information regarding the account held by the account holder.
The communication device receives an authentication message from the client computer and receives an authentication message.
The control device authenticates 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.
The communication device receives a selection message indicating the selection of insurance products from the client computer, and receives the selection message.
The communication device transmits an application message including an insurance number corresponding to the selected message to a second computer device implemented by an insurer who provides the insurance product.
In response to the transmission of the application message, the communication device receives a consent message from the client computer indicating that the policyholder has agreed to the insurance contract.
A computer device that features that. The computer device according to claim 1, wherein the control device generates a temporary contract number, associates the temporary contract number with the insurance number, and stores the temporary contract number in the storage device as contract information. The temporary contract number is included in the application message and is included in the application message.
The consent message includes the temporary contract number and the securities number corresponding to the insurance contract.
The control device updates the contract information corresponding to the temporary contract number based on the securities number.
The computer device according to claim 2. The computer device according to any one of claims 1 to 3, wherein the insurance product corresponds to an insurance product for which the policyholder does not stipulate the presentation of identity verification documents. The second computer device includes a plurality of computer devices implemented by a plurality of insurers, and the application message has a common format commonly used among the plurality of computer devices. The computer device according to any one of claims 1 to 4. The communication device transmits the insurance product list that accepts the selection of the insurance product to the client computer, and the communication device transmits the insurance product list.
The insurance product list includes a link for transitioning to an insurance application screen provided by an insurer who provides the insurance product when the insurance product is selected.
The computer device according to any one of claims 1 to 5. An insurance product list that accepts the selection of the insurance product is transmitted 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.
The computer device according to any one of claims 1 to 5. When the insurance product corresponds to an insurance product for which the policyholder presents the identity verification document, the insurance application screen includes a screen for uploading the identity verification document to the second computer device. The computer device according to claim 6 or 7. When the insurance product corresponds to an insurance product for which the seller of the insurance product describes the insurance product, the insurance application screen is a video call with a third computer device used by the seller. The computer device according to any one of claims 6 to 8, further comprising a button for activating. A method executed by a computer device that causes an account holder who holds an account in the bank to conclude an insurance contract corresponding to an insurance product sold by the bank as a policyholder. Includes a storage device that stores account information and authentication information related to the account held by the account holder in association with each other.
The step of receiving the authentication message from the 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.
The step of receiving a selection message indicating the selection of insurance products from the client computer, and
A step of sending an application message including an insurance number corresponding to the selected message to a second computer device implemented by the insurer who provides the insurance product.
In response to the transmission of the application message, a step of receiving a consent message indicating that the policyholder has agreed to the insurance contract from the client computer, and a step of receiving the consent message.
A method characterized by being equipped with. A computer program comprising computer-executable instructions, wherein the computer-executable instruction causes the computer device to execute the method according to claim 10, when executed by the computer device.

Images