Service management device, service management system, service management method, and program

Abstract

To improve the convenience for a user.SOLUTION: A settlement management apparatus includes a control unit configured to: cause a display unit to display a first interface screen in a state in which a user is logged in for using an electronic settlement application; provide completion information indicating that identity verification has been completed to a service server which provides an other service to the user in cooperation with a mini application when an application button is operated for making an application for using the other service included in the first interface screen and when a use mode of the user for an electronic settlement service satisfies conditions set in the electronic settlement service and the identity verification of the user has been completed in the electronic settlement service; instruct the service server to proceed with a process related to the application; and cause the service server to temporarily stop at least the application when the application button is operated and when the set conditions are not satisfied or the identity verification of the user has not been completed.SELECTED DRAWING: Figure 4

Description

[Technical field]

[0001] The present invention relates to a payment management device, a payment management system, an electronic payment application, a payment management method, and a program. [Background technology]

[0002] 2. Description of the Related Art Conventionally, in electronic commerce, a system is known in which electronic authentication is performed for identity verification and electronic payment is made based on the electronic authentication (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2002-123726 A Summary of the Invention [Problem to be solved by the invention]

[0004] However, the above-mentioned devices may be inconvenient for users or service providers.

[0005] The present invention has been made in consideration of these circumstances, and one of its objectives is to provide a payment management device, a payment management system, an electronic payment app, a payment management method, and a program that can improve user convenience. [Means for solving the problem]

[0006] One aspect of the present invention is a payment management device that provides an electronic payment service, which has a control unit that displays a first interface screen on a display unit when a user is logged in to use an electronic payment app, and when an application button for applying to use other services included on the first interface screen is operated, and when the user's usage of the electronic payment service meets conditions set in the electronic payment service and identity verification of the user has been completed in the electronic payment service, provides completion information indicating that the identity verification has been completed to a service server that operates in the electronic payment app and provides the other service to the user in cooperation with a mini-app that provides the other service, and instructs the service server to proceed with processing related to the application, and when the application button is operated and the set conditions are not met or identity verification of the user has not been completed, causes the service server to at least temporarily stop the application. Effect of the Invention

[0007] According to one aspect of the present invention, it is possible to provide a payment management device, a payment management system, an electronic payment application, a payment management method, and a program that can improve user convenience. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram showing an example of a configuration for realizing an electronic payment service. [Diagram 2] FIG. 1 is a sequence diagram illustrating an example of a general flow of electronic payment in pattern 1. [Diagram 3] FIG. 11 is a sequence diagram illustrating an example of the general flow of electronic payment in pattern 2. [Figure 4] FIG. 2 is a configuration diagram of a payment server 100. [Diagram 5] FIG. 13 is a diagram showing an example of the contents of user information 172. [Figure 6] FIG. 13 is a diagram showing an example of the contents of affiliated store / store information 176. [Figure 7]This is a conceptual diagram of the processing (part 1). [Figure 8] This is a conceptual diagram of the processing (part 2). [Figure 9] 10 is a diagram for explaining the functional configuration of a first manager 128 and a second manager 130. FIG. [Figure 10] 13 is a diagram showing an example of information registered by a second management unit 130. FIG. [Figure 11] 2 is a diagram showing a mini application 30 included in a payment application 20. FIG. [Figure 12] FIG. 2 is a diagram showing an example of an interface image IM1. [Figure 13] FIG. 13 is a diagram for explaining the process of opening a bank account using the mini app 30. [Figure 14] FIG. 13 is a diagram showing an example of an interface screen IM8. [Figure 15] FIG. 13 is a diagram for explaining the process when applying for use of a specific service using a mini app 30. [Figure 16] 11 is a sequence diagram showing an example of a flow of processes executed by a service system and a payment system. FIG. [Figure 17] FIG. 1 is a conceptual diagram of information sharing. [Figure 18] FIG. 13 is a conceptual diagram of providing a result of identity verification. [Figure 19] FIG. 13 is a diagram for explaining a process of correcting information on an input content confirmation screen. [Figure 20] 11 is a sequence diagram showing an example of a flow of processes executed by a service system and a payment system. FIG. [Figure 21] FIG. 13 is a diagram for explaining the conditions for applying for a service provided by a service system using a mini appli 30. [Figure 22] 13 is a flowchart showing an example of the flow of an authentication process. [Figure 23] 11A and 11B are diagrams illustrating an example of a transition of an interface screen when authentication is performed. [Figure 24] FIG. 13 is a diagram showing an example of the contents of user information 172A in the second embodiment. [Diagram 25] FIG. 13 is a diagram for explaining conditions under which a flag is set. [Figure 26] FIG. 11 is a diagram illustrating a part of a functional configuration of a payment server 100A according to a second embodiment. [Figure 27] FIG. 13 is a diagram for explaining the processing of another example (1). DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] A payment management device, a payment management system, an electronic payment application, a payment management method, and a program according to the present invention will be described below with reference to the drawings. Also, an information processing device, an information processing method, and a program will be described below with reference to the drawings.

[0010] The service management device is realized by one or more processors. The service management device provides a service, and includes a control unit (e.g., a content providing unit) that executes a process to display a second interface screen on the display unit for allowing the user to input the first information when a button for starting a first service included in a first interface screen displayed on a display unit of a user terminal device is operated while the user is logged in to use a service app, and the first information among the information required for the application including the first information and the second information is not stored in a storage device managed by the service, and to display a third interface screen on the display unit for allowing the user to input the second information into a first mini app that runs in the service app and provides the first service when the button is operated and the first information among the information required for the application is stored in the storage device. The above service is any service, such as an electronic payment service, a chat app, or a social network service. In the following, an electronic payment service will be described as an example.

[0011] The first information is, for example, information acquired by a user inputting information on an interface screen provided by an electronic payment application. The second information is, for example, information acquired by a user inputting information on an interface screen provided by a mini application. The first information is, for example, information required for use of the service of the first mini application and for use of a service of a mini application different from the first mini application. The second information is, for example, information required for use of the service of the first mini application. The first interface screen may be a screen including a button for starting the service of the service. The first interface screen may be a screen provided by an electronic payment application or a screen provided by a mini application. The button for starting the service of the first service is a button operated to start the use of the service, and is, for example, a button corresponding to an operation that provides user information to a service server when the user uses the service and triggers the use of the service. In other words, the button for starting the service can be an application button for applying for the service.

[0012] The process of displaying the third interface screen on the display unit refers to displaying the third interface screen on the display unit in cooperation with the first mini app or a service server corresponding to the first mini app, for example, the control unit instructing the first mini app or the service server to display the third interface screen.

[0013] A payment management device that provides an electronic payment service, comprising: a control unit that displays a first interface screen on a display unit when a user is logged in to use an electronic payment app; when an application button included in the first interface screen is operated to apply for use of other services, and when the user's usage of the electronic payment service satisfies conditions set in the electronic payment service and identity verification of the user has been completed in the electronic payment service, provides completion information indicating that the identity verification has been completed to a service server that operates in the electronic payment app and provides the other service to the user in cooperation with a mini-app that provides the other service, and instructs the service server to proceed with processing related to the application; and when the application button is operated and the set conditions are not met or identity verification of the user has not been completed, causes the service server to at least temporarily stop the application.

[0014] The above "instructing the service server to proceed with the process related to the application" means, for example, having the mini app or service server display an interface screen for application on a display unit or provide a service. Temporarily suspending means, for example, having the payment app, payment server, mini app, or service server display an interface screen on a display unit indicating that the service is unavailable, or providing information indicating that identity verification, predetermined processing, screening, etc. are required.

[0015] The information processing device includes a first acquisition unit that acquires user information, which is one or both of the user's usage pattern of the electronic payment service and information about the user provided by the user to use the electronic payment service; a second acquisition unit that acquires communication information, which is one or both of information about a device used by the user to use the electronic payment service and information about the network used by the user; a derivation unit that derives the user's trustworthiness based on the user information and the communication information; and a provision unit (e.g., a first management unit) that provides the trustworthiness to a service server that provides a service different from the electronic payment service (see second embodiment).

[0016] First Embodiment [Electronic payment service] FIG. 1 is a diagram showing an example of a configuration for realizing an electronic payment service. The electronic payment service is realized mainly by a payment server 100. The payment server 100 communicates with, for example, one or more user terminal devices 10, one or more first store terminal devices 50, one or more second store terminal devices 70, and one or more service servers 200-1 to 200-3 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. Hereinafter, when the service servers 200-1 to 200-3 are not distinguished from each other, they are referred to as the service server 200. The payment server 100 is an example of a "payment management device" or a "service management device".

[0017] The user terminal device 10 is, for example, a portable terminal device such as a smartphone or a tablet terminal. The user terminal device 10 is a computer device having at least an optical reading function, a communication function, a display function, an input reception function, and a program execution function. In the following description, components for realizing these functions are referred to as a camera, a communication device, a touch panel, a CPU (Central Processing Unit), etc. In the user terminal device 10, a processor such as a CPU executes a payment application 20, thereby operating to provide an electronic payment service to a user in cooperation with a payment server 100. The payment application 20 controls the camera, the communication device, the touch panel, etc.

[0018] 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).

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

[0020] The payment server 100 realizes electronic payment based on payment information received from the user terminal device 10 or the first store terminal device 50. The first store terminal device 50 may include a POS device and an affiliated store server, in which case the payment information is sent from the POS device to the payment server 100 via the affiliated store server. In the following description, this is not particularly distinguished, and it is assumed that the payment information is sent from the first store terminal device 50. The payment server 100 performs electronic payment, for example, by decreasing the charge balance managed in association with the user ID and increasing the item value of the affiliated store's sales. The item value of the affiliated store's sales is not used as electronic money itself, for example, but an amount corresponding to the item value of the sales is transferred to a bank account in a cycle according to an agreement between the affiliated store and the electronic payment service. Electronic payment may include a method that allows a purchase of a larger amount than the charge balance at the time of purchase by using a method such as revolving payment or credit payment.

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

[0022] In the case of pattern 1 (hereinafter referred to as user scan) shown in FIG. 2, the user terminal device 10 with the payment application 20 activated decodes the store code image 60 by the optical reading function (S1). The store code image 60 includes store URL (Uniform Resource Locator) information. This store URL is an electronic payment service domain to which store-identifying information is added, and is associated with an affiliated store ID, a store ID, etc. in the payment server 100 (described later). The payment application 20 transmits the first payment information including the store URL and the account ID to the payment server 100 (S2). The payment server 100 searches for store information (described later) from the affiliated store ID and the store ID corresponding to the store URL, acquires the affiliated store name and the store name information (S3), and transmits it to the payment application 20 (S4). The user inputs the payment amount into the user terminal device 10 on the screen on which the affiliated store name and the store name are displayed (S5). Then, the user terminal device 10 generates second payment information including at least the payment amount and transmits it to the payment server 100 (S6). The payment server 100 completes the electronic payment as described above based on the received second payment information (S7). Then, the payment server 100 transmits a payment completion notice (information for displaying a payment completion screen) to the payment application 20 (S8), and the payment application 20 displays the payment completion screen (S9). Note that 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. For example, the payment application 20 displays the screen on which the payment amount is input on the display unit, so that the above S5 is omitted. When the user checks the amount and performs a predetermined operation, the first payment information including the payment amount is transmitted to the payment server 100. Information on the affiliated store name and the store name may be included and displayed on the payment completion screen.

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

[0024] 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, issuance of a one-time code may be omitted in the store scan, and the payment application 20 may display a code image generated based on the user's account ID. In this case, the payment server 100 identifies the user corresponding to the account ID instead of identifying the user corresponding to the one-time code.

[0025] [Payment server] 4 is a configuration diagram of the payment server 100. The payment server 100 includes, for example, a communication unit 110, a login status management unit 120, a content providing unit 122, a payment processing unit 124, an information processing unit 126, a first management unit 128, and a second management unit 130. The components other than the communication unit 110 and the storage unit 170 are realized by, for example, a hardware processor such as a CPU executing a program (software). Some or all of these components may be realized by hardware (including circuitry) such as an LSI (Large Scale Integration), an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array), or a GPU (Graphics Processing Unit), or may be realized by cooperation between software and hardware. The program may be stored in advance in a storage device (a storage device having a non-transient storage medium) such as a hard disk drive (HDD) or a flash memory, or may be stored in a removable storage medium (a non-transient storage medium) such as a DVD or a CD-ROM, and may be installed in the storage device by mounting the storage medium in a drive device. Note that a part of the processing executed in the payment application 20 may be executed in the payment server 100, and a part of the processing executed in the payment server 100 may be executed in the payment application 20. Some of the functional configurations included in the payment server 100 may be included in other devices. For example, the first management unit 128 and the second management unit 130 may be included in other devices different from the payment server 100. In the present embodiment, as an example, the first management unit 128 and the second management unit 130 are described as being included in the payment server 100.

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

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

[0028] The login status management unit 120 manages the login status of each user. For example, the login status management unit 120 permits login based on a phone number and password entered by the user, and transitions the status from a login status to a logout status based on a logout operation by the user.

[0029] The content providing unit 122 has, for example, a function of a Web server, and provides information (content and interface screen) for displaying various screens of the electronic payment service to the user terminal device 10. The content providing unit 122 appropriately reads out necessary content from the payment content information 174 and provides it to the user terminal device 10. The user terminal device 10 accepts various inputs by the user while the content is being played by the payment application 20, and transmits the above-mentioned payment information and the like to the payment server 100.

[0030] The payment processing unit 124 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 124 performs payment processing while referring to the user information 172.

[0031] The information processing unit 126 searches for information managed in the user information 172 and determines whether or not desired information is managed. The processing of the first management unit 128 and the second management unit 130 will be described in detail later.

[0032] FIG. 5 is a diagram showing an example of the contents of the user information 172. The user information 172 is an example of the registration information of a user. The user information 172 is, for example, a user URL, an account ID, a telephone number, a password, and other information associated with the user, such as an email address, a user ID, a name, an address, a date of birth, a registration date, a charge balance, a bank account, a credit card number, other service linkage information, radio wave authentication settings, carrier payment settings, a chat friend list, charge history information, payment history information, and chat history information. When registering for the electronic payment service, it is necessary to register a telephone number and a password. The account ID is issued to the user by the payment server 100, and the user ID is an ID that can be set by the user at will (but does not have to be set). Other information other than the user URL, account ID, telephone number, password, registration date, charge balance, charge history information, and payment history information is information that can be set by the user at will. Hereinafter, the instance (electronic payment account) of a user associated with these pieces of information is referred to as an account. The user URL is used for remittance processing between users. The registration date is the date on which the user registered with the electronic payment service (the date on which the account was created).

[0033] The charge balance is information indicating the balance of electronic money that is set by a user by transferring money to the account in advance. Means of transfer include transfer from an ATM (Automatic Teller Machine) of a designated business (bank) and transfer from a registered bank account. The bank account and credit card number are information (account number, card number) of a bank account or credit card number that can be deposited into the electronic payment service. The other service link information is the login ID of another service that links with the electronic payment service (for example, operated by an operator belonging to the same business group). The radio wave authentication setting is setting information when authentication is performed by communication with a specific communication carrier. The carrier payment setting is setting information for transferring at least a part of the payment made using the electronic payment service to a payment to the communication carrier. The chat friend list is a list of other users who are the chat partners in the chat function provided by the electronic payment service. The charge history information is a history of the user transferring money to the electronic payment service in advance to increase the charge balance. The payment history information is information that indicates the details of the payment made by the user for each payment (date and time, store ID of the store where the purchase was made, payment amount, etc.). The chat history information is a history of the content of the chats that the user has had.

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

[0035] The information processing unit 126 manages various information. The information processing unit 126 manages information obtained from the payment application 20 and information obtained from the service server 200, and provides information held by the payment server 100 to the payment application 20 and the service server 200.

[0036] [Service Server] Service server 200 is a server device that provides a service different from the electronic payment service provided in the electronic payment service. Service server 200 cooperates with payment application 20 and payment server 100 to provide a service to a user within the electronic payment service. Service server 200 provides a service in response to, for example, a user's operation on mini app 30, which will be described later.

[0037] [Processing Overview] The payment server 100 collects information from other services (service servers 200), and aggregates and manages the collected information. The payment server 100 provides some or all of the aggregated information to other services. FIG. 7 is a conceptual diagram (part 1) of the process. By this process, for example, when a user applies for a service as described later, the payment server 100 provides information to the service. The service can accept the application by using the provided information. For example, the user can pre-fill the user's information based on the aggregated information in the field to be input, so that pre-filling is expanded. Pre-filling means that the user's information is input in advance into the input field without relying on the user's operation. In addition, the payment server 100 can perform various analyses using the aggregated information to realize marketing optimization.

[0038] Furthermore, the payment server 100 can provide the service server 200 with either or both of the result of identity verification (so-called eKYC: electronic Know Your Customer) performed at the start of a given transaction in the payment service and information provided by the user for identity verification. This allows the service server 200 to omit newly performing identity verification or receiving the same information.

[0039] FIG. 8 is a conceptual diagram of the process (part 2). For example, when using an electronic payment service, a user provides customer information to the electronic payment service, and further provides documents for identity verification and an image of the required appearance to the electronic payment service. The electronic payment service performs identity verification using the provided information, and the user is able to use the electronic payment service. Identity verification is a process of verifying whether the information input by the user matches the information for identity verification provided by the user (for example, an identity verification document or an image captured by the user). For example, when the information input by the user matches the information on a driver's license, which is an identity verification document, and the image of the driver's license matches the appearance of the captured image, identity verification is completed. Identity verification may be performed automatically by computer processing, or part or all of the process may be performed by staff. Furthermore, public personal authentication may be used for identity verification. For example, identity verification may be performed using electronic information on a My Number card.

[0040] When identity verification is completed, the payment server 100 acquires information indicating that identity verification has been completed. If the user subsequently wishes to use deferred payment, asset management, or banking services provided in the electronic payment service, the user must apply separately for the use of these services.

[0041] For example, if the processing of this embodiment is not performed, the user must input customer information, provide documents for identity verification, and an image of the required appearance to the service server 200 when applying for each service, and the service server 200 must then perform screening, authentication, and the like. Thus, inputting and providing information when applying for each service places a heavy burden on the user. In addition, it is inconvenient for the service provider as well, since users are more likely to abandon the application process midway.

[0042] Therefore, in this embodiment, the payment server 100 provides information about the user, the authentication result of the identity verification, and the like to other service servers 200, thereby helping the user to use the service without the user providing information to each service. A specific description will be given below.

[0043] [Explanation of the functional configuration of the first management unit (information provider) and the second management unit (acquirer)] 9 is a diagram for explaining the functional configuration of the first management unit 128 and the second management unit 130. The first management unit 128 provides user information and information (e.g., authentication results of identity verification) managed by the payment server 100 in response to a request from the service server 200. For example, when a user applies for a service, the service server 200 requests the payment server 100 to provide user information necessary for the application, and obtains information in response to the request from the first management unit 128.

[0044] The second management unit 130 receives information provided by a user via the service server 200 from the service server 200 and information managed by the service server 200, and acquires this information. The second management unit 130 stores the provided information in the storage unit 170. For example, when the second management unit 130 receives information of a specific user, the second management unit 130 registers the provided information in association with the identification information of the user in the storage unit 170. One or both of the first management unit 128 and the second management unit 130 are interfaces that function as APIs (Application Programming Interfaces).

[0045] For example, the second management unit 130 can acquire information acquired in the asset management service server 200, and the first management unit 128 can provide the information acquired in the asset management service server 200 to the bank service server 200. This allows the payment server 100 to act as a hub for different services, allowing information acquired in each service to be shared among the different services. The above process is an example of a process of "providing the second information acquired by the acquisition unit (information acquired in the asset management service server 200) to a second service server (e.g., a bank service server) that runs in the electronic payment app and corresponds to a second mini app that provides another service."

[0046] FIG. 10 is a diagram showing an example of information registered by the second management unit 130. This information is, for example, information included in the user information 172. This user information 172 is, for example, information in which information IF1 (first information) and information IF2 (second information) are associated with a user ID (or account ID). Information IF1 is user information acquired by the payment application 20 and the payment server 100. Information IF1 includes, for example, information indicating the user's name, address, date of birth, occupation, status, confirmation date and time, confirmation method, and confirmation subject. The status is information indicating whether or not a predetermined confirmation has been performed. In the example of FIG. 10, for example, it indicates that the identity confirmation process has been completed. The confirmation date and time is the date and time when the identity confirmation was performed. The confirmation method is information indicating the document used for identity confirmation. The document is, for example, a driver's license or a My Number card. The confirmation subject is a subject that performed identity confirmation. In the example of FIG. 10, identity confirmation is performed by an administrator of the electronic payment service.

[0047] The information IF2 is information provided by the mini app 30 and the service server 200 (information registered by the second management unit 130), which will be described later. The information IF2 is, for example, information input by the user to an interface screen that the mini app 30 and the service server 200 cause to be displayed on the display unit of the user terminal device 10.

[0048] As described above, the type of information IF1 (first information) and the type of information IF2 (second information) may be predetermined or may be dynamically changed. For example, the payment server 100 may set the user's information held as information IF1, and other information as information IF2. For example, the user's name, attributes, contact information, and place of employment may be set as information IF1, and the rest may be set as information IF2. In this case, whether the payment server 100 holds information IF2 or not, the mini app 30 may provide the user with an interface screen (for example, an interface screen IM7 in FIG. 13 or an interface screen IM10 in FIG. 15 described later) and set the information input by the user as information IF2. In addition, when the payment server 100 holds information IF2, the payment application 20 may display an interface screen including information IF2 on the display unit of the user terminal device 10 and request the user to confirm the information.

[0049] As described above, the user information 172 of the payment server 100 manages information provided within the electronic payment service and information provided in other services.

[0050] [Interface image including a launch button to launch the mini app] The payment app includes one or more mini apps 30. FIG. 11 is a diagram showing the mini apps 30 included in the payment app 20. The mini app 30 is, for example, an app that uses the payment app 20 as a platform. The mini app 30 is, for example, an application program developed by a service provider that provides the service of the service server 200 to run within the payment app 20. The service provider develops the mini app 30 by referring to an SDK (Software Development Kit), which is a program and technical documentation for app development provided by an administrator of the payment app 20. The mini app 30 is, for example, an app that runs while the payment app 20 is running. For example, part or all of the mini app 30 may be installed when the payment app 20 is installed, or part or all of the mini app 30 may be installed from the service server 200 corresponding to the mini app 30.

[0051] The content providing unit 122 or the payment application 20 causes the display unit of the user terminal device 10 to display an interface image including a launch button for launching the mini application 30. For example, the content providing unit 122 causes the payment application 20 to display an interface image IM1, which will be described later.

[0052] 12 is a diagram showing an example of interface image IM1. Interface screen IM1 (an example of a first interface screen) is content provided in an electronic payment service, and includes QR codes (registered trademark) and barcodes used in electronic payments, and information related to various electronic payment-related services. Area AR1 of interface image IM1 includes one or more buttons for launching mini app 30. When launch button B1 is operated, bank mini app 30 is launched. The mini app 30 provides a service to the user in cooperation with, for example, the bank's service server 200.

[0053] [Processing related to mini app usage (part 1)] FIG. 13 is a diagram for explaining the process when opening a bank account using the mini app 30. In response to a user's operation, the mini app 30 cooperates with the service server 200 to display an interface screen IM2 (another example of the first interface screen) on the display unit. When a button (e.g., B2 or B3 in FIG. 13) for opening a bank account on the interface screen IM2 is operated, the information processing unit 126 of the payment server 100 acquires information indicating that the operation has been performed, and determines whether or not the user's name, attributes (e.g., date of birth, nationality, occupation, etc.), contact information, place of employment, and other information are registered in the user information 172. These pieces of information are acquired or managed by the payment server 100. The information processing unit 126 may perform this determination in response to a request from the service server 200. B2 or B3 in FIG. 13 is an example of a "start button" or an "application button". Also, the button B1 in FIG. 12 is another example of a "start button" or an "application button". For example, if operating button B1 in FIG. 12 starts processing for applying for use of a service, button B1 may be a "start button" or an "application button."

[0054] For example, if the user's name, attributes, contact information, and place of employment are not registered (the first information is not stored in the storage device managed by the electronic payment service), the payment server 100 and the payment application 20 display interface screens IM3, IM4, IM5, and IM6 on the display unit (interface screens for registered information are omitted). The interface screens IM3, IM4, IM5, and IM6 are examples of "second interface screens."

[0055] Interface screen IM3 is a screen for the user to input the name, interface screen IM4 is a screen for the user to input attributes, interface screen IM5 is a screen for the user to input contact information, and interface screen IM6 is a screen for the user to input the place of work. For example, information indicating that the information inputted into the interface screens will be registered in the user information 172 of the electronic payment service and will also be used in the mini app 30 (other services) is displayed. For example, information such as "These information will be registered in the user information of the electronic payment service and will also be used in the mini app" is displayed. When a specific button is operated, the user is deemed to have consented to the inputted information being used in the mini app 30.

[0056] When the information input by the user or the information provided by the user requires examination or authentication, the payment server 100 and the payment application 20 display an interface screen (not shown) for examination or authentication. For example, an interface screen for attaching or capturing an image of a driver's license, a My Number card, or a person is provided. When an image is attached to the interface screen and transmitted to the payment server 100, a predetermined examination or authentication is performed in the payment server 100, and processing according to the result of the examination or authentication is performed. For example, if the examination or authentication is positive, the information used for the examination or authentication and the result of the examination or authentication are registered in the user information 172, and if the examination or authentication is negative, the payment server 100 requests the user to provide other information. Note that examination or authentication may take a certain amount of time. If it takes time, the user may stop inputting here, wait for the examination, or resume inputting after the examination, or if it is permitted by the service providing the mini app 30, the user may proceed with inputting information other than the information waiting for examination.

[0057] After the payment server 100 acquires the predetermined information, the payment server 100 associates the acquired information with the user's identification information of the user information 172, stores the acquired information in the storage unit 170, and provides the stored information to the service server 200. The payment server 100 may provide the acquired information to the service server 200 in response to acquiring the predetermined information, or may provide the acquired information to the service server 200 in response to a request from the service server 200. The mini app 30 and the service server 200 display an interface screen IM7 on the display unit. The interface screen IM7 is information required for a service provided by the service server 200. For example, the information is information required by a service administrator when a user applies for a service. This information is information preset for each service, and is, for example, information not registered in the user information 172.

[0058] When the service server 200 acquires information required for the service, the service server 200 and the mini app 30 display an interface screen IM8 on the display unit. FIG. 14 is a diagram showing an example of the interface screen IM8. The interface screen IM8 is a confirmation screen for the input information. For example, the mini app 30 and the service server 200 display the interface screen IM8 on the display unit, which includes content in which the information acquired by the payment server 100 and the information acquired by the service server 200 are arranged in predetermined positions, as described above. This allows the user to check his or her own information.

[0059] [Processing related to the use of mini-apps (part 2)] 15 is a diagram for explaining the process when applying for use of a specific service using the mini app 30. In this process, it is assumed that the user's name, attributes, contact information, and place of work information are registered in the user information 172 (the first information is stored in the storage device).

[0060] In response to a user's operation, the mini app 30 cooperates with the service server 200 to display an interface screen IM9 on the display unit. When a button for inputting customer information on the interface screen IM9 is operated, the payment server 100 skips the process of acquiring information, and displays an interface screen IM10 on the display unit for the mini app 30 and the service server 200 to acquire information (My Number) required for using the service. The interface screen IM10 is an example of a "third interface screen." If the payment server 100 holds the required information, the payment server 100 provides the required information to the service server 200.

[0061] When the service server 200 acquires the information required for the service, the service server 200 and the mini app 30 display on the display unit an interface screen IM11 including content in which the information acquired by the payment server 100 and the information acquired by the service server 200 are arranged in predetermined positions, similar to the interface screen IM8 in Fig. 14 described above. This allows the user to check information such as the name and attributes entered at the start of a predetermined transaction of the payment service, and to check the information entered at the start of a predetermined transaction of the service. The process of correcting this information will be described later.

[0062] Furthermore, when multiple types of information IF1 (for example, the user's name, attributes, contact information, and workplace information) are not stored in the user information 172, the payment server 100 displays an interface screen on the display unit to allow the user to input the unstored types of information IF1, registers the information IF1 inputted on the interface screen in the user information 172 in association with the user's identification information, and provides the multiple types of information IF1 associated with the user's identification information to the service server 200. Thus, even when the payment server 100 does not store some of the information IF1, it can obtain some of the information IF1 and provide the information IF1 to the service server 200.

[0063] In addition, even if the information IF1 is stored in the storage unit 170, the payment server 100 may display an interface screen on the display unit of the user terminal device 10 to prompt the user to confirm the stored information IF1. For example, the user's information IF1 stored in the storage unit 170 is pre-filled on this interface screen. For example, if some information of the information IF1 is not stored in the payment server 100, the payment server 10 may display an interface screen on the display unit of the user terminal device 10 to prompt the user to input the unstored information IF1, and may display an interface screen on the display unit of the user terminal device 10 with the stored information IF1 pre-filled to prompt the user to confirm the stored information IF1. For example, if the user's name is not stored, the payment server 100 may display the interface screen IM3 on the user terminal device 10, and if other information IF1 is stored, may display the interface screens IM4-IM6 with the stored information IF1 pre-filled on the display unit of the user terminal device 10.

[0064] The above information IF1 (first information) may be information that satisfies a predetermined standard. The predetermined standard is, for example, a standard required for applying for a service. For example, the name may be registered in kanji, hiragana, or katakana, or the address may be registered. When the payment server 100 stores information IF1 (first information) that does not satisfy the predetermined standard, the payment server 100 may display an interface screen (such as interface screen IM3-6) with this information prefilled on the display unit of the user terminal device 10, and may request the user to correct the information so that it satisfies the predetermined standard.

[0065] [Sequence diagram for using mini apps] 16 is a sequence diagram showing an example of the flow of processing executed by the service system and the payment system. The service system is one or both of the mini app 30 and the service server 200, and the payment system is one or both of the payment application 20 and the payment server 100. The service system and the payment system share identification information for identifying a user.

[0066] First, the user activates the mini app 30 via the operation of the payment app 20, and when the user performs an operation to make a specific application provided by the service system, the service system requests the payment system to provide information about the user (S50). The payment system searches for user information 172 (S52) and transmits the search results to the service system (S54). For example, if the payment server 100 holds information (first information, information IF1) for the payment server 100 to acquire or manage, it provides this information to the service system.

[0067] If the payment server 100 does not hold the information to be acquired or managed by the payment server 100, the payment system executes a process for inputting the information (for example, providing an interface screen) (S56). Next, the payment system provides the input information to the service system (S58). In addition, the input information is registered in association with the user's identification information in the user information 172.

[0068] Next, the service system executes a process for having the user input information required by the service (S60). Next, the service system provides the input information to the payment system (S62). Next, the payment system registers the information in association with the user identification information of the provided user information 172 (S64). Note that the processes of S62 and S64 may be omitted, or information for which the user has agreed to share the information with the payment system may be provided to the payment system. Also, whether to omit the processes of S62 and S64 may be determined depending on the type of the service system.

[0069] As described above, the service system can perform processing related to the user's use of the service by using information obtained by or managed by the payment server 100. Fig. 17 is a conceptual diagram of information sharing. For example, when a user logs in to the payment application 20 and starts a transaction for another service, the service server 200 can perform screening and procedures for the start of the transaction by using information input at the start of a specific transaction in the payment service, an identity verification document, an image of the user's appearance, and the like.

[0070] This reduces the load on the service server 200 for acquiring information. In addition, the user does not need to input the same information twice, which reduces the load on the user.

[0071] In the above description, it has been described that the information acquired by the payment server 100 is provided to the service server 200. In addition to this (or instead), the result of identity verification by the payment server 100 may be provided to the service server 200. FIG. 18 is a conceptual diagram of providing identity verification results. For example, in a state where a user is logged in to the payment application 20, when the user starts a transaction for another service, the service server 200 provides the result of identity verification (so-called eKYC) performed at the start of a predetermined transaction in the payment service and the results of other examinations to the service server 200. The service server 200 can perform examination and procedures for the start of a transaction using or referring to the provided result of identity verification and the results of other examinations.

[0072] [Processing for correction of information] FIG. 19 is a diagram for explaining a process of correcting information on the input content confirmation screen. When a user operates a button for correcting information on interface screen IM11 (input content confirmation screen), payment application 20 and payment server 100 display interface screens IM12, IM13, and IM14 (an example of a "fourth interface screen") on the display unit. Interface screen IM12 includes information indicating that updating of personal identification information is necessary to edit user information, an update button for performing the update, and the like. Updating personal identification information means, for example, updating information associated with the user's identification information managed in payment server 100. For example, it means that personal identification processing such as sending an image of a driver's license again is necessary.

[0073] For example, when editing an email address, interface screen IM13 for inputting an email address by a predetermined operation is displayed, and when the email address is edited and the predetermined operation is performed, interface screen IM14 is displayed. An authentication email is sent to the input email address, and when the user performs an operation for authentication using the authentication email on interface screen IM14, the email address is updated.

[0074] As described above, when the user information acquired by the payment system or the user information acquired by the service system is modified, the payment system executes an interface screen and process for modifying the information, and updates the user information 172 of the user (updates the first information). In this way, the payment system updates the user information 172 of the user and newly registers the updated information in the user information 172, so that when providing information to another service, it is possible to provide information that reflects the modification. This process is an example of a process in which "after the first information is updated, when a start button for starting a second service included in the first interface screen is operated, the control unit provides the changed first information to a second service server corresponding to second mini app 30 that runs in the electronic payment app and provides a second service."

[0075] When an operation to modify information (second information) required for the mini app 30 and the service server 200 to use the service, which is acquired on the interface screen IM10, is performed on the interface screen IM11, the payment server 100 and the payment application 20 do not provide an interface screen for the modification, but display on the display unit an interface screen (an example of a "fifth interface screen") for changing the required information in accordance with the operation for modification by the mini app 30 and the service server 200.

[0076] [Sequence diagram for modifying information] Fig. 20 is a sequence diagram showing an example of the flow of processing executed by the service system and the payment system. First, when a user performs an operation to correct information on the interface screen IM11, the service system transmits information indicating that the operation of correction has been performed to the payment system (S100). Next, the payment system executes processing for correction (S102). For example, an interface screen for inputting information to be corrected may be provided, and the information input or provided by the user may be examined or authenticated.

[0077] Next, the payment server 100 updates the registered information in the user's user information 172 to information corresponding to the correction (S104). As a result, the information updated according to the correction is registered in the user's user information 172. Next, the payment system provides the corrected information to the service system (S106). Next, the service system displays an interface screen including information reflecting the correction on the display unit (S108). For example, if the address is changed, an interface screen in which the address before the change is corrected to the address after the change is displayed on the interface screen IM11.

[0078] As described above, when the user's information is modified by an operation on an interface screen provided by the service system, the payment system performs processing according to the operation to accept the modification, and updates the user's user information 172 according to the modification. This enables the payment server 100 to obtain and hold the latest information, and provide the latest information to other services.

[0079] [Conditions for applying for services provided by the service system using mini-apps] 21 is a diagram for explaining the conditions for applying for a service provided by the service system using the mini app 30. For example, some or all of conditions 1 to 8 are application conditions using information managed in the above-mentioned payment service.

[0080] For example, when the user is logged in to use payment app 20 (condition 2), an interface screen is displayed on the display unit, an application button included in the interface screen is operated to apply for use of other services, and the user's usage of the electronic payment service meets the conditions set in the electronic payment service (e.g. condition 7) and the user's identity verification has been completed in the electronic payment service (e.g. conditions 1 and 5), completion information indicating that identity verification has been completed is provided to service server 200 which operates in payment app 20 and provides other services to the user in cooperation with mini app 30, and instructs service server 200 to proceed with processing related to the application, and if button B1 is operated and the set conditions are not met or the user's identity verification has not been completed, service server 200 is caused to at least temporarily halt the application.

[0081] When proceeding with the application process, the payment server 100 executes the processes described above with reference to Figures 13 to 15 etc. For example, the payment server 100 causes the payment application 20 to display an interface screen for inputting information (first information input) or causes the mini application 30 to display an interface screen for inputting information (second information input) depending on the information held by the payment server 100.

[0082] Furthermore, when an application button for applying for use of the first service or an operation button for starting use of the first service included in an interface screen displayed on the display unit is operated while the user is logged in to use the payment application 20, the payment server 100 causes the display unit to display an interface screen for executing authentication using a biometric authentication function installed in the user terminal device 10 of the user, and when biometric authentication (condition 6) is established in response to the user's operation on the interface screen, causes the display unit to display an interface screen corresponding to the operation. In other words, when biometric authentication is established, use of a predetermined service provided by the service server 200 is permitted.

[0083] (Condition 1) The administrator of the electronic payment service has performed a predetermined confirmation of the user, and the predetermined confirmation has been completed. For example, the confirmation items performed at the start of use of the electronic payment service have been completed. For example, when the predetermined confirmation has been completed, a flag indicating whether or not identity verification has been completed is added to the identification information of the user in the user information 172, and by sharing this flag, the payment server 100 or the service server 200 can determine whether or not condition 1 is satisfied (see FIG. 10).

[0084] (Condition 2) The user must be logged in to the payment application 20. By logging in to the payment application 20, the user can use the mini app 30 and apply for a service using the mini app 30.

[0085] (Condition 3) The user's identification information is shared between the payment service and the service system. This is because the service server 200 can acquire information managed by the payment server 100 by cooperating with the second management unit 130 using the user's identification information as a key (see FIG. 9 described above). It is assumed that consent to providing the user's information to the service server 200 has been obtained from the user.

[0086] (Condition 4) The service is capable of acquiring information on the identity verification date and time and the verification method of the target user via the second management unit 130 (e.g., an API). For example, the service is capable of acquiring the identity verification date and time and the verification method managed by the payment server 100 as shown in Fig. 10 described above. For example, the service is capable of acquiring the above information by cooperating with the second management unit 130.

[0087] (Condition 5) The entity that performs the transaction confirmation is the administrator of the electronic payment service. Transaction confirmation is confirmation for the use of electronic payment services. The entity that performs this confirmation is the administrator of the electronic payment service.

[0088] (Condition 6) The electronic payment service performs a predetermined authentication when a specific transaction is made using the mini app 30. This will be described later (see Figs. 22 and 23).

[0089] (Condition 7) The user is not a user who has performed a transaction suspected of impersonation in an electronic payment service or a transaction with a customer suspected of lying. For example, the payment server 100 uses a predetermined judgment criterion to identify a user who satisfies the above conditions, and executes a suspend process for the identified user. The suspend process means to suspend or stop the identified user's use of the electronic payment service and related services.

[0090] (Condition 8) The user does not satisfy the usage prohibition condition. Whether or not the usage prohibition condition is satisfied is determined based on, for example, information associated with the user's identification information in the user information 172. The usage prohibition condition is, for example, various conditions such as a user that is set in advance.

[0091] [Explanation regarding (Condition 6)] When the user is logged in to use the payment application 20 and a button for starting the first service included in the first interface screen displayed on the display unit is operated, or when a process for receiving the service in response to the operation of the button for starting the service is completed (for example, after the application is completed), the payment server 100 displays on the display unit an interface screen for executing authentication using a biometric authentication function installed in the user terminal device 10 of the user, and when biometric authentication is established in response to the user's operation on the interface screen, displays on the display unit an interface screen for proceeding with the process in response to the operation. The interface screen in response to the operation is, for example, an interface screen for proceeding with the application or an interface screen for starting the service.

[0092] FIG. 22 is a flow chart showing an example of the flow of the authentication process. First, the payment application 20 judges whether an operation for performing a specific transaction has been performed on the mini application 30 (S200). If an operation has been performed, the payment application 20 displays an interface screen requesting a specific authentication on the display unit (S202). The specific authentication is, for example, authentication realized by a function (for example, an OS (operating system) or an application program) installed in the user terminal device 10. For example, it is authentication for unlocking the user terminal device 10. The authentication may be, for example, biometric authentication or authentication using a password. The biometric authentication is, for example, authentication using face authentication, fingerprint, iris, etc. The biometric information used for authentication is information registered by the user using the function of the user terminal device 10.

[0093] Next, the user terminal device 10 judges whether or not authentication has been established (S204). If authentication has been established, the mini app 30 and the service server 200 provide a service (S206). For example, the process for starting a transaction with the user may be continued, or the transaction may be started. If authentication has not been established, the mini app 30 and the service server 200 do not provide a service, and one routine of this process ends.

[0094] 23 is a diagram showing an example of the transition of an interface screen when authentication is performed. For example, when an operation to start a transaction is performed on an interface screen for starting a transaction provided by the mini app 30, the payment application 20 displays an interface screen including information indicating that authentication is to be performed on the display unit. If the user agrees to this, the user terminal device 10 performs authentication. If authentication is successful, the mini app 30 displays an interface screen for starting a transaction on the display unit.

[0095] For example, assuming that the above authentication is not used, the user needs to provide images of the driver's license taken from multiple angles, images of the back of the driver's license, images of the user's appearance, and the like to the payment server 100 or the service server 200. In contrast, in this embodiment, authentication is performed as described above, and the above processing is omitted, improving user convenience.

[0096] In the above process, authentication is performed when applying for use of the service, but in addition (or instead), authentication may be performed each time use of the service is started after application is completed (however, authentication may be omitted for a certain period after authentication). This improves security.

[0097] According to the first embodiment described above, the payment server 100 executes appropriate processing according to the information held or the result of identity verification. This allows the user to easily use the service, and the service server 200 can provide the user with the service by utilizing the information managed by the payment server 100 or the result of identity verification. As a result, the convenience for the user is improved, and the processing load of the service server 200 is reduced.

[0098] <Second embodiment> The second embodiment will be described below. In the second embodiment, information indicating a risk regarding a transaction with a user is associated with the user identification information of the user information, and this information is provided to the service server 200. The following description will focus on the differences from the first embodiment.

[0099] Fig. 24 is a diagram expressing a part of the functional configuration of the payment server 100A of the second embodiment. The payment server 100A includes, for example, a first acquisition unit 132, a second acquisition unit 134, and a flag generation unit (derivation unit) 136 in addition to the functional configuration of the payment server 100 of the first embodiment. Some of these functional configurations may be included in other devices. The payment server 100A is an example of an "information processing device".

[0100] The first acquisition unit 132 acquires user information, which is either or both of the user's usage mode of the electronic payment service and information about the user provided by the user in order to use the electronic payment service. The usage mode is, for example, the user's history of using the electronic payment service, such as the payment amount and information about the store where the payment was made. The information about the user is information provided to the electronic payment service when the user applies to use the electronic payment service. For example, this is information IF1 in FIG. 10 described above.

[0101] The second acquisition unit 134 acquires communication information, which is one or both of information about the device used by the user to use the electronic payment service and information about the network used by the user. The information about the device is information about the type of device of the user terminal device 10 and information such as an IP address (Internet Protocol Address). The information about the network is information about the Internet service provider accessed by the user terminal device 10 and information about the network used for communication. For example, this information is acquired by the payment application 20 and provided to the payment server 100.

[0102] The flag generating unit 136 derives the reliability of the user based on the user information and the communication information. The flag generating unit 136 generates a risk flag according to the reliability, for example, or derives a score according to the reliability. These pieces of information are provided to the service server 200. For example, the second management unit 130 provides the service server 200 with information indicating the reliability, information on the user held by the payment server 100, and information indicating the result of identity verification in response to a request from the service server 200. For example, when a user is logged in to use the payment application 20 and an application button for applying for use of another service included in an interface screen displayed on the display unit is operated, the second management unit 130 may provide the service server 200 with information indicating the reliability, information on the user, and information indicating the result of identity verification in response to a request from the service server 200.

[0103] The flag generating unit 136 is set based on, for example, user information, communication information, and also conditions associated with the user (conditions based on user information) and conditions not associated with the user (conditions based on communication information). Fig. 25 is a diagram for explaining conditions for setting a flag. Conditions associated with the user include, for example, that the user satisfies a predetermined condition, that a condition in the user's usage mode of the electronic payment service is satisfied, and that there is a defect in the information managed in the payment server 100.

[0104] A user meeting a predetermined condition means that the user is a user who has been registered in advance on a list. For example, high-risk users are registered on this list. A user meeting a condition in the manner of use of the electronic payment service means, for example, that the electronic payment service is being used in a pre-set manner, such as making a predetermined number of large payments or more. A deficiency in information means, for example, an inconsistency in the information (for example, a mismatch between the prefecture and city / ward / town / village of the address) or a deficiency in necessary information (for example, a lack of necessary information).

[0105] Conditions that are not linked to a user include, for example, access from a pre-set device, access from a pre-set IP address, and access via a pre-set Internet service provider. For example, if a device, IP address, or Internet service provider that is deemed to be high risk is used, it is deemed to be high risk.

[0106] The flag generating unit 136 sets a flag when the user satisfies the above-mentioned conditions for setting a flag. The generated flag is provided to the service server 200. For example, when the second management unit 130 provides user information to the service server 200, the second management unit 130 provides the flag to the service server 200 in association with the user information. This enables the service server 200 to recognize that the target user is a high-risk user and to determine whether or not to provide a service in consideration of the recognition result.

[0107] In the above example, a flag is assigned to a high-risk user, but instead of this, a flag according to the level of risk may be assigned. For example, a flag according to the level of risk, such as a high risk flag, a medium risk flag, or a low risk flag, may be assigned. Also, instead of a flag, a score indicating the level of risk may be assigned. The flag generation unit 136 derives a score by referring to a criterion based on the above-mentioned conditions, and associates the derived score with the identification information of the user.

[0108] 26 is a diagram showing an example of the contents of user information 172A in the second embodiment. In addition to the information described in the user information 172, the user information 172A associates a risk flag with the user's identification information.

[0109] Also, for example, the flag generating unit 136 may assign a flag to the user's identification information according to the risk from among predetermined types of flags including a gray flag, a black flag, and a white flag. A black flag is a flag set for a user who meets a condition not linked to the user. Also, a black flag may be set for a user who meets a predetermined condition among the conditions linked to the user. A black flag is a flag indicating that the reliability is less than a second threshold value.

[0110] The gray flag is a flag set for a user whose user information satisfies a predetermined condition among the conditions associated with the user (for example, a user who satisfies the conditions related to electronic payment or the information is incomplete) and does not fall under the conditions not associated with the user. The gray flag is a flag indicating that the reliability is less than a first threshold and is equal to or greater than a second threshold.

[0111] A white flag is assigned to a user who does not meet the conditions associated with the user and the conditions not associated with the user.

[0112] For example, when a white flag user performs an operation to apply for use of the mini app 30 service, the payment server 100 allows the user to use the service without going through the procedures required by a grey flag user, which will be described later.

[0113] For example, when a user with a gray flag performs an operation to apply for use of the mini app 30 service, the payment server 100 requests the user to perform identity verification again, which is performed by the electronic payment service. For example, the payment server 100 displays an interface screen for performing identity verification again on the display unit. Note that this interface screen may be displayed by the service server 200 that has acquired the gray flag.

[0114] For example, when a user with a black flag performs an operation to apply for use of the service of the mini app 30, the payment server 100 causes the display unit to display an interface screen including information indicating that the service is not available. Note that this interface screen may be displayed by the service server 200 that has acquired the black flag.

[0115] According to the second embodiment described above, the payment server 100 generates information on the risk of the user and provides the generated information to the service server 200. This allows the service server 200 to refer to the acquired information indicating the risk and determine whether to provide a service to the user. As a result, a more accurate determination regarding the provision of the service is made.

[0116] <Other examples (1)> In the above example, it was explained that when a user operates the mini app 30 while logged in to the payment app 20, the information held in the payment server 100 is shared with the service server 200. However, instead of this (or in addition to this), the information may be shared when the user's user terminal device 10 accesses the service server 200 without using the mini app 30.

[0117] FIG. 27 is a diagram for explaining the process of the other example (1). For example, the user terminal device 10 accesses the bank service server 200 without going through the mini app 30, and the user is about to open a bank account. For example, when an operation for opening a bank account is performed on an interface screen provided by the service server 200, the service server 200 inquires the user as to whether or not to log in to an electronic payment service and link the electronic payment service with the bank service server 200. When the user selects linkage and performs a predetermined operation to input the user's identification information and password used for logging in and the electronic payment service, the bank service server 200 acquires the user's information and the result of identity verification managed by the payment server 100 from the payment server 100. The bank service server 200 can proceed with the process of opening the bank account by using the acquired information and the result of identity verification.

[0118] As described above, even without going through the mini app 30, the user can have his / her own information stored in the payment server 100 used in other service servers 200, thereby improving user convenience and reducing the processing load of the service server 200.

[0119] <Other examples (2)> When the payment server 100 updates information associated with the user's identification information of the user information 172 in response to a user's operation, the payment server 100 may provide information indicating that the information has been updated or the contents of the update to the predetermined service server 200. For example, when a user updates his / her address on an interface screen provided by the payment server 100 while applying for a bank account, the payment server 100 may provide information indicating that the address has been updated to, for example, the service server 200 of the credit card company (the predetermined service server 200). For example, since it is necessary to obtain the latest information in credit card credit, settlement, etc., when information is updated in applying for another service, the payment server 100 provides information indicating that the information has been updated and the contents of the update to the service server 200 of the credit card company.

[0120] As described above, when the user information is updated, the payment server 100 provides information about the update to the other service servers 200, so that the service servers 200 and the payment server 100 can hold the latest information. In addition, the user does not need to update information for all services, which improves user convenience.

[0121] <Other examples (3)> When a user updates user information on an interface screen provided by the service server 200 and the service server 200 updates the user information, the service server 200 may provide the payment server 100 with information indicating that the user information has been updated and the contents of the update. The payment server 100 may update the user information in the user information 172 based on this information. Furthermore, the payment server 100 may provide other service servers 200 with the information indicating that the information has been updated and the contents of the update.

[0122] As described above, when the user information is updated in the service server 200, the payment server 100 can obtain information related to the update from the service server 200, thereby holding the latest information.

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

[0124] 10 User terminal device 20. Payment App 30 Mini Apps 50 First store terminal device 60 Store Code Image 70 Second store terminal device 100 Payment Server 121 Service Information Acquisition Department 122 Contents Provider 124 Payment processing unit 126 Information Processing Department 128 1st Management Department 130 2nd Management Department 132 First acquisition part 134 Second Acquisition Department 136 Flag Generation Unit 170 Storage section 172 User information 174 Payment Content Information

Claims

1. A service management device that provides a predetermined service, When an application button for applying to use other services included in the first interface screen displayed on the terminal device's display unit is operated, and the user's usage of the predetermined service satisfies the conditions set in the predetermined service, and the user's identity verification has been completed in the predetermined service, the application of the predetermined service, in cooperation with the mini-application that provides the other service, provides completion information indicating that the identity verification has been completed to the service server that provides the other service to the user, and instructs the service server to proceed with the processing related to the application. If the application button is pressed and the set conditions are not met, or if the user's identity verification is not completed, the control unit instructs the service server to at least temporarily suspend the application. A service management device equipped with the following features.

2. The control unit, When an application button for applying to use the first service or an operation button for starting to use the first service, included in the first interface screen displayed on the display unit, is operated, an interface screen for performing authentication using the biometric authentication function installed in the user's terminal device is displayed on the display unit. When biometric authentication is successful in response to the user's operation on the interface screen, the interface screen for proceeding with the processing corresponding to the operation is displayed on the display unit. The service management device according to claim 1.

3. The control unit provides the user's identification information to the service server corresponding to the mini-application and shares the user's identification information. The service management device according to claim 1.

4. The system further includes an information provision unit that acquires completion information indicating that the identity verification corresponding to the shared user identification information stored in the memory unit has been completed, date and time information indicating the date and time when the identity verification was completed, and method information indicating the method of the identity verification, and provides the acquired completion information, date and time information and method information to the service server. The service management device according to claim 3.

5. In promoting the aforementioned applications, The control unit, when the first information among the information necessary for the application, including the first information and the second information, is stored in the storage device, executes a process to display a third interface screen on the display unit for causing the user to input the second information into the first mini-application that provides the first service, which is the other service. The first information is information required for using the services of the first mini-app and for using the services of mini-apps different from the first mini-app. The second information is information necessary for using the service of the first mini-app. A service management device according to any one of claims 1 to 3.

6. In promoting the aforementioned applications, If the first information among the information necessary for the application, including the first information and the second information, is not stored in the storage device, the control unit displays an interface screen on the display unit for the user to input the first information. The first information is information required for using the services of the first mini-app that provides the first service, which is the other service, and for using the services of a mini-app different from the first mini-app. The second information is information necessary for using the service of the first mini-app. A service management device according to any one of claims 1 to 3.

7. The system further includes an information provision unit that provides the first information entered into the interface screen to the first service server corresponding to the first mini-application. The service management device according to claim 6.

8. The information provision unit provides the first service server with the identity verification authentication result obtained based on the identity verification information acquired from the user's terminal device and the first information. The service management device according to claim 7.

9. The service management device according to claim 8, The system comprises a service server that initiates the provision of a service to a user based on the first information and the authentication result, Service management system.

10. The system further includes an acquisition unit that acquires the second information from a first service server corresponding to a first mini-application that provides the first service, which is another service. The service management device according to claim 5.

11. The system further includes an information provision unit that provides the second information acquired by the acquisition unit to a second service server corresponding to a second mini-application that provides the other services. The service management device according to claim 10.

12. A service management method for providing a predetermined service, Computers When an application button for applying to use other services included in the first interface screen displayed on the terminal device's display unit is operated, and the user's usage of the predetermined service satisfies the conditions set in the predetermined service, and the user's identity verification has been completed in the predetermined service, the application of the predetermined service, in cooperation with the mini-application that operates and provides the other service, provides completion information indicating that the identity verification has been completed to the service server that provides the other service to the user, and instructs the service server to facilitate the application. If the application button is pressed and the set conditions are not met, or if the user's identity verification is not completed, the service server will not prompt the application. Service management methods.

13. A program that provides a predetermined service, On the computer, When an application button for applying to use other services included in the first interface screen displayed on the terminal device's display unit is operated, and the user's usage of the predetermined service satisfies the conditions set in the predetermined service, and the user's identity verification has been completed in the predetermined service, the application of the predetermined service, in cooperation with a mini-application that provides the other service, provides completion information indicating that the identity verification has been completed to the service server that provides the other service to the user, and instructs the service server to proceed with the application process. If the application button is pressed and the set conditions are not met, or if the user's identity verification is not completed, the service server is instructed to at least temporarily suspend the application. A program that executes the command.

Images