JP2005215889A - Personal identification method and personal identification program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a personal identification method which can easily conduct surer personal identification, and also provide a personal identification program. <P>SOLUTION: A company system 21, which receives purchase proposal information from a user terminal 10, transmits a personal identification request to a banking system 30 which is determined to be a request destination from a debit account number included in the purchase proposal information. The banking system 30 transmits an approval request mail to the user terminal 10 of a mail address which is correlated to a deposit account identifier in a deposit account information storage part 32. The user accesses the banking system 30 via the user terminal 10 to log in. A management computer 31 checks a personal identification number included in the logging-in with a personal identification number stored at the deposit account information storage part 32 and informs the company system 21 of the checking result. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

  The present invention relates to an identity verification method and an identity verification program for confirming the identity of a user.

  For example, when opening a new account or applying for the purchase of a mobile phone, it is common to fill in the application form with information about the applicant, such as the address and telephone number, along with the name of the applicant. At this time, you may be asked to submit a certificate such as a license or passport to verify the identity of the applicant. Therefore, the application procedure as described above cannot be performed unless a card or document that can be used as such a certificate is carried.

  Also, when carrying and using various cards and documents, there is a risk of being lost or stolen. In view of this, a safe identification method that does not require carrying a card or the like for proof and is not likely to be used illegally has been disclosed (see, for example, Patent Document 1). In Patent Document 1, a palm of a registrant is photographed and registered in advance. Then, take a picture of the palm of the person to be confirmed at the purchase place of various products, the window of the use facility, etc. or the confirmation place such as the entrance of a residence or a confidential facility, and compare and judge the palm of this photographed registrant . Permitting cash withdrawals and deposits, purchases of goods, use of transportation, admission to and use of facilities and confidential facilities, issuance of certificates, etc. only when they are identified and confirmed as the same person.

A system for performing personal authentication using a credit card is also disclosed (see, for example, Patent Document 2). In Patent Document 2, when the payment terminal reads the personal information recorded on the credit card, the payment terminal transmits the personal information to the payment center. The settlement center transmits a barcode image associated with the received personal information to the user's mobile phone. The reader of the payment terminal reads the barcode image displayed on the mobile phone. Then, the payment terminal performs personal authentication by comparing the personal authentication data included in the barcode image from the mobile phone with the personal information recorded on the credit card. By using this personal authentication system, unauthorized use of the card by another person can be prevented.
JP-A-11-203479 (FIG. 1) JP 2003-317020 A (FIGS. 2 to 4)

  However, the technique of Patent Document 1 requires a system for registering the registrant's palm in advance. Therefore, it may take a lot of time to newly construct such a system.

  Further, in the technique of Patent Document 2, identity verification is performed by displaying a barcode image on a user's mobile phone when using a credit card. For this reason, even if you have a credit card, users who do not have a mobile phone cannot use this system. Therefore, there is a case where the identity verification cannot be easily performed.

  The present invention has been made in view of the above-described problems, and an object thereof is to provide a personal identification method and a personal identification program that can easily perform more reliable personal identification.

In order to solve the above-mentioned problem, the invention described in claim 1 is connected to a user terminal and a requester terminal that requests a user's identity confirmation via a network, and includes user account information. An identity verification method for confirming the identity of a user using a management computer connected to an account information storage unit that stores associated personal identification information, wherein the management computer sends an identity from the requesting terminal. A request receiving stage for receiving a confirmation request including user information for identifying a user to be confirmed, a user account is identified based on the received user information, and the user account is related to the identified user account In response to the authentication request stage for transmitting an identification confirmation request for prompting the user to input the personal identification information, and in response to the identification confirmation request, the user can use the user account for the user account. A verification information providing step of performing identity verification by comparing the password information entered at the end with the password information recorded in the account information storage unit, and transmitting information according to the result to the requesting terminal. Inclusion is included.

  According to a second aspect of the present invention, in the identity verification method according to the first aspect, the account information storage unit stores information related to the identity verification method in association with the user account information, and the confirmation information The providing stage is characterized by transmitting information on the identity verification method according to the result of identity verification.

  The invention according to claim 3 is the identity verification method according to claim 1 or 2, wherein the account information storage unit stores user terminal information of a user in association with the user account information, The management computer further includes a user terminal information acquisition step of acquiring the user terminal information of the user from the account information storage unit based on the user account information included in the confirmation request, and the authentication request step includes: The management computer makes a request to the user terminal specified by the user terminal information acquired in the user terminal information acquisition step, and the confirmation information providing step is received from the user terminal that transmitted the identity verification approval request. The gist is to collate the password information with the password information recorded in the account information storage unit.

  According to a fourth aspect of the present invention, in the identity verification method according to any one of the first to third aspects, the management computer assigns a request identifier for identifying the confirmation request received from the request source terminal. The authentication requesting step transmits the request identifier data to the user terminal, and the confirmation information providing step is based on the request identifier data included in the information received from the user terminal. The gist is to notify the requesting terminal specified by the information according to the result.

  According to a fifth aspect of the present invention, in the identity verification method according to the fourth aspect, the management computer receives an access from the user terminal and presents a plurality of request identifiers to the user terminal; The present invention further includes a specifying step of specifying a request identifier that matches the request identifier transmitted in the authentication request step from the plurality of request identifiers.

  A sixth aspect of the present invention is the identity verification method according to any one of the first to fifth aspects, wherein the management computer is a request for performing identity verification for the request source that received the request in the request reception stage. The method further includes an original confirmation step, and the authentication request step is characterized in that the management computer transmits a result of the identity verification of the request source in the request source confirmation step to the user terminal.

  The invention described in claim 7 is the identity verification method according to any one of claims 1 to 5, wherein the management computer is a request for performing identity verification for the request source that received the request in the request reception stage. Further comprising an original confirmation step, wherein the authentication request step is performed for the user terminal of the user specified from the user account information included in the confirmation request from the request source that has been verified in the request source confirmation step. The gist is that the management computer makes a request.

The invention described in claim 8 is connected to the user terminal and the request source terminal for requesting the identity verification of the user through the network, and stores the password information associated with the user account information. An identity verification program for verifying a user's identity using a management computer connected to an account information storage unit, wherein the management computer identifies the user who is the subject of identity verification from the requesting terminal. Request receiving means for receiving a confirmation request including user information for performing identification, identifying a user account based on the received user information, and inputting the password information related to the identified user account to the user Authentication request means for transmitting an identity confirmation acceptance request for prompting and password information entered by the user into the user terminal for the user account in response to the identity confirmation acceptance request The verify your identity by collating the personal identification information recorded in the account information storage unit, and summarized in that function as check information providing means for transmitting information corresponding to this result to the requesting terminal.

  According to a ninth aspect of the present invention, in the identity verification program according to the eighth aspect, the account information storage unit stores information related to the identity verification method in association with the user account information, and the confirmation information The providing means is to send information relating to the identity verification method as information according to the result.

  The invention described in claim 10 is the identity verification program according to claim 8 or 9, wherein the account information storage unit stores user terminal information of a user in association with the user account information, Based on the user account information included in the confirmation request, the management computer further functions as user terminal information acquisition means for acquiring the user terminal information of the user from the account information storage unit, the authentication request means, The management computer makes a request to the user terminal specified by the user terminal information acquired by the user terminal information acquisition means, and the confirmation information providing means is received from the user terminal that transmitted the identity confirmation acceptance request. The gist is to collate the password information and the password information recorded in the account information storage unit.

  The invention described in claim 11 is the identity verification program according to any one of claims 8 to 10, wherein the management computer is assigned a request identifier for identifying the confirmation request received from the request source terminal. The authentication requesting means transmits the request identifier data to the user terminal, and the confirmation information providing means is based on the request identifier data included in the information received from the user terminal. The gist is to notify the requesting terminal specified by the information according to the result.

  The invention described in claim 12 is the identity verification program according to claim 11, wherein the management computer receives the access from the user terminal and presents a plurality of request identifiers to the user terminal, and The gist is to further function as a specifying unit that specifies a request identifier that matches the request identifier transmitted from the plurality of request identifiers in the authentication request unit.

  A thirteenth aspect of the present invention is the identity verification program according to any one of the eighth to twelfth aspects, wherein the management computer requests the management computer to verify the identity of the request source that has received the request at the request receiving means. Further, the authentication requesting unit causes the management computer to transmit a result of the identity verification of the requesting source by the requesting source checking unit to the user terminal.

The invention described in claim 14 is the identity verification program according to any one of claims 8 to 12, wherein the management computer requests the management computer to verify the identity of the request source that has received the request. Further functioning as an original confirmation means, the authentication request means for the user terminal of the user specified from the user account information included in the confirmation request from the request source that has been verified by the request source confirmation means The gist is that the management computer makes a request.

(Function)
According to the invention described in claim 1 or 8, when a request for identity verification is made from the requesting terminal, the management computer specifies the user based on the user account information included in the request, and this user Request the user terminal to send the password information. The management computer confirms the identity based on the information received from the user terminal of the user in response to this request and the password information associated with the user account information and stored in advance in the storage unit. The corresponding information is notified to the requesting terminal. For this reason, since identity verification is performed using the existing password information stored in the storage unit managed by the management computer, identity verification can be easily performed. Further, since the user can confirm the identity by notifying the management computer of the personal identification information, the identity can be easily confirmed by notifying the requester of the user account information. On the other hand, the requester who performs identity verification simply sends a confirmation request including user account information from the requester terminal, and the management computer performs identity verification on behalf of the requester. it can.

  According to the invention described in claim 2 or 9, the management computer transmits information related to the identity verification method associated with the user account information according to the result of identity verification. Therefore, the requester can know the identity verification method provided. Therefore, the requester can determine compatibility with the identity verification method required by the requester based on the information on the identity verification method. For example, when the identity verification method required by the request source is different, the identity verification by the identity verification method required by the request source can be further performed.

  According to the invention described in claim 3 or 10, the authentication request stage is performed for the user terminal specified by the user terminal information recorded in the storage unit managed by the management computer. Therefore, an authentication request is issued to the user terminal specified by the user terminal information recorded in the storage unit managed by the management computer, not the user terminal specified by the user terminal information received by the request source terminal. Is called. Therefore, the management computer intervenes between the requester and the user, so that it is possible to prevent the identity verification from being completed when another person has been completed.

  According to the invention described in claim 4 or 11, the management computer assigns a request identifier for specifying the confirmation request received from the request source terminal. Then, the management computer notifies the request source terminal specified based on the data of the request identifier included in the information received from the user terminal that requested the authentication, information corresponding to the result. For this reason, even when there are requests for identity verification from a plurality of request sources to the same user, identity verification can be performed only for the request source for which the user desires identity verification.

  According to the invention described in claim 5 or 12, the management computer presents a plurality of request identifiers to the user terminal in response to access from the user terminal. The management computer specifies a request identifier that matches the request identifier transmitted in the authentication request stage from the received request identifier. Therefore, the user can easily specify the request identifier to be approved from the plurality of identifiers displayed on the user terminal without inputting the request identifier.

  According to the invention described in claim 6 or 13, the management computer confirms the identity of the request source, and transmits the result of the identity verification of the request source to the user terminal. For this reason, the user can determine whether or not to transmit the personal identification information with reference to the result of the identity confirmation regarding the received requester. Therefore, both the user and the requester can confirm each other.

  According to the invention described in claim 7 or 14, the management computer confirms the identity of the request source, and only performs identity verification based on the confirmation request from the request source that has been confirmed. For this reason, the management computer performs identity verification only for the requester who has been confirmed. Therefore, when the user terminal receives the approval request, the password information can be transmitted with peace of mind.

  According to the present invention, more reliable identity verification can be easily performed.

  Hereinafter, an embodiment embodying the present invention will be described with reference to FIGS. In the present embodiment, a person confirmation method for confirming whether or not a user who has applied for purchase of a mobile phone is the person himself / herself will be described.

  In the identity verification method of the present embodiment, a computer terminal is used as the user terminal 10 as shown in FIG. The user terminal 10 includes a display 15, a keyboard, and a mouse. The user terminal 10 displays an application screen and an approval mail screen on the display 15. The user terminal 10 is also instructed to input character data and send data using a keyboard and mouse.

The user terminal 10 is connected to a company system 21 and a bank system 30 as request source terminals via the Internet I as a network.
The company system 21 is a system computer owned by the company 20 that sells products. In this embodiment, the company 20 is a sales company that sells mobile phone terminals via the Internet I. Further, the company system 21 of the company 20 is connected to the bank system 30 via the Internet I in the same manner as the user terminal 10.

  The enterprise system 21 records data relating to mobile phones to be sold. Furthermore, the company system 21 records address data for accessing the system of the financial institution that is the requester of the personal identification. Specifically, the IP address, mail address, URL (Uniform Resource Locator), etc. of the bank system 30 associated with each bank code are used as this address data.

  On the other hand, the bank system 30 includes a management computer 31. The management computer 31 includes a CPU, a RAM, a ROM, and the like (not shown), and performs processing described later (processing including a request reception stage, an authentication request stage, a confirmation information provision stage, a user terminal information acquisition stage, and an assignment stage). The management computer 31 functions as a request receiving unit, an authentication requesting unit, a confirmation information providing unit, a user terminal information obtaining unit, a granting unit, and the like by executing a personal identification program for this purpose.

The management computer 31 is connected to a deposit account information storage unit 32 and an identity verification request information storage unit 33 as account information storage units.
As shown in FIG. 2, the deposit account information storage unit 32 stores deposit account information 320 relating to bank deposit accounts. The deposit account information 320 is recorded in the deposit account information storage unit 32 when a customer opens an account. Further, the deposit account information 320 includes data relating to a deposit account identifier, a customer identifier, a personal identification number, an e-mail address, personal information, and personal identification information.

In the deposit account identifier data area, data relating to an identifier for specifying a deposit account of a customer opened in a bank is recorded. The deposit account identifier data of this embodiment includes data related to a branch code, a deposit type code, and an account number.

In the customer identifier data area, data relating to an identifier for identifying the holder of the deposit account is recorded. This customer identifier data is used when performing identity verification.
In the personal identification number data area, data relating to the personal identification number related to the deposit account is recorded. This personal identification number data is data used when a transaction is performed using a customer's deposit account. In the present embodiment, the personal identification number data is used when verifying the identity together with the customer identifier data.

  In the mail address data area, a mail address that is a destination used when an electronic mail is transmitted to the user is recorded. This e-mail address is used when the bank system 30 notifies the customer such as approval of identity verification.

  In the principal information data area, data of information about the user who is the principal of the deposit account is recorded. This is information about the user such as the user's name, address, postal code, telephone number, and date of birth.

  In the identity verification information data area, data relating to a method for confirming the identity when the account is opened is recorded. Examples of the method for confirming the identity include “confirm with a license”, “confirm with a passport”, and “confirm with a resident's card”.

  On the other hand, as shown in FIG. 3, the personal identification request information storage unit 33 stores personal identification request information 330 used for performing personal identification. The identity verification request information 330 is recorded when a user identity verification request is received from the company system 21 or the like. The identity verification request information 330 includes data regarding an identity verification request identifier, a deposit account identifier, a request source, a reply time limit, and a confirmation completion flag.

In the personal identification request identifier data area, data relating to an identifier for identifying a personal identification request is recorded.
In the deposit account identifier data area, data relating to an identifier related to a deposit account for which a request for identity verification is made is recorded. The identity verification request information 330 and the deposit account information 320 are associated with each other through the data recorded in the deposit account identifier data area.

  In the request source data area, data related to the request source who requested the identity verification is recorded. Specifically, the request source data is data such as the name of the request source and the mail address of the request source for returning the confirmation result.

  In the reply time limit data area, data relating to a reply time limit for receiving a reply from the user for the purpose of identity verification is recorded. In this embodiment, this reply deadline is uniformly determined after a predetermined period (for example, 10 hours) after receiving the identity verification request. This reply deadline is a deadline for notifying the requester that the identity could not be confirmed when the identity could not be confirmed.

  In the confirmation completion flag data area, data relating to a flag indicating whether or not the identity confirmation is completed is recorded. Specifically, in this data area, a flag “0” is recorded when the identity verification has not been performed yet, and a flag “1” is recorded when the identity verification is completed. The

Next, in the system configured as described above, processing when a user makes a contract for purchasing a product using the user terminal 10 will be described with reference to FIGS.
The user accesses the corporate system 21 via the Internet I using the user terminal 10. The enterprise system 21 of the enterprise 20 transmits information such as a model and a charge related to the mobile phone being sold to the user terminal 10. When purchasing a mobile phone from the company 20 based on the received information, the user makes a request for a mobile phone purchase application screen from the user terminal 10. Thereby, the enterprise system 21 transmits purchase application screen data to the user terminal 10. This purchase application screen data includes purchase product screen data and purchase settlement screen data. The user terminal 10 that has received the purchase application screen data first displays the purchase product screen 500 of FIG.

  The purchased product screen 500 includes a model selection column 501 for selecting a model desired for purchase and a rate plan selection column 502 for a mobile phone usage contract. Further, the purchase product screen 500 includes a cancel button 507 for canceling the process and a next screen button 508 for displaying the purchase settlement screen.

  Here, the user selects a model desired to purchase in the model selection field 501 and further selects a desired rate plan in the price plan selection field 502. Then, the user selects the next screen button 508.

When the next screen button 508 is selected, the user terminal 10 displays the purchase settlement screen 510 of FIG.
The purchase settlement screen 510 includes a name description column 511, an e-mail address description column 512, an address description column 513, a telephone number description column 514, a payment method selection button 515, and a number description column 516. The name entry column 511 is a column for entering the name of the user who is the applicant. The e-mail address description column 512 is a column for describing the e-mail address of the user terminal of the user. The address description column 513 is a column for describing the user's address. The telephone number description column 514 is a column for describing a user's telephone number. The payment method selection button 515 is a button for selecting a payment method for a product to be purchased. The number description column 516 is a column for describing a number corresponding to a payment method, that is, an account number or a credit number.

  Further, the purchase settlement screen 510 includes a cancel button 517 for canceling the process and a send button 518. The send button 518 is a button for sending information on the purchase product screen 500 and the purchase settlement screen 510.

  Here, the user inputs a name, an e-mail address, an address, and a telephone number in each of the description columns 511, 512, 513, and 514 using the keyboard and mouse of the user terminal 10. Then, the user selects the “bank withdrawal” payment method selection button 515 and enters the withdrawal account number in the number description column 516. Here, the number including the bank code and the deposit account identifier data is input as the withdrawal account number. After completing the input in each field, the transmission button 518 is selected.

  When the transmission button 518 on the purchase settlement screen 510 is selected, the user terminal 10 transmits the purchase application information to the company system 21 (step S1-1). This purchase application information includes data on the model of the mobile phone terminal that the user wishes to purchase, data on the rate plan, the name, e-mail address, address, telephone number, payment method, and payment method of the user who is the purchaser. Data on the withdrawal account number.

The company system 21 records the received purchase application information. Then, the company system 21 determines a person confirmation request destination (step S1-2). Specifically, the company system 21 extracts a bank code from the withdrawal account number data of the purchase application information. Then, the enterprise system 21 acquires address data for accessing the bank system 30 corresponding to the extracted bank code.

  Next, the company system 21 transmits an identity confirmation request to the bank system 30 determined as the identity confirmation request destination (step S1-3). This identity verification request includes request source data such as the name of the company 20 and a reply destination mail address. Further, the identity verification request includes a deposit account identifier extracted from the withdrawal account number of the purchase application information.

  The management computer 31 of the bank system 30 verifies the deposit account identifier based on the received identity verification request data (step S1-4). Specifically, first, the management computer 31 searches the deposit account information storage unit 32 for deposit account information 320 related to the received deposit account identifier. Here, when there is no deposit account identifier that matches the received deposit account identifier in the deposit account information storage unit 32, the management computer 31 stops the processing. Then, the management computer 31 specifies the request source company system 21 based on the received request source data, and transmits to the specified company system 21 that the identity cannot be confirmed.

  On the other hand, when the deposit account information 320 related to the received deposit account identifier can be extracted, the management computer 31 records each data in the personal identification request information storage unit 33. Specifically, the management computer 31 records deposit account identifier data and request source data included in the received identity verification request. Further, the management computer 31 assigns an identity confirmation request identifier to this data, and records the identity confirmation request identifier data. Furthermore, the management computer 31 sets a reply deadline based on the received time, and records this reply deadline data. Further, the management computer 31 records a confirmation completion flag of “0”.

  Next, the management computer 31 sends an approval request mail for identity verification (step S1-5). Specifically, the management computer 31 first obtains from the deposit account information storage unit 32 the mail address data corresponding to the deposit account identifier based on the deposit account identifier stored in the identity verification request information storage unit 33. . Then, the management computer 31 transmits an approval request e-mail to the user terminal 10 of the acquired e-mail address.

The user terminal 10 that has received the approval request e-mail displays an e-mail screen 600 shown in FIG.
The e-mail screen 600 includes the name of the company 20 that has applied for identity verification and the identity verification request identifier. Further, the e-mail screen 600 includes a character string 601 including a URL and a character string 602 of a mail address. The URL of the character string 601 indicates the access destination of the bank system 30 that is used when the identification confirmation is approved.

  This character string 601 includes data (parameters) related to the identity verification request identifier. The e-mail address of the character string 602 is an e-mail address that is used when the identity verification is not approved.

  Here, the user logs in to the bank system 30 using the user terminal 10 in order to approve the identity verification (step S1-6). Specifically, when the user selects a character string 601 on the email screen 600, the user terminal 10 accesses the bank system 30. At this time, the user terminal 10 delivers the identity verification request identifier parameter included in the character string 601 to the bank system 30.

The management computer 31 of the bank system 30 transmits login screen data. This login screen data includes identity verification request identifier data.
The user terminal 10 that has received the login screen data displays a login screen 700 for personal authentication shown in FIG.

  The login screen 700 includes a customer number input field 701 and a login password input field 702. The customer number input field 701 is an input field for inputting a customer identifier. The login password input column 702 is a column for inputting a login password. In the present invention, the login password is a password related to a bank deposit account, and is a password used for identity authentication when a transaction is performed using a customer deposit account.

Further, the login screen 700 includes a cancel button 707 and a login button 708.
Here, the user inputs the customer identifier number in the customer number input field 701 and the password as the login password in the login password input field 702 via the user terminal 10 and selects the login button 708. . As a result, the user terminal 10 transmits the data regarding the customer number and the personal identification number and the identity verification request identifier data included in the login screen data of the login screen 700 to the bank system 30.

  Next, the management computer 31 of the bank system 30 performs a confirmation process based on the received login data (step S1-7). Specifically, the management computer 31 first extracts the deposit account information 320 including the customer identifier that matches the received customer number from the deposit account information storage unit 32. Then, the management computer 31 confirms whether the personal identification number associated with the extracted customer identifier matches the personal identification number received. At this time, if the passwords do not match, the management computer 31 transmits to the user terminal 10 that login is not possible.

  On the other hand, if the passwords match, the management computer 31 extracts the deposit account customer identifier of the deposit account information 320. Then, the management computer 31 extracts the person confirmation request information 330 including the extracted deposit account identifier from the person confirmation request information storage unit 33. Further, the management computer 31 checks whether or not the identity confirmation request identifier of the extracted identity confirmation request information 330 matches the received identity confirmation request identifier.

  If the management computer 31 fails to confirm, the management computer 31 sets the confirmation completion flag to “1” and ends the confirmation process. Then, the management computer 31 transmits information indicating that the identity cannot be confirmed to the company system 21 specified based on the request source data of the identity confirmation request information 330.

  On the other hand, when the identity confirmation request identifier can be confirmed, the management computer 31 sets the confirmation completion flag to “1” and completes the confirmation process. Then, the management computer 31 notifies the company system 21 specified based on the request source data of the personal identification request information 330 that the personal identification has been completed (step S1-8). In this notification, the company system 21 transmits the personal identification information recorded in the deposit account information storage unit 32 to the company system 21.

The company system 21 that has received the notification of the completion of identity verification notifies the user terminal 10 of the user that the procedure has been completed (step S1-9).
If the user who received the e-mail on the e-mail screen 600 in FIG. 7 does not remember making a mobile phone purchase application to the sales company of the enterprise system 21, the e-mail address of the character string 602 is sent. The mail is returned from the user terminal 10. The management computer 31 having this mail address acquires the request source data from the person confirmation request information storage unit 33 based on the person confirmation request identifier included in the reply mail. Then, the management computer 31 notifies the sales company of the company system 21 that is the request source that the identity cannot be confirmed, sets the confirmation completion flag to “1”, and ends the processing.

  On the other hand, the management computer 31 extracts, from the principal confirmation request information storage unit 33, the principal confirmation request information 330 whose reply deadline has passed while the confirmation completion flag is “0”. Then, the management computer 31 notifies the sales company of the company system 21 that is the request source that the identity cannot be confirmed, sets the confirmation completion flag to “1”, and ends the processing.

According to this embodiment, the following effects can be obtained.
-In this embodiment, the management computer 31 collates a deposit account child identifier based on the personal identification request data received from the company system 21 (step S1-4). Then, the management computer 31 transmits an approval request mail to the user terminal 10 of the user specified by the verification of the deposit account identifier (step S1-5). The user terminal 10 that has received the approval request mail logs into the bank system 30 (step S1-6). The management computer 31 performs a confirmation process based on the received login data (step S1-7). Accordingly, identity verification is performed using the existing personal identification number data stored in the deposit account information storage unit 32 managed by the management computer 31. For this reason, since the management computer 31 does not need to set personal identification information for identity verification or notify the user terminal 10 of this, it is possible to efficiently perform identity verification.

  Further, since the user can confirm the identity by notifying his / her personal identification number data to the management computer 31, the user can easily confirm the identity by including the withdrawal account number data in the purchase application information. You can go there.

  In the present embodiment, the management computer 31 sends an approval request email including the URL of the login screen 700 to the user terminal 10. Therefore, the user can easily access the login screen 700 using the user terminal 10 that has received the approval request. Therefore, the user can easily approve the identity verification.

  In the present embodiment, the identity verification is performed by the management computer 31. For this reason, when the user terminal 10 transmits purchase application information (step S1-1), it is not necessary to confirm the identity on the spot. Therefore, the user can also perform a login operation for inputting a personal identification number to the user terminal 10 by moving to a place where others cannot see it. Therefore, it is possible to reduce the possibility that the personal identification number is leaked by an operation input when performing identity verification.

  In the present embodiment, the management computer 31 transmits an approval request mail to the user terminal 10 specified by the mail address stored in the deposit account information storage unit 32 in association with the user account identifier. (Step S1-5). For this reason, since the bank system 30 intervenes between the company 20 of the sales company and the user at the time of identity verification, it is possible to suppress the identity verification by impersonating another person.

  In the present embodiment, the management computer 31 performs a confirmation process based on the received login data (step S1-7). Then, when the confirmation process is completed, the management computer 31 notifies the company system 21 that the personal identification has been completed (step S1-8). For this reason, since the management computer 31 informs the corporate system 21 not only of the information about the user but only the result of the identity confirmation, it is possible to suppress the leakage of the information about the user and to confirm the identity more safely. It can be carried out.

  In the present embodiment, when the deposit account identifier that matches the deposit account identifier included in the identity verification request received from the company system 21 is not stored in the deposit account information storage unit 32, the management computer 31 Information to the effect is transmitted to the company system 21. Thereby, the company system 21 can immediately grasp that it is a fictitious deposit account identifier.

  In the present embodiment, the management computer 31 includes the e-mail address of the e-mail to be returned when the identity confirmation is rejected in the e-mail of the approval request transmitted to the user terminal 10. When the management computer 31 receives an e-mail at this e-mail address, the management computer 31 notifies the company system 21 that the user's identity could not be confirmed upon receiving a rejection of the identity verification. Therefore, when the user does not verify the identity, the management computer can notify the enterprise system 21 early that the identity cannot be confirmed.

  In the present embodiment, the management computer 31 sets the reply deadline and sets the confirmation completion flag to “0” when receiving the identity confirmation request from the company system 21. The confirmation completion flag is a flag that is changed to “1” when the user terminal 10 logs in and the confirmation processing is completed. Then, the management computer 31 notifies the company system 21 that the identity confirmation request has not been confirmed for the identity confirmation request whose confirmation completion flag is “0” even after the reply deadline has passed. For this reason, when a user refuses identity verification, it is not necessary to perform any processing. That is, since the user only needs to perform processing when he / she thinks that personal identification is necessary, it is simple.

  In the present embodiment, when receiving a confirmation request from the company system 21, the management computer 31 assigns a principal confirmation request identifier for identifying the confirmation request, and records this in the principal confirmation request information storage unit 33. To do. Then, the management computer 31 receives the personal identification request identifier together with the password entered on the login screen 700. Further, when the received personal identification number matches the personal identification number stored in the deposit account information storage unit 32, the management computer 31 completes the personal authentication for the requesting company system 21 associated with the personal identification request identifier. Send a message to the effect. For this reason, even when there are requests for identity verification from a plurality of company systems 21 to the same user, notification of completion of identity verification can be sent only to the company system 21 for which the user wishes to identify himself / herself. it can.

  In the present embodiment, the management computer 31 transmits the personal identification information recorded in the deposit account information storage unit 32 when notifying the corporate system 21 that the personal identification has been completed. In other words, the company 20 obtains information about the method of identity verification via the company system 21. For this reason, the company 20 can determine the suitability of the identity verification method required by the company 20 based on the acquired information on the identity verification method. Then, it can be used as a reference when the company 20 performs other processing such as identity verification by a more reliable method.

In addition, you may change this embodiment as follows.
In the above embodiment, when the confirmation process is completed based on the information from the user terminal 10, the management computer 31 transmits a message to that effect to the request source. At this time, the management computer 31 may receive an account withdrawal settlement request together with the identity verification request, execute settlement based on the settlement request when the identity verification is completed, and notify the requester of the settlement execution result. Thereby, the requesting company system 21 can complete the settlement as well as the identity verification.

In the above embodiment, the case where the user identity is confirmed with respect to the enterprise system 21 has been described. However, the present invention is not limited to this, and the corporate system 21 may be confirmed with respect to a bank account user. That is, the management computer 31 may further function as a request source confirmation unit to perform the request source confirmation stage. In this case, a request source confirmation process shown in FIG. 9 is performed between steps S1-4 and S1-5 of the process shown in FIG. That is, in the request source confirmation process, when the verification of the deposit account identifier is completed based on the identity confirmation request from the company system 21 (step S1-4), the bank system 30 first acquires the transfer account data (step S1-4). S2-1). This transfer account data is information relating to an account into which a debit amount is transferred from the user's account, that is, information relating to the account of the company 20, and includes data relating to a bank code, a branch code, a deposit type code and an account number. Specifically, the management computer 31 obtains from the principal confirmation request data when the transfer account data is included in the principal confirmation request data. If it is not included in the personal identification request data, the company system 21 is requested to transmit the transfer account information, and the transfer account data is acquired from the company system 21.

  Next, when the bank code included in the acquired transfer account data is a bank code indicating its own bank, the management computer 31 of the bank system 30 checks the transfer account (step S2-2). Specifically, the management computer 31 detects from the deposit account information 320 recorded in the deposit account information storage unit 32 a deposit account identifier that matches the deposit account identifier obtained by removing the bank code from the transfer account data. If there is a matching deposit account identifier, an approval request mail is transmitted to the company system 21 using the mail address associated therewith. The company system 21 that has received the approval request mail logs in to the bank system 30 in the same manner as in step S1-6 (step S2-4). And the bank system 30 performs the confirmation process (step S2-5) about a request source similarly to said step S1-7.

  When the request source confirmation process (step S2-5) is completed, the management computer 31 transmits an approval request mail to the user (step S1-5). At this time, the management computer 31 may write in the approval request mail that the bank system 30 has completed the identity verification of the request source.

  Further, when the transfer account of the request source is an account of another bank, the bank system 30 that has received the request for identification is sent to the bank system 30 of the other bank with the transfer account of the request source. A request may be made to verify the identity of the requester.

  When the confirmation about the request source is performed in this way, the management computer 31 may transmit confirmation information of the request source to the user terminal 10. Thereby, the user can determine whether or not to approve the identity verification with reference to the result of the identity verification regarding the received requester. Further, the management computer 31 may perform identity verification based only on an identity confirmation request from a requester who has been confirmed. In this case, the user can safely transmit the personal identification number for confirming the identity with confidence that the request source of the approval request received from the management computer 31 has a certain credibility.

  In the above embodiment, the method for confirming the identity at the time of opening the account as the identity verification information in the deposit account information storage unit 32 is information relating to identity verification. The information related to identity verification is not limited to this, and information on a method for performing identity verification when using an account may be added. For example, the user's fingerprint data may be registered at the time of opening an account, and the fact that identity verification is performed using the fingerprint data may be transmitted to the company system 21 as information relating to identity verification.

Further, for example, it may be an identity confirmation level indicating how much the identity is confirmed with certainty. Specifically, when identity verification is performed based on an identifier and password used when a user uses a network service, the lowest level “level 1” identity verification level is recorded as information about the identity. The Further, when the identity verification is performed based on the electronic signature data issued for the user, the “level 2” identity verification level having a higher level is recorded. Further, when the identity verification is performed based on the voice print data of the user or the image data related to the face, the “level 3” identity verification level having a higher level is recorded. In addition, the user's fingerprint data, glow data, and vein data for specifying a single user is recorded with the highest level “identification level” of “level 4”. When each “level” is recorded as the personal information in the deposit account information storage unit 32, the management computer 31 provides the personal verification level information together with the notification of the personal verification to the requester of the personal verification. To do. Thereby, for example, when the company that owns the corporate system 21 is a credit credit sales company, the credit credit sales company can also determine whether or not to acquire additional user information based on the rank. .

  In the above embodiment, the bank system 30 that has completed the confirmation process based on the login from the user terminal 10 notifies the company system 21 of the completion of the identity confirmation. Instead, the bank system 30 may provide information about the user to the company system 21. For example, the company system 21 transmits information on the user included in the purchase application information together with the identity verification request. After the confirmation process is completed based on the login from the user terminal (step S1-7), the bank system 30 compares the information about the user received together with the identity confirmation request with the identity confirmation information of the deposit account information 320. Information regarding the user may be notified to the enterprise system 21 depending on whether or not they match. Further, the user identification information stored in the deposit account information storage unit 32 may be provided to the user.

  In the embodiment described above, the management computer 31 transmits an approval request mail so as to transmit the password information to the user terminal 10 having the mail address stored in the deposit account information storage unit 32. Not limited to this, the management computer 31 may transmit an approval request mail to the user terminal 10 having the mail address acquired by the company system 21 from the user terminal 10. In this case, the management computer 31 does not have to manage the mail address in the deposit account information storage unit 32.

  In the above embodiment, the user terminal 10 logs in to the bank system 30 by displaying the login screen 700 by selecting the character string 601 included in the email screen 600. Not limited to this, the user terminal 10 may log in for identity verification from the homepage of the bank system 30 or the like separately from the e-mail. In this case, it is possible to confirm the bank system 30 that has sent the e-mail screen 600 e-mail.

  In the above embodiment, a computer terminal owned by a user is used as the user terminal 10. The user terminal 10 is not limited to this. For example, an automated teller machine (ATM) may be used as the user terminal 10 as long as the user can input a personal identification number. In this case, the user receives an identity confirmation request transmitted from the management computer 31 by the user's fixed telephone or postcard. Then, when authenticating, the user may go to an automatic teller machine and input a personal identification number in order to permit identification. In this case, the management computer 31 may further function as a presentation unit and a specification unit, and the presentation step and the specification step may be further performed. Specifically, the user inputs his customer identifier into the automatic teller machine. The management computer 31 displays all the identity verification request identifiers associated with the input customer identifier on the automatic teller machine. And a user should just input a PIN after selecting the identification confirmation identifier of the received identification confirmation acceptance request.

  In the above embodiment, when a user and a company make a sales contract, the identity of the user is confirmed. However, the present invention is not limited to this, and for example, it may be used as a system for supporting individual sales by proving that each individual is an individual in an Internet auction.

1 is a system schematic diagram according to an embodiment of the present invention. Explanatory drawing of the data recorded on the deposit account information storage part. Explanatory drawing of the data recorded on the personal identification request information storage part. Explanatory drawing of the process sequence of the identity verification process in embodiment. Explanatory drawing of the purchase goods screen in embodiment. Explanatory drawing of the purchase payment screen in embodiment. Explanatory drawing of the email transmitted to the computer terminal in embodiment. Explanatory drawing of the login screen in embodiment. Explanatory drawing of the process sequence of the company confirmation process of the identity verification process in another example.

Explanation of symbols

  DESCRIPTION OF SYMBOLS I ... Internet as a network, 10 ... User terminal, 21 ... Corporate system as a request source terminal, 31 ... Management computer, 32 ... Deposit account information storage part as account information storage part.

Claims (14)

The terminal is connected to the user terminal and the requesting terminal for requesting the identity verification of the user through the network, and is connected to the account information storage unit that stores the password information associated with the user account information. A method for verifying the identity of a user using a management computer,
The management computer is
A request receiving stage for receiving a confirmation request including user information for identifying a user who is the object of identity verification from the requesting terminal;
An authentication request step of identifying a user account based on the received user information and transmitting an identification confirmation request for prompting the user to input personal identification information related to the identified user account;
In response to the request for confirmation of identity verification, the user information is verified by comparing the password information entered by the user into the user terminal for the user account and the password information recorded in the account information storage unit. And a confirmation information providing step of transmitting information according to the result to the request source terminal. The account information storage unit stores information related to the identity verification method in association with the user account information,
2. The identity verification method according to claim 1, wherein the confirmation information providing step transmits information on the identity verification method according to a result of the identity verification. The account information storage unit stores user terminal information of a user in association with the user account information,
The management computer further comprises a user terminal information acquisition step of acquiring the user terminal information of the user from the account information storage unit based on the user account information included in the confirmation request,
In the authentication request step, the management computer makes a request to the user terminal specified by the user terminal information acquired in the user terminal information acquisition step,
3. The confirmation information providing step of comparing the password information received from the user terminal that has transmitted the identity verification request with the password information recorded in the account information storage unit. The identity verification method described. The management computer further includes a granting step of granting a request identifier for specifying the confirmation request received from the request source terminal,
The authentication request step transmits data of the request identifier to the user terminal,
The said confirmation information provision step notifies the information according to a result to the request origin terminal specified based on the data of the said request identifier contained in the information received from the said user terminal. The identity verification method according to any one of 3 above. The management computer is
A presentation stage in which a plurality of request identifiers are presented to the user terminal in response to access from the user terminal;
5. The identity verification method according to claim 4, further comprising a specifying step of specifying a request identifier that matches the request identifier transmitted in the authentication request step from the plurality of request identifiers. The management computer further includes a request source confirmation step of performing identity verification for the request source that received the request in the request reception step,
6. The principal according to claim 1, wherein in the authentication request stage, the management computer transmits a result of identity confirmation of a request source in the request origin confirmation stage to the user terminal. Confirmation method. The management computer further includes a request source confirmation step of performing identity verification for the request source that received the request in the request reception step,
In the authentication request step, the management computer requests the user terminal of the user specified from the user account information included in the confirmation request from the request source that has been verified in the request source confirmation step. The identity verification method according to claim 1, wherein the identification method is performed. The terminal is connected to the user terminal and the requesting terminal for requesting the identity verification of the user through the network, and is connected to the account information storage unit that stores the password information associated with the user account information. An identity verification program for confirming the identity of a user using a management computer,
The management computer,
Request receiving means for receiving a confirmation request including user information for identifying a user who is a target of identity verification from the request source terminal;
Authentication request means for identifying a user account based on the received user information, and transmitting a request for confirmation of identity for prompting the user to input personal identification information related to the identified user account; and In response to the request for confirmation of identity verification, the user information is verified by comparing the password information entered by the user into the user terminal for the user account and the password information recorded in the account information storage unit. An identity verification program that functions as confirmation information providing means for transmitting information corresponding to the request to the requesting terminal. The account information storage unit stores information related to the identity verification method in association with the user account information,
9. The identity confirmation program according to claim 8, wherein the confirmation information providing means transmits information relating to the identity confirmation method as information corresponding to a result. The account information storage unit stores user terminal information of a user in association with the user account information,
Based on the user account information included in the confirmation request, the management computer further functions as user terminal information acquisition means for acquiring the user terminal information of the user from the account information storage unit,
The authentication request unit is configured such that the management computer makes a request to the user terminal specified by the user terminal information acquired by the user terminal information acquisition unit,
10. The confirmation information providing means collates the personal identification information received from the user terminal that transmitted the personal identification approval request with the personal identification information recorded in the account information storage unit. The identity verification program described. The management computer further includes grant means for assigning a request identifier for identifying the confirmation request received from the request source terminal,
The authentication request means transmits data of the request identifier to the user terminal,
The said confirmation information provision means notifies the information according to a result to the request origin terminal specified based on the data of the said request identifier contained in the information received from the said user terminal. The identity verification program according to any one of 10 above. The management computer,
Presenting means for presenting a plurality of request identifiers to the user terminal in response to access from the user terminal, and specifying a request identifier that matches the request identifier transmitted in the authentication requesting means from the plurality of request identifiers The personal identification program according to claim 11, further functioning as a specifying unit. Making the management computer further function as request source confirmation means for verifying the identity of the request source that received the request in the request reception means;
The principal according to any one of claims 8 to 12, wherein the authentication requesting means transmits the management computer's identity confirmation result of the requesting source by the requesting source confirming means to the user terminal. Confirmation program. Making the management computer further function as request source confirmation means for verifying the identity of the request source that received the request in the request reception means;
The authentication request unit is configured so that the management computer requests a user terminal of a user specified from user account information included in a confirmation request from a requester who has completed identity verification in the requester confirmation unit. The identity verification program according to any one of claims 8 to 12, wherein the identification program is executed.

Images