JP7461241B2 - Customer information management server and customer information management method - Google Patents

Description

The present invention relates to a customer information management server and a customer information management method for standardizing at least part of the procedures for registering and updating customer information with two or more businesses.

A variety of services are provided on the Internet, such as Internet banking, Internet securities, credit card details, and Internet shopping.Customers who use these services must contact the business providing each service. , must register customer information such as their name and address. In principle, such customer information is stored and managed in the database of the business providing each service.

In this way, when customer information is managed by each business providing each service, customers who use many services must register their customer information with each business, which makes the process extremely cumbersome. In particular, when a customer's address changes due to moving, the customer must notify each business of the change in registered address. In order to reduce the burden on customers in such cases, inventions have been disclosed that relate to computer systems that collectively accept notifications of changes in customer information registered with multiple businesses and provide the accepted information to each business (see, for example, Patent Documents 1-3).

JP 2002-215844 A Japanese Patent Application Publication No. 2002-366872 Japanese Patent Application Publication No. 2004-13428

In the invention shown as prior art, customers use a service that registers and updates information with each business operator on their behalf, but the problem with using such a service is that it is not possible to use the service that the customer originally wants to use. Apart from this, new services will have to be used to notify changes of address, etc. Although it does not itself provide a unique service, it is very important for customers to download an application to a smartphone, learn how to use it, and register to use a new service. It is expected that you will find it troublesome.

In addition to consideration of protecting personal information in recent years, services provided by financial institutions in particular are now being required to conduct more stringent customer identity verification than ever before under the Act on Prevention of Transfer of Criminal Proceeds as a measure against money laundering, etc. Therefore, it is preferable that services that act as agents for the registration and updating of customer information not only take sufficient measures to protect personal information, but also guarantee the reliability of customer identity verification and are easy for financial institutions and other institutions to participate in.

Furthermore, during the recent coronavirus pandemic, it has become clear that it is necessary to develop remittance methods that can quickly transfer benefits, etc. to citizens. The link between the two is now being debated. In the future, if customers are required to register their My Number with each bank they do business with, registering their My Number with the bank will allow for both customer convenience and high security. It is thought that there will be a need for services to do so.

The present invention has been made to address these issues, and aims to provide a customer information management server and a customer information management method that are easy to use, are based on a system that ensures the reliability of customer identity verification, and standardize at least part of the procedures for registering and updating customer information with two or more businesses.

The present invention, which solves such problems, is a customer information management server connected to computer systems of two or more businesses via a network in order to standardize at least a part of the procedures related to the registration or update of customer information, and is characterized by comprising: an address generating means for generating a unique address on a network to be assigned to a page accessed by a customer who wishes to register or update his/her own customer information; an address transmitting means for transmitting the address generated by the address generating means to a server of a mobile phone business to which a mobile terminal operated by the customer is connected by an application program authenticated by the caller's telephone number; and a customer information processing means for, when receiving a request to register or update customer information from the mobile terminal that has accessed the address, checking the predetermined requirements for registering or updating customer information, and, if it is confirmed that the requirements are met, registering or updating the customer information of the customer corresponding to the address stored in a customer information storage means that stores the customer information, based on the registration or update request. The address generating means generates an address on a network to be assigned to a page accessed by the customer to register or update his/her own customer information, and the customer information processing means can also be characterized by receiving a request to register or update customer information transmitted by specifying the address.

In this way, in the present invention, a predetermined address such as a page that accepts requests to register or update customer information is sent to a customer terminal via a mobile phone carrier's server, and a page with a link to that address is received and displayed on the customer's mobile terminal by an application program such as a message app (preferably an interactive messenger) that is authenticated by the caller's telephone number. This allows customers to request registration or updates of customer information for two or more carriers using a message app or the like provided by the mobile phone carrier as an interface, making it possible for the customer to carry out the procedure from a message app or the like on their mobile phone that they use on a daily basis, improving operability. Furthermore, the request to register or update customer information is accepted from a mobile terminal authenticated by the mobile phone carrier via a flow that goes through the server of the mobile phone carrier, which performs customer identity verification based on the so-called Mobile Phone Fraud Prevention Act, so that the reliability of identity verification is also guaranteed.

In addition, by assigning a unique URL or other address to the page that accepts requests to register or update customer information or the page where a session to accept such requests is started, and configuring the system to identify target customers by the URL or other address specified in the request to register or update customer information or the URL or other address of the page where a session to accept such requests is started, it is possible to efficiently identify customers who are registering or updating customer information even in a flow that goes through the mobile phone operator's server.

The customer information management server according to the present invention includes an address information storage means for receiving the telephone number of the one customer or an identification key associated with the telephone number from the server of the mobile phone carrier, and storing the telephone number or the identification key in association with the address generated by the address generation means, and the customer information processing means can be characterized in that it identifies the customer corresponding to the address by the telephone number or the identification key stored in the address information storage means in association with the address accessed by the mobile terminal.

With this configuration, the customer information management server can also identify the customer using the customer's phone number or an identification key such as a customer ID associated with the phone number. Even without using a key, a customer can be identified by the telephone number of a mobile phone or the like that they use on a daily basis, and it becomes possible to use services provided by the customer information management server.

In the customer information management server according to the present invention, the customer information stored in the customer information storage means includes a customer's phone number or an identification key associated with the phone number, and an image file of the customer's face photo. and the customer information processing means receives an image file of a face photo of the customer together with the registration or update request, and includes an image file of a face photo that is determined to be the same person as the face photo of the received image file. When customer information is stored in the customer information storage means, the customer's phone number included in the customer information or the identification key associated with the phone number is stored in the customer's phone number received from the server of the mobile phone carrier. The predetermined requirements may include matching a telephone number or an identification key associated with the telephone number.

In the customer information management server according to the present invention, the customer information stored in the customer information storage means includes a customer's phone number or an identification key associated with the phone number, and an image file of the customer's face photo. and the customer information processing means receives an image file of the customer's facial photograph together with the registration or update request, and associates the customer's telephone number with the customer's telephone number received from the server of the mobile phone carrier or with the telephone number. If customer information including a customer telephone number that matches an identification key or an identification key associated with the telephone number is stored in the customer information storage means, the face photograph of the received image file is included in the customer information. The predetermined requirements may include that the person is determined to be the same person as the face photograph in the image file.

In this way, the combination of the customer's telephone number or the identification key associated with the telephone number and the face photograph of the image file, which is included in the customer information stored in the customer information storage means, is the customer's face photograph received by the customer information management server. If it is checked whether the phone number or the identification key associated with the phone number matches the combination of the face photo in the image file, this configuration is suitable for preventing "spoofing" using another person's personal information or face photo. becomes.

In the customer information management server according to the present invention, the customer information processing means includes an image file of the customer's own facial photo (first facial photo) taken by the customer in conjunction with the registration or update request, and an image file of the customer's own facial photo (first facial photo). receiving an image file of an identification document containing a second facial photograph), and the predetermined requirements include that the first facial photograph and the second facial photograph are determined to be the same person. You can also.

In this way, if identity verification using facial photographs is performed at the stage of standardized procedures on the customer information management server, it will be possible to create a structure that will easily reduce the procedural burden of identity verification required for each business operator. Become. Note that the customer's own facial photo (first facial photo) received by the customer information processing means may be an image taken by the customer on the spot with a smartphone camera, or an image that has been taken in advance and can be used with a smartphone. It may also be an image stored in .

The customer information management server according to the present invention can also be characterized in that a link with an address generated by the address generating means embedded therein is set on the operation screen of the application program for requesting registration or updating of customer information, which is sent from the server of the mobile phone carrier to the mobile terminal, and when the link is selected on the operation screen displayed on the mobile terminal, the customer information processing means receives a request to register or update customer information with the specified address.

When configured in this way, the operation screen of the mobile device used to request the registration or update of customer information, which is sent via the mobile phone operator's server, will have a link to an address that can identify the customer, allowing the customer to request the registration or update of customer information through seamless operations from a mobile phone messaging app, etc.

The customer information management server according to the present invention may also be characterized in that, in the customer information processing means, when a request to register or update customer information received from the mobile terminal is a request to register a customer's My Number, the customer information processing means includes a My Number transmission means for transmitting the customer's My Number to a computer system of one or more business operators with whom the customer has business, when the customer's My Number is registered in the customer information storage means. The customer information management server may also be characterized in that the customer information processing means includes a My Number deletion means for deleting the customer's My Number registered in the customer information storage means at a predetermined timing after the My Number transmission means transmits the My Number to the computer system of the one or more business operators.

With this configuration, when a customer needs to register their My Number for each bank they do business with, the process will go through the mobile phone carrier's server, which ensures the reliability of identity verification. By accepting My Number registration from mobile terminals authenticated by telephone carriers, we ensure a high level of security, and the interface uses mobile phone messaging apps that customers use on a daily basis. It also increases convenience for customers by allowing them to register their My Number with multiple banks in one procedure.

The present invention can also be specified as a customer information management method executed by the customer information management server according to the present invention.

The customer information management method according to the present invention uses a customer information management server connected to the computer systems of two or more business operators via a network, in order to standardize at least a part of the procedures related to registering or updating customer information. A customer information management method carried out, wherein the customer information management server generates a unique network address to be assigned to a page accessed by one customer to register or update his or her own customer information. a generation step, the customer information management server transmits the address to a server of a mobile phone carrier to which the mobile terminal operated by the customer connects using a predetermined application program authenticated by the caller's phone number; an address sending step of sending the address generated in the generating step; and when the customer information management server receives a customer information registration or update request sent specifying the address, a step for registering or updating the customer information; When the predetermined requirements are confirmed and it is confirmed that the requirements are met, the customer information of the customer corresponding to the address stored in the customer information storage means for storing customer information is transferred based on the registration or update request. A customer information management method is characterized by comprising the steps of: registering or updating customer information.

The present invention can also be specified as a customer information management method executed by the customer information management server of the present invention having each of the configurations described above.

According to the present invention, when a server is provided that shares procedures for registering and updating customer information with two or more businesses, customers can request registration or updates using a mobile phone messaging app or the like without registering for a specific service, which provides excellent operability for customers. In addition, by accepting registration and updates of customer information via the server of a mobile phone business operator that requires strict identity verification, a system is provided that ensures the reliability of customer identity verification. This system reduces the effort required for customers to notify a change of address when moving or to register their My Number with a bank, and also makes business processing at the business operator that manages customer information more efficient.

FIG. 1 is a diagram showing an overview of an embodiment of a customer information management server according to the present invention. 2 is a block diagram showing a configuration of a customer information management server according to the present invention; FIG. FIG. 2 is a diagram showing an overview of data flow between a customer terminal, a mobile carrier server, and a customer information management server in the present invention. 2 is a first flowchart showing a process flow of registering or updating customer information by the customer information management server according to the present invention. FIG. 7 is a second flowchart showing a process flow of registering or updating customer information by the customer information management server according to the present invention. FIG. FIG. 2 is a first diagram showing an example of the flow of newly registering information regarding a deposit account used by a customer in the customer information management server according to the present invention. FIG. 2 is a second diagram showing an example of the flow of newly registering information about a deposit account used by a customer in the customer information management server according to the present invention. FIG. 2 is a first diagram illustrating an example of the flow of additionally registering information regarding a deposit account used by a customer in the customer information management server according to the present invention. FIG. 2 is a second diagram showing an example of the flow of additionally registering information about a deposit account used by a customer in the customer information management server according to the present invention. FIG. 11 is a first diagram showing an example of a flow for updating a customer's address registered in a customer information management server according to the present invention. FIG. 11 is a second diagram showing an example of the flow of updating a customer's address registered in the customer information management server according to the present invention. FIG. 1 is a first diagram showing an example of the flow of registering an account transfer in a customer information management server according to the present invention. FIG. 2 is a second diagram showing an example of the flow of registering an account transfer in the customer information management server according to the present invention. FIG. 1 is a first diagram showing an example of the flow of registering a My Number at a bank using the customer information management server according to the present invention. FIG. 2 is a second diagram showing an example of the flow of registering My Number at a bank using the customer information management server according to the present invention.

The following describes in detail the form for implementing the present invention with reference to the drawings. Note that the following description shows an example of an embodiment of the present invention, and the present invention is not limited to the embodiment shown below. In the following embodiment, a financial institution such as a bank is used as an example of a user institution that uses customer information with standardized registration and update procedures, but the user institution in the present invention is not limited to financial institutions and can include various business operators that manage customer information.

FIG. 1 shows an overview of an embodiment of a customer information management server according to the present invention. In Figure 1, it is possible to access via the Internet from a customer terminal such as a smartphone, and it is possible to access banking systems (A Bank System and B Bank System), securities company system (C Securities System), and life insurance company system (D Life Insurance Company System). A customer information management server connected via a network to a computer system of a user institution, such as a customer information management system, corresponds to the customer information management server according to the present invention.

A customer of a user institution such as a bank or securities company uses an application program such as a message application (preferably an interactive messenger) provided by a mobile carrier (mobile phone operator) on a customer terminal such as a smartphone to contact the mobile carrier server. When connected, a predetermined page such as a chat room of the application program includes menus and links to be selected when requesting registration or updating of customer information with standardized procedures. When the customer selects these menus, etc., the customer is connected to the customer information management server according to the present invention, and when the customer sends data such as identification documents and account information necessary for registration and update, the customer information management server connects to the integrated ATM network. Inquiries are made, and predetermined verification processes such as identity verification and account verification are performed.

When these confirmation processes are completed, the customer information managed on the customer information management server and shared by multiple user institutions will be registered or updated, and the necessary information will be sent to the relevant user institutions with the consent of the user. Information is sent. When the update or registration process is completed after receiving approval from the user institution, the customer terminal is notified that the update or registration process has been completed.

As described above, in the present invention, registration and updating of customer information is requested from the customer terminal via the mobile carrier server using an application program such as a message application provided by the mobile carrier. By using the application program provided by the mobile carrier that customers use on a daily basis as an interface, we can improve the usability of customers when registering and updating customer information, and also make it possible to sign contracts on the condition of strict identity verification. By accepting requests for registration and update of customer information after being authenticated by the mobile carrier with which the service has been signed, the system ensures the reliability of customer identity verification.

Figure 2 is a diagram showing an example of the configuration of a customer information management server according to the present invention as a functional block. In Figure 2, the customer information management server 10 connected to a customer terminal 20, a mobile carrier server 30, a user institution system 50, etc. via a network corresponds to the customer information management server according to the present invention.

The customer information management server 10 is a computer equipped with a CPU, main memory, auxiliary storage devices such as a HDD, and a function for connecting to networks including the Internet. Programs stored in the auxiliary storage device are read into the main memory, and the CPU executes calculations to realize the specified functions.

The physical configuration of the computer that constitutes the customer information management server 10 is not particularly limited, and functions other than the customer information management function of the present invention may be provided in the same computer. Furthermore, each function required for the present invention may be realized physically by a single computer, or may be realized using multiple computers.

The one-time URL generation unit 11, customer information processing unit 13, identity verification unit 14, account verification unit 15, customer information provision unit 17, and notification transmission unit 18 of the customer information management server 10 are all functionally specified. A program corresponding to the function of each part stored in an auxiliary storage device such as an HDD is read into the main memory, and the function corresponding to each part is realized by executing arithmetic processing by the CPU.

The one-time URL memory unit 12 and customer information storage unit 16 of the customer information management server 10 are assigned predetermined memory areas of an auxiliary storage device such as a HDD. These memory areas do not have to be physically located on one computer, but may be located on multiple computers such as computers that make up a database server.

The customer terminal 20 is a mobile terminal such as a smartphone to which a telephone number is assigned, but it is possible to use a predetermined application program such as a message application that is authenticated by the caller's telephone number provided by the mobile carrier. However, the configuration is not particularly limited as long as it is a network terminal that can access the customer information management server 10 via the Internet and send and receive information.

The configuration of the mobile carrier information server 30 is not particularly limited as long as it is a computer capable of sending and receiving information via a network such as the Internet, but it is necessary for it to have a function of authenticating the telephone number of the sender of a specified application program such as a message app used in the customer terminal 20 and communicating with the customer terminal 20. A specified memory area of an auxiliary storage device such as a HDD of the computer corresponding to the mobile carrier information server 30 is assigned to the contract holder information storage unit 31.

The integrated ATM network 40 is a network that interconnects ATMs between banks, and by querying this network, the existence and validity of a deposit account can be confirmed. For example, a host computer that manages the deposit accounts operated by the bank can be used as the user institution system 50-52, but the transmission and reception of information with the customer information management server 10 may be performed via a network terminal such as a PC that can communicate with the core computer system, or a web server, rather than directly communicating with such a core computer system.

Based on the above configuration, the method of managing customer information by the customer information management server 10 in the present invention will be explained using Figures 3 to 5.

Figure 3 shows an overview of the data flow between the customer terminal 20, mobile carrier server 30, and customer information management server 10 when customer information is registered or updated according to the present invention. The flowcharts in Figures 4-5 show the processing flow of the customer information management server 10 during this period, and the flow of the customer information registration or update process according to the present invention will be explained along these lines.

A customer who wishes to use the services provided by the customer information management server 10 to collectively register and update customer information (such as the customer's personal information) requested by multiple business operators with which they do business (here, Bank A, Bank B, Securities C, D Life Insurance, etc.) first becomes a subscriber and uses a customer terminal 20 such as a smartphone to which a telephone number has been assigned, as shown in Figure 3, to launch a messaging app provided by the mobile carrier.

This message application is an application program provided by a mobile carrier that is authenticated by the caller's telephone number, and is installed on the customer terminal 20. When you perform an operation to start a message application on the customer terminal 20, a request to start the application program is sent to the mobile carrier server 30, and the mobile carrier server 30 retrieves the caller's phone number (from the SIM card inserted in the customer terminal 20). The read phone number) is compared with valid phone numbers stored in the subscriber information storage unit 31, which is a database of mobile phone subscribers, to authenticate the phone number. If it is confirmed that the activation request is valid from the subscriber, activation of the message application on the customer terminal 20 is permitted.

On the operation screen of the message application of the customer terminal 20, as illustrated in FIG. Is displayed. When one of the services provided by the customer information management server 10 such as "account information registration" or "address change" is selected from these menus, the mobile carrier server 30 selects the previously authenticated customer terminal. In addition to the telephone number 20, the customer information management server 10 is notified that a menu such as "account information registration" or "address change" has been selected.

At this point, the mobile carrier server 30 hands over the customer information management server 10 the customer's phone number that can identify the customer operating the customer terminal 20, but the key information for identifying the customer is the phone number. However, the present invention is not limited to this, and an identification key such as a customer ID uniquely associated with a telephone number may be used. Considering security, it may be preferable to use an identification key such as a customer ID that is uniquely associated with the telephone number, rather than using the telephone number itself.

Subsequently, as shown in the flowchart of FIG. 4, the customer information management server 10 receives the customer's phone number (or an identification key such as a customer ID uniquely associated with the phone number) from the mobile carrier server 30. , "Register account information", "Change address", etc., is received on the customer terminal 20 (S01), the one-time URL generation unit 11 is activated, and the customer registers his or her own customer information. A one-time URL, which is a unique network address, is generated (S02) to be assigned to the page to be accessed when updating.

The one-time URL generated by the one-time URL generation unit 11 is linked to the customer's telephone number (or an identification key such as a customer ID uniquely associated with the telephone number) received from the mobile carrier server 30 and temporarily stored in the one-time URL storage unit 12 (S03), and the generated one-time URL is then transmitted to the mobile carrier server 30.

In the mobile carrier server 30 that has received the one-time URL from the customer information management server 10, as shown in FIG. 3, a button that is pressed to request registration or updating of customer information is provided in the file of the operation screen to be displayed in the message application running on the customer terminal 20, and the one-time URL received from the customer information management server 10 is embedded in the button to set a link. The file of the operation screen with such a button is sent from the mobile carrier server 30 to the customer terminal 20, and a button for requesting registration or updating of customer information with a link to the one-time URL is displayed on the screen of the customer terminal 20. Note that the method of setting a link to the one-time URL in the operation screen to be displayed in the message application is not limited to the method of displaying a button on the screen and having the customer press it, and a display format other than a button, such as setting a hyperlink in text, may also be used.

When a customer wants to register or update his or her own customer information that is shared by multiple user institutions in the customer information management server 10, data such as identification documents required for identity verification etc. (" Enter the customer's own information to be registered or updated ("registration/update data" in Figure 3) and press the button displayed on the operation screen to request registration or update of customer information. do.

When a button displayed on the operation screen is pressed, a request to register or update customer information, including identity verification data and registration/update data, is sent from the customer terminal 20 to the customer information management server 10. Since this button has a link to a one-time URL, a request with the one-time URL specified in the address is sent to the customer information management server 10.

In the customer information management server 10 that receives this request, the customer information processing unit 13 is started and the process shown in the flowchart of Figure 5 is executed. When a request to register or update customer information with a one-time URL specified in the address, along with identity verification data and registration/update data is received (S11), the information temporarily stored in the one-time URL storage unit 12 is checked to identify the customer's telephone number (or an identification key such as a customer ID uniquely associated with the telephone number) stored in association with the one-time URL specified in the request (S12).

Furthermore, based on the identity verification data received from the customer terminal 20, the identity verification unit 14 performs identity verification (S13) and checks whether the customer has been spoofed (S14), which will be described later using the example of Figure 6-13, and if necessary, the account verification unit 15 checks the existence and validity of the deposit account (S15).If these checks confirm that the specified requirements are met (Yes in all S13-15), the customer information stored in the customer information storage unit 16 for the customer identified by the telephone number specified in S12 (or an identification key such as a customer ID uniquely associated with the telephone number) is updated based on the registration/update data included in the customer information registration or update request received from the customer terminal 20 (S16).

At the same time, the customer information providing unit 17 is started, and transmits the registered or updated customer information together with other necessary information such as an image file of the identity verification document to the user institution systems 50-52 of user institutions such as financial institutions that have conducted transactions with the customer whose customer information has been registered or updated and require the registered or updated customer information (S17). After that, the system waits for approval from the destination user institution, and once it is confirmed that approval has been obtained, the notification transmitting unit 18 is started, and a notification that the customer information has been registered or updated is transmitted to the customer terminal 20.

If it is determined that any of the requirements are not met in the customer identity verification (S13) by the identity verification unit 14 or in the verification of whether or not the customer is being impersonated (S14), or in the verification of the existence and validity of the deposit account by the account verification unit 15 (S15) (No in any of S13-15), the customer information registration or update process is not accepted and an error process is performed (S18).

FIG. 6-13 shows a specific example of how to register or update customer information using the customer information management server according to the present invention. The flow will be explained in detail.

Figure 6-7 shows an example of the flow for registering new information about a deposit account used by a customer, Figure 8-9 shows an example of the flow for registering additional information about a deposit account used by a customer, Figure 10-11 shows an example of the flow for updating a customer's address, and Figure 12-13 shows an example of the flow for registering an account transfer. All of these examples are specific examples of the process shown in the flowchart of Figure 5, in which a one-time URL is generated in the process shown in the flowchart of Figure 4, and then the generated one-time URL receives a request to register or update customer information specified in the address, and registers or updates the customer information.

FIG. 6-7 shows a case where a customer wants to standardize procedures such as notifying a change of address to a bank with which the customer has transactions (Bank A in this case) using the service provided by the customer information management server 10. This figure shows the flow of registering information regarding an account as customer information, and corresponds to a case where a customer who has not previously registered information regarding a deposit account is newly registering information regarding the deposit account.

As shown in FIG. 6, a customer who wishes to newly register information regarding a bank's deposit account in the customer information management server 10 can take a photo of himself or herself on a predetermined deposit account registration page displayed on a message app on the customer terminal 20. An image file of a self-portrait of your face photo, an image file of a driver's license with your face photo displayed, and an image file of a cash card of the deposit account you want to register (in this case, Bank A's deposit account). Specify image files and press the button provided on the deposit account registration page to send these image files. Since this button has a link to a one-time URL, a request to newly register information regarding a deposit account containing these image files, with the one-time URL specified as the address, is sent to the customer information management server 10. be done.

The customer information processing unit 13 of the customer information management server 10 that received the request retrieves the customer's telephone number (or a phone number and As shown in Figure 6, the received selfie image, driver's license image, and cash card image can be It is specified that the customer is identified by an identification key such as a customer ID uniquely associated with the number.

Next, as shown in FIG. 7, the face photo in the selfie image and the face photo included in the driver's license image are determined by image recognition processing to be of the same person, and the identity verification unit 14 performs identity verification of the customer. In addition, these face photos are compared with the face photos included in each customer information stored in the customer information storage unit 16 to determine whether the request is made by impersonating the customer. Specifically, if a face photo determined to be of the same person is registered, it is determined whether the customer whose face photo is included in the customer information is the same person as the customer who sent the request, that is, whether their telephone numbers (or an identification key such as a customer ID uniquely associated with the telephone number) match, or conversely, if customer information of a customer whose telephone number (or an identification key such as a customer ID uniquely associated with the telephone number) matches is stored in the customer information storage unit 16, it is determined whether the received face photo matches the face photo included in the registered customer information to determine whether the request is the result of impersonation.

Regarding the deposit account, the account confirmation unit 15 transmits information identifying the deposit account, such as the financial institution code, branch code, account type, and account number, read by image recognition processing of the cash card image to the integrated ATM network 40. to inquire whether the applicable deposit account exists as a valid deposit account.

As described above, once it has been confirmed that there are no problems with the customer's identity, including confirmation that it does not fall under the category of identity theft, and the existence and validity of the deposit account, the phone number (or phone number and unique Information such as the account number regarding the deposit account is newly registered in the customer information stored in the customer information storage unit 16 of the customer identified by the associated identification key (such as the customer ID), and the information such as the account number regarding the deposit account is newly registered. It becomes possible to link the customer information stored in the customer information storage unit 16 with the customer information of the bank where the deposit account is registered (Bank A in this case); Here, the approval waiting status of Bank A) is recorded in the customer information.

In addition, the image file of the driver's license used for identity verification and the image file of the customer's face photo (either the face photo of the self-portrait image or the face photo displayed on the driver's license may be used, or both may be used. ), the image of the cash card used for account confirmation may also be stored in the customer information storage unit 16 in association with the customer's phone number (or an identification key such as a customer ID uniquely associated with the phone number). .

When new information such as the account number for a deposit account is registered in the customer information stored in the customer information storage unit 16, the customer information providing unit 17 transmits the image files of the driver's license and cash card received from the customer terminal 20, the customer's name and address stored as customer information in the customer information storage unit 16, the account number of the deposit account read from the image file of the cash card, and other information to the institution system (here, Bank A's bank system) 50 of the bank where the deposit account is registered (here, Bank A).

The bank (here, Bank A), which is the user institution, receives this information and performs prescribed procedures such as identity verification in accordance with the bank's rules. When the registration of the deposit account, i.e., linkage with the customer information management server 10, is approved, the customer information management server 10 is notified of this, and the status of the customer information stored in the customer information storage unit 16, which was recorded as waiting for approval, is updated to approved. When the linkage between the customer information stored in the customer information storage unit 16 of the customer information management server 10 and the customer information of the bank where the deposit account is registered (here, Bank A), is thus realized, the notification sending unit 18 notifies the customer terminal 20 of this.

In the above example shown in Figures 6-7, an image of a driver's license is sent as the identity document, but the document used for identity verification may be any other document or medium as long as it displays the customer's face photo. For example, a My Number card or a passport may be used. If a My Number card is used for identity verification and it is necessary to link the My Number to a deposit account and manage it at the bank where the customer is registered (here, Bank A), the My Number identified from the My Number card (the My Number card is used only for face photo matching, and the My Number linked to the deposit account may be the My Number entered separately by the customer, or the My Number read from a notification card or a resident's card with the My Number written thereon that is sent separately by the customer) may be stored as part of the customer information in the customer information storage unit 16, and the My Number may be sent to the institution system (here, Bank A's bank system) 50. The flow of registering the My Number to be managed by linking it to a deposit account will be described in detail later using Figures 14-15.

In addition, an image of the cash card is sent to identify the account number of the deposit account, etc. However, instead of sending such an image and identifying the deposit account through image recognition processing, the customer may input and send information required to identify the deposit account, such as the financial institution code and account number, into the customer terminal 20, and the deposit account may be identified from this information.

In addition, information such as the customer's name and address stored in the IC chip of the My Number card or driver's license may be read by the customer terminal 20 and transmitted to the customer information management server 10, and the results of comparing this information with the customer information stored in the customer information storage unit 16 may be used to verify the customer's identity, but the specific methods of such identity verification and account verification are not particularly limited in the present invention.

FIGS. 8-9 further shows that when a customer wants to standardize procedures such as notification of change of address with another bank (in this case, Bank B) with which the customer has transactions, through the service provided by the customer information management server 10, the customer This flowchart shows the flow of registering information regarding a bank's deposit account as customer information, and corresponds to a case where a customer who has previously registered information regarding another deposit account additionally registers information regarding the deposit account. As explained using Figure 6-7, when registering information regarding a new deposit account, identity verification is performed using a driver's license, etc., so here we will additionally register information regarding the deposit account. When doing so, we will explain on the premise that we will not ask you to send the information necessary for identity verification, but we will request you to send us the information necessary for identity verification, such as an image of your driver's license, and we will request new information regarding your deposit account. Identity verification similar to that used when registering may be a requirement for registration.

In this case, the customer also sends the specified information to the customer information management server 10 from a specified deposit account registration page displayed on the customer terminal 20 by a message app. However, as shown in FIG. 8, the page for registering an additional deposit account does not require the customer to send a selfie or driver's license image. Instead, the customer specifies an image file of an image of the cash card of the deposit account they wish to register (here, a deposit account at Bank B), and presses a button on the deposit account registration page to send the image file. This button has a link to a one-time URL, so a request to register additional information about the deposit account, including an image file of the cash card, with the one-time URL specified as the address, is sent to the customer information management server 10.

The customer information processing unit 13 of the customer information management server 10 that received the request retrieves the customer's telephone number (or a phone number and As shown in FIG. 8, the image of the received cash card can be identified by the telephone number (or the customer ID, etc. uniquely associated with the telephone number). identification key).

Next, as shown in FIG. 9, the account confirmation unit 15 integrates the information identifying the deposit account, such as the financial institution code, branch code, account type, and account number, read by image recognition processing of the cash card image. The information is sent to the ATM network 40 to inquire whether the corresponding deposit account exists as a valid deposit account.

When the existence and validity of the deposit account is confirmed, the customer information stored in the customer information storage unit 16 of the customer identified by the phone number (or an identification key such as a customer ID uniquely associated with the phone number) Information such as the account number regarding the deposit account is additionally registered, and the customer information stored in the customer information storage unit 16 of the customer information management server 10 and the customer of the bank (here, Bank B) where the deposit account is registered are registered. Information can be linked, but at this point, the status of waiting for approval from the bank where the deposit account is registered (Bank B in this case) is recorded in the customer information.

When information such as the account number of the deposit account is added to the customer information stored in the customer information storage unit 16, the customer information providing unit 17 transmits the image file of the cash card received from the customer terminal 20, the customer's name and address stored as customer information in the customer information storage unit 16, the account number of the deposit account read from the image file of the cash card, and other information to the institution system (here, the bank system of Bank B) 51 of the bank where the deposit account is registered (here, Bank B). In order to verify the identity of the customer at the bank where the deposit account is registered (here, Bank B), it may also be possible to transmit an image file of the customer's face photo and an image file of an identification document such as a driver's license stored in the customer information storage unit 16 in association with the customer's telephone number (or an identification key such as a customer ID uniquely associated with the telephone number).

The bank that is the user institution that receives this information (here, Bank B) performs prescribed procedures such as identity verification in accordance with the bank's rules, and registers the deposit account, that is, the customer information management server 10. When the collaboration is approved, the customer information management server 10 is notified of this, and the status recorded in the customer information stored in the customer information storage section 16 as Waiting for Approval is updated to Approved. In this way, when the customer information stored in the customer information storage section 16 of the customer information management server 10 is linked with the customer information of the bank where the deposit account is registered (here, Bank B), the notification sending section 18 notifies the customer terminal 20 of this fact.

FIG. 10-11 shows a state in which the customer information stored in the customer information storage unit 16 of the customer information management server 10 and the customer information of multiple user institutions (here, Bank A and Bank B) have been linked. This figure shows the flow of updating some customer information after reporting a change of address due to relocation.

As shown in FIG. 10, a customer who wishes to report an address change and update customer information in the customer information management server 10 takes a photo of himself or herself on a predetermined address change notification page displayed on a message app on the customer terminal 20. An image file of a self-portrait of the customer's face, a driver's license with the customer's face photo displayed (My number card or passport with the customer's face photo displayed, etc.) can also be used to newly enter information about the bank account. ), specify the image file of the image taken, enter your new address after moving, and press the button on the address change notification page to save these image files. Submit information. This button has a link to a one-time URL, so a request to update part of the customer information by notifying a change of address and updating part of the customer information, including these image files, specifying the one-time URL as the address will be sent to the customer information. It is sent to the management server 10.

The customer information processing unit 13 of the customer information management server 10 that received the request retrieves the customer's telephone number (or a phone number and As shown in Figure 10, the received selfie image, driver's license image, and information related to the new address can be It is specified that the customer is identified by an identification key such as a customer ID uniquely associated with the number.

Next, as shown in Figure 11, identity verification is performed by using image recognition processing to determine whether the face photo in the self-portrait image and the face photo included in the driver's license image are the same person's face photo. The customer's identity verification is performed by the unit 14. Furthermore, these facial photograph images are compared with the facial photograph images included in each customer information stored in the customer information storage unit 16 to determine whether the request is an impersonation of the principal. Specifically, if a face photo that is considered to be the same person is registered, whether the customer whose face photo is included in the customer information is the same person as the customer who sent the request, or whether the phone number (or phone number and Customer information is stored for customers whose telephone numbers (or identification keys such as customer IDs, etc. uniquely associated with telephone numbers) match, or conversely, whose telephone numbers (or identification keys such as customer IDs, etc. uniquely associated with telephone numbers) match. If the received face picture is stored in the customer information section 16, it is determined whether the received face picture is a result of impersonation based on whether the face picture included in the registered customer information matches.

In addition, the new address after the move can be read from the image file of the driver's license using image recognition processing, and it can be confirmed whether it matches the new address entered by the customer into the customer terminal 20 and received by the customer information processing unit 13.

As described above, once it is confirmed that there are no problems with the customer's identity verification, including confirmation that it does not fall under the category of spoofing, and the accuracy of the new address entered by the customer, Among the customer information stored in the customer information storage unit 16 of the customer identified by the identification key (such as customer ID associated with the customer ID), the customer's address is updated to the new address after moving. The status of waiting for approval from the user institutions (Bank A and Bank B in this case) that are the cooperation destinations of is recorded in the customer information.

When part of the customer information stored in the customer information storage unit 16, in this case the customer's address, is updated, the customer information providing unit 17 transmits information such as the image file of the driver's license received from the customer terminal 20, the updated customer address stored as customer information in the customer information storage unit 16, and the deposit account number used by the bank to identify the customer, to the bank or other institution where the deposit account is registered, i.e., the user institution system (here, the bank systems of Bank A and Bank B) 50 of each user institution (here, Bank A and Bank B) with which the customer information is linked.

The banks, etc. (here, Bank A and Bank B), which are the user institutions that receive this information, carry out prescribed procedures such as identity verification in accordance with the rules of the banks, etc., and when the address change notification from the customer is approved, this is notified to the customer information management server 10, and the status recorded in the customer information stored in the customer information storage unit 16 as waiting for approval is updated to approved. When the customer's address, which is part of the customer information stored in the customer information storage unit 16 of the customer information management server 10, is updated in this way, the notification sending unit 18 notifies the customer terminal 20 of this.

FIG. 12-13 shows a state in which the customer information stored in the customer information storage unit 16 of the customer information management server 10 and the customer information of multiple user institutions (in this case, Bank A and D Life) have been linked. This shows the flow of registering the related account transfers by those institutions.

In this example, as shown in FIG. 12, the messages are displayed on the customer terminal 20 using the message app for A Bank and D Life Insurance, which are user institutions that have realized the cooperation of customer information with the customer information management server 10. On the designated bank transfer notification page, you can submit an image file of a self-portrait taken by yourself, a driver's license that displays your own face photo (My Number card, passport, etc. that displays the customer's face photo) This is the same as when registering information regarding a new deposit account. Specify the image file of the image of the account transfer request form requesting the transfer, and send these image files by pressing the button provided on the account transfer notification page. Since this button has a link to a one-time URL, a request for registering account transfer for customer information containing these image files that specifies the one-time URL as the address is sent to the customer information management server 10. Sent.

The customer information processing unit 13 of the customer information management server 10 that received the request retrieves the customer's telephone number (or a phone number and As shown in FIG. or an identification key such as a customer ID uniquely associated with a telephone number).

Next, as shown in Figure 13, identity verification is performed by using image recognition processing to determine whether the face photo in the self-portrait image and the face photo included in the driver's license image are of the same person. The customer's identity verification is performed by the unit 14. Furthermore, these facial photograph images are compared with the facial photograph images included in each customer information stored in the customer information storage section 16 to determine whether the request is an impersonation of the principal. Specifically, if a face photo that is considered to be the same person is registered, whether the customer whose face photo is included in the customer information is the same person as the customer who sent the request, or whether the phone number (or phone number and Customer information is stored for customers whose phone numbers (or identification keys such as customer IDs that are uniquely associated with phone numbers) match, or conversely, whose phone numbers (or identification keys such as customer IDs that are uniquely associated with phone numbers) match. If the received face photo is stored in the customer information section 16, it is determined whether the received face photo matches the face photo included in the registered customer information to determine whether or not it is due to impersonation.

Once it is confirmed that there are no problems with the customer's identity, including confirmation that there is no impersonation, in the manner described above, information regarding the direct debit of D Life Insurance premiums from a deposit account at Bank A, read by image recognition processing from the direct debit request form, is registered in the customer information stored in the customer information storage unit 16 for the customer identified by the telephone number (or an identification key such as a customer ID uniquely associated with the telephone number). However, the direct debit is not valid at this point, and a status of awaiting approval from the institutions with which the customer information is linked (in this case, Bank A and D Life Insurance), is recorded in the customer information.

When new account transfer information is registered in the customer information stored in the customer information storage unit 16 in this way, the customer information provision unit 17 transmits the image files of the driver's license and account transfer request form received from the customer terminal 20, as well as information such as the customer's address stored as customer information in the customer information storage unit 16, to the bank where the deposit account used for the account transfer is opened (here, Bank A) and the user institution system 50 of the receiving institution (here, D Life Insurance).

The user institutions that receive this information, the bank where the deposit account used for the direct debit is opened (here, Bank A) and the recipient (here, D Life Insurance), carry out prescribed procedures such as identity verification in accordance with the rules of each user institution, and when the direct debit is approved, this is notified to the customer information management server 10, and the status recorded in the customer information stored in the customer information storage unit 16 as waiting for approval is updated to approved. When information regarding the direct debit is registered in the customer information stored in the customer information storage unit 16 of the customer information management server 10 in this way, the notification sending unit 18 notifies the customer terminal 20 of this.

Figures 14-15 show the flow of a customer registering their My Number, which is managed in association with their deposit accounts at multiple banks (here, Bank A and Bank B), when the customer information stored in the customer information storage unit 16 of the customer information management server 10 is linked to the customer information of multiple user banks.

A customer who wishes to register a My Number that is managed in association with a deposit account of a plurality of banks where the customer information management server 10 and the customer information are linked, specifies an image file of a selfie image of the face taken by the customer, an image file of an image of a My Number card showing the customer's face photo, and an image file of an image of the My Number card showing the customer's face photo on a predetermined My Number registration page displayed by a message app on the customer terminal 20 as shown in FIG. 14 (a driver's license or passport showing the face photo may be used for face photo matching for identity verification, instead of the My Number card, and in that case, an image file of an image of the driver's license or passport is also specified). Enters the customer's My Number (the customer may be required to send a notification card or a copy of a residence certificate showing the My Number as a document that can identify the My Number), and presses a button provided on the My Number registration page to send information such as these image files. Since a link to a one-time URL is attached to this button, a request to register a My Number that is managed in association with a deposit account of a bank including these image files, with the one-time URL specified as the address, is sent to the customer information management server 10.

The customer information processing unit 13 of the customer information management server 10 that received the request retrieves the customer's telephone number (or a phone number and As shown in Figure 14, the received selfie image, My Number card image, and My Number can be identified by the phone number (or identification key such as a customer ID associated with the phone number). It is specified that the customer is identified by an identification key such as a customer ID associated with the customer.

Next, as shown in Figure 15, the face photo of the self-portrait and the image of the My Number card (if an image of a driver's license etc. is also sent as described above, the face photo will be compared with the driver's license). It is also possible to use an image of a driver's license, etc.) to determine whether the face photographs included in the images are of the same person through image recognition processing, and the identity verification section 14 executes the customer identity verification. Furthermore, these facial photograph images are compared with the facial photograph images included in each customer information stored in the customer information storage section 16 to determine whether the request is an impersonation of the principal. Specifically, if a face photo that is considered to be the same person is registered, whether the customer whose face photo is included in the customer information is the same person as the customer who sent the request, or whether the phone number (or phone number and Customer information is stored for customers whose telephone numbers (or identification keys such as customer IDs, etc. uniquely associated with telephone numbers) match, or conversely, whose telephone numbers (or identification keys such as customer IDs, etc. uniquely associated with telephone numbers) match. If the received face picture is stored in the customer information section 16, it is determined whether the received face picture is a result of impersonation based on whether the face picture included in the registered customer information matches.

Furthermore, the My Number is read from the image file of the My Number card through image recognition processing, inputted by the customer into the customer terminal 20, and received by the customer information processing unit 13 (or the customer's My Number received by the customer information processing unit 13). It may also be confirmed whether the My Number matches the My Number read from a notification card or a copy of a resident's card on which the My Number is written. In this case, as a countermeasure against input errors and fraudulent registration, please use the check digit of the My Number, and name the identity verification document (driver's license, My Number Card, etc.) and My Number confirmation document (My Number Card, notification card, etc.). It is also possible to adopt a method such as verification of date of birth or date of birth.

Once the customer's identity has been verified in this way, including whether there is any impersonation, and the accuracy of the My Number entered by the customer has been confirmed to be correct, the My Number is registered in the customer information stored in the customer information storage unit 16 for the customer identified by the telephone number (or an identification key such as a customer ID uniquely associated with the telephone number), and at this stage the customer information is recorded with a status of awaiting approval from the institutions with which the customer information is linked (here, Bank A and Bank B).

When the customer's Individual Number is registered in the customer information stored in the customer information storage unit 16, the customer information providing unit 17 transmits the image file of the Individual Number card received from the customer terminal 20, the registered Individual Number, the customer's address stored as customer information in the customer information storage unit 16, the deposit account number used by the bank to identify the customer, etc. to the bank where the deposit account is registered, i.e., the user institution system (here, the bank systems of Bank A and Bank B) 50 of each bank (here, Bank A and Bank B) with which the customer information is linked.

Each of the banks (here, Bank A and Bank B), which are the user institutions that receive this information, carries out prescribed procedures such as identity verification in accordance with the bank's rules, and when the registration of the My Number, which is managed in association with the customer's deposit account, is approved, this is notified to the customer information management server 10, and the status recorded in the customer information stored in the customer information storage unit 16 as waiting for approval is updated to approved. In this way, when it is confirmed that the My Number, which is managed in association with the deposit account of each bank that has been linked to the customer information management server 10, has been registered, the notification sending unit 18 notifies the customer terminal 20 of this.

The My Number registered as part of the customer information stored in the customer information storage unit 16 of the customer is retained in the customer information storage unit 16 as it is, and is subsequently transferred from the linked bank's user institution system 50, etc. The My Number may be provided upon request, but if the customer information management server 10 does not continue to hold the My Number due to security issues, the status recorded in the customer information may be approved. At a predetermined timing after the information such as My Number is sent to the user institution system 50 of the collaborating bank, etc., the registered My Number is updated from the customer information stored in the customer information storage unit 16. All you have to do is delete it.

In addition, in the above embodiment, a link to a one-time URL generated to identify a customer's phone number (or an identification key such as a customer ID uniquely associated with the phone number) is a link to the customer information registration or The explanation was based on the assumption that the button is set to the button that is pressed when requesting an update, and the request for registering or updating customer information is sent by specifying the one-time URL as the address, but the one-time URL for setting the link is The present invention is not limited to the example shown here, and the present invention can also be implemented by setting links to other pages accessed by customers who wish to register or update their own customer information.

For example, a link to a one-time URL for accessing a top page of a service for registering or updating customer information, a page presenting a menu of such a service, or a page requesting the customer to re-authenticate or confirm precautions when using such a service is set on the operation screen of the application, and when access to these pages is accepted, the customer's telephone number (or an identification key such as a customer ID uniquely associated with the telephone number) temporarily stored in the one-time URL storage unit 12 in association with the one-time URL specified at the time of access is identified, and a session is established with the customer terminal 20 that accepted the access, and the session is managed in a state in which the customer terminal 20 can be identified. If the session ID that identifies the session and the customer's telephone number (or an identification key such as a customer ID uniquely associated with the telephone number) are temporarily stored in association with each other, it is possible to identify the telephone number (or an identification key such as a customer ID uniquely associated with the telephone number) of the customer who sent the request to register or update customer information that was subsequently accepted from the customer terminal 20 in the same session, and it is possible to produce the same effects as the embodiments described so far.

10 Customer information management server 11 One-time URL generation section 12 One-time URL storage section 13 Customer information processing section 14 Identity confirmation section 15 Account confirmation section 16 Customer information storage section 17 Customer information provision section 18 Notification transmission section 20 Customer terminal 30 Mobile carrier Server 31 Contractor information storage unit 40 Integrated ATM network 50 User institution system 51 User institution system 52 User institution system

Claims (10)

A customer information management server connected via a network to the computer systems of two or more business operators in order to standardize at least part of the procedures related to registration or updating of customer information,
address generation means for generating a unique network address to be assigned to a page accessed by a customer who wishes to register or update his or her customer information;
address transmitting means for transmitting the address generated by the address generating means to a server of a mobile phone carrier to which the mobile terminal operated by the customer is connected by an application program authenticated by the caller's telephone number;
When a customer information registration or update request is received from the mobile terminal that has accessed the address, predetermined requirements for registering or updating customer information are confirmed, and if it is confirmed that the requirements are met, the customer information is customer information processing means for registering or updating the customer information of the customer corresponding to the address stored in the customer information storage means storing, based on the registration or update request;
A customer information management server comprising: The address generating means generates an address on a network to be assigned to a page accessed by the one customer to register or update his own customer information,
2. The customer information management server according to claim 1, wherein the customer information processing means receives a customer information registration or update request sent by specifying the address. Receive a telephone number of the one customer or an identification key associated with the telephone number from a server of the mobile phone operator, and store the telephone number or the identification key in association with the address generated by the address generation means. It is equipped with an address information storage means to
2. The customer information processing means identifies the customer corresponding to the address using a telephone number or an identification key stored in the address information storage means in association with the address accessed by the mobile terminal. The customer information management server described in 1 or 2. The customer information stored in the customer information storage means includes a customer's phone number or an identification key associated with the phone number, and an image file of a customer's face photo,
The customer information processing means receives an image file of a face photo of the customer together with the registration or update request, and stores customer information including an image file of a face photo that is determined to be of the same person as the face photo in the received image file. When stored in the customer information storage means, the customer's phone number included in the customer information or the identification key associated with the phone number is the customer's phone number or 4. The customer information management server according to claim 3, wherein the predetermined requirement includes matching an identification key associated with the telephone number. The customer information stored in the customer information storage means includes a customer's telephone number or an identification key associated with the telephone number, and an image file of a customer's face photograph,
The customer information management server according to claim 3 or 4, characterized in that the customer information processing means receives an image file of a customer's facial photograph together with the registration or update request, and if customer information including a customer telephone number or an identification key associated with the telephone number that matches the customer telephone number or the identification key associated with the telephone number received from the mobile phone carrier's server is stored in the customer information storage means, the facial photograph in the received image file is determined to be the same person as the facial photograph in the image file included in the customer information. A customer information management server as described in any one of claims 1 to 5, characterized in that the customer information processing means receives an image file of a facial photograph (first facial photograph) taken by the customer and an image file of an identity document containing the customer's facial photograph (second facial photograph) together with the registration or update request, and the specified requirements include a requirement that the first facial photograph and the second facial photograph are determined to be of the same person. The address generated by the address generation means is displayed on the operation screen of the application program, which is transmitted from the server of the mobile phone carrier to the mobile terminal and is used by customers who wish to register or update customer information to access a predetermined page. A link with an embedded is set,
Claim 1, wherein the customer information processing means receives a registration or update request for customer information in which the address is specified by selecting the link on the operation screen displayed on the mobile terminal. 7. The customer information management server according to any one of 6 to 6. A customer information management server as described in any one of claims 1 to 7, characterized in that, in the customer information processing means, when a request to register or update customer information received from the mobile terminal is a request to register the customer's My Number, the customer's My Number is registered in the customer information storage means, and the customer information management server further comprises a My Number transmission means for transmitting the My Number to the computer system of one or more business operators with which the customer does business. My number deletion, which deletes the customer's My Number registered in the customer information storage means at a predetermined timing after the My Number transmission means transmits the My Number to the computer system of the one or more business operators; 9. The customer information management server according to claim 8, further comprising means. A customer information management method executed by a customer information management server connected to computer systems of two or more businesses via a network in order to standardize at least a part of the procedures for registering or updating customer information, comprising:
an address generation step in which the customer information management server generates a unique network address to be assigned to a page accessed by a customer who wishes to register or update his/her customer information;
an address transmission step in which the customer information management server transmits the address generated in the address generation step to a server of a mobile phone carrier to which a mobile terminal operated by the customer is connected using a predetermined application program that is authenticated by a caller's telephone number;
a customer information processing step in which, when the customer information management server receives a request to register or update customer information from the mobile terminal that has accessed the address, it checks predetermined requirements for registering or updating customer information, and if it is confirmed that the requirements are met, it registers or updates the customer information of the customer corresponding to the address stored in a customer information storage means that stores customer information, based on the registration or update request;
13. A method for managing customer information, comprising: