JP7247416B1 - Information processing device, information processing method, and program - Google Patents

Abstract

An object of the present invention is to improve the convenience of personal authentication for a user when the user changes the model of a terminal device. A receiving unit that receives, from a first terminal device of a user, a login request to an application or a web service that includes at least first identification information that can uniquely identify the first terminal device; If the first identification information included in the login request does not match the identification information stored in the storage unit in advance and capable of uniquely identifying a terminal device that has logged in to the application or the Web service in the past, the first identification information 1 receiving from the terminal device information indicating whether or not the user possesses a terminal device with a telephone number linked in the past to the usage registration of the application or the web service; An information processing apparatus comprising: an authentication unit that switches a login authentication method for the application or the web service for a terminal device. [Selection drawing] Fig. 3

Description

The present invention relates to an information processing device, an information processing method, and a program.

2. Description of the Related Art Conventionally, there has been known a technique of authenticating a user when the user uses a terminal device to use a web service or an application program. For example, in Patent Document 1, when the terminal identification information is registered in advance in the information processing apparatus, personal authentication is performed only by the terminal identification information, and when the terminal identification information is not registered, password authentication is performed. Techniques for registering terminal identification information later are disclosed.

Japanese Patent Publication No. 2019-517087

However, in the conventional technology, when the user changes the model of the terminal device, there are cases where the convenience of personal authentication is low for the user.

The present invention has been made in consideration of such circumstances, and is an information processing apparatus capable of improving the convenience of identity authentication for the user when the user changes the model of the terminal device. , an information processing method, and a program.

One aspect of the present invention is a receiving unit that receives a login request to an application or a web service that includes at least first identification information that can uniquely identify the first terminal device from a user's first terminal device; When the first identification information included in the received login request does not match the identification information stored in the storage unit in advance and capable of uniquely identifying a terminal device that has logged in to the application or the web service in the past , from the first terminal device, receiving information indicating whether or not the user possesses a terminal device with a telephone number that has been linked to the registration for use of the application or the web service in the past, and according to the received information, and an authentication unit that switches a login authentication method for the application or the web service for the first terminal device.

According to one aspect of the present invention, when a user changes the model of a terminal device, it is possible to improve the convenience of personal authentication for the user.

1 is a diagram showing an example of a configuration for realizing an electronic payment service; FIG. 2 is a diagram exemplifying a rough flow of electronic payment using the payment application 20. FIG. 2 is a configuration diagram of a settlement server 100; FIG. 4 is a diagram showing an example of contents of user information 172. FIG. 8 is a flowchart illustrating an example of login authentication processing; 4 is a diagram showing an example of inquiry processing to the user terminal device 10. FIG. 6 is a flowchart showing an example of SMS authentication processing; FIG. 5 is a sequence diagram showing an example of QR authentication processing; FIG. 10 is a diagram showing an example of a display screen of the second user terminal device 10B displaying a QR code;

Hereinafter, an information processing apparatus, an information processing method, and a program according to the present invention will be described with reference to the drawings. An information processing device is realized by one or more processors. In the following explanation, the information processing device provides an electronic payment service, and is referred to as a "payment server". Any service may be provided. An electronic payment service is a service that supports payment related to purchase of goods and services at a store. A store is, for example, a physical store (actual store) that exists in real space.

<First Embodiment>
[Electronic payment service]
FIG. 1 is a diagram showing an example of a configuration for realizing an electronic payment service. An electronic payment service is implemented centering on the payment server 100 . The settlement server 100 communicates with each of one or more user terminal devices 10 and one or more shop terminal devices 50 via the network NW, for example. The network NW includes, for example, the Internet, a LAN (Local Area Network), wireless base stations, provider devices, and the like.

The user terminal device 10 includes, for example, a portable terminal device such as a smart phone or a tablet terminal. The user terminal device 10, which is a portable terminal device, has at least an optical reading function, a communication function, a display function, an input reception function, and a program execution function. In the following description, configurations for realizing these functions are respectively referred to as a camera, a communication device, a touch panel, a CPU (Central Processing Unit), and the like. In the user terminal device 10, the payment application 20 is executed by a processor such as a CPU, and operates in cooperation with the payment server 100 to provide electronic payment services to the user. The payment application 20 controls a camera, a communication device, a touch panel, and the like.

In the user terminal device 10 , the web browser 30 is executed by a processor such as a CPU to access the web payment service provided by the payment server 100 . The electronic payment by the payment application 20 and the electronic payment by the web browser 30 can be performed using a common charge balance, which will be described later.

The user terminal device 10 further includes, for example, a non-portable terminal device such as a desktop personal computer. The user terminal device 10, which is a non-portable terminal device, has at least a communication function, a display function, an input reception function, and a program execution function. Since the user terminal device 10, which is a non-portable terminal device, does not necessarily have an optical reading function (in other words, the payment application 20 cannot necessarily be executed), the user terminal device 10 includes at least the web browser 30, and the web browser 30 to at least perform electronic payments. The user terminal device 10 including the portable terminal device and the non-portable terminal device is an example of the "first terminal device" and the "second terminal device".

The store terminal device 50 is installed, for example, in a store. The store terminal device 50 is a computer device having at least a product price acquisition function, an optical reading function, a program execution function, and a communication function. The store terminal device 50 includes a so-called POS (Point of Sale) device, and the POS device may realize the product price acquisition function and the optical reading function. The store code image 60 is placed in a store and is a code image such as a QR code (registered trademark) printed on a medium such as paper or plastic. Note that the store code image 60 may be displayed on a display placed at the store.

The payment server 100 realizes electronic payment using the payment application 20 based on the payment information received from the user terminal device 10 or the store terminal device 50 . The settlement server 100 performs electronic settlement, for example, by increasing or decreasing the charge balance managed in association with the user ID (in other words, depositing and withdrawing electronic money). Electronic payment may include those that enable purchase of a larger amount than the charge balance at the time of purchase by methods such as revolving payment and credit payment.

The settlement server 100 further provides a web settlement service that can be used using the web browser 30, as described above. In the web payment service as well, electronic payment is performed by increasing or decreasing the charge balance managed in association with the user ID. It may include the ability to purchase more than the charge balance at the time of purchase. In the present embodiment, for simplicity of explanation, the payment server 100 that provides the electronic payment service via the payment application 20 and the payment server 100 that provides the web payment service via the web browser 30 are used in common. Although described as servers, the servers providing these two services may be separate.

FIG. 2 is a diagram illustrating a general flow of electronic payment using the payment application 20. As shown in FIG. There may be two patterns, pattern 1 and pattern 2, for electronic payment using the payment application 20 . In the case of pattern 1, first, the payment application 20 is activated on the user terminal device 10, and a code image such as a QR code or barcode is displayed. The user holds up (presents) the display surface of the user terminal device 10 to the shop terminal device 50 . The shop terminal device 50 decodes the code image with an optical reading function and acquires information such as an account ID. The shop terminal device 50 then generates payment information including the account ID, payment amount, shop ID, etc., and transmits the payment information to the payment server 100 . The information on the payment amount is acquired in advance by reading a bar code, manually inputting it, or the like. Based on the received information, the settlement server 100 transfers the settlement amount from the user's electronic settlement account to the store's electronic settlement account, thereby completing the settlement process.

In the case of pattern 2, the user terminal device 10 with the payment application 20 activated decodes the store code image 60 by the optical reading function. The store code image 60 includes information such as the store name. The user inputs the settlement amount into the user terminal device 10 on the screen on which the store name and the like are displayed. Then, the user terminal device 10 generates payment information including the account ID, payment amount, store ID, etc., and transmits the payment information to the payment server 100 . The payment server 100 performs payment processing based on the received information. It should be noted that electronic payment may be performed only in one of the above patterns. Also, the "account ID" described in FIG. 2 may be other information (such as a telephone number) that can be used as user identification information.

On the other hand, in the case of the web payment service via the web browser 30, for example, after the user accesses the online shopping site using the web browser 30 and selects an item to purchase, the user logs in to the web payment service, and after logging in, the displayed Execute electronic payment by entering the payment amount on the displayed payment screen. The settlement server 100 performs settlement processing based on the input payment amount.

[Settlement server]
FIG. 3 is a configuration diagram of the settlement server 100. As shown in FIG. The payment server 100 includes, for example, a communication unit 110, a payment content providing unit 120, a payment processing unit 122, a notification unit 124, an authentication unit 126, an information management unit 128, and a storage unit 170. Components other than communication unit 110 and storage unit 170 are implemented by, for example, a hardware processor such as a CPU executing a program (software). Some or all of these components are hardware (circuit part; circuitry) or by cooperation of software and hardware. The program may be stored in advance in a storage device (a storage device with a non-transitory storage medium) such as a HDD (Hard Disk Drive) or flash memory, or may be stored in a removable storage such as a DVD or CD-ROM. It may be stored in a medium (non-transitory storage medium) and installed in the storage device by loading the storage medium into the drive device.

The storage unit 170 is an HDD, flash memory, RAM (Random Access Memory), or the like. The storage unit 170 may be a NAS (Network Attached Storage) device that can be accessed by the settlement server 100 via a network. Information such as user information 172 and payment content information 174 is stored in the storage unit 170 .

The communication unit 110 is a communication interface for connecting to the network NW. The communication unit 110 is, for example, a network interface card. The communication unit 110 has a function as a transmission unit that transmits information via the network NW and a function as a reception unit that receives information via the network NW.

The payment content providing unit 120 has, for example, a function of a web server, and provides information (contents) for displaying various screens of the electronic payment service via the payment application 20 or the web payment service via the web browser 30. Provided to the user terminal device 10 . The payment content providing unit 120 appropriately reads necessary content from the payment content information 174 and provides it to the user terminal device 10 . The user terminal device 10 accepts various inputs from the user while the content is being reproduced by the payment application 20 or the web browser 30, and sends the payment information for the electronic payment service and the payment information for the web payment service to the payment server. Send to 100.

The payment processing unit 122 performs payment processing based on the payment information transmitted from the user terminal device 10 or the shop terminal device 50 . The payment processing unit 122 performs payment processing while referring to the user information 172 .

[User information]
FIG. 4 is a diagram showing an example of the contents of the user information 172. As shown in FIG. The user information 172 is an example of user registration information. The user information 172 includes, for example, an account ID (which may be omitted), a minimum necessary telephone number and password for new registration, an e-mail address, a user ID, a device ID, a charge balance, a bank account , credit card number, charge history information, and settlement history information. Information other than the phone number, password, device ID, charge balance, charge history information, and settlement history information is optional setting information. Hereinafter, a user instance (electronic settlement account) associated with these pieces of information will be referred to as an account. A phone number may be used as a login ID for an electronic payment service.

The user ID is an example of user identification information for the settlement server 100 to identify the user, and is information such as the user's nickname that can be arbitrarily set by the user. The device ID is information for the payment server 100 to identify the user terminal device 10 . The device ID is, for example, ID information assigned by an OS (Operating System) operating on the user terminal device 10 so as to uniquely identify the user terminal device 10 . Further, for example, the device ID may be information generated by combining information such as IMEI (International Mobile Equipment Identifier), information on the manufacturer of the user terminal device 10, and OS ID. The device ID is an example of "first identification information" and "second identification information". Also, the device ID that can be acquired may differ depending on the application of the user terminal device 10 used by the user. For example, in the case of using the electronic payment service via the payment application 20 and the case of using the web payment service via the web browser 30, the device ID acquired by the payment server 100 that provides the payment service is the user's ID. Even if the terminal device 10 is the same, it may be different. As will be described later, the present invention makes it possible to authenticate a single user terminal device 10 even if a single user terminal device 10 is given a different device ID for each access route to a payment service. is.

The charge balance is information indicating the balance of electronic money set by the user transferring money to the account in advance. Methods of remittance include remittance from an ATM (Automatic Teller Machine) of a designated trader (bank), remittance from a registered bank account, and the like. Each of the bank account and credit card number is information (account number, card number) of a bank account or credit card number that can deposit money into the electronic payment service. The charge history information is a history of the user's advance remittance to the electronic payment service to increase the charge balance. The payment history information is information indicating details of payments made by the user (date and time, shop ID of the shop where the purchase was made, payment amount, etc.) for each payment.

[Phishing method]
The user may attempt to log in to the electronic payment service using a terminal device other than the terminal device that has already been authenticated as the terminal device used by the user, such as when changing the model of the smartphone. . In this case, generally, the user inputs the authentication information from the existing terminal device or the new terminal device, and the authentication processing of the new terminal device is performed. However, if the authentication information is illegally acquired by another person, there is a possibility that the user illegally logs into the electronic payment service from the other person's terminal device. Therefore, the present embodiment aims to prevent unauthorized login by others (for example, phishing criminals). Therefore, before describing the details of the processing of the present embodiment, the method of phishing will be described.

Phishing is a fraudulent act to obtain information such as a user's login ID, password, and authentication code via the Internet. In recent years, the number of phishing sites has increased rapidly, and there is no end to the number of victims who are deprived of information such as login IDs, passwords, and authentication codes. This embodiment aims to reduce the number of login attempts by phishing criminals and to discourage phishing criminals from setting up a phishing site by increasing the login strength.

Phishers acquire the user's login ID (telephone number, etc.) and password in the following flow.
(1) A phishing criminal makes a user access a fake login site and enter a login ID and password.
(2) The phisher uses the input login ID and password to attempt to log in to the authorized login site from the terminal device of the phisher. At this time, since the access is from other than the user's terminal device, a message containing the authentication code is sent to the user's terminal device by SMS (Short Message Service) or the like in order to prevent unauthorized access.
(3) The phishing criminal displays a screen prompting the user to enter the authentication code notified by SMS on the fake login site.
(4) The phisher inputs the authentication code entered by the user into the fake login site into the legitimate login site using the terminal device of the phisher, and completes the login.

In the above phishing method, the user incorrectly entered the authentication code on the fake login site, and the phishing user used his/her own terminal device different from the user terminal device 10 and the stolen authentication code. The problem is that the login is completed by Therefore, in the present embodiment, the device ID transmitted to the payment server 100 when the user terminal device 10 accesses the payment application 20 or the login screen of the web payment service, and the device ID described in the SMS (Short Message Service) notification The user terminal device 10 is authenticated by collating it with the device ID sent to the settlement server 100 when the URL (Uniform Resource Locator) is clicked. As a result, the device ID sent when the phishing terminal device accesses the login screen differs from the device ID sent when the user terminal device 10 clicks on the URL described in the SMS notification. Phishing can be prevented. Furthermore, since the authentication of this embodiment can be executed using only one terminal device, for example, it is convenient for users who have only one terminal device in the new environment due to model change or the like. can also be improved. Details of the present embodiment will be described below.

[Login authentication process]
FIG. 5 is a flowchart illustrating an example of login authentication processing. The processing according to this flowchart is executed by the settlement server 100 . First, the communication unit 110 of the payment server 100 receives a login request to the payment application 20 or the web payment service from the user terminal device 10 (S11). The login request includes information such as login ID (telephone number, etc.), password, and device ID. Hereinafter, the user terminal device 10 that has sent the login request will be referred to as the "first user terminal device 10A".

Next, the authentication unit 126 compares the login ID (telephone number, etc.) and password included in the login request with the user information 172 to determine whether or not login authentication has succeeded (S12). Specifically, the authentication unit 126 determines that the login ID (telephone number, etc.) included in the login request is registered in the user information 172 and the password included in the login request matches the password included in the user information 172. If so, it is determined that the login authentication has succeeded. On the other hand, the authentication unit 126 determines that the login ID (telephone number, etc.) included in the login request is not registered in the user information 172, or the password included in the login request does not match the password included in the user information 172. In this case, it is determined that login authentication has failed.

If the authentication unit 126 determines that the login authentication has failed, the authentication unit 126 transmits a login failure notification to the first user terminal device 10A (S13), and ends the processing according to this flowchart.

On the other hand, when the authentication unit 126 determines that the login authentication has succeeded, the authentication unit 126 compares the device ID included in the login request with the user information 172 to determine whether the login is from the new environment ( S14). Here, the new environment means a terminal device that has not been authenticated as a terminal device used by the user. Also, the existing environment means a terminal device that has already been authenticated as a terminal device used by the user.

Specifically, when the device ID included in the login request and the device ID included in the user information 172 do not match, the authentication unit 126 determines that the login is from the new environment. On the other hand, if the device ID included in the login request matches the device ID included in the user information 172, the authentication unit 126 determines that the login is from the existing environment.

If the authentication unit 126 determines that the login is not from the new environment (that is, if it is determined that the login is from the existing environment), it transmits a login success notification to the first user terminal device 10A (S15), The processing according to this flowchart ends.

On the other hand, when the authentication unit 126 determines that the login is from the new environment, the authentication unit 126 determines that the first user terminal device 10A has only one user terminal that uses the payment application 20 or the web payment service. (S16). In step S16, when receiving information from the first user terminal device 10A that the number of terminals using the payment application 20 or the web payment service is only one, the authentication unit 126 performs SMS authentication processing described later. (S17). On the other hand, when it is determined in step S16 that the number of terminals using the payment application 20 or the web payment service is not only one, the authentication unit 126 executes QR authentication processing, which will be described later (S18). This completes the processing of this flowchart.

In step S16 above, the authentication unit 126 inquires of the first user terminal device 10A whether or not the number of terminals using the payment application 20 or the web payment service is only one. This is a process for confirming whether the user has a terminal with the telephone number linked to the user registration for the electronic payment service (user information 172) (i.e., if there is only one terminal, this means that the user does not have a terminal with the phone number linked to the user registration). Therefore, the authentication unit 126 may more directly inquire whether the user has an old terminal that used the electronic payment service in the past.

FIG. 6 is a diagram showing an example of inquiry processing to the first user terminal device 10A. As shown in FIG. 6, when the authentication unit 126 determines that the login is from the new environment, for example, the first user terminal device 10A selects whether or not the number of terminals to be used is only one. Send an inquiry screen for In FIG. 6, button B1 represents a button for selecting only one terminal, and button B2 represents a button for selecting multiple terminals. . The first user terminal device 10A, for example, when the user clicks the button B1 on the first user terminal device 10A, the settlement server 100 sends information indicating that the number of terminals used is only one. At the same time, the user clicks the button B2 on the first user terminal device 10A to transmit information indicating that there are multiple terminals to be used to the settlement server 100. FIG. As a result, the authentication unit 126 can determine whether or not the number of used terminals is only one in step S16 of the flowchart of FIG.

[SMS authentication process]
FIG. 7 is a flowchart showing an example of SMS authentication processing. The processing according to this flowchart is executed by the settlement server 100 when it is determined in step S16 of the flowchart of FIG. 5 that the number of terminals used is only one.

First, the authentication unit 126 determines whether the login request received in step S11 of the flowchart of FIG. 5 was received via the payment application 20 or via the web browser 30 (S21 ). If the received login request is determined to have been received via the payment application 20, the notification unit 124 sends the URL for accessing the payment application 20, that is, accesses the payment server via the payment application 20 or provides information An SMS notification describing a URL for transmission is transmitted to the user terminal device 10 associated with the telephone number registered in the user information 172 (S22). On the other hand, if the received login request is determined to have been received via the Web browser 30, the notification unit 124 accesses the URL for accessing the Web payment service, that is, accesses the payment server via the Web browser. Alternatively, an SMS notification describing a URL for information transmission is transmitted to the user terminal device 10 associated with the telephone number registered in the user information 172 (S23). Hereinafter, the user terminal device 10 associated with the telephone number registered in the user information 172 will be referred to as "second user terminal device 10B". With such a configuration, the payment service can be accessed with the same application as the application when the user sent the login request in step S11. In other words, even if a single user terminal device 10 is assigned a different device ID for each access route to the payment service, the user terminal device 10 can be authenticated.

Next, when the user clicks on the URL described in the SMS notification sent to the second user terminal device 10B, the authentication unit 126 receives the device ID from the second user terminal device 10B in response to the click. is received (S24). Next, the authentication unit 126 determines whether or not the device ID of the first user terminal device 10A and the device ID of the second user terminal device 10B match (S25). When it is determined that the device ID of the first user terminal device 10A and the device ID of the second user terminal device 10B match, the authentication unit 126 instructs the first user terminal device 10A to use the payment application 20 or the web payment service. is permitted (S26). Next, the information management unit 128 updates the user information 172 (S27). Specifically, the information management unit 128 converts the device ID included in the login request transmitted from the first user terminal device 10A (that is, the device ID of the first user terminal device 10A) into the login request included in the login request. It is written in the user information 172 in association with an ID (telephone number, etc.). On the other hand, when it is determined that the device ID of the first user terminal device 10A and the device ID of the second user terminal device 10B do not match, the authentication unit 126 executes QR authentication processing, which will be described later (S27). This completes the processing of this flowchart.

In step S25, the authentication unit 126 determines whether or not the device ID acquired when requesting login matches the device ID acquired when the URL described in the SMS notification is clicked. there is At this time, the authentication unit 126 may receive the device ID from the payment application 20 when requesting login, and may receive the device ID from the web browser 30 when the URL described in the SMS notification is clicked. In other words, while the payment application 20 is installed in the first user terminal device 10A, the payment application 20 is not installed in the second user terminal device 10B. It means that the web browser 30 has started up. In other words, this means that the first user terminal device 10A and the second user terminal device 10B are different. 10A and the second user terminal device 10B may proceed to the QR authentication process.

[QR authentication process]
FIG. 8 is a sequence diagram showing an example of QR authentication processing. The process of the sequence diagram shown in FIG. 8 is performed when it is determined that there are a plurality of user terminal devices in step S16 of the flowchart of FIG. is executed when

First, the communication unit 110 of the settlement server 100 transmits an SMS notification to the second user terminal device 10B (S31). SMS notification is notification by a short message using the user's phone number. The SMS notification includes a URL (Uniform Resource Locator) for accessing the payment application 20 or web payment service. Alternatively, the communication unit 110 of the payment server 100 may send a push notification describing the URL to the payment application 20 of the second user terminal device 10B.

Upon receiving the SMS notification from the settlement server 100, the second user terminal device 10B transmits information indicating that the user has clicked on the URL described in the SMS notification to the settlement server 100 (S32). Next, the authentication unit 126 of the settlement server 100 generates a QR code in which the authentication information is coded (S33). For example, the authentication information may be time-limited information such as a one-time password. Also, the authentication unit 126 transmits the generated QR code from the communication unit 110 to the second user terminal device 10B (S34). When receiving the QR code from the payment server 100, the second user terminal device 10B displays the QR code on the screen of the payment application 20 (S35).

FIG. 9 is a diagram showing an example of the display screen of the second user terminal device 10B on which the QR code is displayed. As shown in FIG. 9, on the display screen of the second user terminal device 10B, a QR code C and a message such as "Please read the QR code with the new terminal" are displayed.

Next, the first user terminal device 10A in the new environment captures the QR code displayed on the second user terminal device 10B (S36). Specifically, the user uses the camera of the first user terminal device 10A to photograph the QR code displayed on the second user terminal device 10B.

Also, the first user terminal device 10A acquires authentication information by decoding the captured QR code (S37). Then, the first user terminal device 10A transmits the acquired authentication information to the settlement server 100 (S38).

When the communication unit 110 of the settlement server 100 receives the authentication information from the first user terminal device 10A, the authentication unit 126 of the settlement server 100 performs verification processing of the authentication information (S39). Specifically, the authentication unit 126 determines whether or not the authentication information included in the QR code sent to the second user terminal device 10B matches the authentication information received from the first user terminal device 10A. . If the authentication information included in the QR code sent to the second user terminal device 10B does not match the authentication information received from the first user terminal device 10A, the authentication unit 126 sends a login disapproval notice to the communication unit 110. to the first user terminal device 10A.

On the other hand, if the authentication information included in the QR code transmitted to the second user terminal device 10B matches the authentication information received from the first user terminal device 10A, the authentication unit 126 sends a login permission notice to the communication unit. 110 to the first user terminal device 10A (S110). As a result, login from the first user terminal device 10A in the new environment is permitted.

After that, the information management unit 128 updates the user information 172 (S111). Specifically, the information management unit 128 converts the device ID included in the login request transmitted from the first user terminal device 10A (that is, the device ID of the first user terminal device 10A) into the login request included in the login request. It is written in the user information 172 in association with an ID (telephone number, etc.). This completes the processing of this flowchart.

Note that in the present embodiment, the authentication unit 126 executes QR authentication processing when there are multiple terminals to be used or when SMS authentication fails. However, the present invention is not limited to such a configuration, and when there are a plurality of terminals to be used, or when SMS authentication fails, an SMS notification describing an authentication code (for example, a 4-digit PIN code) is sent first. 2 may be transmitted to the user terminal device 10B, and the user may enter the authentication code on the first user terminal device 10A and transmit it to the settlement server 100 for authentication. Thereby, even if the first user terminal device 10A does not have a camera photographing function, the authentication process can be executed. If the QR authentication process fails, the authentication process using the authentication code described above may be executed. For example, the screen on which the QR code of FIG. 9 is displayed may be configured to display a transition button when the QR code cannot be read by another terminal, and to display the authentication code.

Furthermore, if it is determined in step S14 of FIG. 5 that the login is from the new environment, the settlement server 100 omits the processing of step S16 and directly proceeds to step S18 to proceed to the processing of the sequence diagram of FIG. You can move. In that case, in step S32 of the sequence diagram of FIG. 8, the authentication unit 126 of the settlement server 100 acquires the device ID of the second user terminal device 10B, and compares it with the device ID acquired in step S11 of FIG. do. If these two device IDs match, the authentication unit 126 may permit login from the first user terminal device 10A. Such a configuration saves the user the trouble of responding to the inquiry in step S16.

According to the present embodiment described above, even if the user has only one terminal device in the new environment due to a model change or the like, the device ID acquired at the time of login request and the SMS notification If the device ID obtained when clicking the URL described in the above matches the device ID, the authentication of the user is completed. As a result, when the user changes the model of the terminal device, it is possible to improve the convenience of personal authentication for the user.

As described above, the mode for carrying out the present invention has been described using the embodiments, but the present invention is not limited to such embodiments at all, and various modifications and replacements can be made without departing from the scope of the present invention. can be added.

10 User terminal device 20 Payment application 30 Web browser 50 Store terminal device 60 Store code image 100 Payment server 110 Communication unit 120 Payment content providing unit 122 Payment processing unit 124 Notification unit 126 Authentication unit 128 Information management unit 170 Storage unit

Claims (13)

a receiving unit that receives, from a user's first terminal device, a login request to an application or a web service that includes at least first identification information that can uniquely identify the first terminal device;
When the first identification information included in the received login request does not match the identification information stored in the storage unit in advance and capable of uniquely identifying a terminal device that has logged in to the application or the web service in the past , from the first terminal device, receiving information indicating whether or not the user possesses a terminal device with a telephone number that has been linked to the registration for use of the application or the web service in the past, and according to the received information, an authentication unit that switches a login authentication method for the application or the web service for the first terminal device,
Information processing equipment. The information indicating whether or not the user owns a terminal device with a telephone number that has been linked to the usage registration of the application or the web service in the past is whether or not the number of terminals currently used by the user is more than one. is information indicating whether
The information processing device according to claim 1 . The information indicating whether or not the user owns a terminal device with a telephone number that has been linked to the usage registration of the application or the Web service in the past is the terminal device with which the user has used the application or the Web service in the past. It is information indicating whether or not it is held,
The information processing device according to claim 1 . When the first identification information and the identification information do not match, the authentication unit provides the first terminal device with a phone number associated with the application or web service used by the user in the past. and, as a result of the inquiry, information indicating whether or not the user owns a terminal device with a telephone number that has been linked to the usage registration of the said application or said web service in the past. receive,
The information processing apparatus according to claim 2 or 3. wherein the application or the web service is a web service for realizing electronic payment using the terminal device of the user;
The information processing device according to claim 1 . Accessing the app or the web service when receiving from the first terminal device information indicating that the user does not have a terminal device with a phone number that has been linked to the registration for use of the app or the web service in the past A notification unit that notifies the second terminal device of the user linked to the identification information stored in advance in the storage unit,
The information processing device according to claim 1 . When the second terminal device attempts to access the application or the web service via the address, the authentication unit transmits second identification information that can uniquely identify the second terminal device to the second terminal device. received from the terminal device, determines whether the first identification information and the second identification information match, and if it is determined that the first identification information and the second identification information match, the allowing the first terminal device to log in to the app or the web service;
The information processing device according to claim 6 . When receiving, from the first terminal device, information indicating that the user possesses a terminal device with a telephone number that has been previously linked to the application or the Web service usage registration, the authentication unit receives from the first terminal device Execute authentication processing that requires information exchange between the device and the second terminal device of the user linked to the identification information stored in advance in the storage unit,
The information processing device according to claim 1 . The authentication unit generates code information in which authentication information is coded as authentication processing that requires the exchange of information, and transmits the code information to the second terminal device, and the first terminal device captures the code information. and decode the authentication information from the first terminal device, and when the received authentication information matches the transmitted authentication information, the first terminal device receives the application or the allow login to web services,
The information processing apparatus according to claim 8 . The authentication unit transmits authentication information to the second terminal device as an authentication process requiring the exchange of information, and authenticates the authentication information input to the first terminal device by the user to the first terminal device. and if the received authentication information and the transmitted authentication information match, the first terminal device is permitted to log in to the application or the web service,
The information processing apparatus according to claim 8 . When it is determined that the first identification information and the second identification information do not match, the authentication unit performs the usage associated with the identification information stored in advance in the storage unit and the first terminal device. perform authentication processing that requires information exchange with the second terminal device of the person,
The information processing apparatus according to claim 7. the computer
receiving, from a first terminal device of a user, a login request to an application or a web service that includes at least first identification information that can uniquely identify the first terminal device;
When the first identification information included in the received login request does not match the identification information stored in the storage unit in advance and capable of uniquely identifying a terminal device that has logged in to the application or the web service in the past , from the first terminal device, receiving information indicating whether or not the user possesses a terminal device with a telephone number that has been linked to the registration for use of the application or the web service in the past, and according to the received information, switching the login authentication method for the application or the web service for the first terminal device;
Information processing methods. to the computer,
receiving from a user's first terminal device a request to log in to an app or web service that includes at least first identification information that can uniquely identify the first terminal device;
When the first identification information included in the received login request does not match the identification information stored in the storage unit in advance and capable of uniquely identifying a terminal device that has logged in to the application or the web service in the past , from the first terminal device, receiving information indicating whether or not the user possesses a terminal device with a telephone number that has been linked to the registration for use of the application or the web service in the past, and according to the received information, switching the login authentication method for the application or the web service for the first terminal device;
program.

Images