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

Abstract

To provide an information processing device, an information processing method, a program, and a system that can ensure the consistency of personal information when the personal information is linked between multiple organizations or services. [Solution] An information processing device comprising: an acquisition unit that acquires update information indicating an update to identification information related to a user stored in a memory unit from a user terminal device of an electronic payment service; an update unit that updates the identification information stored in the memory unit based on the update information; and a notification unit that notifies one or more service servers that provide services different from the electronic payment service of the update to the identification information.

Description

[Technical Field]

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

[0002] Conventionally, there are known techniques for linking personal information of users between multiple organizations or services. For example, Patent Literature 1 discloses a technique for linking personal information held by multiple organizations, calculating the trustworthiness of each organization based on the linked personal information, and presenting information provided by organizations with high trustworthiness to data users. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Publication No. 2020-149645 Summary of the Invention [Problem to be solved by the invention]

[0004] However, with conventional technologies, when personal information is shared among multiple organizations or services, the consistency of the personal information may not be guaranteed.

[0005] The present invention has been made taking these circumstances into consideration, and one of its objectives is to provide an information processing device, information processing method, program, and system that can ensure the consistency of personal information when the personal information is shared between multiple organizations or services. [Means for solving the problem]

[0006] One aspect of the present invention is an information processing device comprising: an acquisition unit that acquires update information indicating an update to identification information related to a user stored in a memory unit from a user terminal device of an electronic payment service; an update unit that updates the identification information stored in the memory unit based on the update information; and a notification unit that notifies one or more service servers that provide services different from the electronic payment service of the update to the identification information. [Effects of the Invention]

[0007] According to one aspect of the present invention, it is possible to provide an information processing device, information processing method, program, and system that can ensure the consistency of personal information when the personal information is linked between multiple organizations or services. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram illustrating an example of a configuration for realizing an electronic payment service. [Figure 2] This is a sequence diagram (part 1) illustrating the general flow of electronic payment. [Figure 3] This is a sequence diagram (part 2) illustrating the general flow of electronic payment. [Figure 4] FIG. 2 is a configuration diagram of a payment server 100. [Figure 5] FIG. 10 is a diagram showing an example of the contents of user information 172. [Figure 6] FIG. 10 is a diagram showing an example of the contents of affiliated store / store information 176. [Figure 7] FIG. 2 is a diagram illustrating the configuration of a service server 200. [Figure 8] FIG. 10 is a diagram showing an example of a top screen of the payment application 20. [Figure 9] FIG. 10 is a diagram showing an example of a screen that is displayed when a mini-appli button is clicked on the top screen of payment application 20. [Figure 10] FIG. 10 is a diagram showing an example of a screen for correcting personal verification information in payment application 20. [Figure 11]10 is a diagram for explaining the authentication process executed by an authentication unit 146. FIG. [Figure 12] FIG. 10 is a diagram showing an example of a screen displayed after authentication by an authentication unit 146 is completed. [Figure 13] FIG. 10 is a diagram showing an example of the contents of an update notification target table 178. [Figure 14] 10 is a diagram showing an example of a setting screen for setting an update notification target by a notification unit 150. FIG. [Figure 15] FIG. 10 is a diagram showing an example of transition from a mini appli to a payment appli 20. [Figure 16] 1 is a sequence diagram showing an example of the flow of processing executed by the user terminal device 10, the payment server 100, and the service server 200 in cooperation with each other. DETAILED DESCRIPTION OF THE INVENTION

[0009] Hereinafter, with reference to the drawings, embodiments of an information processing device, an information processing method, a program, and an application program of the present invention will be described. Various devices, such as a "server," a "management device," and an "information providing device," that provide services to users or perform internal analysis, may be realized by a group of distributed devices, and each device may be operated by a different business. Furthermore, the hardware owner (the cloud server provider) and the business that actually operates the device may also be different. The application program and the payment server work together to provide an electronic payment service. In the following description, the application program is referred to as a "payment app." An electronic payment service is a service that supports payments for the purchase of goods and services at a store. A store is, for example, a physical store (real store) existing in real space, but may also include a virtual store for e-commerce transactions. A virtual store may also include a store operated by an entity other than the operator of the electronic payment service. In such a case, a transition to an interface screen for the electronic payment service may be performed when making a payment for a purchase at the virtual store. In an electronic payment service, a 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 primarily conducted 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] Figure 1 shows 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, 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, etc.

[0011] The user terminal device 10 is, for example, a portable terminal device such as a smartphone or 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 acceptance 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 app 20, which operates in cooperation with the payment server 100 to provide electronic payment services to users. The payment app 20 is installed on 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, tablet terminal, personal computer, etc. An interface for affiliated stores 72 runs on the second store terminal device 70. The interface for affiliated stores 72 may be an app for affiliated stores or a browser. The interface for affiliated stores 72 accepts coupon settings and the like from 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 the 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 payment information is sent from the POS device via the affiliated store server to the payment server 100. In the following explanation, this distinction will not be made and it is assumed that payment information is sent from the first store terminal device 50.

[0015] The service server 200 provides a service operated by a different operator from the electronic payment service. The service server 200 may provide the service as a mini-app (described later) on the electronic payment service, or may provide the service to the user terminal device 10 as its own website or application program. Here, the term "service" may include, for example, online shopping services (shopping mall services, reuse e-commerce services, etc.), food services (delivery, takeout, etc.), financial services (investment, insurance, etc.), and various types of services that can be provided through apps or the web.

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

[0017] 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 running, decodes the store code image 60 using its optical reading function (S1). The store code image 60 includes store URL (Uniform Resource Locator) information. This store URL is the domain of the electronic payment service to which store identification information has been added, and is associated with an affiliated store ID, store ID, etc. in the payment server 100 (described below). The payment application 20 sends first payment information including the store URL and account ID to the payment server 100 (S2). The payment server 100 searches for store information (described below) using the affiliated store ID and store ID corresponding to the store URL, acquires the affiliated store name and store name information (S3), and sends this to the payment application 20 (S4). The user enters the payment amount into the user terminal device 10 on the screen displaying the affiliated store name and store name (S5). Then, the user terminal device 10 generates second payment information including at least the payment amount and sends it to the payment server 100 (S6). The payment server 100 makes the electronic payment based on the received second payment information (S7). The payment server 100 then sends a payment completion notice (information for displaying a payment completion screen) to the payment app 20 (S8), and the payment app 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 information on the payment amount in addition to the store URL. In this case, the step of the user inputting the payment amount is omitted, and the payment amount information is included in the first payment information and sent to the payment server 100. Information on the affiliated store name and store name may be included and displayed on the payment completion screen.

[0018] In the case of pattern 2 (hereinafter referred to as store scan) shown in FIG. 3, the payment app 20 sends a request to issue a one-time code to the payment server 100 when the payment app 20 is launched, when a payment operation is performed in the payment app 20, at the automatic update timing (e.g., every minute), and at other timings (S11). The payment server 100 generates a one-time code (S12) and sends it to the payment app 20 (S13). The payment app 20 displays a code image, such as a QR code or 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 in-store terminal device 50, and the first in-store terminal device 50 decodes the code image using its optical reading function and obtains the one-time code, etc. (S15). The first in-store terminal device 50 then generates payment information including the one-time code, payment amount, affiliated store ID, store ID, etc., and sends it to the payment server 100 (S16). The payment amount information is acquired in advance by reading a barcode, manually entering it, etc. Based on the received information, the payment server 100 identifies the user corresponding to the one-time code and performs electronic payment (S17). Then, the payment server 100 sends a payment completion notice to the payment application 20 (S18), and the payment application 20 displays a payment completion screen (S19).

[0019] 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 store scanning, 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.

[0020] [Payment server] FIG. 4 is a configuration diagram of payment server 100. Payment server 100 includes, for example, communication unit 110, payment content providing unit 120, payment processing unit 130, information management unit 140, and storage unit 170. The components other than communication unit 110 and storage unit 170 are implemented by, for example, a hardware processor such as a CPU executing a program (software). Some or all of these components may be implemented by hardware (including circuitry) such as a large-scale integration (LSI), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a graphics processing unit (GPU), or may be implemented by a combination of software and hardware. The program may be stored in advance in a storage device (a storage device with a non-transitory storage medium) such as an HDD (hard disk drive) or flash memory, or may be stored in a removable storage medium (a non-transitory storage medium) such as a DVD or CD-ROM, and installed in the storage device by inserting the storage medium into 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, the details of which will be described later. The information management unit 140 is an example of an "information processing device" in the claims.

[0021] The storage unit 170 is a HDD, flash memory, 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 update notification target table 178.

[0022] The communication unit 110 is a communication interface for connecting to the network NW, and is, for example, a network interface card.

[0023] 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 reads out necessary content from the payment content information 174 as appropriate and provides it to the user terminal device 10. The user terminal device 10 accepts various inputs from the user while content is being played by the payment application 20, and transmits the above-mentioned payment information and the like to the payment server 100.

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

[0025] FIG. 5 is a diagram showing an example of the contents of user information 172. User information 172 is an example of user registration information. User information 172 includes, for example, a user URL, account ID, telephone number, and password, as well as an email address, user ID, name, address, date of birth, nationality, occupation, registration date, identity verification status, charge balance, credit card payment settings, credit card limit, credit card payment amount, available credit card payment amount, payment method settings, bank account, credit card number, charge history information, and payment history information. The user URL is used for remittance processing between users. Registration of a phone number and password is required when registering for an electronic payment service. The account ID is issued to the user by the payment server 100, and the user ID can be set arbitrarily by the user (or does not have to be set). Similarly, the email address, name, address, date of birth, nationality, and occupation can be set arbitrarily by the user (or do 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). Identity verification is information indicating whether or not a user has completed identity verification by uploading their identity verification document (e.g., a public identification document such as a driver's license) to the payment server 100 using the payment app 20 to prove the authenticity of their name, address, date of birth, etc., and is set to either "completed" or "not completed." If identity verification is "completed," the user will be able to withdraw the charge balance to a bank account, as described below. Hereinafter, the user's instance (electronic payment account) associated with this information will be referred to as an account.

[0026] The charge balance indicates the balance of electronic money set by the user by transferring funds to the account in advance. Transfer methods include transfers from a designated bank's ATM (Automatic Teller Machine) or from a registered bank account. The credit payment setting indicates whether the settings for electronic credit payment have been completed and is set to either "Completed" or "Not Completed." The credit payment limit is the monthly credit payment limit. The credit payment amount is the amount of credit payment already used in the current month. The available credit payment amount is the amount of credit payment available in the current month, calculated by subtracting the credit payment amount from the credit payment limit. While the figure shows only one credit payment limit, in reality, there may also be daily limits, and the lower of these may be set as the credit payment limit. Further details on credit payments will be discussed later. The payment method setting indicates whether the user will currently make electronic payments using the charge balance or by credit payment. The bank account and credit card number are information on the bank account or credit card number (account number, card number) that can be used to deposit funds into the electronic payment service. The charge history information is a history of the user's previous transfers to the electronic payment service to increase the charge balance. The payment history information is information that shows the breakdown 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.).

[0027] 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 ID is associated with an affiliated store name and sales amount (described above), 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 store's location, and payment patterns.

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

[0029] [Service Server] FIG. 7 is a configuration diagram of service server 200. Service server 200 includes, for example, communication unit 210, service providing unit 220, information updating unit 230, and storage unit 250. The components other than communication unit 110 and storage unit 250 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 a circuit unit) such as an LSI, ASIC, FPGA, or GPU, or may be realized by a combination of software and hardware. The program may be stored in advance in a storage device such as an HDD or flash memory (a storage device having a non-transitory storage medium), or may be stored in a removable storage medium (a non-transitory storage medium) such as a DVD or CD-ROM, and installed in the storage device by inserting the storage medium into a drive device.

[0030] The storage unit 250 is a HDD, flash memory, RAM, etc. The storage unit 250 may be a NAS device that the service server 200 can access via a network. The storage unit 250 stores information such as user information 252.

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

[0032] Service providing unit 220 provides services other than the electronic payment service to the user while communicating with mini-applis (described later) installed in payment application 20 via communication unit 210. As will be described later, information updating unit 230 updates user information 252 related to users of the service (which are the same as users of the payment service) in response to notifications from notification unit 150 of payment server 100. User information 252 includes at least a portion of user information 172, and includes, for example, at least a portion of information such as the user's name, sex, date of birth, address, nationality, and occupation.

[0033] [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 references the user information 172 to acquire the "payment method setting" of the user. For users 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 proceeds. The item value of the affiliated store's sales proceeds is not itself used as electronic money, for example, but rather the amount corresponding to the item value of the sales proceeds is transferred to a bank account in a cycle according to an agreement between the affiliated store and the electronic payment service.

[0034] The payment processing unit 130 performs electronic payments for users whose "setting information" is set to "credit card payment" as follows. Credit card payment is a payment method in 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, allowing electronic payments within the credit card payment limit and independent of the remaining balance. To receive the credit card payment service, a user may be required to obtain a credit card provided by the operator of the electronic payment service. The monthly amount used for credit card payment is settled on the following month's payment date, for example, by debit from a bank account. In this case, the payment processing unit 130 makes a provisional settlement by adding the settlement amount to the credit card payment amount and subtracting the same amount from the available credit card balance. On the closing date, the payment processing unit 130 performs the process described above to debit the current month's payment on the following month's payment date, or requests the credit card company operator to perform this process. If the settlement amount exceeds the available credit card balance at the time of provisional settlement, an error notification is returned to the payment app 20.

[0035] [Top screen] FIG. 8 is a diagram showing an example of the top screen of the payment application 20. A code image CI is displayed on the top screen. The code image CI includes, for example, a barcode and a QR code. A selector switch SW is displayed next to the code image CI, allowing the user to select whether to make an electronic payment using the remaining balance or a credit card payment. The "switch" and "button" refer to a graphical user interface (GUI) implemented in cooperation with a touch panel. In FIG. 7, "credit" is displayed, indicating that the electronic payment is set to be made using a credit card. For example, a user can swipe the selector switch SW to select whether to make an electronic payment using the remaining balance or a credit card payment. The top screen also includes an operation area OA and transition buttons TB1, TB2, and TB3. The operation area OA includes buttons for instructing key operations in electronic payment, such as a button for instructing scanning (starting a user scan), a button for transferring the remaining balance to another user, a button for displaying the points earned by the user, and a button for displaying the history of electronic payments made by the user. When transition button TB1 is operated, the screen transitions to a payment screen that displays the code image used for electronic payment and the available balance. When transition button TB2 is operated, the screen transitions to a screen that displays the available balance for balance payment or credit payment. In Figure 7, electronic payment using the charge balance is set, so when transition button TB2 is operated, the available balance for balance payment is displayed. When transition button TB3 is operated, the screen transitions to a screen for amending the user's account information.

[0036] [Mini App] Below the operation area OA, a group of buttons (switches) M1, M2, ... for launching mini apps are further displayed. A mini app is an app that operates using the payment app 20 as a platform and provides some kind of service. A service provider develops a mini app by referring to an SDK (Software Development Kit), which is an app development program and technical documentation provided by the administrator of the payment app 20. A mini app is an app that operates while the payment app 20 is running, for example. For example, a part or all of the mini app may be installed when the payment app 20 is installed, or a part or all of the mini app may be installed from a service server corresponding to the mini app. For example, when a mini app is launched, the mini app accesses the service server 200 that provides the service corresponding to the mini app, and the mini app and the service server 200 work together to provide the service to the user. In this case, the service server 200 may be the payment server 100 itself. As an example, Figure 7 displays button M1 for a mini-app that provides functions related to food delivery services offered by affiliated stores, and button M2 for a mini-app that provides functions for investing in investment products (e.g., stocks, bonds, etc.) offered by securities companies. However, buttons for launching various types of mini-apps may be displayed, such as a reservation app for using amusement facilities such as movie theaters, or a payment app for paying for public transportation fares.

[0037] [Notification of updated identity verification information] When a user clicks on the mini app button M1 or M2 on the top screen of Fig. 8, the payment application 20 transitions to the screen of the corresponding mini app. Fig. 9 is a diagram showing an example of a screen that is displayed when a mini app button is clicked on the top screen of the payment application 20. Fig. 9 shows, as an example, a screen that is displayed when a user clicks on the mini app button M1 for the first time (or when a user has clicked on the mini app button M1 in the past but has not completed the process described below).

[0038] 9 includes, for example, an information area IA1 indicating the type of information linked between payment server 100 and service server 200, an information area IA2 indicating whether or not to permit notification of the update to service server 200 when personal identification information (at least a part of user information 172) registered in payment server 100 is updated, a button B1 for returning to the top screen, and a button B2 for agreeing to the contents shown in information areas IA1 and IA2 and proceeding to use the mini app. Personal identification information is an example of "identification information" in the claims.

[0039] When a user clicks a mini app button on the top screen of FIG. 8 for the first time, the payment application 20 transmits to the payment server 100 information indicating the use of the mini app (in other words, the service provided by the corresponding service server 200) corresponding to the mini app button. The acquisition unit 142 of the payment server 100 acquires the information indicating the use of the mini app transmitted by the payment application 20. When the acquisition unit 142 acquires the information indicating the use of the mini app, the display control unit 144 transmits personal identification information to the payment application 20 to display it. At this time, as shown in FIG. 8, the payment application 20 displays, in information area IA1, for example, information indicating that electronic payment service registration information will be linked to the service server 200 in addition to the personal identification information. Here, the personal identification 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 information registered by the user when using the electronic payment service and associated information (e.g., account ID, phone number, email address, charge balance, registration date, etc.).

[0040] When the user presses, for example, accordion button AC1, payment application 20 displays a list of personal identification information shared between payment server 100 and service server 200, while when the user presses, for example, accordion button AC2, payment application 20 displays a list of electronic payment service registration information shared between payment server 100 and service server 200. This allows the user to check the list of information shared between payment server 100 and service server 200.

[0041] Information area IA2 indicates whether or not to permit notification of the update to service server 200 when the user updates the personal identification information registered with payment server 100 on payment application 20. More specifically, for example, if the user permits notification to service server 200 and then updates the personal identification information on the setting screen of payment application 20, notification unit 150 notifies service server 200 that the personal identification information has been updated and the details of the update. When service server 200 receives the notification from notification unit 150, information update unit 230 updates user information 252 stored in storage unit 250. Note that such a notification function by notification unit 150 may be enabled by default, without payment application 20 displaying information area IA2 to obtain permission from the user.

[0042] When the user clicks button B1, payment application 20 transitions the screen to the top screen. On the other hand, when the user clicks button B2, notification unit 150 notifies service server 200 by transmitting personal identification information and electronic payment service registration information to service server 200 (i.e., cooperates with service server 200).

[0043] In this way, when a user uses a service provided by service server 200 that is different from the electronic payment service, the user does not need to re-enter the personal identification information on the service, but instead links the personal identification information to service server 200. If the user subsequently updates the personal identification information stored in service server 200, information related to the update is notified to service server 200. This ensures the integrity of personal information when it is linked between multiple organizations or services. Note that the electronic payment service registration information shown in FIG. 8 is not necessarily required; it is sufficient that at least the personal identification information is displayed in information area IA1 and, after the user's consent, is linked to service server 200 via payment server 100.

[0044] [Edit identity verification information] FIG. 10 is a diagram showing an example of a screen for correcting personal identification information in the payment app 20. FIG. 10 shows, as an example, an account setting screen that is displayed when a user presses transition button TB3, which indicates account setting, on the top screen of the payment app 20. As shown in FIG. 10, the account setting screen includes, for example, personal identification information such as last name, first name, gender, date of birth, address, and nationality, and symbols IN1 to IN6 represent input buttons for correcting this personal identification information. More specifically, when a user presses any of input buttons IN1 to IN6, the payment app 20 displays an input form for correcting the corresponding item of personal identification information. For example, when a user presses input button IN1, IN2, or IN3, the payment app 20 displays a character input form for correcting the last name, first name, or address. Meanwhile, when a user presses input button IN3, IN4, or IN6, the payment app 20 displays a selection form for correcting the gender, date of birth, or nationality.

[0045] When the user presses button B4 after making the corrections, the payment application 20 transmits correction information including the correction details of the user's personal identification information to the payment server 100. When the acquisition unit 142 receives the correction information, the authentication unit 146 executes authentication processing to authenticate the correction information based on the received correction information. On the other hand, when the user presses button B3 without making any corrections, 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 transitioned to, for example, when the user presses button B4 on the screen shown in Fig. 10. The authentication unit 146 executes the authentication process to verify the authenticity of the correction information for the personal identification 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, as candidates for the authentication process to be executed, button B5 for selecting personal identification using an IC card identification card issued by a public institution and button B6 for selecting personal identification using a driver's license.

[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 having the user terminal device 10 read the IC card identification or driver's license via near field communication. More specifically, after reading the IC card identification or driver's license via near field communication, the user terminal device 10 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 personal identification information. Note that the authentication process may further include any form of authentication, such as password entry or biometric authentication. On the other hand, when the user presses button B7, the payment application 20 transitions from the screen shown in FIG. 11 to the screen shown in FIG. 10.

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

[0049] At the same time, the notification unit 150 notifies the service server 200 of the fact that the personal identification information has been updated by the user and the details of the update. The operation of the service server 200 that has been notified of the update of the personal identification information may differ depending on the 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 not automatically update the user information 252 but may instead display a pop-up on the service (mini app) provided by the service server 200 requesting that the personal identification information be updated, and prompt the user to manually update the personal identification information again on the service.

[0050] In this way, when the user modifies the personal identification information on payment application 20, authentication unit 146 performs authentication, and after the authentication is completed, notification unit 150 notifies each service server 200 of the update of the personal identification information. When personal information is linked between multiple organizations or services, the consistency of the personal information can be guaranteed.

[0051] [Update notification target settings] In the above description, when a user modifies personal identification information on payment application 20, notification unit 150 notifies each service server 200 of the update of the personal identification information. However, the present invention is not limited to such a configuration, and notification unit 150 may refer to update notification target table 178, which specifies the services to be notified of the update of the personal identification information, and notify only specific services of the update of the personal identification information.

[0052] FIG. 13 is a diagram showing an example of the contents of update notification target table 178. In update notification target table 178, for example, information such as the service (mini app) and whether or not to issue an update notification is associated with each user. The "whether or not to issue an 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 a user modifies their personal identification information on payment application 20, notification unit 150 refers to update notification target table 178 and identifies services for which "whether or not to issue an update notification" is set to "yes." Notification unit 150 notifies service server 200 of the identified service of an update to the personal identification information. This allows the target of update notifications to be changed for each service according to the requests of each service provider or user.

[0053] Fig. 14 is a diagram showing an example of a setting screen for updating notification targets by notification unit 150. Fig. 14 shows, as an example, an account setting screen that is displayed when a user presses transition button TB3, which indicates account setting, on the top screen of payment application 20.

[0054] The screen shown in FIG. 14 includes, for example, an information area IA3 for setting "Whether to Receive Update Notifications" for each service for each user, a button B8 for returning to the top screen, and a button B9 for saving the setting in the information area IA3 to the update notification target table 178. When a user sets "Whether to Receive Update Notifications" in the information area IA3 and presses the button B9, the payment application 20 transmits the set "Whether to Receive Update Notifications" to the payment server 100, and the setting unit 152 stores the received setting "Whether to Receive Update Notifications" in the update notification target table 178. If the user subsequently modifies the personal identification information on the payment application 20, the notification unit 150 transmits the modified information of the personal identification information only to the service server 200 for the service for which the user set update notifications to "Yes." Note that the user's change of the setting for "Whether to Receive Update Notifications" may be enabled for all services or for some services. For example, in the example shown in FIG. 14, "Whether to Receive Update Notifications" can be set for food delivery, while "Whether to Receive Update Notifications" for securities may be fixed at "Yes."

[0055] 14 illustrates an example in which a user sets the target of update notification on payment application 20, but the target of update notification may be set and changed in advance by the operator of the electronic payment service. Also, for example, an interface for setting "whether or not to send update notification" may be provided on second store terminal device 70 of each affiliated store, and the "whether or not to send update notification" may be set and changed at the discretion of the operator of each affiliated store.

[0056] [Transition from mini app to payment app] As described above, service server 200 may automatically update user information 252 in response to a notification from notification unit 150. In this case, service server 200 may transmit only link information to the account setting screen of payment application 20, without permitting modification of account information on the mini appli, and allow modification of account information on payment application 20.

[0057] FIG. 15 is a diagram showing an example of a transition from a mini app to the payment app 20. The left part of FIG. 15 shows an operation screen of the mini app, and the right part of FIG. 15 shows the account settings 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 settings screen of the payment app 20. When a user presses the link information L1, the mini app transitions the screen to the account settings screen of the payment app 20. If the link information is not displayed and modification of account information is permitted only on the payment app 20, a user operating the mini app will not be able to find a way to modify account information on the mini app, which could confuse the user. Therefore, by displaying at least link information to the account settings screen of the payment app 20, unified account information management can be achieved without confusing a user who is attempting to modify account information on the mini app.

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

[0059] First, the user terminal device 10 accepts a press of a mini app button by the user on the payment application 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, the acquisition unit 142 acquires notification information indicating the use of the mini app transmitted by the user terminal device 10, and the display control unit 144 transmits a request for permission to transmit an update notification of the personal identification information (and, if necessary, the personal identification information and electronic payment service registration information) to the user terminal device 10 to display the same (S14).

[0060] Next, the user terminal device 10 displays a request for permission to issue an update notification of the personal identification information (S16). Next, the user terminal device 10 transmits the permission to issue an 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 to issue an update notification of the personal identification information in the update notification target table 178 (S20).

[0061] Next, the user terminal device 10 accepts the 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 accepted via the payment application 20 to the payment server 100 (S24). Next, the authentication unit 146 executes the authentication process of the corrected personal identification information (S26).

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

[0063] In addition, the processes of S14 to S18 in the above sequence diagram may be omitted, and in that case, in S20, in response to the user starting to use the mini app, the setting unit 152 will automatically store permission for update notifications of personal identification information in the update notification target table 178.

[0064] Furthermore, in this embodiment, service server 200 provides services via mini-applis. However, the present invention is not limited to such a configuration, and service server 200 may provide services via a web app (website) or a native app. In this case, for example, when a user selects a web app or native app related to another service on payment app 20, payment app 20 may display personal identification information before the screen transition, and, upon obtaining consent from the user, link the personal identification information to the web app or native app. This also ensures the accuracy of personal information when the information is linked between multiple organizations or services.

[0065] Furthermore, in this embodiment, mini apps are installed in payment app 20, which serves as a super app. However, the present invention is not limited to such a configuration, and the super app that installs the mini apps may be an app that implements any function other than payment app 20 (e.g., a messaging function, an SNS function, an image posting function, a video posting function, a search engine function, etc.). For example, multiple types of mini apps may be developed and installed on an SNS app that implements an SNS service, and in response to a user correcting their identity verification information on the SNS app, the SNS app may notify multiple service servers 200 that provide multiple other types of mini apps of the corrected identity verification information. In this case, the SNS app may notify service server 200 of the correction of the identity verification information via an SNS server (corresponding to payment server 100 in this embodiment) that cooperates with the SNS service to provide the SNS service.

[0066] Furthermore, in this embodiment, the functions of payment application 20 and 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, display control by display control unit 144 and authentication processing by authentication unit 146 may be implemented in payment application 20.

[0067] According to the embodiment described above, update information indicating an update to the user's identification information stored in a storage unit is obtained from the user terminal device of the electronic payment service user, the identification information stored in the storage unit is updated based on the update information, and the update of the identification information is notified to one or more service servers that provide services other than the electronic payment service. This makes it possible to ensure the consistency of personal information when the personal information is shared between multiple organizations or services.

[0068] 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]

[0069] 10 User terminal device 20. Payment App 100 Payment Server 120 Payment Contents Department 130 Payment processing unit 140 Information Management Department 142 Acquisition Department 144 Display control unit 146 Authentication Department 148 Update Department 150 Notification Department 152 Setting section

Claims

1. an acquisition unit that acquires, from a user terminal device of a user of an electronic payment service, update information indicating an update of the user's identification information stored in a storage unit; 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; Information processing device.

2. the notification unit refers to a table that specifies target services that are to be notified of the update of the identification information, in association with the user, and determines one or more service servers that are to be notified of the update of the identification information. The information processing device according to claim 1 .

3. a setting unit that displays information about the target service defined in the table on the user terminal device and enables the user terminal device to set the target service; The information processing device according to claim 2 .

4. The service is provided on a payment app that operates in conjunction with the electronic payment service on the user terminal device. The information processing device according to claim 1 .

5. The computer Acquires update information indicating an update of identification information related to the user stored in a storage unit from a user terminal device of the user of the electronic payment service, updating the identification information stored in the storage unit based on the update information; notifying one or more service servers that provide a service different from the electronic payment service of the update of the identification information; Information processing methods.

6. On the computer, acquires, from a user terminal device of a user of the electronic payment service, update information indicating an update of the identification information related to the user stored in the storage unit; updating the identification information stored in the storage unit based on the update information; notifying one or more service servers that provide a service different from the electronic payment service of the update of the identification information; program.

7. A system comprising 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, The payment server an acquisition unit that acquires, from a user terminal device of the user of the electronic payment service, update information indicating an update of the identification information related to the user stored in a storage unit; 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 an update of the identification information, the one or more service servers update the identification information related to the user stored in a storage unit of the one or more service servers in response to the notification of the update of the identification information; system.

8. A system comprising: a payment server that provides an electronic payment service; and a payment application that operates a service different from the electronic payment service in conjunction with the payment server, The payment server an acquisition unit that acquires, from a user terminal device that has the payment application installed, update information indicating an update of identification information related to the user of the electronic payment service stored in a storage unit; 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 the service of the update of the identification information, the payment application causes the user to update the identification information stored in the storage unit of the payment server, thereby causing the payment server to notify the one or more service servers of the update of the identification information; system.

Images