Information processing apparatus, information processing method, program, and system

Abstract

To provide an information processing apparatus, an information processing method, a program, and a system capable of ensuring the consistency of personal information when the personal information is linked among a plurality of organizations and services. 【Solution means】In a configuration where a settlement server communicates with each of one or more user terminal devices, one or more first store terminal devices, one or more second store terminal devices 7, and one or more service servers via a network NW to realize an electronic settlement service, the settlement server includes an acquisition unit 142 that acquires update information indicating an update of identification information regarding a user stored in a storage unit 170 from the user terminal device of a user of the electronic settlement service, an update unit 148 that updates the identification information stored in the storage unit 170 based on the acquired update information, and a notification unit 150 that notifies one or more service servers that provide a service different from the electronic settlement service of the update of the identification information.

Description

Technical Field

[0001] The present invention relates to an information processing apparatus, an information processing method, a program, and a system.

Background Art

[0002] Conventionally, a technique for linking personal information of users among a plurality of organizations and services has been known. For example, Patent Document 1 discloses a technique for linking personal information held by a plurality of organizations respectively, calculating the reliability of each organization based on the linked personal information, and presenting information provided by an organization with high reliability to data users.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, in the conventional technology, when personal information is linked among a plurality of organizations and services, the consistency of the personal information may not be ensured.

[0005] The present invention has been made in consideration of such circumstances, and an object thereof is to provide an information processing apparatus, an information processing method, a program, and a system capable of ensuring the consistency of personal information when the personal information is linked among a plurality of organizations and services.

Means for Solving the Problems

[0006] One aspect of the present invention is an information processing apparatus including: an acquisition unit that acquires update information indicating an update of identification information regarding a user, stored in a storage unit, from a user terminal device of a user of an electronic payment service; an update unit that updates the identification information stored in the storage unit based on the update information; and a notification unit that notifies one or more service servers providing a service different from the electronic payment service of the update of the identification information.

Advantages of the Invention

[0007] According to one aspect of the present invention, it is possible to provide an information processing apparatus, an information processing method, a program, and a system that can ensure the consistency of personal information when the personal information is linked among a plurality of organizations and services.

Brief Description of the Drawings

[0008]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Mode for Carrying Out the Invention

[0009] Hereinafter, with reference to the drawings, embodiments of an information processing apparatus, an information processing method, a program, and an application program of the present invention will be described. Various apparatuses such as "server", "management apparatus", and "information providing apparatus" that provide services to users or perform internal analysis may be realized by a decentralized group of apparatuses, and the operators of each apparatus may be different. Also, the holder of the hardware of the apparatus (provider of the cloud server) and the operator who actually operates the apparatus may be different. The application program and the payment server cooperate to provide an 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 payment for the purchase of goods and services in a store. The store is, for example, a physical store (actual store) existing in the real space, but may include a virtual store for e-commerce. The virtual store may include those provided by a subject different from the operator of the electronic payment service. In that case, when making a purchase payment in the virtual store, it may be controlled to transition to the interface screen of the electronic payment service. In the electronic payment service, the store is, for example, treated as belonging to a franchise (brand), and processing such as payment when a purchase action is performed in the store is mainly performed between the user and the franchise. Alternatively, processing such as payment may be performed 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 centering around a payment server 100. The payment server 100 communicates with, for example, each of one or more user terminal devices 10, one or more first store terminal devices 50, one or more second store terminal devices 70, and one or more service servers 200 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, the configurations for realizing these functions are respectively referred to as a camera, a communication device, a touch panel, a CPU (Central Processing Unit), etc. In the user terminal device 10, the payment application 20 is executed by a processor such as a CPU, and thus operates to provide an electronic payment service to the user in cooperation with the payment server 100. The payment application 20 is installed in the user terminal device 10 from, for example, an application store, and controls a camera, a communication device, a 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. Note that the store code image 60 may be displayed by a display placed in the store (which may be a display of a terminal device such as a smartphone).

[0013] The second store terminal device 70 is used by the operator of the franchise store. The second store terminal device 70 is a smartphone, a tablet terminal, a personal computer, or the like. In the second store terminal device 70, an interface 72 for franchise stores operates. The interface 72 for franchise stores may be a franchise store application or a browser. The interface 72 for franchise stores accepts settings of coupons and the like by the operator of the franchise store and transmits them to the settlement server 100. The second store terminal device 70 which is a smartphone has functions of displaying a code image corresponding to a store code image or reading a code image displayed by the user terminal device 10 by executing a franchise store application.

[0014] The settlement server 100 realizes electronic settlement based on the settlement 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 a franchise store server. In that case, the settlement information is transmitted from the POS device to the settlement server 100 via the franchise store server. In the following description, without particularly distinguishing this, it is assumed that the settlement information is transmitted from the first store terminal device 50.

[0015] The service server 200 provides services operated by an operation entity different from the electronic settlement service. The service server 200 may provide the service as a mini application described later on the electronic settlement service, or may provide it to the user terminal device 10 as its own website or application program. Here, the service may include, for example, an online shopping service (such as a shopping mall service, a reuse EC service, etc.), a food service (such as delivery, takeout, etc.), a financial service (such as investment, insurance, etc.), and various forms of services that can be provided through an application or the web.

[0016] FIG. 2 and FIG. 3 are sequence diagrams illustrating a rough flow of electronic settlement. There may be two patterns, pattern 1 and pattern 2, in the electronic settlement.

[0017] In the case of pattern 1 shown in FIG. 2 (hereinafter referred to as user scan), the user terminal device 10 in the state where the payment application 20 is activated decodes the store code image 60 by the optical reading function (S1). The store code image 60 includes information on the store URL (Uniform Resource Locator). This store URL is obtained by adding information capable of identifying the store to the domain of the electronic payment service, and is associated with a franchise store ID, a store ID, etc. in the payment server 100 (described later). The payment application 20 transmits 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 franchise store ID and the store ID corresponding to the store URL, obtains information on the franchise store name and the store name (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 where the franchise 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 an electronic payment based on the received second payment information (S7). Then, the payment server 100 transmits a payment completion notification (information for displaying a payment completion screen) to the payment application 20 (S8), and the payment application 20 displays the payment completion screen (S9). When the store code image 60 is displayed by a display placed 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 for the user to input 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 franchise store name and the store name may be included and displayed on the payment completion screen.

[0018] In the case of Pattern 2 shown in FIG. 3 (hereinafter referred to as store scan), when the settlement application 20 is launched, when an operation to make a payment is performed in the settlement application 20, when the timing of automatic update (for example, every minute) is reached, and at other timings, the settlement application 20 sends a request for issuing a one-time code to the settlement server 100 (S11). The settlement server 100 generates a one-time code (S12) and sends it to the settlement application 20 (S13). The settlement application 20 displays a code image such as a QR code or a barcode generated based on the one-time code (S14). The user shields (presents) the display surface of the user terminal device 10 against the first store terminal device 50, and the first store terminal device 50 decodes the code image by means of an optical reading function and acquires a one-time code or the like (S15). Then, the first store terminal device 50 generates settlement information including a one-time code, a settlement amount, a franchise store ID, a store ID, etc., and sends it to the settlement server 100 (S16). The information on the settlement amount has been acquired in advance by barcode reading, manual input, or the like. The settlement server 100 identifies the user corresponding to the one-time code based on the received information and performs an electronic settlement (S17). Then, the settlement server 100 sends a settlement completion notification to the settlement application 20 (S18), and the settlement application 20 displays a settlement completion screen (S19).

[0019] Note that the electronic settlement may be performed in only one of the above patterns. Also, the "account ID" described in FIG. 2 may be other information (for example, a telephone number) that can be used as identification information of the user. Further, in the store scan, the issuance of the one-time code may be omitted, and the settlement application 20 may display a code image generated based on the user's account ID. In that case, instead of identifying the user corresponding to the one-time code, the settlement server 100 identifies the user corresponding to the account ID.

[0020] [Settlement Server] FIG. 4 is a configuration diagram of the settlement server 100. The settlement server 100 includes, for example, a communication unit 110, a settlement content providing unit 120, a settlement processing unit 130, an information management unit 140, and a storage unit 170. Components other than the communication unit 110 and the storage unit 170 are realized, for example, by a hardware processor such as a CPU executing a program (software). Some or all of these components may be realized by hardware (including a circuit unit; circuitry) such as LSI (Large Scale Integration), ASIC (Application Specific Integrated Circuit), FPGA (Field-Programmable Gate Array), or GPU (Graphics Processing Unit), or may be realized by the cooperation of software and hardware. The program may be stored in advance in a storage device (a storage device having a non-transitory storage medium) such as an HDD (Hard Disk Drive) or a flash memory, or may be stored in a removable storage medium (a non-transitory storage medium) such as a DVD or a CD-ROM, and may be installed in the storage device when the storage medium is mounted on a drive device. The information management unit 140 further includes an acquisition unit 142, a display control unit 144, an authentication unit 146, an update unit 148, a notification unit 150, and a setting unit 152. Details of these functional units will be described later. The information management unit 140 is an example of the "information processing device" in the claims.

[0021] The storage unit 170 is an HDD, a flash memory, a RAM (Random Access Memory), or the like. The storage unit 170 may be a NAS (Network Attached Storage) device accessible by the settlement server 100 via a network. Information such as user information 172, settlement content information 174, franchise / store information 176, and update notification target table 178 is stored in the storage unit 170.

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

[0023] The settlement content providing unit 120 has, for example, the function of a web server and provides information (content) for displaying various screens of the electronic settlement service to the user terminal device 10. The settlement content providing unit 120 appropriately reads necessary content from the settlement content information 174 and provides it to the user terminal device 10. The user terminal device 10 receives various inputs by the user in a state where the content is reproduced by the settlement application 20, and transmits the above-mentioned settlement information and the like to the settlement server 100.

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

[0025] FIG. 5 is a diagram showing an example of the content of user information 172. The user information 172 is an example of the registration information of the user. The user information 172 includes, for example, a user URL, an account ID, a phone number, a password, as well as an email address, a user ID, name, address, date of birth, nationality, occupation, registration date, presence or absence of identity verification, remaining charge balance, credit payment setting, credit payment limit, credit payment usage amount, available credit payment amount, payment method setting, bank account, credit card number, charge history information, payment history information, and other information associated with each other. The user URL is used for money transfer processing between users. When newly registering for the electronic payment service, it is mandatory to register a phone 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 the user can optionally set (it is not necessary to set it). Similarly, the email address, name, address, date of birth, nationality, and occupation are information that the user can optionally set (it is not necessary to set it). The registration date is the date when the user registered for the electronic payment service (the date when the account was created). Identity verification means, for example, information indicating whether the user has completed identity verification by uploading his or her identity verification documents (for example, a public identity certificate such as a driver's license) to the payment server 100 using the payment application 20 to prove the authenticity of the name, address, date of birth, etc., and is set to either "completed" or "not completed". When the identity verification is "completed", the user can, for example, withdraw the remaining charge balance to the bank account as described below. Hereinafter, an instance of the user (electronic payment account) with these pieces of information associated with each other is referred to as an account.

[0026] The remaining balance of the charge indicates the information on the remaining balance of the electronic money set by the user's prior transfer to the account. As means of transfer, there are transfers from the ATM (Automatic Teller Machine) of a designated business operator (bank), transfers from a registered bank account, etc. The credit payment setting indicates whether the setting for enabling electronic settlement by credit payment has been completed or not, and is set to either "completed" or "not completed". The credit payment limit is the limit amount of credit payment available per month. The amount of credit payment used is the amount of credit payment already used in the current month. The available amount of credit payment is the amount of credit payment available in the current month, which is obtained by subtracting the amount of credit payment used from the credit payment limit. Although only one credit payment limit is shown in the figure, in reality, there are further upper limits per day, etc., and the lower of them may be set as the credit payment limit. Further details of the credit payment will be described later. The settlement method setting is the setting information indicating whether the user performs electronic settlement using the remaining balance of the charge or performs settlement by credit payment at that time. Each of the bank account and the credit card number is the information (account number, card number) of the bank account or credit card number that can receive deposits for the electronic settlement service. The charge history information is the history of the user's prior transfer to the electronic settlement service to increase the remaining balance of the charge. The settlement history information is the information showing the breakdown of the settlements made by the user (date and time, store ID of the store where the purchase action was taken, settlement amount, settlement method, etc.) for each settlement.

[0027] Figure 6 is a diagram showing an example of the content of the 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 the store URL, a second table 176B in which an affiliated store name and the sales amount (described above) are associated with the affiliated store ID, and a third table 176C in which a store name is associated with the store ID. In addition to these information, the affiliated store / store information 176 may include information such as the category of the affiliated store or store, the location of the store, and the settlement pattern.

[0028] The information management department 140 manages user information 172 and franchise / store information 176 based on the information acquired from the user terminal device 10 and the second store terminal device 70. The information management department 140 adds, edits, deletes, etc. new records for the user information 172, franchise / store information 176, and update notification target table 178.

[0029] [Service server] Figure 7 is a configuration diagram of the service server 200. The service server 200 includes, for example, a communication unit 210, a service providing unit 220, an information update unit 230, and a storage unit 250. Components other than the communication unit 110 and the storage unit 250 are realized, for example, by a hardware processor such as a CPU executing a program (software). Some or all of these components may be realized by hardware (including circuit parts) such as LSI, ASIC, FPGA, GPU, or may be realized by the cooperation of software and hardware. The program may be stored in advance in a storage device (a storage device having a non-transitory storage medium) such as an HDD or a flash memory, or may be stored in a removable storage medium (a non-transitory storage medium) such as a DVD or a CD-ROM, and may be installed in the storage device by mounting the storage medium on a drive device.

[0030] The storage unit 250 is an HDD, a flash memory, a RAM, etc. The storage unit 250 may be a NAS device accessible by the service server 200 via a network. Information such as user information 252 is stored in the storage unit 250.

[0031] The communication unit 210 is a communication interface for connecting to the network NW. The communication unit 210 is, for example, a network interface card.

[0032] The service providing unit 220 provides services other than the electronic payment service to the user while executing communication with a mini-application (to be described later) installed in the payment application 20 via the communication unit 210. As will be described later, the information updating unit 230 updates the user information 252 regarding the service user (who is the same as the user of the payment service) in response to a notification from the notification unit 150 of the payment server 100. The user information 252 includes at least a part of the user information 172, and includes, for example, at least a part of information such as the user's name, gender, date of birth, address, nationality, occupation, and the like.

[0033] [Electronic Payment] When the payment processing unit 130 acquires payment information from the user terminal device 10 or the first store terminal device 50, it 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 reducing the charge balance managed in association with the user ID and increasing the item value of the sales amount of the franchise store. The item value of the sales amount of the franchise store is not used as electronic money itself, and the amount corresponding to the item value of the sales amount is transferred to the bank account in a cycle according to the agreement between the franchise store and the electronic payment service.

[0034] For users whose "settings information" is set to "credit payment", the payment processing unit 130 performs electronic payments as follows. Credit payment is a payment method through cooperation with a credit card company, which is a separate entity from the operator of the electronic payment service. The operator of the electronic payment service acts as the creditor and allows electronic payments that do not depend on the remaining recharge amount within the credit payment limit. In addition, in order to receive the credit payment service, it may be required to obtain a credit card provided by the operator of the electronic payment service. The amount used for credit payment is settled in one lump sum on the payment date of the following month, for example, by direct debit from a bank account. In this case, the payment processing unit 130 performs provisional settlement by adding the settlement amount to the credit payment usage amount and subtracting the same amount from the available credit payment amount. At the end of the month, it performs the process of direct debiting 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 the process. If the settlement amount exceeds the available credit payment amount at the time of provisional settlement, an error notification is returned to the payment application 20.

[0035] [Top screen] FIG. 8 is a diagram showing an example of the top screen of the settlement application 20. On the top screen, a code image CI is displayed. The code image CI includes, for example, a barcode and a QR code. Also, beside the code image CI, a switching switch SW for switching between performing electronic settlement based on the remaining charge amount and performing electronic settlement by credit payment is displayed. Note that "switch" and "button" are GUIs (Graphical User Interfaces) realized in cooperation with the touch panel. In FIG. 7, "credit" is displayed, which means that the setting is for performing electronic settlement by credit payment. The user can switch between performing electronic settlement based on the remaining charge amount and performing electronic settlement by credit payment, for example, by swiping the switching switch SW. Also, the top screen includes an operation area OA, a transition button TB1, a transition button TB2, and a transition button TB3. In the operation area OA, buttons for instructing scanning (starting user scanning), buttons for remitting the remaining charge amount to other users, buttons for displaying the points acquired by the user, buttons for displaying the history of electronic settlements executed by the user, etc., buttons for instructing main operations in electronic settlement are provided. When the transition button TB1 is operated, it transitions to a payment screen that displays the code image used for electronic settlement and the available amount. When the transition button TB2 is operated, it transitions to a screen that displays the available amount in balance payment or credit payment. In FIG. 7, since electronic settlement based on the remaining charge amount is set, when the transition button TB2 is operated, the available amount in balance payment is displayed. When the transition button TB3 is operated, it transitions to a screen for correcting the user's account information.

[0036] [Mini App] Below the operation area OA, for example, there are further button (switch) groups M1, M2, ··· for starting mini-apps. The mini-apps operate with the payment app 20 as a platform and provide some kind of service. Service providers develop mini-apps by referring to an SDK (Software Development Kit), such as a program or technical document for app development provided by the administrator of the payment app 20. The mini-apps are, for example, apps that operate when the payment app 20 is running. For example, when the payment app 20 is installed, part or all of the mini-apps may be installed, or part or all of the mini-apps may be installed from a service server corresponding to the mini-apps. For example, when a mini-app is launched, the mini-app accesses a service server 200 that provides a service corresponding to the mini-app, and the mini-app and the service server 200 cooperate to provide a service to the user. At this time, the service server 200 may be the payment server 100 itself. In FIG. 7, as an example, a button M1 of a mini-app that provides a function related to the food delivery service provided by a franchise store and a button M2 of a mini-app that provides a function of investing in investment products (such as stocks and bonds) provided by a securities company are displayed. However, buttons for starting various types of mini-apps, such as a reservation app for using amusement facilities such as movie theaters and a payment app for paying public transportation fares, may be displayed.

[0037] [Update Notification of Personal Identification Information] When the user clicks the mini-app button M1 or M2 on the top screen of FIG. 8, the payment app 20 causes the screen to transition to the corresponding mini-app screen. FIG. 9 is a diagram showing an example of a screen displayed when the mini-app button is clicked on the top screen of the payment app 20. FIG. 9 represents, as an example, a screen displayed when the user clicks the mini-app button M1 for the first time (or, if clicked in the past but the process described below has not been completed).

[0038] The screen shown in FIG. 9 includes, for example, an information area IA1 indicating the types of information coordinated between the settlement server 100 and the service server 200, and an information area IA2 indicating whether to permit notification to the service server 200 regarding an update when the personal authentication information (at least a part of the user information 172) registered in the settlement server 100 is updated. It also includes a button B1 for returning to the top screen and a button B2 for proceeding with the use of the mini-app upon agreeing to the contents shown in the information areas IA1 and IA2. The personal authentication information is an example of the "identification information" in the claims.

[0039] When the user clicks the mini-app button on the top screen of FIG. 8 for the first time, the settlement app 20 transmits information indicating the use of the mini-app (in other words, the service provided by the corresponding service server 200) to the settlement server 100. The acquisition unit 142 of the settlement server 100 acquires the information indicating the use of the mini-app transmitted by the settlement app 20. When the acquisition unit 142 acquires the information indicating the use of the mini-app, the display control unit 144 transmits the personal authentication information to the settlement app 20 for display. At this time, as shown in FIG. 8, the settlement app 20 causes the information area IA1 to display, for example, in addition to the personal authentication information, information indicating that the electronic payment service registration information is to be coordinated with the service server 200. Here, the personal authentication information represents the user's identification information (e.g., name, date of birth, postal code, address, nationality, occupation, etc.), while the electronic payment service registration information represents the information registered by the user when using the electronic payment service and its associated information (e.g., account ID, phone number, email address, charge balance, registration date, etc.).

[0040] When the user presses, for example, the accordion button AC1, the payment app 20 displays a list of identity verification information shared between the payment server 100 and the service server 200. On the other hand, when the user presses, for example, the accordion button AC2, the payment app 20 displays a list of electronic payment service registration information shared between the payment server 100 and the service server 200. Thereby, the user can check the list of information shared between the payment server 100 and the service server 200.

[0041] The information area IA2 indicates whether to permit the service server 200 to be notified of an update when the user updates the identity verification information registered in the payment server 100 on the payment app 20. More specifically, for example, when the user permits the notification to the service server 200 and then updates the identity verification information on the setting screen of the payment app 20, the notification unit 150 notifies the service server 200 of the fact that the identity verification information has been updated and the content of the update. When the service server 200 receives the notification from the notification unit 150, the information update unit 230 updates the user information 252 stored in the storage unit 250. Note that such a notification function by the notification unit 150 may be enabled by default without the payment app 20 displaying the information area IA2 and obtaining permission from the user.

[0042] When the user clicks the button B1, the payment app 20 causes the screen to transition to the top screen. On the other hand, when the user clicks the button B2, the notification unit 150 notifies (i.e., coordinates with) the service server 200 by transmitting the identity verification information and the electronic payment service registration information to the service server 200.

[0043] In this way, when a user uses a service different from the electronic payment service provided by the service server 200, the user does not need to re-enter the personal verification information on the service. Instead, the personal verification information is linked to the service server 200. After that, when the user updates the personal verification information stored in the service server 200, information regarding the update is notified to the service server 200. Thereby, when personal information is linked among a plurality of organizations and services, the integrity of the personal information can be ensured. Note that the electronic payment service registration information shown in FIG. 8 is not necessarily essential. At least the personal verification information is displayed in the information area IA1, and after obtaining consent from the user, it may be linked to the service server 200 via the payment server 100.

[0044] [Modification of Personal Verification Information] FIG. 10 is a diagram showing an example of a screen for modifying personal verification information in the payment application 20. As an example, FIG. 10 shows an account setting screen that is displayed when the user presses a transition button TB3 representing account settings on the top screen of the payment application 20. As shown in FIG. 10, the account setting screen includes information such as surname, given name, gender, date of birth, address, nationality, etc. as personal verification information. Reference numerals IN1 to IN6 represent input buttons for modifying these personal verification information. More specifically, when the user presses any one of the input buttons IN1 to IN6, the payment application 20 displays an input form for modifying the corresponding item of the personal verification information. For example, when the user presses the input button IN1, IN2, or IN3, the payment application 20 displays a character input form for modifying the surname, given name, or address. On the other hand, when the user presses the input button IN3, IN4, or IN6, the payment application 20 displays a selection form for modifying the gender, date of birth, or nationality.

[0045] After the user makes a correction and presses button B4, the payment application 20 transmits correction information including the content of the user's identity verification information correction made by the user to the payment server 100. When the acquisition unit 142 receives the correction information, the authentication unit 146 executes an authentication process for authenticating the received correction information based on the received correction information. On the other hand, when the user presses button B3 without making a correction, the payment application 20 returns the screen of FIG. 10 to the screen of FIG. 9.

[0046] FIG. 11 is a diagram for explaining the authentication process executed by the authentication unit 146. The screen shown in FIG. 11 is, for example, a screen that transitions when the user presses button B4 on the screen shown in FIG. 10. The authentication unit 146 executes an authentication process to verify the authenticity of the correction information of the identity verification information received from the payment server 100. For example, as shown in FIG. 11, the display control unit 144 causes the payment application 20 to display a button B5 for selecting identity verification by an IC card identity certificate issued by a public institution and a button B6 for selecting identity verification by a driver's license as candidates for the authentication process to be executed.

[0047] When the user presses button B5 or button B6, the authentication unit 146 executes the authentication process corresponding to the selected button, for example, by causing the user terminal device 10 to read an IC card identity certificate or a driver's license by near field communication. More specifically, when the user terminal device 10 reads an IC card identity certificate or a driver's license by near field communication, it transmits the read information to the payment server 100, and the authentication unit 146 executes the authentication process by comparing the received information with the correction information of the identity verification information. Note that the authentication process may further include any form of authentication such as password input or biometric authentication. On the other hand, when the user presses button B7, the payment application 20 causes the screen shown in FIG. 11 to transition to the screen shown in FIG. 10.

[0048] When the authentication by the authentication unit 146 is completed, the display control unit 144 causes the screen of the payment application 20 to transition to the screen of the personal confirmation information and the electronic payment service registration information reflecting the correction information. FIG. 12 is a diagram showing an example of the screen displayed after the authentication by the authentication unit 146 is completed. As shown in FIG. 12, when the authentication by the authentication unit 146 is completed, the display control unit 144 causes the payment application 20 to display the personal confirmation information again in a state reflecting the correction information. For example, in the case of FIG. 12, the display control unit 144 causes the personal confirmation information to be displayed again with the content of the item related to the address corrected from "XXX XXX" to "YYY YYY". At the same time, the update unit 148 stores the correction information in the storage unit 170 as new user information 172. For example, in the case of FIG. 12, the update unit 148 stores the new address "YYY YYY" in the storage unit 170 as the user information 172.

[0049] At the same time, the notification unit 150 notifies the service server 200 of the fact that the personal confirmation information has been updated and the update content by the user. The operation by the service server 200 notified of the update of the personal confirmation information may vary depending on each service server 200. As described above, the information update unit 230 of the service server 200 may automatically update the user information 252 in response to the notification, or may display a pop-up requesting the update of the personal confirmation information, for example, on the service provided by the service server 200 (on the mini application), and manually update the personal confirmation information again on the service.

[0050] In this way, when the user corrects the personal confirmation information on the payment application 20, after the authentication by the authentication unit 146 is completed and the authentication is completed, the notification unit 150 notifies each service server 200 of the update of the personal confirmation information. When personal information is linked among a plurality of organizations and services, the consistency of the personal information can be ensured.

[0051] [Settings for Update Notification Targets] In the above description, the case where when the user corrects the identity verification information on the payment application 20, the notification unit 150 notifies each service server 200 of the update of the identity verification information has been described. However, the present invention is not limited to such a configuration, and the notification unit 150 may refer to an update notification target table 178 that defines the services to be notified of the update of the identity verification information, and notify only specific services of the update of the identity verification information.

[0052] FIG. 13 is a diagram showing an example of the content of the update notification target table 178. The update notification target table 178 associates, for example, information such as services (mini-applications) and the presence or absence of update notifications for each user. The "presence or absence of update notification" may be set in advance by the operator of each service, or may be freely set by each user as described below. When the user corrects the identity verification information on the payment application 20, the notification unit 150 refers to the update notification target table 178 and identifies the services for which the "presence or absence of update notification" is set to "yes". The notification unit 150 notifies the service server 200 of the specific service of the update of the identity verification information. Thereby, according to the requests of each service provider and user, the target of the update notification can be changed for each service.

[0053] FIG. 14 is a diagram showing an example of a setting screen for the update notification target by the notification unit 150. FIG. 14 represents, as an example, an account setting screen that is displayed when the user presses a transition button TB3 representing account settings on the top screen of the payment application 20.

[0054] The screen shown in FIG. 14 includes, for example, an information area IA3 for setting "presence or absence of update notification" for each service for each user, a button B8 for returning to the top screen, and a button B9 for saving the content set in the information area IA3 to the update notification target table 178. When the user sets the "presence or absence of update notification" on the information area IA3 and presses the button B9, the payment app 20 transmits the set "presence or absence of update notification" to the payment server 100, and the setting unit 152 stores the received setting content of the "presence or absence of update notification" in the update notification target table 178. Thereafter, when the user modifies the personal verification information on the payment app 20, the notification unit 150 transmits the correction information of the personal verification information only to the service server 200 of the service for which the update notification is set to "yes" by the user. Note that the setting change of the "presence or absence of update notification" by the user may be enabled for all services or may be enabled for some services. For example, in the case of FIG. 14, for food delivery, the "presence or absence of update notification" can be set, while for securities, the "presence or absence of update notification" may be fixed to "yes".

[0055] Note that in FIG. 14, an example in which the user sets the update notification target on the payment app 20 has been described, but the update notification target may be set and changed in advance by the operator of the electronic payment service. Also, for example, an interface for setting the "presence or absence of update notification" may be provided on the second store terminal device 70 of each franchise store, and the "presence or absence of update notification" may be set and changed according to the judgment of the operator of each franchise store.

[0056] [Transition from Mini App to Payment App] As described above, the service server 200 may automatically update the user information 252 in response to the notification from the notification unit 150. In that case, the service server 200 may only report the link information to the account setting screen of the payment app 20 without permitting the correction of the account information on the mini app, and may cause the account information to be corrected on the payment app 20.

[0057] FIG. 15 is a diagram showing an example of the transition from the mini-app to the payment app 20. The left part of FIG. 15 represents the operation screen of the mini-app, and the right part of FIG. 15 represents the account setting screen of the payment app 20 shown in FIG. 10. As shown in the left part of FIG. 15, the mini-app displays, for example, link information L1 to the account setting screen of the payment app 20. When the user presses the link information L1, the mini-app transitions the screen to the account setting screen of the payment app 20. If the link information is not displayed and the modification of the account information is only permitted on the payment app 20, the user operating the mini-app cannot discover the method of modifying the account information on the mini-app, which may cause confusion to the user. Therefore, by displaying at least the link information to the account setting screen of the payment app 20, it is possible to realize the unified management of the account information without confusing the user who attempts to modify the account information on the mini-app.

[0058] [Process Flow] Hereinafter, with reference to FIG. 16, the process flow executed by the cooperation of the user terminal device 10, the payment server 100, and the service server 200 will be described. FIG. 16 is a sequence diagram showing an example of the process flow executed by the cooperation of the user terminal device 10, the payment server 100, and the service server 200. The process shown in FIG. 16 is executed, for example, when the user first presses a button corresponding to a certain mini-app on the top screen shown in FIG. 16.

[0059] First, the user terminal device 10 receives the pressing of the mini-app button by the user on the payment app 20 (S10). Next, the user terminal device 10 notifies the payment server 100 of the use of the mini-app corresponding to the pressed button (S12). Next, when the acquisition unit 142 acquires the notification information indicating the use of the mini-app transmitted by the user terminal device 10, the display control unit 144 transmits a request for permission to update the personal confirmation information (and, if necessary, the personal confirmation information and the electronic payment service registration information) to the user terminal device 10 so as to be displayed (S14).

[0060] Next, the user terminal device 10 causes a permission request for an update notification of the personal identification information to be displayed (S16). Next, the user terminal device 10 transmits the permission for the update notification of the personal identification information received via the payment application 20 to the payment server 100 (S18). Next, the setting unit 152 stores the permission for the update notification of the personal identification information in the update notification target table 178 (S20).

[0061] Next, the user terminal device 10 receives a correction of the personal identification information via the payment application 20 (S22). Next, the user terminal device 10 transmits the correction information of the personal identification information received via the payment application 20 to the payment server 100 (S24). Next, the authentication unit 146 executes an authentication process for the corrected personal identification information (S26).

[0062] Next, the update unit 148 stores the corrected personal identification information in the user information 172 of the storage unit 170 (S28). Next, the notification unit 150 transmits an update notification of the personal identification information to the service server 200 (S30). Next, the information update unit 230 stores the corrected personal identification information in the storage unit 250 (S24). Thus, the processing of this sequence diagram ends.

[0063] Note that the processing of S14 to S18 in the above sequence diagram processing may be omitted. In that case, in S20, in response to the user's start of using the mini application, the setting unit 152 automatically stores the permission for the update notification of the personal identification information in the update notification target table 178.

[0064] Furthermore, in this embodiment, the service server 200 provides services via mini-apps. However, the present invention is not limited to such a configuration, and the service server 200 may provide services via a web app (website) or a native app. In that case, for example, when the user selects a web app or a native app related to another service on the payment app 20, the payment app 20 displays the identity verification information before the screen transition, and in response to obtaining the consent of the user, the identity verification information may be linked to the web app or the native app. Even in this way, when personal information is linked among multiple organizations or services, the accuracy of the personal information can be guaranteed.

[0065] Furthermore, in this embodiment, the mini-app is installed in the payment app 20 as a super app. However, the present invention is not limited to such a configuration, and the super app that installs the mini-app may be an app that implements any function other than the payment app 20 (for example, a messaging function, an SNS function, an image posting function, a video posting function, a search engine function, etc.). For example, a plurality of types of mini-apps are developed and installed on an SNS app that implements an SNS service. In response to the user modifying the identity verification information on the SNS app, the SNS app may notify a plurality of service servers 200 that provide a plurality of other types of mini-apps of the modified information of the identity verification information. At that time, the SNS app may notify the service server 200 of the modification of the identity verification information via an SNS server (corresponding to the payment server 100 of this embodiment) that collaboratively provides the SNS service.

[0066] Furthermore, in this embodiment, the functions of the payment app 20 and the payment server 100 (information management unit 140) are distributed as described above, but the distribution of these functions may be changed as appropriate. For example, the display control by the display control unit 144 and the authentication process by the authentication unit 146 may be implemented in the payment app 20.

[0067] According to the embodiments described above, update information indicating an update of the identification information regarding the user stored in the storage unit is acquired from the user terminal device of the user of the electronic payment service, and based on the update information, the identification information stored in the storage unit is updated, and the update of the identification information is notified to one or more service servers that provide services different from the electronic payment service. Thereby, when personal information is linked among a plurality of organizations and services, the consistency of the personal information can be ensured.

[0068] As described above, the embodiments for implementing the present invention have been described using the embodiments. However, the present invention is not limited to such embodiments at all, and various modifications and substitutions can be made without departing from the gist of the present invention.

Explanation of Signs

[0069] 10 User terminal device 20 Payment application 100 Payment server 120 Payment content providing unit 130 Payment processing unit 140 Information management unit 142 Acquisition unit 144 Display control unit 146 Authentication unit 148 Update unit 150 Notification unit 152 Setting unit

Claims

1. An acquisition unit that acquires update information indicating an update of identification information regarding the user stored in a storage unit from a user terminal device of a user of an electronic payment service; An update unit that updates the identification information stored in the storage unit based on the update information; A notification unit that notifies one or more service servers that provide a service different from the electronic payment service of the update of the identification information; A display control unit that, when the user selects an update of the identification information on a screen of the service of the user terminal device, causes the screen of the service to transition to a screen of the electronic payment service, and displays an input screen for inputting the update content of the identification information on the transitioned screen. An information processing device.

2. A computer acquires update information indicating an update of identification information regarding the user stored in a storage unit from a user terminal device of a user of an electronic payment service; updates the identification information stored in the storage unit based on the update information; notifies one or more service servers that provide a service different from the electronic payment service of the update of the identification information; when the user selects an update of the identification information on a screen of the service of the user terminal device, causes the screen of the service to transition to a screen of the electronic payment service, and displays an input screen for inputting the update content of the identification information on the transitioned screen. An information processing method.

3. A computer is caused to acquire update information indicating an update of identification information regarding the user stored in a storage unit from a user terminal device of a user of an electronic payment service; update the identification information stored in the storage unit based on the update information; notify one or more service servers that provide a service different from the electronic payment service of the update of the identification information; when the user selects an update of the identification information on a screen of the service of the user terminal device, cause the screen of the service to transition to a screen of the electronic payment service, and display an input screen for inputting the update content of the identification information on the transitioned screen. A program.

4. A system including a payment server that provides an electronic payment service and one or more service servers that provide a service different from the electronic payment service, wherein the payment server An acquisition unit that acquires update information indicating an update of identification information regarding the user stored in the storage unit from the user terminal device of the user of the electronic payment service; An update unit that updates the identification information stored in the storage unit based on the update information; A notification unit that notifies the service server of the update of the identification information; A display control unit that, when the user selects an update of the identification information on the screen of the service of the user terminal device, causes the screen of the service to transition to the screen of the electronic payment service, and displays an input screen for inputting the update content of the identification information on the transitioned screen; and The one or more service servers update the identification information regarding the user stored in the storage unit of the one or more service servers in response to being notified of the update of the identification information. System.

5. A system comprising a payment server that provides an electronic payment service, and a payment application that operates in conjunction with the payment server to implement the electronic payment service and operates a service different from the electronic payment service. The payment server is An acquisition unit that acquires update information indicating an update of identification information regarding the user of the electronic payment service stored in the storage unit from the user terminal device equipped with the payment application; An update unit that updates the identification information stored in the storage unit based on the update information; A notification unit that notifies the one or more service servers that provide the service of the update of the identification information; A display control unit that, when the user selects an update of the identification information on the screen of the service of the user terminal device, causes the screen of the service to transition to the screen of the electronic payment service, and displays an input screen for inputting the update content of the identification information on the transitioned screen; and The payment application causes the payment server to notify the one or more service servers of the update of the identification information by causing the user to update the identification information stored in the storage unit of the payment server. System.

Images