JP7370414B1 - User information update system, user information update method, and program - Google Patents

Abstract

The present invention provides a user information update system that reduces a user's effort when updating user information registered in a service. In a user information update system in which a first server 10, a second server 20, and a user terminal 30 can be connected to a network such as the Internet or a LAN, the first server includes a registration section, a reliance determination section, and an update section. . The registration unit registers the first user information of the user in the first service. The reliance determination unit determines whether or not the user's identity verification in the first service was performed relying on the second service in which the user has completed identity verification. The update unit updates the first user information based on the second service information acquired from the second service when it is determined that the user's identity verification in the first service was performed based on the second service. Execute processing. [Selection diagram] Figure 4

Description

The present disclosure relates to a user information update system, a user information update method, and a program.

2. Description of the Related Art Conventionally, in various services, identity verification has been performed using identity verification documents such as a driver's license. For example, Patent Document 1 describes an identity verification system in which a plurality of first businesses that are entrusted with identity verification and a second business that entrusts identity verification to the first businesses cooperate. ing. In the identity verification system of Patent Document 1, when a user starts using a service of a second business operator, identity verification is entrusted to the second business operator or a first business operator selected by the user.

Japanese Patent Application Publication No. 2021-056649

In the above-mentioned services, when user information such as name or address is updated, identity verification is performed to check whether a malicious third party is attempting to illegally update the user information. It is possible that However, if identity verification is performed every time user information is updated, security will be improved, but convenience will be impaired because it will require more effort for legitimate users. In this respect, the technique of Patent Document 1 merely entrusts the user's identity verification at the time of starting to use the service, and therefore cannot reduce the user's effort when updating user information.

One of the purposes of the present disclosure is to reduce the user's effort when updating user information registered in a service.

The user information update system according to the present disclosure includes a registration unit that registers first user information of a user in a first service, and a second service that performs identity verification of the user in the first service. a reliance determination unit that determines whether or not the execution was performed relying on the service; an update unit that executes an update process regarding the first user information based on the second service information acquired from the first user information.

According to the present disclosure, it is possible to reduce the user's effort when updating user information registered in a service.

FIG. 1 is a diagram showing an example of the overall configuration of a user information update system. FIG. 3 is a diagram illustrating an example of the flow of a procedure for starting to use the first service. It is a figure which shows an example of the flow by which a user updates 1st user information. FIG. 2 is a functional block diagram showing an example of functions realized by the user information update system. FIG. 3 is a diagram showing an example of a first database. It is a figure which shows an example of the process of a 3rd display control part. It is a figure which shows an example of a 2nd database. FIG. 2 is a diagram illustrating an example of processing executed by the user information update system. FIG. 2 is a diagram illustrating an example of processing executed by the user information update system. It is a figure which shows an example of the functional block in a modification.

[1. Overall configuration of user information update system]
An example of an embodiment of a user information update system according to the present disclosure will be described. FIG. 1 is a diagram showing an example of the overall configuration of a user information update system. For example, the user information update system 1 includes a first server 10, a second server 20, and a user terminal 30. These can be connected to a network N such as the Internet or a LAN.

The first server 10 is a server computer for the first service. In this embodiment, a case will be exemplified in which a trading service for trading crypto assets corresponds to the first service, but the first service may be any service and is not limited to a crypto asset trading service. . For example, the first service may be an electronic commerce service, a travel reservation service, a payment service, a financial service, a communication service, or an SNS.

Control unit 11 includes at least one processor. The storage unit 12 includes volatile memory such as RAM and nonvolatile memory such as flash memory. The communication unit 13 includes at least one of a communication interface for wired communication and a communication interface for wireless communication.

The second server 20 is a server computer for a second service. In this embodiment, a case where the second service corresponds to a financial service provided by a bank will be exemplified, but the second service may be any service and is not limited to financial services. The second service may be a service different from the first service. The second service may be the same type of service as the first service, and in this case, it may be a service provided by a different entity than the first service. For example, the second service may be an electronic commerce service, a travel reservation service, a payment service, a communication service, or an SNS. If the first service is a service other than a crypto asset trading service, the second service may be a crypto asset trading service.

The hardware configurations of the control section 21, the storage section 22, and the communication section 23 may be the same as those of the control section 11, the storage section 12, and the communication section 13, respectively.

User terminal 30 is a user's computer. For example, the user terminal 30 is a personal computer, a smartphone, a tablet terminal, or a wearable terminal. The hardware configurations of the control section 31, the storage section 32, and the communication section 33 may be the same as those of the control section 11, the storage section 12, and the communication section 13, respectively. The operation unit 34 is an input device such as a touch panel. The display section 35 is a liquid crystal display or an organic EL display.

Note that the programs stored in the storage units 12, 22, and 32 may be supplied via the network N. In addition, a program stored in a computer-readable information storage medium is connected to a reading section (for example, an optical disk drive or a memory card slot) that reads the information storage medium, or an input/output device for inputting and outputting data with an external device. (e.g., a USB port).

Further, the user information update system 1 only needs to include at least one computer, and is not limited to the example shown in FIG. 1. For example, the second server 20 and user terminal 30 may exist outside the user information update system 1. In this case, the user information update system 1 does not include the second server 20 and the user terminal 30. The user information update system 1 may include only the first server 10. The user information update system 1 may include the first server 10 and other computers of the first service.

[2. Overview of user information update system]
For example, assume that the user has started using the second service but has not yet started using the first service. In this case, the user performs a usage start procedure to start using the first service. In this embodiment, a case will be described in which the procedure for starting to use the first service is performed online, but the procedure for starting to use the first service may be performed in writing instead of online.

FIG. 2 is a diagram illustrating an example of the flow of the procedure for starting to use the first service. In this embodiment, a case is assumed in which the first business operator "AAA Wallet" which provides the first service and the second business operator "AAA Bank" which provides the second service belong to the same corporate group "AAA Group". As an example, the first business operator and the second business operator only need to be able to cooperate with each other, and do not need to belong to the same corporate group.

For example, when a user operates the user terminal 30 to access the first server 10, a login screen G1 is displayed on the display unit 35. In this embodiment, an example is given where the user needs to become a member of the "AAA group" in order to start the procedure for starting to use the first service. It may also be possible to start a procedure for starting the use of one service.

For example, if the user is already a member of the "AAA group", he or she enters the user ID and password of the "AAA group" into the input forms F10 and F11. When the user selects button B12, login processing is executed. If the login process is successful, a registration screen G2 for registering user information is displayed on the display unit 35. If the user is not a member of the "AAA group", the user selects button B13 to become a member of the "AAA group".

For example, the user inputs user information such as name, address, and telephone number into input forms F20A to F20C. Hereinafter, when input forms F20A to F20C are not distinguished, they will simply be referred to as input form F20. User information is information related to users. User information may be of any type and is not limited to name, address, and phone number. For example, user information may be email address, gender, date of birth, occupation, place of work, or other personal information. User information may be information that is not classified as personal information.

For example, if some user information is registered as member information of the "AAA group", this user information may be used in the registration screen G2. User information that is used for the registration screen G2 and user information that requires input by the user may coexist. When the user inputs user information, an identity verification screen G3 for executing identity verification is displayed on the display unit 35.

Identity verification is to confirm whether or not the person is the person. For example, identity verification is performed using an identity verification document such as a driver's license or personal number card. Various confirmation methods can be used for identity confirmation itself. For example, a confirmation method of mailing a copy of an identity verification document or a confirmation method called eKYC may be used. In this embodiment, the first service's identity verification can rely on the second service.

Relying on the second service means reusing the second service's identity verification. For example, if the user has completed identity verification in the second service, all or part of the identity verification procedure in the first service (for example, mailing a copy of the identity verification document, or photographing or reading the identity verification document) Omitting is equivalent to relying on the second service. As in this embodiment, when the bank's financial services correspond to the second service, executing identity verification using the account transfer function corresponds to relying on the second service.

Various confirmation methods can also be used to confirm the identity of the second service. As in this embodiment, when the bank's financial service corresponds to the second service, confirmation methods adopted by various banks can be used. It is up to the user whether or not to rely on the second service to confirm the identity of the first service. Even if the user completes the identity verification of the second service, the user may not rely on the second service.

In this embodiment, a case where the user relies on the second service will be exemplified. For example, when the user selects button B30, the user terminal 30 accesses the second server 20. Although not shown in FIG. 2, when the user terminal 30 accesses the second server 20, an authentication process is executed on the second service side to confirm the validity of the user. For the authentication process itself, various authentication methods can be used. For example, login authentication, one-time password authentication, pin number authentication, or biometric authentication may be used.

For example, if the authentication process is successful, the identity verification of the first service based on the second service is completed. In this case, the user's identity verification for the first service is completed without the user having to undergo procedures such as mailing identity verification documents on the first service side. If the user does not use the second service (does not have a bank account with "AAA Bank"), the user can perform normal identification using identification documents by selecting button B31. Carry out the procedures.

For example, when the identity verification for the first service is completed, an application completion screen G4 indicating that the procedure for starting to use the first service is completed is displayed on the display unit 35. The user information input on the registration screen G2 is registered in the first service. Hereinafter, the user information registered in the first service will be referred to as first user information. The user information registered in the second service is referred to as second user information. Once a trading account for trading crypto assets is opened, the user can start using the first service.

In this embodiment, the user can update the first user information registered in the first service at any timing. For example, when the user logs in to the first service, the display unit 35 can display a my page screen for checking the user's first user information. The user can update the first user information from the my page screen.

FIG. 3 is a diagram illustrating an example of a flow in which a user updates first user information. For example, buttons B50A to B50C for updating the first user information are displayed on the my page screen G5. Hereinafter, when buttons B50A to B50C are not distinguished, they will simply be referred to as button B50. The user selects the button B50 of the first user information that he/she wishes to update. The example in FIG. 3 shows a flow in which a user updates an address.

For example, when the user selects the address button B50B, an update screen G6 for updating the address is displayed on the display unit 35. The user inputs a new address into the input form F60. In this embodiment, the address includes a postal code and a character string indicating the prefecture and city, ward, town, or village. The user may enter a new address from scratch or may enter a new address by changing part of the old address. Similarly to other first user information, one piece of first user information may include a plurality of items. For example, if it is a name, the name may include the name in kanji and the name in kana. The name in kanji and the name in kana may be treated as separate first user information.

In this embodiment, when important first user information such as name or address is updated, in principle, identity verification is required again. However, a user who relies on the second service for identity verification during the usage start procedure can also rely on the second service for identity verification when updating the first user information. In the example of FIG. 3, it is assumed that the user relies on the second service for identity verification during the usage start procedure.

In this embodiment, when important first user information is updated, it is determined whether the new first user information input by the user matches the second user information registered in the second service. It will be judged. If these match, updating of the first user information is permitted. If these do not match, the first user information will not be allowed to be updated unless the user updates the second user information. In order to update the important first user information, the user needs to update the second user information in advance. When updating the second user information, identity verification is performed on the second service side.

For example, when the user selects the button B61, it is determined whether the new first user information input on the update screen G6 matches the second user information. If the user has logged in to the second service in advance and updated the second user information, these will match. When updating the second user information, it is assumed that the second service side performs identity verification again. The fact that the user has updated the second user information in advance means that the second service has already verified the user's identity again.

For example, when the new first user information and the second user information match, an authentication screen G7 for executing authentication processing on the second service side is displayed on the display unit 35. In this authentication process, the same authentication method as used during the usage start procedure may be used, or a different authentication method from that used during the use start procedure may be used. If the new first user information and the second user information do not match, a first proposal screen G9 of FIG. 6, which will be described later, is displayed on the display unit 35, and updating of the first user information is not permitted.

For example, the user enters the pin number of the bank account in the second service and the one-time password sent to the user's e-mail address registered in the second service into the input forms F70 and F71. When the user selects button B72, authentication processing is executed on the second service side. If the authentication process is successful, an update completion screen G8 indicating that the address registered in the first service has been updated is displayed on the display unit 35. When other important first user information such as name is updated, the first user information is updated in the same manner as in FIG. 3.

As described above, when a user relying on a second service updates important first user information, the user information update system 1 of the present embodiment updates new first user information input by the user and second user information. It is determined whether or not the user information matches the user information. If these match, updating of the first user information is permitted. This makes it possible to reduce the user's effort while maintaining security. Hereinafter, details of the user information update system 1 will be explained.

[3. Functions achieved by the user information update system]
FIG. 4 is a functional block diagram showing an example of functions realized by the user information update system 1. As shown in FIG.

[3-1. Functions realized by the first server]
The data storage section 100 is realized by the storage section 12. Registration unit 101, first user information acquisition unit 102, instruction determination unit 103, reliance determination unit 104, comparison request unit 105, update unit 106, first display control unit 107, second display control unit 108, and third display control unit The unit 109 is realized by the control unit 11.

[Data storage unit]
The data storage unit 100 stores data necessary for providing the first service to the user. For example, the data storage unit 100 stores a first database DB1.

FIG. 5 is a diagram showing an example of the first database DB1. The first database DB1 is a database that stores various information regarding users of the first service. For example, the first database DB1 stores a user ID, password, first user information, and identity verification information. This user ID and password may be the same as the user ID and password as a member of the "AAA group", or may be a user ID and password unique to the first service.

In the example of FIG. 5, three pieces of first user information such as name, address, and telephone number are shown, but the first user information stored in the first database DB1 may be any number of pieces of first user information, such as , one, two, or four or more. All of the first user information may be updatable, or there may be first user information that cannot be updated once registered. First user information for which registration is mandatory and first user information for which registration is optional may coexist.

The personal identification information is information indicating whether or not the personal identification of the first service was performed based on the second service. For example, when the identity verification information is the first value (“relying” in FIG. 5), it means that the identity verification of the first service was executed relying on the second service. The identity verification information having the second value (“unique” in FIG. 5) means that the identity verification of the first service was performed without relying on the second service.

For example, the first server 10 executes the user identification for the first service during the usage start procedure according to the flow described in FIG. 3 . When the user's identity verification relies on the second service, the first server 10 sets the user's identity verification information to a first value. If the user's identity verification does not rely on the second service, the first server 10 sets the user's identity verification information to a second value.

Note that the information stored in the first database DB1 is not limited to the example shown in FIG. 5. The first database DB1 may store any information regarding users. For example, the first database DB1 may store transaction account information regarding a user's transaction account and bank account information regarding a bank account linked with the transaction account.

[Registration Department]
The registration unit 101 registers the user's first user information in the first service. Registering the first user information in the first service means recording the first user information in the computer of the first service. In this embodiment, storing the first user information in the first database DB1 corresponds to registering the first user information in the first service. For example, the registration unit 101 registers a plurality of pieces of first user information in the first service. In the present embodiment, the registration unit 101 registers the first user information input during the procedure for starting to use the first service with the first service. If the first user information that was not input during the procedure for starting to use the first service is input after the fact by the user, the registration unit 101 registers the first user information that was input after the fact. Good too.

[First user information acquisition unit]
The first user information acquisition unit 102 acquires new first user information input by the user. The new first user information is the first user information that the user is trying to update. In this embodiment, the first user information acquisition unit 102 acquires the first user information input on the update screen G6 as new first user information. The new first user information may be stored in advance in the user terminal 30 instead of being input by the user. The new first user information may be obtained from the second server 20 or another computer. In Modification 8, which will be described later, new first user information is acquired from the second server 20.

[Instruction judgment section]
The instruction determination unit 103 determines whether an instruction has been given to update specific first user information among the plurality of pieces of first user information. The specific first user information is the important first user information mentioned above. The specific first user information is first user information that requires identification at the time of update. In this embodiment, a case will be described in which an address corresponds to specific first user information, but the specific first user information may be any first user information and is not limited to an address. For example, the specific first user information may be a name or other first user information. It is assumed that the specific first user information is specified in advance by the administrator of the first service.

[Reliance determination section]
The reliance determination unit 104 determines whether or not the user's identity verification in the first service was performed relying on the second service in which the user has completed identity verification. Hereinafter, this determination will simply be referred to as dependency determination processing. In this embodiment, when a certain user inputs new first user information, the reliance determination unit 104 executes the reliance determination process based on the identification information associated with the user ID of this user. If information other than the identity verification information indicates whether or not the identity verification of the first service was performed relying on the second service, the reliance determination unit 104 determines whether or not the identity verification of the first service was performed based on the other information. Then, the dependency determination process can be executed.

[Comparison request section]
When new first user information is input, the comparison requesting unit 105 requests the second service to compare the new first user information and the second user information. Hereinafter, these comparisons will be simply referred to as comparison processing. For example, the comparison requesting unit 105 requests the second server 20 to perform a comparison process by transmitting new first user information and the user ID of the user who input the new first user information. . A request for comparison processing is made by transmitting data in a predetermined format. In this embodiment, the comparison process is not executed on the first service side, so the second user information is not transmitted onto the network N. In addition, since various kinds of second user information are stored in the second database DB2, which will be described later, the comparison requesting unit 105 asks the second server 20 which second user information the comparison is requested to. information that can be identified may be transmitted.

[Update section]
The update unit 106 executes update processing regarding the first user information. The update process is a process of replacing registered first user information with new first user information. Updates can also be referred to as changes or overwrites. In this embodiment, new first user information is input on the first service side, so the update process is to change the registered first user information to the new first user information input on the first service side. This is a replacement process. As in Modification 8, which will be described later, when new second user information input on the second service side is reflected in the first service, the new second user information is reflected as new first user information. This processing corresponds to update processing.

For example, when it is determined that the user's identity verification in the first service was performed based on the second service, the update unit 106 performs the update process based on the second service information acquired from the second service. Execute. If it is not determined that the identity verification for the first service was performed based on the second service, the update unit 106 executes the update process not based on the second service information. In this case, the updating unit 106 may perform the updating process when the identity verification is performed again, as in Modification 4 described later.

[Second service information]
The second service information is information acquired from the second service in order to execute the update process. In this embodiment, an example is given where the second service information indicates a comparison result between new first user information and second user information. The comparison result includes a third value indicating that the new first user information and the second user information match (for example, a numerical value or character string that means "match"), and a third value indicating that they do not match. and a fourth value (for example, a numeric value or a character string that means "mismatch"). The second service information may be information obtained from the second service, and may be information other than the comparison results. In Modification 8, which will be described later, new second user information input by the user on the second service side corresponds to second service information.

In this embodiment, the update unit 106 determines whether the new first user information matches the second user information of the user registered in the second service based on the second service information. . For example, the updating unit 106 determines whether the new first user information and the second user information match based on the comparison result indicated by the second service information. The update unit 106 determines that the new first user information and the second user information match when the comparison result is the third value, and when the comparison result is the fourth value, the update unit 106 determines that the new first user information and the second user information match. It is not judged if they match.

For example, the update unit 106 executes the update process when it is determined that the new first user information and the second user information match. In this embodiment, the update unit 106 does not execute the update process if it is determined that these do not match, but as in Modification 3, which will be described later, after the identity verification is performed again, Update processing may also be performed.

Note that the comparison process may be executed on the first service side. In this case, the update unit 106 transmits the user ID of the user who has input new first user information to the second server 20. The second server 20 specifies which user's second user information is requested based on the user ID, acquires the second user information of the corresponding user from a second database DB2, which will be described later, and provides the first user information. Send to server 10. It is assumed that information that allows identification of which second user information is requested is also transmitted from the first server 10 to the second server 20.

For example, the update unit 106 acquires the second user information of the user from the second server 20. In this case, the second user information corresponds to the second service information. The update unit 106 compares the new first user information and the second user information, which is the second service information, to determine whether or not they match. Although the method for determining whether these match or not is different from the above example, it is similar in that whether or not the update process can be executed is controlled according to the determination result.

In the present embodiment, when it is determined that an update of the specific first user information has been instructed, the updating unit 106 determines whether the new specific first user information and the second user information match. Determine. If it is determined that an instruction has been given to update other first user information other than the specific first user information, the updating unit 106 does not determine whether or not they match. The update unit 106 updates the update process when it is determined that the new specific first user information and the second user information match. If it is not determined that the new specific first user information and the second user information match, the update process is not updated.

For example, the update unit 106 may determine whether a portion of the new first user information and a portion of the second user information match. Taking an address as an example, the updating unit 106 determines whether a part of the address that is new first user information and a part of the address that is second user information match. The portion for which a match is required may be at the beginning, middle, or end. For example, in the case of an address, a match of only the postal code may be required, or a match of the prefecture or city, ward, town, or village may be required. The update unit 106 executes an update process when it is determined that a part of the new first user information and a part of the second user information match. The update unit 106 does not perform the update process if it is not determined that a part of the new first user information and a part of the second user information match.

For example, the updating unit 106 updates the new first user information with the second user information corresponding to the new first user information, and the other first user information and the other first user information. It may be determined whether the second user information corresponding to the user information matches. That is, not only the first user information to be updated but also other first user information that is not updated may be subjected to the comparison process. The other first user information may be any first user information. For example, if the user is updating their address, the other first user information may be the name, the bank account number, the bank account branch number, or all of these.

For example, the updating unit 106 updates the new first user information with the second user information corresponding to the new first user information, and the other first user information and the other first user information. If it is determined that the user information and the corresponding second user information match, the update process is executed. That is, the update unit 106 executes the update process when both of these two determination processes are determined to be a match. The updating unit 106 does not perform the update process if one of the two is not determined to be a match, or if both are not determined to be a match.

In this embodiment, in the second service, when new first user information is input, authentication processing regarding the user is executed, so the updating unit 106 determines whether the authentication processing executed in the second service is successful. , and when it is determined that the new first user information and the second user information match, the update process is executed. The update unit 106 does not perform the update process if the authentication process is not successful or if it is not determined that the new first user information and the second user information match.

[First display control section]
The first display control unit 107 executes display control for displaying the authentication screen G7 in the second service on the user terminal 30 when new first user information is input. Since the authentication screen G7 is a screen on the second service side, the display control is a process for causing the second server 20 to access the user terminal 30. The screen on the second service side is a screen displayed in the domain of the second service or a screen displayed on an application of the second service.

In this embodiment, after the update screen G6 of FIG. 3 is displayed, redirection to the authentication screen G7 occurs, so display control corresponds to the processing of this redirection. Display control is not limited to redirect processing. For example, when the authentication screen G7 is displayed on an application of the second service instead of the browser, the process of starting the application of the second service or bringing it to the foreground may correspond to display control.

[Second display control section]
The second display control unit 108 causes the user terminal 30 to display an update completion screen G8 for the first service when the update process is executed. In this embodiment, since the second display control unit 108 is realized by the first server 10, sending the display data of the update completion screen G8 to the user terminal 30 causes the update completion screen G8 to be displayed. Equivalent to. The display data may be any data for displaying some screen on the user terminal 30. For example, when a browser is used, the display data is HTML data. For example, when an application of the first service installed on the user terminal 30 is used, the display data is data necessary for displaying some screen on the application.

[Third display control section]
FIG. 6 is a diagram illustrating an example of processing by the third display control unit 109. When the new first user information and the second user information are not determined to match, the third display control unit 109 displays a first proposal screen G9 for proposing updating of the second user information on the user terminal. 30. In this embodiment, since the third display control unit 109 is realized by the first server 10, sending the display data of the first proposal screen G9 to the user terminal 30 causes the first proposal screen G9 to be displayed. It corresponds to that. As mentioned above, the display data may be any data.

In the example of FIG. 6, the first proposal screen G9 includes a message M90 proposing updating of the second user information, and a button B91 to the second service my page screen G10. The third display control unit 109 may suggest updating of the second user information using images other than the message M90 and the button B91. When the user selects button B91, a second service my page screen G10 is displayed on the user terminal 30. The user can update the second user information from the my page screen G10. When the my page screen G10 is displayed, it is assumed that a login process to the second service is executed.

[3-2. Functions realized by the second server]
The data storage section 200 is realized by the storage section 22. The authentication section 201 and the comparison section 202 are realized by the control section 21.

[Data storage]
The data storage unit 200 stores data necessary for providing the second service to the user. For example, the data storage unit 200 stores a second database DB2.

FIG. 7 is a diagram showing an example of the second database DB2. The second database DB2 is a database that stores various information regarding users in the second service. For example, the second database DB2 stores a user ID, password, and second user information. This user ID and password may be the same as the user ID and password as a member of the "AAA group", or may be a user ID and password unique to the second service.

If the user ID and password stored in the second database DB2 are unique to the second service, the user ID in the first service and the user ID in the second service are mutually unique in the second database DB2. shall be associated. That is, the second server 20 can specify which user of the first service is which user of the second service.

In the example of FIG. 7, three pieces of second user information such as name, address, and telephone number are shown, but any number of pieces of second user information may be stored in the second database DB2. The number of second user information stored in the second database DB2 may be any number, for example, one, two, or four or more. Like the first user information, the second user information may also be updateable at any timing. The user logs into the second service and updates the second user information.

A plurality of pieces of second user information corresponding to a plurality of pieces of first user information are registered in the second service. Registering the second user information in the second service means recording the second user information in the computer of the second service. In this embodiment, storing the second user information in the second database DB2 corresponds to registering the second user information in the second service.

The second user information corresponding to the first user information is the same type of second user information as the first user information. For example, if the first user information is an address, the second user information corresponding to the first user information is the address registered in the second service. For example, if the second user information is a name, the second user information corresponding to the first user information is the name registered in the second service.

It is assumed that second user information corresponding to specific first user information among the plurality of first user information is registered in the second service. Therefore, when specific first user information is updated, there is second user information to be compared. For example, if the comparison process is executed when the address and name are updated in the first service, it is sufficient that at least the address and name are registered in the second service. The second database DB2 may store arbitrary data, for example, authentication information (for example, a personal identification number or one-time password) necessary for authentication processing.

[Authentication Department]
The authentication unit 201 executes the authentication processing described above. In the present embodiment, the authentication unit 201 performs PIN authentication and one-time password authentication based on the PIN number and one-time password input on the authentication screen G7. The authentication unit 201 can perform any other authentication processing. Other authentication methods are as described above.

[Comparison section]
The comparison unit 202 executes the comparison process described above. For example, when the comparison process is requested from the first server 10, the comparison unit 202 acquires the second user information associated with the user ID of the user who is the target of the comparison process. The comparison unit 202 compares the first user information received from the first server 10 and the acquired second user information. Comparison here means determining whether or not they match. The comparison unit 202 may determine whether there is a complete match or whether there is a partial match. The comparison unit 202 transmits second service information indicating these comparison results to the first server 10.

[3-3. Functions realized on user terminal]
The data storage section 300 is realized by the storage section 32. The display control unit 301 and the operation reception unit 302 are realized by the control unit 31.

[Data storage]
The data storage unit 300 stores data necessary for the user to use each of the first service and the second service. For example, the data storage unit 300 stores a browser for displaying each screen described in this embodiment. When each screen is displayed on each application of the first service and the second service, the data storage unit 300 stores these applications.

[Display control section]
The display control unit 301 causes the display unit 35 to display each screen described in this embodiment.

[Operation reception department]
The operation accepting unit 302 accepts operations on each screen described in this embodiment.

[4. Processing executed by the user information update system]
8 and 9 are diagrams illustrating an example of processing executed by the user information update system 1. This process is executed by the control units 11, 21, and 31 operating according to programs stored in the storage units 12, 22, and 32, respectively. 8 and 9, among the processes executed by the user information update system 1, the processes related to updating the first user information are mainly shown.

As shown in FIG. 8, the user terminal 30 executes a login process with the first server 10 for the user to log in to the first service (S1). In S1, the user inputs a user ID and password into the user terminal 30. The first server 10 permits login to the first service when the input user ID and password combination exists in the first database DB1. When a user logs in to the first service, he or she can use various services such as crypto asset trading. Here, processing when the first user information is updated will be described.

When the user performs an operation to display the my page screen G5, the user terminal 30 executes a process to display the my page screen G5 with the first server 10 (S2). In S2, the first server 10 refers to the first database DB1 and acquires the first user information of the logged-in user. The first server 10 displays the my page screen G5 on the user terminal 30 based on the acquired first user information.

When the user selects button B50, user terminal 30 transmits a request to display update screen G6 to first server 10 (S3). It is assumed that this display request includes information that allows identification of the type of first user information to be updated (that is, information that allows identification of which button B50 has been selected). When the first server 10 receives the request to display the update screen G6 (S4), it determines whether specific first user information is to be updated (S5). In S5, the first server 10 determines whether the first user information to be updated is a name or an address (that is, whether buttons B50A and 50B are selected).

If it is not determined that the specific first user information is updated (S5: N), the first server 10 executes an update process with the user terminal 30 (S6), and this process ends. In this case, other first user information (for example, telephone number) that is not specific first user information is updated, so identity verification is not performed. The first server 10 acquires new first user information input by the user from the user terminal 30 and stores it in the first database DB1.

In S5, if it is determined that the specific first user information is updated (S5: Y), the first server 10 performs the reliance determination process based on the user identification information stored in the first database DB1. (S7). If it is not determined that the identity verification of the first service was performed based on the second service (S7: N), the first server 10 performs identity verification again with the user terminal 30 to confirm the identity of the first user. Information update processing is executed (S8), and this processing ends. Details of the process in S8 will be explained in Modification 3, which will be described later.

In S7, if it is determined that the identity verification of the first service was performed based on the second service (S7: Y), the first server 10 displays an update screen G6 with the user terminal 30. Processing for this purpose is executed (S9). When the user inputs new first user information into the input form F60 and selects button B61, the user terminal 30 transmits the new first user information input by the user to the first server 10 (S10). .

When the first server 10 receives new first user information (S11), it requests the second server 20 to compare the new first user information (S12). In S12, the user ID of the logged-in user is also transmitted. When the second server 20 receives the request for comparison processing (S13), it executes the comparison processing based on the second database DB2 (S14). In S14, the second server 20 acquires second user information associated with the user ID received from the first server 10 from the second database DB2 and executes a comparison process.

9, the second server 20 transmits second service information indicating the comparison result in S14 to the first server 10 (S15). Upon receiving the second service information (S16), the first server 10 determines whether the new first user information and the second user information match based on the received second service information. (S17).

If it is not determined that the new first user information and the second user information match (S17: N), the first server 10 performs a process for displaying the first proposal screen G9 with the user terminal 30. is executed (S18), and the process ends. When the user selects the button B91 on the first proposal screen G9, the second user information is updated from the my page screen G10 of the second service. Thereafter, when the processes in FIGS. 8 and 9 are executed again, the determination process in S17 is affirmed and the processes in and after S19 are executed.

In S17, if it is determined that the new first user information and the second user information match (S17: Y), the first server 10 redirects the user terminal 30 to the second server 20 (S19). , a process for displaying the authentication screen G7 is executed between the second server 20 and the user terminal 30 (S20). The second server 20 executes authentication processing with the user terminal 30 (S21), and determines whether the authentication processing is successful (S22). If the authentication process fails (S22: failure), this process ends.

In S22, if the authentication process is successful (S22: success), the second server 20 transmits a success notification indicating that the authentication process was successful to the first server 10 (S23). When the first server 10 receives the success notification from the second server 20 (S24), it executes the update process (S25). The first server 10 executes a process to display the update completion screen G8 with the user terminal 30 (S26), and this process ends.

The user information update system 1 of the present embodiment updates information based on the second service information acquired from the second service when it is determined that the user's identity verification in the first service was performed based on the second service. , execute the update process. As a result, complicated identification is not required when updating the first user information, so it is possible to reduce the user's effort when updating the first user information. In order to reduce the user's effort and update the first user information, it is necessary to complete the identity verification based on the second service in advance (in other words, it is necessary to complete the identity verification on the second service side). ), security can be maintained by preventing a malicious third party from updating the first user information without permission. It is also possible to reduce the operations of the first business operator that provides the first service.

Further, the user information update system 1 executes an update process when it is determined that the new first user information and the second user information match. As a result, in order to execute the update process, the new first user information and the second user information must match, so a malicious third party can update the first user information without permission. This makes it easier to prevent such incidents and improves security. For example, even if a third party somehow impersonates another person and logs into the first service, the third party cannot update the other person's first user information without permission, which increases security. If the user ID and password of the second service are different from those of the first service, a third party must also steal this user ID and password, and it is difficult to steal these, thereby increasing security. If identity verification is required when updating the second user information in the second service, a third party cannot successfully verify the identity, thereby increasing security.

Further, the user information update system 1 determines whether an instruction has been given to update specific first user information among the plurality of pieces of first user information. The user information update system 1 updates the update process when it is determined that the new specific first user information and the second user information match. As a result, by executing the comparison process only when specific primary user information is updated, which could cause a major disadvantage if a malicious third party updates it without permission, when other primary user information is updated. The user's convenience will be improved. From the first server 10 and the second server 20, even when other first user information is updated, even if a malicious third party updates it without permission, other first user information is updated. Since there is no need to request and execute the request, the processing load on the first server 10 and the second server 20 can be reduced.

Further, the user information update system 1 executes an update process when it is determined that a part of the new first user information and a part of the second user information match. This makes it possible to prevent the conditions for executing the update process from becoming excessively strict, thereby increasing user convenience while maintaining security. For example, when a user updates an address, if the only condition is that the postal code of the address matches, it is possible to prevent the address from being unable to be updated due to incorrect spelling of the street number or condominium name.

Further, the user information update system 1 is configured such that the new first user information and the second user information corresponding to the new first user information match, and the other first user information and the other user information match. If it is determined that the first user information and the second user information correspond to each other, the update process is executed. This increases the conditions for executing the update process, making it difficult for a malicious third party to update the first user information without permission, thereby increasing security.

Further, the user information update system 1 performs the update process when the authentication process executed by the second service is successful and it is determined that the new first user information and the second user information match. Execute. As a result, in order to execute the update process, the authentication process on the second service side needs to be successful, making it difficult for a malicious third party to update the first user information without permission, thereby increasing security.

Further, the user information update system 1 executes display control to display the authentication screen G7 in the second service on the user terminal 30 when new first user information is input. When the update process is executed, the user information update system 1 causes the user terminal 30 to display an update completion screen G8 for the first service. This makes the series of steps for accessing the second server 20 to perform the authentication process seamless, thereby increasing convenience for the user.

Further, the user information update system 1 determines whether the new first user information and the second user information match based on the comparison result indicated by the second service information. This allows the second server 20 to execute the comparison process, thereby reducing the processing load on the first server 10. When the second server 20 executes the comparison process, the second user information is not transmitted onto the network N, so that the second user information is less likely to leak.

Further, when it is determined that the new first user information and the second user information do not match, the user information update system 1 displays a first proposal screen G9 on the user terminal for proposing an update of the second user information. 30. Thereby, when there is a possibility that the second user information is old, the user can be prompted to update the second user information. The user can seamlessly update the second user information from the first proposal screen G9, which increases convenience.

[5. Modified example]
Note that the present disclosure is not limited to the embodiments described above. Changes can be made as appropriate without departing from the spirit of the present disclosure.

FIG. 10 is a diagram illustrating an example of functional blocks in a modified example. The first update request section 110 , the holding section 111 , the first reconfirmation section 112 , the second reconfirmation section 113 , the fourth display control section 114 , and the second update request section 115 are realized by the control section 11 .

[5-1. Modification example 1]
For example, in the embodiment, a case has been described in which when the button B91 on the first proposal screen G9 is selected, the my page screen G10 of the second service is displayed on the display unit 35. The second user information may be updated using new first user information input by the user without the user inputting new second user information to the my page screen G10.

The user information update system 1 includes a first update request section 110. When the user agrees to update the second user information on the first proposal screen G9, the first update request unit 110 updates the second user information for the second service based on the new first user information. request. This consent is obtained by performing a predetermined operation on the first proposal screen G9. For example, selecting button B91 corresponds to agreeing.

The request to update the second user information is made by transmitting data in a predetermined format. The first update request unit 110 requests the second server 20 to update the second user information by transmitting new first user information input by the user. It is assumed that the user ID is also transmitted along with this request. The second server 20 can specify which user's second user information should be updated based on this user ID.

In the second service, when an update of the second user information is requested, the second user information is updated based on new first user information. When the second server 20 receives a request to update the second user information from the first server 10, the second server 20 acquires the new first user information received from the first server 10 as new second user information. The second server 20 updates the second user information by overwriting the existing second user information with the new second user information.

In the user information update system 1 of the first modification, when the user agrees to update the second user information on the first proposal screen, the second user information is updated based on the new first user information. This can reduce the user's effort when updating the second user information.

[5-2. Modification 2]
For example, in embodiments, if the second user information is old, the user needs to log into the second service and update the second user information, and then enter new first user information again. In the second modification, new first user information input by the user is held, so that the user does not have to input it again.

The user information update system 1 includes a holding unit 111. The holding unit 111 holds the new first user information when it is not determined that the new first user information and the second user information match. Retaining means recording new first user information in the data storage unit 100. For example, the holding unit 111 stores new first user information in the first database DB1 in association with the user ID. The new first user information may be held in a part other than the first database DB1.

When the second user information is updated in the second service, the update unit 106 determines whether the new first user information and the new second user information match. This determination process is executed in the same manner as in the embodiment. However, since there is no need to re-enter new first user information, the new first user information held by the holding unit 111 is used in the determination process. The update unit 106 executes an update process based on the held first user information when it is determined that the new first user information and the new second user information match. The update unit 106 may execute the above-described determination process and update process when the user accesses the first server 10 again, or automatically executes the above-described process even if the user does not access the first server 10. Determination processing and update processing may be performed.

The user information update system 1 of the second modification retains the new first user information when it is not determined that the new first user information and the second user information match. Due to this. Since the user does not need to re-enter new first user information, the user's convenience is improved.

[5-3. Modification 3]
For example, if it is not determined that the new first user information and the second user information match, the identity verification in the first service may be performed again. In this case, identity verification may be performed based on the second service, but in the third modification, identity verification unique to the first service is performed. The point that this identity verification can use various methods is as explained in the embodiment.

The user information update system 1 includes a first reconfirmation section 112. The first reconfirmation unit 112 executes identity confirmation again in the first service when it is determined that the new first user information and the second user information do not match. For example, the first reconfirmation unit 112 requests the user to take a photograph of an identity verification document and analyzes the image obtained from the user terminal 30 to perform identity verification again. For example, in the case of an identity verification document equipped with an IC chip, such as a personal number card, the user terminal 30 uses short-range wireless communication to acquire the information necessary for identity verification from the IC chip. Good too. The first reconfirmation unit 112 may perform identity confirmation again based on information acquired using short-range wireless communication.

The update unit 106 executes the update process when the re-identification is successful. In modification 3, even if old second user information is registered in the second service, if the first service side can verify the user's identity, the update unit 106 executes the update process.

The user information update system 1 of the third modification executes the identity verification again in the first service when it is not determined that the new first user information and the second user information match. The user information update system 1 executes an update process when the user's identity verification is successful again. As a result, even if the user does not log in to the second service and update the second user information, the update process can be executed through the identity verification performed on the first service side, thereby increasing convenience for the user.

[5-4. Modification example 4]
For example, as described in the embodiment, the first service allows identity verification that does not rely on the second service. Even if the user holds a bank account for the second service, identity verification that does not rely on the second service may be performed. In this case, in order for the user to update the first user information, identity verification may be performed again.

The user information update system includes a second reconfirmation section 113. If the identity verification that does not rely on the second service has been performed, the second reconfirmation unit 113 performs another identity verification in the first service when executing the update process. The process of the second reconfirmation unit 113 is different from the process of the first reconfirmation unit 112 of the third modification in that the target is a user whose identity has been verified without relying on the second service, but there are other points. The same applies to The update unit 106 executes the update process when the re-identification is successful. This modification differs from Modification 3 in that the update process requires identity verification by the second reconfirmation unit 113 instead of the first reconfirmation unit 112, but is similar in other respects.

In the case where the user information update system 1 of Modification 4 performs identity verification that does not rely on the second service, the user information update system 1 performs identity verification again in the first service when executing the update process. The user information update system 1 executes an update process when the user's identity verification is successful again. Thereby, even if only the processing on the first service side is used, it is possible to perform update processing that improves user convenience while maintaining security.

[5-5. Modification 5]
For example, the first service may be able to perform identity verification that relies on the second service after identity verification that does not rely on the second service is performed. For example, assume that a user who was not using the second service when starting to use the first service starts using the second service after starting to use the first service. In this case, the user may be able to perform identity verification based on the second service after the fact. The flow of this subsequent identity verification may be the same as the flow of identity verification at the time of starting to use the first service.

If identity verification that relies on the second service is performed after identity verification that does not rely on the second service is performed, the update unit 106 can execute the update process without requiring identity verification again. be. In this case, the update unit 106 may execute the update process in the same manner as the flow described in the embodiment, without executing the identity verification unique to the first service as in the third or fourth modification.

The user information update system 1 of the fifth modification does not require identity verification again when identity verification that relies on the second service is performed after identity verification that does not rely on the second service is performed. Update processing can be executed. This increases convenience for the user who subsequently performs identity verification based on the second service.

[5-6. Modification 6]
For example, the first service may be able to perform identity verification based on a second service selected from a plurality of second services. In modification 6, in addition to the bank financial services described in the embodiment, the second services that can be relied upon for identity verification of the first service include a securities company's financial services and a telecommunications company's communication services. shall be. The number of second services is not limited to three as in Modification 6, but may be any number. For example, the number of second services may be two or four or more.

The flow of identity verification based on each second service may be the same as the flow described in the embodiment. Which second service to rely on among the plurality of second services may be selected by the user, or may be determined based on a predetermined priority order. The update unit 106 executes an update process based on the second service information obtained from the selected second service. Although it differs from the embodiment in that there are multiple second services, the flow itself of acquiring the second service information from the second service relied on for identity verification of the first service and executing the update process is different from the embodiment. The same is true.

The user information update system 1 of the sixth modification executes an update process based on second service information acquired from a second service selected from a plurality of second services. This increases flexibility when relying on identity verification in the first service.

[5-7. Modification 7]
For example, in Modification 6, it is assumed that the identity verification for the first service is performed based on the second service, which is a bank's financial service. When the user updates the first user information, the second user information registered in other second services may be outdated, so the user is not required to update the second user information in other second services. May be prompted.

The user information update system includes a fourth display control section 114. The fourth display control unit 114 determines whether the new first user information matches the second user information of the selected second service, and the new first user information is registered in another second service. If the second user information of the user who has been provided does not match, the user terminal 30 displays a second proposal screen for proposing an update of the second user information of the other second service. Although illustration of the second proposal screen is omitted, it differs from the first proposal screen G9 in that an update of the second user information of another second service is proposed, but is similar in other respects. It is assumed that the second proposal screen includes links to other second services.

The user information update system 1 of the seventh modification causes the user terminal 30 to display the second proposal screen. This makes it easier for the user to update the second user information of another second service, increasing convenience for the user.

[5-8. Modification 8]
For example, the second service information may be new second user information acquired from the second service when the second user information is updated by the second service. For example, the second server 20 transmits the updated second user information to the first server 10. It is assumed that the first server 10 stores the user ID for the second service. Therefore, the first server 10 is able to specify which user of the first service is the same as which user of the second service.

The second user information may be transmitted from the second server 20 to the first server 10 at any timing. For example, when the second user information is updated in the second service, the second user information may be transmitted from the second server 20 to the first server 10 each time. For example, a list of users whose second user information has been updated on that day may be transmitted from the second server 20 to the first server 10 by processing such as night batch processing.

In addition, for example, when the user updates the second user information, the user inquires whether or not to update the first user information, and when the user performs an operation to update the first user information, the second user information The second user information may be transmitted from the server 20 to the first server 10. In this case, authentication processing for the first service may be performed on the user. This authentication process may be an authentication process using authentication information stored on the first service side, and may be, for example, one-time password authentication, transaction account password authentication, or biometric authentication.

The update unit 106 executes update processing based on the new second user information. The update unit 106 acquires new second user information as new first user information and executes an update process. For example, the update unit 106 may automatically execute the update process without asking the user, or update the update process at the timing when the user logs in to the first service or when the second user information is updated. The update process may be executed after inquiring the user whether or not to execute the process.

In the user information update system 1 of Modification 8, the second service information is new second user information acquired from the second service when the second user information is updated by the second service. This makes it possible to automate the process of updating the first user information, thereby increasing convenience for the user. If the second service performs identity verification when the second user information is updated in the second service, a malicious third party will not be able to successfully verify the identity of the second service. , it is possible to improve user convenience while increasing security.

[5-9. Modification 9]
For example, in addition to the first service, there may be a third service that allows identity verification based on the second service. The flow of identity verification in the third service may be the same as in the first service. In this case, if the user updates the first user information, it seems necessary to also update the third user information registered in the third service.

Therefore, when the user updates the first user information, the third service may be requested to update the third user information. The third service is a service different from the first service and the second service. The third service may be any service exemplified in the description of the first service and the second service. The third user information differs from the first user information and the second user information in that it is user information registered in the third service, but is similar in other respects.

The user information update system includes a second update request section 115. When the update process is executed, the second update requesting unit 115 registers the third service for which identity verification can be performed based on the second service based on the new first user information. requesting an update of the third user information of the specified user. This request is different from the first update request unit 110 described in Modification 1 in that the request is for the third service, but is similar in other respects.

When the update process is executed, the user information update system 1 of Modification 9 updates the third service based on the new first user information with respect to the third service that allows identity verification based on the second service. A request is made to update the third user information of the user registered in the service. Thereby, the effort of the user to update the third user information can be reduced.

[5-10. Other variations]
For example, the modifications described above may be combined.

For example, functions described as being implemented by the first server 10 may be implemented by the second server 20 or another server computer. Functions described as being implemented by the second server 20 may also be implemented by the first server 10 or other server computers. For example, the functions described as being implemented by the first server 10 or the second server 20 may be shared among multiple computers. Each function may be realized by at least one computer.

[6. Additional notes]
For example, the user information update system 1 can also have the following configuration.

(1)
a registration unit that registers first user information of the user in the first service;
a reliance determination unit that determines whether or not the user's identity verification in the first service was performed relying on a second service in which the user completed identity verification;
When it is determined that the user's identity verification in the first service was performed based on the second service, the information regarding the first user information is determined based on the second service information acquired from the second service. an update unit that executes update processing;
User information update system including.
(2)
The user information update system further includes a first user information acquisition unit that acquires new first user information input by the user,
The update section is
Based on the second service information, determine whether the new first user information and second user information of the user registered in the second service match;
performing the update process when it is determined that the new first user information and the second user information match;
The user information update system described in (1).
(3)
the registration unit registers a plurality of pieces of first user information in the first service;
The user information update system further includes an instruction determination unit that determines whether an instruction has been given to update specific first user information among the plurality of first user information,
The update section is
If it is determined that an update of the specific first user information has been instructed, determining whether the new specific first user information and the second user information match;
updating the update process when it is determined that the new specific first user information and the second user information match;
The user information update system described in (2).
(4)
The update section is
determining whether a portion of the new first user information and a portion of the second user information match;
executing the update process when it is determined that a part of the new first user information and a part of the second user information match;
The user information update system according to claim (2) or (3).
(5)
the registration unit registers a plurality of pieces of first user information in the first service;
A plurality of pieces of second user information corresponding to the plurality of pieces of first user information are registered in the second service,
The update section is
The new first user information and the second user information corresponding to the new first user information match, and the other first user information corresponds to the other first user information. and the second user information,
The new first user information and the second user information corresponding to the new first user information match, and the other first user information corresponds to the other first user information. executing the update process if it is determined that the second user information matches the second user information;
The user information update system according to any one of (2) to (4).
(6)
In the second service, when the new first user information is input, an authentication process regarding the user is executed,
The update unit is configured to perform the update process when the authentication process executed by the second service is successful and it is determined that the new first user information and the second user information match. execute,
The user information update system according to any one of (2) to (5).
(7)
The user information update system includes:
a first display control unit that performs display control to display an authentication screen for the second service on the user terminal of the user when the new first user information is input;
a second display control unit that causes the user terminal to display an update completion screen for the first service when the update process is executed;
The user information update system according to (6), further comprising:
(8)
The user information update system performs a comparison that requests the second service to compare the new first user information and the second user information when the new first user information is input. further comprising a request part;
The second service information indicates a comparison result between the new first user information and the second user information,
The updating unit determines whether the new first user information and the second user information match based on the comparison result indicated by the second service information.
The user information update system according to any one of claims (2) to (7).
(9)
The user information update system displays a first proposal screen for proposing an update of the second user information when it is determined that the new first user information and the second user information match. further including a third display control unit that causes the display to be displayed on the user's user terminal;
The user information update system according to any one of (2) to (8).
(10)
The user information update system updates the second service to the second service based on the new first user information when the user agrees to update the second user information on the first proposal screen. further comprising a first update request unit that requests update of user information;
In the second service, when updating of the second user information is requested, the second user information is updated based on the new first user information.
The user information update system described in (9).
(11)
The user information update system further includes a holding unit that holds the new first user information when it is determined that the new first user information and the second user information match,
The update section is
When the second user information is updated in the second service, determining whether the new first user information and the new second user information match;
If it is determined that the new first user information and the new second user information match, executing the update process based on the retained first user information;
The user information update system according to any one of (2) to (10).
(12)
The user information update system further includes a first reconfirmation unit that executes identity confirmation again in the first service when it is determined that the new first user information and the second user information match. including,
The update unit executes the update process when the re-identification is successful.
The user information update system according to any one of (2) to (11).
(13)
The first service also allows for identity verification that does not rely on the second service,
The user information update system includes a second reconfirmation unit that executes identity confirmation again in the first service when executing the update process when identity confirmation that does not rely on the second service is executed. further including;
The update unit executes the update process when the re-identification is successful.
The user information update system according to any one of (1) to (12).
(14)
In the first service, after identity verification that does not rely on the second service is performed, it is possible to perform identity verification that relies on the second service,
If identity verification that relies on the second service is performed after identity verification that does not rely on the second service, the update unit may perform the update process without requiring the identity verification again. is executable,
The user information update system according to (13).
(15)
The first service can perform identity verification based on the second service selected from the plurality of second services,
The update unit executes the update process based on the second service information obtained from the selected second service.
The user information update system according to any one of (1) to (14).
(16)
The user information update system is configured such that the new first user information matches the second user information of the selected second service, and the new first user information matches the other second user information. If the second user information of the user registered in the second service does not match, a second proposal screen for proposing an update of the second user information of the other second service is displayed to the user. further comprising a fourth display control unit that causes the display to be displayed on the user terminal;
The user information update system according to (15).
(17)
The second service information is new second user information obtained from the second service when the second user information is updated by the second service,
The update unit executes the update process based on the new second user information.
The user information update system according to any one of (1) to (16).
(18)
When the update process is executed, the user information update system updates the third service based on the new first user information to a third service that allows identity verification based on the second service. further comprising a second update request unit that requests an update of the third user information of the user registered in the
The user information update system according to any one of (1) to (17).

1 user information update system, N network, 10 first server, 11, 21, 31 control unit, 12, 22, 32 storage unit, 13, 23, 33 communication unit, 20 second server, 30 user terminal, 34 operation unit , 35 Display section, G1 Login screen, G2 Registration screen, G3 Identity confirmation screen, G4 Application completion screen, G5 My page screen, G6 Update screen, G7 Authentication screen, G8 Update completion screen, G9 1st proposal screen G9 My page screen , 100 data storage unit, 101 registration unit, 102 first user information acquisition unit, 103 instruction determination unit, 104 reliance determination unit, 105 comparison request unit, 106 update unit, 107 first display control unit, 108 second display control unit , 109 third display control section, 110 first update request section, 111 holding section, 112 first reconfirmation section, 113 second reconfirmation section, 114 fourth display control section, 115 second update request section, 200 data storage section, 201 authentication section, 202 comparison section, 300 data storage section, 301 display control section, 302 operation reception section, B12, B13, B30, B50, B50A, B50B, B61, B72, B91 button, F10, F20, F60, F70 input form, M90 message.

Claims (20)

a registration unit that registers first user information of the user in the first service;
a reliance determination unit that determines whether or not the user's identity verification in the first service was performed relying on a second service in which the user completed identity verification;
When it is determined that the user's identity verification in the first service was performed based on the second service, the information regarding the first user information is determined based on the second service information acquired from the second service. an update unit that executes update processing;
User information update system including. The user information update system further includes a first user information acquisition unit that acquires new first user information input by the user,
The update section is
Based on the second service information, determine whether the new first user information and second user information of the user registered in the second service match;
performing the update process when it is determined that the new first user information and the second user information match;
The user information update system according to claim 1. the registration unit registers a plurality of pieces of first user information in the first service;
The user information update system further includes an instruction determination unit that determines whether an instruction has been given to update specific first user information among the plurality of first user information,
The update section is
If it is determined that an update of the specific first user information has been instructed, determining whether the new specific first user information and the second user information match;
updating the update process when it is determined that the new specific first user information and the second user information match;
The user information update system according to claim 2. The update section is
determining whether a portion of the new first user information and a portion of the second user information match;
executing the update process when it is determined that a part of the new first user information and a part of the second user information match;
The user information update system according to claim 2 or 3. the registration unit registers a plurality of pieces of first user information in the first service;
A plurality of pieces of second user information corresponding to the plurality of pieces of first user information are registered in the second service,
The update section is
The new first user information and the second user information corresponding to the new first user information match, and the other first user information corresponds to the other first user information. and the second user information,
The new first user information and the second user information corresponding to the new first user information match, and the other first user information corresponds to the other first user information. executing the update process if it is determined that the second user information matches the second user information;
The user information update system according to claim 2 or 3. In the second service, when the new first user information is input, an authentication process regarding the user is executed,
The update unit is configured to perform the update process when the authentication process executed by the second service is successful and it is determined that the new first user information and the second user information match. execute,
The user information update system according to claim 2 or 3. The user information update system includes:
a first display control unit that performs display control to display an authentication screen for the second service on the user terminal of the user when the new first user information is input;
a second display control unit that causes the user terminal to display an update completion screen for the first service when the update process is executed;
The user information update system according to claim 6, further comprising: The user information update system performs a comparison that requests the second service to compare the new first user information and the second user information when the new first user information is input. further comprising a request part;
The second service information indicates a comparison result between the new first user information and the second user information,
The updating unit determines whether the new first user information and the second user information match based on the comparison result indicated by the second service information.
The user information update system according to claim 2 or 3. The user information update system displays a first proposal screen for proposing an update of the second user information when it is determined that the new first user information and the second user information match. further including a third display control unit that causes the display to be displayed on the user's user terminal;
The user information update system according to claim 2 or 3. The user information update system updates the second service to the second service based on the new first user information when the user agrees to update the second user information on the first proposal screen. further comprising a first update request unit that requests update of user information;
In the second service, when updating of the second user information is requested, the second user information is updated based on the new first user information.
The user information update system according to claim 9. The user information update system further includes a holding unit that holds the new first user information when it is determined that the new first user information and the second user information match,
The update section is
When the second user information is updated in the second service, determining whether the new first user information and the new second user information match;
If it is determined that the new first user information and the new second user information match, executing the update process based on the retained first user information;
The user information update system according to claim 2 or 3. The user information update system further includes a first reconfirmation unit that executes identity confirmation again in the first service when it is determined that the new first user information and the second user information match. including,
The update unit executes the update process when the re-identification is successful.
The user information update system according to claim 2 or 3. The first service also allows for identity verification that does not rely on the second service,
The user information update system includes a second reconfirmation unit that executes identity confirmation again in the first service when executing the update process when identity confirmation that does not rely on the second service is executed. further including;
The update unit executes the update process when the re-identification is successful.
The user information update system according to any one of claims 1 to 3. In the first service, after identity verification that does not rely on the second service is performed, it is possible to perform identity verification that relies on the second service,
If identity verification that relies on the second service is performed after identity verification that does not rely on the second service, the update unit may perform the update process without requiring the identity verification again. is executable,
The user information update system according to claim 13. The first service can perform identity verification based on the second service selected from the plurality of second services,
The update unit executes the update process based on the second service information obtained from the selected second service.
The user information update system according to any one of claims 1 to 3. The user information update system is configured such that the new first user information matches the second user information of the selected second service, and the new first user information matches the other second user information. If the second user information of the user registered in the second service does not match, a second proposal screen for proposing an update of the second user information of the other second service is displayed to the user. further comprising a fourth display control unit that causes the display to be displayed on the user terminal;
The user information update system according to claim 2 or 3 . The second service information is new second user information acquired from the second service when the second user information is updated by the second service,
The update unit executes the update process based on the new second user information.
The user information update system according to claim 2 or 3 . When the update process is executed, the user information update system updates the third service based on the new first user information to a third service that allows identity verification based on the second service. further comprising a second update request unit that requests an update of the third user information of the user registered in the
The user information update system according to claim 2 or 3. The computer is
a registration step of registering first user information of the user in the first service;
a reliance determination step of determining whether or not the user's identity verification in the first service was performed relying on a second service in which the user completed identity verification;
When it is determined that the user's identity verification in the first service was performed based on the second service, the information regarding the first user information is determined based on the second service information acquired from the second service. an update step that performs an update process;
How to update user information. a registration unit that registers the first user information of the user in the first service;
a reliance determination unit that determines whether or not the user's identity verification in the first service was performed relying on a second service in which the user completed identity verification;
When it is determined that the user's identity verification in the first service was performed based on the second service, the information regarding the first user information is determined based on the second service information acquired from the second service. an update unit that executes update processing;
A program that allows a computer to function as a computer.

Images