Service providing device, service providing method, and program

Abstract

To provide a service providing device, a service providing method, and a program capable of improving the security of authentication processing using code information.SOLUTION: A service providing device for providing a service to a user in cooperation with an application operating on a terminal device of the user comprises: a service providing section that provides the service to the user who has presented a code image by the application; a management section that manages validity of the code image; and a detection section that detects unauthorized use of the service on the basis of code information read from the code image presented by the user. In a case where a duplication notification indicating that the operation of duplicating the code image in the terminal device has been performed is received from the application, the management section invalidates the code image to be duplicated by the operation.SELECTED DRAWING: Figure 4

Description

[Technical field]

[0001] The present invention relates to a service providing device, a service providing method, and a program. [Background technology]

[0002] Conventionally, electronic payment services have been developed that use a QR code (registered trademark, the same applies below) to authenticate a user who is trying to change the terminal device used to log in to the service (see, for example, Patent Document 1). More specifically, a QR code for authentication is sent to the terminal device before the change, and the QR code is read by the terminal device after the change, thereby authenticating the change of terminal device. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent No. 7104259 Summary of the Invention [Problem to be solved by the invention]

[0004] With conventional technology, there was a possibility that the QR code used for authentication could be duplicated by screen capture, which meant that a third party who obtained the duplicated QR code could pose as the legitimate user and successfully complete authentication fraudulently.

[0005] The present invention has been made in consideration of the above circumstances, and one of its objectives is to provide a service providing device, a service providing method, and a program that can improve the security of authentication processing using code information. [Means for solving the problem]

[0006] One aspect of the present invention is a service providing device that works in cooperation with an application program running on a user's terminal device to provide a predetermined service to the user, the service providing device comprising: a service providing unit that provides the service to a user who presents a code image via the application program; a management unit that manages the validity of the code image; and a detection unit that detects unauthorized use of the service based on code information read from the code image presented by the user, wherein when a copy notification is received from the application program indicating that an operation to copy the code image has been performed on the terminal device, the management unit invalidates the code image that was the subject of the copy by the operation. Effect of the Invention

[0007] According to one aspect of the present invention, it is possible to provide a service providing device, a service providing method, and a program that can improve the security of authentication processing using code information. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram showing an example of a configuration for realizing an electronic payment service. [Diagram 2] This is a sequence diagram (part 1) illustrating the general flow of electronic payment. [Diagram 3] This is a sequence diagram (part 2) illustrating the general flow of electronic payment. [Figure 4] 1 is a configuration diagram of a payment server 100 according to a first embodiment. [Diagram 5] FIG. 13 is a diagram showing an example of the contents of user information 172. [Figure 6] FIG. 13 is a diagram showing an example of the contents of affiliated store / store information 176. [Figure 7] FIG. 13 is a diagram showing an example of the contents of chord related information 178. [Figure 8] FIG. 11 is a diagram illustrating an example of a terminal operation related to a second information linkage. [Figure 9]11 is a sequence chart illustrating an example of a first process flow in the spoofing prevention process. [Figure 10] 13 is a sequence chart illustrating an example of a second process flow in the spoofing prevention process. [Figure 11] FIG. 13 is an image diagram illustrating a situation in which a second process in the spoofing prevention process is executed. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Hereinafter, with reference to the drawings, an embodiment of the service providing device, the service providing method, and the program of the present invention will be described. Various devices for providing services to users and performing internal analysis, such as the "server", "management device", and "information providing device" that will appear below, may be realized by a group of distributed devices, and each device may be operated by a different business operator. Furthermore, the owner of the hardware of the device (the cloud server provider) and the business operator that actually operates the device may also be different. The application program and the payment server work together to provide the electronic payment service. In the following description, the application program is referred to as a payment application. The electronic payment service is a service that supports payments related to the purchase of goods and services at a store. The store is, for example, a physical store (real store) that exists in the real world, but may also include a virtual store for electronic commerce. The virtual store may include one provided by an entity different from the operator of the electronic payment service. In that case, when making a payment for shopping at the virtual store, the screen is controlled to transition to an interface screen of the electronic payment service. In the electronic payment service, the store is treated as belonging to, for example, an affiliated store (brand), and processing such as payment when a purchase is made at the store is mainly performed between the user and the affiliated store. Alternatively, processing such as payment may be carried out between the user and the store.

[0010] [Electronic payment service] Fig. 1 is a diagram showing an example of a configuration for realizing an electronic payment service. The electronic payment service is realized mainly by a payment server 100. The payment server 100 communicates with, for example, one or more user terminal devices 10, one or more first store terminal devices 50, and one or more second store terminal devices 70 via a network NW. The network NW includes, for example, the Internet, a LAN (Local Area Network), a wireless base station, a provider device, and the like.

[0011] The user terminal device 10 is, for example, a portable terminal device such as a smartphone or a tablet terminal. The user terminal device 10 is a computer device having 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, components for realizing these functions are referred to as a camera, a communication device, a touch panel, a CPU (Central Processing Unit), etc. In the user terminal device 10, a processor such as a CPU executes a payment application 20, thereby operating to provide an electronic payment service to a user in cooperation with a payment server 100. The payment application 20 is installed in the user terminal device 10 from, for example, an application store, and controls the camera, communication device, touch panel, etc.

[0012] The first store terminal device 50 is installed, for example, in a store. The first 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 first store terminal device 50 includes a so-called POS (Point of Sale) device, and the product price acquisition function and the optical reading function may be realized by the POS device. The store code image 60 is placed in the store, and is a code image such as a QR code (registered trademark) printed on a paper or plastic medium. The store code image 60 may be displayed on a display placed in the store (which may be the display of a terminal device such as a smartphone).

[0013] The second store terminal device 70 is used by the operator of the affiliated store. The second store terminal device 70 is a smartphone, a tablet terminal, a personal computer, or the like. An interface 72 for affiliated stores runs on the second store terminal device 70. The interface 72 for affiliated stores may be an app for affiliated stores or a browser. The interface 72 for affiliated stores accepts coupon settings and the like made by the operator of the affiliated store and transmits them to the payment server 100. The second store terminal device 70, which is a smartphone, has the function of displaying a code image corresponding to a store code image and reading a code image displayed by the user terminal device 10 by executing the app for affiliated stores.

[0014] The payment server 100 realizes electronic payment based on payment information received from the user terminal device 10 or the first store terminal device 50. The first store terminal device 50 may include a POS device and an affiliated store server, in which case the payment information is sent from the POS device via the affiliated store server to the payment server 100. In the following explanation, no distinction is made between these two and it is assumed that the payment information is sent from the first store terminal device 50.

[0015] 2 and 3 are sequence diagrams illustrating the general flow of electronic payment. There may be two patterns of electronic payment: pattern 1 and pattern 2.

[0016] In the case of pattern 1 (hereinafter referred to as user scan) shown in FIG. 2, the user terminal device 10 with the payment application 20 activated decodes the store code image 60 by the optical reading function (S1). The store code image 60 includes store URL (Uniform Resource Locator) information. This store URL is an electronic payment service domain to which store-identifying information is added, and is associated with an affiliated store ID, a store ID, etc. in the payment server 100 (described later). The payment application 20 transmits the first payment information including the store URL and the account ID to the payment server 100 (S2). The payment server 100 searches for store information (described later) from the affiliated store ID and the store ID corresponding to the store URL, acquires the affiliated store name and the store name information (S3), and transmits it to the payment application 20 (S4). The user inputs the payment amount into the user terminal device 10 on the screen on which the affiliated store name and the store name are displayed (S5). Then, the user terminal device 10 generates second payment information including at least the payment amount, and transmits it to the payment server 100 (S6). The payment server 100 performs electronic payment based on the received second payment information (S7). The payment server 100 then transmits a payment completion notice (information for displaying a payment completion screen) to the payment application 20 (S8), and the payment application 20 displays the payment completion screen (S9). Note that when the store code image 60 is displayed on a display installed in the store, the store code image 60 may include not only the store URL but also information on the payment amount. In this case, the procedure in which the user inputs the payment amount is omitted, and the information on the payment amount is included in the first payment information and transmitted to the payment server 100. Information on the affiliated store name and the store name may be included in the payment completion screen and displayed.

[0017] In the case of pattern 2 (hereinafter referred to as store scan) shown in FIG. 3, when the payment application 20 is started, when a payment operation is performed in the payment application 20, when an automatic update timing (e.g., every minute) occurs, and at other timings, the payment application 20 transmits a request for issuing a one-time code to the payment server 100 (S11). The payment server 100 generates a one-time code (S12) and transmits it to the payment application 20 (S13). The payment application 20 displays a code image such as a QR code or a barcode generated based on the one-time code (S14). The user holds (presents) the display surface of the user terminal device 10 over the first store terminal device 50, and the first store terminal device 50 decodes the code image by an optical reading function and obtains the one-time code, etc. (S15). The first store terminal device 50 then generates payment information including the one-time code, payment amount, affiliated store ID, store ID, etc., and transmits it to the payment server 100 (S16). The payment amount information is acquired in advance by reading a barcode or manually entering it. The payment server 100 identifies the user corresponding to the one-time code based on the received information and performs electronic payment (S17). The payment server 100 then transmits a payment completion notice to the payment application 20 (S18), and the payment application 20 displays a payment completion screen (S19).

[0018] Note that electronic payment may be performed using only one of the above patterns. Furthermore, the "account ID" described in FIG. 2 may be other information (e.g., a phone number) that can be used as user identification information. Furthermore, issuing a one-time code may be omitted in the store scan, and the payment application 20 may display a code image generated based on the user's account ID. In this case, the payment server 100 identifies the user corresponding to the account ID instead of identifying the user corresponding to the one-time code.

[0019] [Payment server] FIG. 4 is a configuration diagram of the payment server 100 according to the first embodiment. The payment server 100 includes, for example, a communication unit 110, a payment content providing unit 120, a payment processing unit 130, an information management unit 140, a login authentication unit 150, and a storage unit 170. The components other than the communication unit 110 and the storage unit 170 are realized by, for example, a hardware processor such as a CPU executing a program (software). Some or all of these components may be realized by hardware (including circuitry) such as an LSI (Large Scale Integration), an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array), or a GPU (Graphics Processing Unit), or may be realized by cooperation between software and hardware. The program may be stored in advance in a storage device (a storage device with a non-transient storage medium) such as an HDD (Hard Disk Drive) or flash memory, or may be stored in a removable storage medium (non-transient storage medium) such as a DVD or CD-ROM, and installed in the storage device by inserting the storage medium into a drive device.

[0020] The storage unit 170 is a HDD, a flash memory, a RAM (Random Access Memory), etc. The storage unit 170 may be a NAS (Network Attached Storage) device that the payment server 100 can access via a network. The storage unit 170 stores information such as user information 172, payment content information 174, affiliated store / shop information 176, and code-related information 178.

[0021] 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.

[0022] The payment content providing unit 120 has, for example, a function of a Web server, and provides information (content) for displaying various screens of the electronic payment service 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 by the user while the content is being played by the payment application 20, and transmits the above-mentioned payment information and the like to the payment server 100.

[0023] The payment processing unit 130 performs payment processing based on the payment information transmitted by the user terminal device 10 or the first store terminal device 50. The payment processing unit 130 performs payment processing while referring to the user information 172.

[0024] FIG. 5 is a diagram showing an example of the contents of the user information 172. The user information 172 is an example of the registration information of a user. The user information 172 is, for example, a user URL, an account ID, a telephone number, a password, as well as information associated with an email address, a user ID, a name, an address, a date of birth, a registration date, a charge balance, a post-payment setting, a post-payment limit, a post-payment usage amount, a post-payment available amount, a payment method setting, a bank account, a credit card number, a charge history information, and a payment history information. The user URL is used for a remittance process between users. When registering for the electronic payment service, it is necessary to register a telephone number and a password. The account ID is issued to the user by the payment server 100, and the user ID is an ID that can be set by the user at will (does not have to be set). Similarly, the email address, and the name, address, and date of birth are information that can be set by the user at will (does not have to be set). The registration date is the date on which the user registered for the electronic payment service (the date on which the account was created). Hereinafter, the user's instance (electronic payment account) to which this information is associated will be referred to as an account.

[0025] The charge balance is information indicating the balance of electronic money that is set by a user by transferring money to an account in advance. The means of transfer include transfer from an ATM (Automatic Teller Machine) of a designated company (bank) and transfer from a registered bank account. The deferred payment setting is information indicating whether or not the setting for enabling electronic payment by deferred payment has been completed, and is set to either "completed" or "not completed." The deferred payment limit is the limit of deferred payment that can be used each month, the deferred payment usage amount is the amount of deferred payment that has already been used in the current month, and the deferred payment available amount is the amount of deferred payment that can be used in the current month, which is calculated by subtracting the deferred payment usage amount from the deferred payment limit. Although only one deferred payment limit is shown in the figure, in reality, there is also a daily upper limit, and the lower of these may be set as the deferred payment limit. Further details of deferred payment will be described later. The payment method setting is setting information indicating whether the user will perform electronic payment using the charge balance or payment by deferred payment at that time. The bank account and credit card number are information on a bank account or credit card number (account number, card number) that can be used to deposit funds into an electronic payment service. Charge history information is a history of the user's previous transfers to the electronic payment service to increase the charge balance. Payment history information is information that indicates the details of payments made by the user for each payment (date and time, store ID of the store where the purchase was made, payment amount, payment method, etc.).

[0026] 6 is a diagram showing an example of the contents of affiliated store / store information 176. The affiliated store / store information 176 includes, for example, a first table 176A in which an affiliated store ID and a store ID are associated with a store URL, a second table 176B in which an affiliated store name and sales amount (described above) are associated with an affiliated store ID, and a third table 176C in which a store ID is associated with a store name. In addition to this information, the affiliated store / store information 176 may also include information such as the category of the affiliated store or store, the location of the store, and payment patterns.

[0027] FIG. 7 is a diagram showing an example of the contents of the code-related information 178. The code-related information 178 includes, for example, a first table 178A in which a user ID is associated with code information, an expiration date, and a code image, and a table 178B in which a source user ID is associated with a reception time, code information, a code image, and source information. The first table 178A is information for managing the code image generated for each user. The code information is information encoded as a code image. “[Image data]” indicates that the image data of the code image is held as the value of the item. The second table 178B is information for managing the code information received from the user terminal device 10. The code image is a means for directly or indirectly linking the code information between the payment application 20 and the payment server 100, and is an image obtained by encoding the code information. The code information includes information for at least identifying the target user and the purpose in the payment server 100. In this embodiment, the purpose of information linking by the code information is assumed to be a payment purpose and a login purpose when changing the terminal.

[0028] The sender user ID is a user ID indicating the user who sent the received code information. The sender user ID is, for example, included in a code image read by the sender user terminal device 10, and is included in the code information sent by the sender user terminal device 10 to the payment server 100. The reception time is the time when the payment server 100 received the code information from the sender user terminal device 10. The received code information is the code information received from the sender user terminal device 10. The received code image is a code image read by the sender user terminal device 10 to acquire the received code information. The sender information is information about the user terminal device 10 that sent the received code information. The sender information includes, for example, information such as an IP address, a MAC address, a terminal model, and a telephone number. Note that the code image is an encoded version of the code information, so that either the code image or the code information may be omitted in the code-related information 178.

[0029] The information management unit 140 manages user information 172, affiliated store / store information 176, and code-related information 178 based on information acquired from the user terminal device 10 and the second store terminal device 70. The information management unit 140 adds new records, edits, deletes, etc. for the user information 172, affiliated store / store information 176, and code-related information 178. The information management unit 140 also has a function to generate a code image from code information and a function to read code information from the code image. The information management unit 140 also has a function to update code information. When the information management unit 140 updates code information, it also updates the code image with the updated code information.

[0030] [Electronic payment] When payment information is acquired from the user terminal device 10 or the first store terminal device 50, the payment processing unit 130 refers to the user information 172 to acquire the "payment method setting" of the user. For a user whose "payment method setting" is set to "charge balance", the payment processing unit 130 performs electronic payment as follows. For example, the payment processing unit 130 performs electronic payment by decreasing the charge balance managed in association with the user ID and increasing the item value of the affiliated store's sales. The item value of the affiliated store's sales is not used as electronic money itself, for example, and an amount corresponding to the item value of the sales is transferred to a bank account in a cycle according to an agreement between the affiliated store and the electronic payment service.

[0031] The payment processing unit 130 performs electronic payment for users whose "setting information" is set to "deferred payment" as follows. Deferred payment is set separately from "credit payment" in cooperation with a credit card company, which is a separate entity from the operator of the electronic payment service, and the operator of the electronic payment service acts as a creditor and allows electronic payment that is not dependent on the charge balance within the deferred payment limit. In order to receive the deferred payment service, a credit card provided by the operator of the electronic payment service may be required. The amount used for deferred payment is settled on the payment date of the following month in a lump sum for one month, for example, by debit from a bank account. In this case, the payment processing unit 130 performs provisional payment by adding the payment amount to the deferred payment amount and subtracting the same amount from the available deferred payment amount, and when the closing date comes, it performs processing to debit the payment for the current month on the payment date of the following month as described above, or requests the operator of the credit card company to perform such processing. In addition, if the payment amount exceeds the available deferred payment amount at the time of provisional payment, an error notification is returned to the payment application 20.

[0032] [Information sharing through code information] The first information linkage based on the code information is information linkage during payment by the store scan method (FIG. 3). As described above, in payment by the store scan method, the payment application 20 generates a code image based on the one-time code received from the payment server 100, and causes the first store terminal device 50 to read the generated code image. The first store terminal device 50 generates payment information based on the one-time code read from the code image, and transmits it to the payment server 100.

[0033] The second information linkage using code information is a linkage of authentication information required for two-factor authentication at a new terminal in a procedure for changing the terminal used for payment application 20 (hereinafter referred to as a "terminal change procedure"). FIG. 8 is a diagram showing an example of terminal operations related to the second information linkage. More specifically, FIG. 8 illustrates an authentication method in which a code image CD1 displayed on a new user terminal device 10B is requested to be read by a new user terminal device 10B as a second factor authentication when logging in to payment application 20 operating on a new user terminal device 10A. Note that the first factor authentication at a new user terminal device 10B may be authentication using a user ID and a password, or may be another authentication method.

[0034] In both the first and second information linkages, if the code information is illegally obtained, the payment app 20 of a legitimate user may be used by another user. For example, in the case of the first information linkage, it is conceivable that a user B1 who illegally obtains a code image of a certain user A1 may have the first store terminal device 50 read the code image of user A1 to make a payment. In this case, the payment means of user A1 will be illegally used by user B1.

[0035] Also, for example, in the case of the second information linkage, assume that user A2 of the new user terminal device 10 illegally obtains the user ID and password of user B2 of the old user terminal device 10 and breaks through the first factor of authentication using the user ID and password of user B2 in the new user terminal device 10. In this case, if user A2 further obtains a code image of user B2, user A2 can break through the second factor of authentication by reading the code image of user B2 with the new user terminal device 10. In this case, user A2 can log in as user B2 in the new user terminal device 10.

[0036] As an example of a method for enabling such unauthorized acquisition of a code image, a method is assumed in which a user of an electronic payment service is led to a phishing site to obtain a screen capture (also called a screenshot) of the code image, and the obtained capture image is sent to the phishing site. The login authentication unit 150 in this embodiment cooperates with the payment application 20 to execute a process for preventing spoofing by unauthorized use of such a code image (hereinafter referred to as "spoofing prevention process").

[0037] FIG. 9 is a sequence chart for explaining an example of the flow of the first process in the spoofing prevention process. The first process is a process for detecting duplication of code information and invalidating the code information for which duplication has been detected. In FIG. 9, the user terminal device 10 is a user terminal device 10 operated by a legitimate user. As a situation in which the first process is executed, for example, a situation is assumed in which a legitimate user who has been guided to a phishing site attempts to obtain a screen capture of a code image according to the instructions of the phishing site. In this case, first, the user operates the user terminal device 10 to cause the payment application 20 to display a code image (S201).

[0038] Next, while the payment application 20 is displaying the code image, the user performs an operation to obtain a screen capture (hereinafter referred to as a "screen capture operation") on the user terminal device 10 (S202). When the payment application 20 detects that a screen capture operation has been performed (S203), it notifies the payment server 100 of the fact (S204: capture detection notification). In this embodiment, the user terminal device 10 is configured to obtain a screen capture by a function of the OS (Operating System). In addition, the OS of the user terminal device 10 is configured to transmit a notification (capture operation notification) that a screen capture operation has been performed to an application program running in the foreground when the OS recognizes a screen capture operation. In this embodiment, the payment application 20 is configured to recognize that the code image has been copied and transmit a capture detection notification to the payment server 100 when a capture operation notification is received while the code image is being displayed.

[0039] Next, in the payment server 100, the information management unit 140 receives the capture detection notification of S204 and invalidates the code image that was the subject of the screen capture (S205). The invalidation of the code image may be realized, for example, by updating the code image, by forcibly expediting the expiration date of the code image, or by setting an invalidation flag on the code image. The information management unit 140 notifies the user terminal device 10 that the code image has been invalidated (S206: invalidation notification). Here, the information management unit 140 is an example of a "detection unit," and the capture detection notification is an example of a "copy notification."

[0040] Next, in the user terminal device 10, the payment application 20 receives the invalidation notification of S206 and displays error information (S207). For example, the error information may be a notification that, when a code image is captured, the captured code image may be sent to a third party and may be used fraudulently. Also, for example, the error information may be a notification that copying of a code image by screen capture is prohibited in the payment application 20, or a notification that the copied code image has been invalidated. By performing such a first process, it is possible to prevent a third party from using the electronic payment service by impersonating a legitimate user through the misuse of a copied code image.

[0041] FIG. 10 is a sequence chart for explaining an example of the flow of the second process in the spoofing prevention process. The second process is a process for detecting fraudulent use of an electronic payment service by a copied code image. In FIG. 10, the first user terminal device 10 and the second user terminal device 30 are terminal devices of a user (fraudulent user) who has fraudulently acquired a screen capture of a code image of a legitimate user. FIG. 11 is an image diagram for explaining a situation in which the second process described in FIG. 10 is executed. Here, as a situation in which the second process is executed, a situation in which a fraudulent code image is read in a terminal to be changed in the second factor authentication during a terminal change procedure is assumed. In the example of FIG. 11, the first user terminal device 10 is a terminal device to be changed, and the second user terminal device 30 is a terminal device for displaying a fraudulently acquired capture image IM1. At the start of the sequence in FIG. 10, the first user terminal device 10 has broken through the first factor authentication for logging in to the payment application 20, and is about to read a code image as second factor authentication information.

[0042] In such a situation, first, the fraudulent user causes the second user terminal device 30 to display a capture image IM1 including a code image CD2 to be read by the first user terminal device 10 (S301). As described above, the capture image IM1 is fraudulently obtained. Next, the fraudulent user causes the payment application 20 operating on the first user terminal device 10 to read the code information by capturing an image of the code image CD2 included in the capture image IM1 displayed on the second user terminal device 30 with the first user terminal device 10 (S302). Hereinafter, the code information read from the code image CD2 is referred to as code information CD2. The payment application 20 transmits the read code information CD2 to the payment server 100 as second-factor authentication information (S303).

[0043] Next, in the payment server 100, the login authentication unit 150 judges whether the sender user is a valid user or not based on the code information CD2 received in S303 (S304). More specifically, the login authentication unit 150 refers to the code related information 178 and recognizes the validity of the received code information. If the code information is validated, the login authentication unit 150 judges that the sender user is a valid user and permits login to the payment application 20 (S305). Here, it is assumed that the sender user is an unauthorized user, so login is not permitted, but if the valid user performs a terminal change procedure, the procedure is completed here.

[0044] On the other hand, if the code information is invalidated, the login authentication unit 150 determines that the user who sent the code is an unauthorized user and does not permit login to the payment application 20. As described above, it is assumed here that the user who sent the code is an unauthorized user. In this case, the code information CD2 read from the capture image IM1 has already been invalidated by the first process when the capture image IM1 was acquired, so an attempt at spoofing by the unauthorized user is detected in S304. In this case, the login authentication unit 150 records information about the unauthorized use as the code-related information 178 (second table) (S306) and transmits information (warning information) for notifying the unauthorized user of a warning to the first user terminal device 10 that is the sender of the code information CD2 (S307). The warning information may include information about the unauthorized use recorded in S306. The payment application 20 of the first user terminal device 10 displays the warning information received from the payment server 100 (S308).

[0045] Here, the case where the code information is invalidated in response to the capture of the code image has been described, but the code information may be invalidated due to a factor other than the screen capture of the code image. In this case, the payment server 100 may be configured to manage the invalidated code information together with the reason. In this case, the payment server 100 may be configured to notify the user of a log-in refusal and warning information when the code information is invalidated and the reason for the invalidation is due to the screen capture of the code image. The payment server 100 may be configured to not permit a log-in when the code information is invalidated, and to notify the user of warning information when the reason for the invalidation is due to the screen capture of the code image.

[0046] In addition to the information described in FIG. 7, the information regarding unauthorized use may include identification information of the terminal device that attempted to log in using the fraudulently obtained capture image (i.e., the invalidated code information), and may also include identification information of the application program that attempted the login.

[0047] In addition, if an attempt at impersonation by a fraudulent user is detected in S304, the payment server 100 may be configured to notify the second user terminal device 30 of the legitimate user of a warning message such as "An attempt has been made to log in to your account using a fraudulent method" instead of / in addition to notifying the first user terminal device 10 of the fraudulent user of warning information (S307, S308).

[0048] According to such second process, it is possible to prevent the code image copied by screen capture from being used illegally. According to the second process of the embodiment, when an attempt at spoofing using an illegally obtained code image is detected, information on the illegal use is recorded. Therefore, the operator of the electronic payment service can identify the illegal user based on the recorded information and consider measures to prevent the illegal use, and can take more appropriate measures against the illegal use.

[0049] According to the embodiment described above, it is possible to improve the security of authentication processing using code information. In the embodiment, a method for detecting or preventing spoofing in a terminal change procedure has been described, but this method is not limited to spoofing in a terminal change procedure, and can be applied to any type of spoofing that involves copying of a code image by screen capture on the user terminal device 10. For example, it can be applied to a code image exchanged in a payment using the store scan method (see FIG. 3). When applied to the store scan method, the code image is invalidated at the time an unauthorized user obtains a screen capture of the code image, so that it is possible to prevent the unauthorized user from misusing the electronic payment account of a legitimate user to make a payment.

[0050] <Modification> The payment server 100 may be configured to perform processing according to the purpose of the code image when invalidating the code image to be captured when a capture detection notification is received from the payment application 20. For example, the purpose of the code image may be included in the code information read from the code image, or may be managed in the payment server 100 in association with the code information. In this case, the payment application 20 reads the code information from the captured code image and transmits it to the payment server 100 together with the capture detection notification, so that the payment server 100 can recognize the purpose of the code information (code image).

[0051] For example, the information management unit 140 may be configured not to invalidate the code information when the use of the code image is a specific use even when a capture detection notification is received. For example, the information management unit 140 may be configured to, when the use of the code image is recognized as a terminal change procedure even when a capture detection notification is received, first confirm with the user that the change destination terminal is at hand, not invalidate the code information when the confirmation is obtained, and invalidate the code information when the confirmation is not obtained. Note that the confirmation that the change destination terminal is at hand may be performed, for example, as follows. First, when the payment server 100 receives a capture detection notification, it causes both the payment application 20 of the change source terminal and the payment application 20 of the change destination terminal to display a screen requesting permission to transmit location information. The payment server 100 may determine that the change destination terminal is at hand when the transmission of location information is permitted in both terminals and the location information is provided, and when both location information indicates a certain range.

[0052] The information management unit 140 may be configured to, when invalidated code information is received from the payment application 20 via the first store terminal device 50 in a payment by the store scan method (see FIG. 3), identify the store where the first store terminal device 50 is installed and include information about the store in the code-related information 178 recorded regarding fraudulent use. The store can be identified by a store ID included in the payment information. Furthermore, when the information management unit 140 receives a capture detection notification, it may be configured to only record that fact (for example, set a flag) for the target code image and not invalidate the code information. Furthermore, when a user uses a code image that has been recorded as having received a capture detection notification in the past, the information management unit 140 may be configured to notify the user via the payment application 20 that the code image may have been copied by screen capture. Furthermore, when the use of the code image is payment, the information management unit 140 may be configured to record information about the affiliated store that is the subject of the payment, the payment amount, and the like, in association with the code information. In this case, when notifying the user that the code image may have been copied by screen capture, the information management unit 140 may be configured to present the user with information regarding payments previously made using the code image (e.g., the affiliated store where the payment was made and the payment amount).

[0053] When an attempt to fraudulently capture a screen of a code image is detected, the payment server 100 may be configured to cooperate with the payment application 20 of the user terminal device 10 where the attempt was made to acquire information about the user terminal device 10. For example, when the user terminal device 10 has a location information acquisition function such as a global positioning system (GPS), the payment server 100 may be configured to cooperate with the payment application 20 to acquire location information of the user terminal device 10. Also, for example, when the user terminal device 10 has a camera, the payment server 100 may be configured to cooperate with the payment application 20 to operate the camera to acquire image data of the surroundings of the user terminal device 10. Also, for example, when the user terminal device 10 has a microphone, the payment server 100 may be configured to cooperate with the payment application 20 to operate a recording function to acquire audio data of the surroundings of the user terminal device 10.

[0054] In the embodiment, the payment application 20 decodes the code image and reads the code information, but the payment server 100 may decode the code image. In this case, the payment application 20 may capture the code image instead of reading the code information from the code image, and transmit the captured code image to the payment server 100.

[0055] The control of the screen displayed by the payment application 20 (decision processing and rendering for switching the display content) may be performed exclusively by the payment application 20, may be performed in cooperation between the payment application 20 and the payment server 100, or may be performed exclusively by the payment server 100.

[0056] The above describes the form for carrying out the present invention using an embodiment, but the present invention is not limited to such an embodiment, and various modifications and substitutions can be made within the scope that does not deviate from the gist of the present invention. [Explanation of symbols]

[0057] 10 User terminal device 20. Payment App 30 Second user terminal device 50 First store terminal device 60 Store Code Image 70 Second store terminal device 72 Merchant Interface 100 Payment Server 110 Communications Department 120 Payment Contents Provider 130 Payment processing unit 140 Information Management Department 150 Login authentication section 170 Storage section 172 User information 174 Payment Content Information 176 Store Information 178 Code Related Information

Claims

1. A service providing device that provides a predetermined service to a user in cooperation with an application program running on a terminal device of the user, a service providing unit that provides the service to a user who presents a code image through the application program; a management unit for managing the validity of the code image; a detection unit that detects fraudulent use of the service based on code information read from a code image presented by the user; Equipped with when a copy notification indicating that an operation of copying the code image has been performed on the terminal device is received from the application program, the management unit invalidates the code image that has been copied by the operation. Service providing device.

2. The code image is used as second-factor authentication information in two-factor authentication when logging in to the service via the application program. The service providing device according to claim 1 .

3. The management unit invalidates the code image by setting an invalid flag for the code image. The service providing device according to claim 1 .

4. the management unit invalidates the code information by forcibly expiring the validity period of the code image ahead of schedule. The service providing device according to claim 1 .

5. The management unit invalidates the code image before the update by updating the code image. The service providing device according to claim 1 .

6. the service provides an electronic payment service to the user; The code image is used as a means for supplying payment information required for payment to the service providing device in the electronic payment service. The service providing device according to claim 1 .

7. The code image is read by a store terminal installed in a store of the affiliated store of the electronic payment service, the store terminal includes the code information read from the code image in the payment information and transmits the same to the service providing device; The service providing device according to claim 6.

8. When the management unit invalidates the code image, the management unit notifies the source of the copy notification. The service providing device according to claim 1 .

9. The management unit identifies the code image that is the subject of the duplication based on the duplication notification, and executes a process according to the purpose of the code image. The service providing device according to claim 1 .

10. the management unit does not invalidate the code information even when the copy notification is received, if the use of the code image is a specific use. The service providing device according to claim 9.

11. the application program reads code information from a code image related to the copy notification, and transmits the read code information together with the copy notification to the service providing device; the management unit recognizes a purpose of the code image based on the code information received from the application program. The service providing device according to claim 9.

12. the service providing unit obtains information read from the code image presented by the application program from a reading device that reads the code image, and provides the service based on the obtained information. The service providing device according to claim 1 .

13. a service providing device for providing a predetermined service to a user in cooperation with an application program running on the user's terminal device, a service providing process for providing the service to a user who presents a code image by the application program; a management process for managing the validity of the code image; A detection process for detecting fraudulent use of the service based on code information read from a code image presented by the user; A service providing method for performing the above, The management process invalidates the code image that has been copied by the operation when the application program notifies the terminal device that an operation for copying the code image has been performed. How we provide services.

14. A service providing device that provides a predetermined service to a user in cooperation with an application program running on the user's terminal device, a service providing process for providing the service to a user who presents a code image by the application program; a management process for managing the validity of the code image; A detection process for detecting fraudulent use of the service based on code information read from a code image presented by the user; A program for executing The management process invalidates the code image that has been copied by the operation when the application program notifies the terminal device that an operation for copying the code image has been performed. program.

Images