JP2024021760A - Service management device, service management system, service application, service management method, and program - Google Patents

Abstract

[Problem] To improve user convenience. [Solution] A service management device that provides a service, in which a button for starting a first service on a first interface screen displayed on a display unit while a user is logged in to a service application. If the first information is not stored in the storage device managed by the electronic payment service, the first information is not stored in the storage device managed by the electronic payment service. If the second interface screen for the user to input is displayed on the display unit, the button is operated, and the first information among the information necessary to receive the service is stored in the storage device, the service application A service management device comprising a control unit that executes processing for displaying on a display unit a third interface screen for allowing a user to input second information into a first mini-app that operates in a first mini-app that provides a first service. [Selection diagram] Figure 4

Description

The present invention relates to a service management device, a service management system, a service application, a service management method, and a program.

BACKGROUND ART Conventionally, in electronic commerce, a system is known that performs electronic authentication for identity verification and performs electronic payment based on the electronic authentication (for example, see Patent Document 1).

Japanese Patent Application Publication No. 2002-123726

However, the above-mentioned devices are sometimes inconvenient for users.

The present invention has been made in consideration of such circumstances, and aims to provide a service management device, a service management system, a service application, a service management method, and a program that can improve user convenience. Make it one of the objectives.

One aspect of the present invention is a service management device that provides an electronic payment service, in which a first interface screen displayed on a display unit when a user is logged in to use a service application. A button for starting the service is operated, and the first information among the information necessary for the application including the first information and the second information is stored in a storage device managed by the electronic payment service. If not, a second interface screen for allowing the user to input the first information is displayed on the display unit, the button is operated, and the first information among the information necessary for the application is stored in the storage device. If so, execute a process for displaying on the display unit a third interface screen for allowing the user to input the second information into a first mini-application running in the service application and providing the first service. This is a service management device equipped with a control unit.

According to one aspect of the present invention, it is possible to provide a service management device, a service management system, a service application, a service management method, and a program that can improve user convenience.

1 is a diagram illustrating an example of a configuration for realizing an electronic payment service. 2 is a sequence diagram illustrating the general flow of electronic payment of pattern 1. FIG. FIG. 7 is a sequence diagram illustrating the general flow of electronic payment of pattern 2. 1 is a configuration diagram of a payment server 100. FIG. 3 is a diagram showing an example of the contents of user information 172. FIG. It is a diagram showing an example of the contents of member store/store information 176. FIG. 2 is a conceptual diagram (part 1) of processing. It is a conceptual diagram (part 2) of a process. 3 is a diagram for explaining the functional configuration of a first management section 128 and a second management section 130. FIG. 7 is a diagram showing an example of information registered by the second management unit 130. FIG. 3 is a diagram showing a mini-app 30 included in a payment application 20. FIG. It is a figure showing an example of interface image IM1. 3 is a diagram for explaining processing when opening a bank account using the mini app 30. FIG. It is a figure showing an example of interface screen IM8. FIG. 3 is a diagram for explaining processing when applying for use of a predetermined service using the mini app 30. FIG. FIG. 2 is a sequence diagram illustrating an example of the flow of processing executed by the service system and the payment system. FIG. 2 is a conceptual diagram of information sharing. It is a conceptual diagram of provision of an identity verification result. FIG. 6 is a diagram for explaining a process in which information is corrected on an input content confirmation screen. FIG. 2 is a sequence diagram illustrating an example of the flow of processing executed by the service system and the payment system. 3 is a diagram for explaining conditions for applying for a service provided by a service system using a mini app 30. FIG. 3 is a flowchart illustrating an example of the flow of authentication processing. FIG. 6 is a diagram showing an example of transition of an interface screen when authentication is performed. It is a figure which shows an example of the content of user information 172A of 2nd Embodiment. FIG. 3 is a diagram for explaining conditions under which a flag is set. It is a diagram showing part of the functional configuration of a payment server 100A according to a second embodiment. FIG. 7 is a diagram for explaining processing of another example (1).

DESCRIPTION OF THE PREFERRED EMBODIMENTS A service management device, a service management system, a service application, a service management method, and a program according to the present invention will be described below with reference to the drawings. Further, an information processing apparatus, an information processing method, and a program will be described below with reference to the drawings.

The service management device is realized by one or more processors. A service management device that provides a service, the first service included in the first interface screen displayed on the display unit of the user terminal device while the user is logged in to use the service application. If the button for starting the application is operated and 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 managed by the service, the first information is not stored in the storage device managed by the service. a second interface screen for allowing the user to input one information is displayed on the display unit, the button is operated, and the first information among the information necessary for the application is stored in the storage device; a control unit that executes processing for displaying on the display unit a third interface screen for allowing the user to input the second information into the first mini-app that operates in the service application and provides the first service; For example, a content providing section). The above-mentioned services are, for example, arbitrary services such as electronic payment services, chat applications, and social network services. In the following description, an electronic payment service will be described as an example.

The first information is, for example, information obtained by a user inputting information on an interface screen provided by an electronic payment application. The second information is, for example, information obtained by the user inputting information on an interface screen provided by the mini app. The first information is, for example, information required for using the service of the first mini app and for using the service of a mini app different from the first mini app. The second information is, for example, information required to use the service of the first mini-app. The first interface screen may be any screen that includes a button for starting the service. The first interface screen may be a screen provided by an electronic payment application or a screen provided by a mini-app. The button for starting the first service is a button that is operated to start using the service. For example, when the user uses the service, the user provides the user's information to the service server and starts the service. This button corresponds to the operation that triggers its use. In other words, the button for starting a service can also be called an application button for applying for a service.

The process for displaying the third interface screen on the display unit is to display 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 may instruct the first mini-app or the service server to display the third interface screen.

A payment management device that provides an electronic payment service, wherein a first interface screen is displayed on a display unit in a state where a user is logged in to use an electronic payment application, and other information included in the first interface screen is displayed on a display unit. The application button for applying to use the service is operated, the manner in which the user uses the electronic payment service satisfies the conditions set in the electronic payment service, and the user's identity verification is completed in the electronic payment service. If so, a completion message indicating that the identity verification has been completed is sent to the service server that operates in the electronic payment application and provides the other service to the user in cooperation with the mini-app that provides the other service. If the user provides information and instructs the service server to proceed with the processing related to the application, and the application button is operated and the set conditions are not met or the user's identity verification is not completed, The service server includes a control unit that causes the application to be stopped at least temporarily.

The above-mentioned "instructing the service server to proceed with the processing related to the application" means, for example, causing the mini app or the service server to display an interface screen for the application on the display unit or to provide the service. That's true. Temporary suspension means, for example, displaying an interface screen on the display section of the payment app, payment server, mini app, or service server indicating that the service is unavailable, or causing the payment app, payment server, mini app, or service server to display an interface screen on the display that indicates that the service is unavailable, or It is to provide information indicating that processing, examination, etc. are necessary.

The information processing device includes a first acquisition unit that acquires user information of one or both of a usage mode of the electronic payment service by the user and information regarding the user provided by the user in order to use the electronic payment service; a second acquisition unit that acquires communication information that is one or both of information regarding a device used by the user in using the electronic payment service and information regarding a network used by the user; and the user information; a deriving unit that derives the reliability of the user based on the communication information; and a providing unit (for example, a first management unit) that provides the reliability to a service server that provides a service different from the electronic payment service. (see second embodiment).

<First embodiment>
[Electronic payment service]
FIG. 1 is a diagram illustrating an example of a configuration for realizing an electronic payment service. The electronic payment service is realized mainly by the payment server 100. The payment server 100 includes, 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. It communicates with each via the 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, if service servers 200-1 to 200-3 are not distinguished, they will be referred to as service servers 200. The payment server 100 is an example of a "payment management device" or a "service management device."

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

The first store terminal device 50 is installed in a store, for example. 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 POS device may realize a product price acquisition function and an optical reading function. The store code image 60 is placed in a store, and a code image such as a QR code (registered trademark) is printed on a paper or plastic medium. Note that the store code image 60 may be displayed on a display (or a display of a terminal device such as a smartphone) placed in the store.

The second store terminal device 70 is used by an operator of a member store. The second store terminal device 70 is a smartphone, a tablet terminal, a personal computer, or the like. In the second store terminal device 70, an interface 72 for member stores operates. The member store interface 72 may be an application for member stores or may be a browser. The member store interface 72 receives coupon settings and the like from the member store operator 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 the store code image and reading the code image displayed by the user terminal device 10 by executing an application for member stores. have

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 a member store server, in which case payment information is transmitted from the POS device to the payment server 100 via the member store server. In the following description, it is assumed that payment information is transmitted from the first store terminal device 50 without making any particular distinction. The payment server 100 performs electronic payment by, for example, decreasing the charge balance managed in association with the user ID and increasing the item value of the member store's sales proceeds. For example, the item value of the sales proceeds of a member store is not used as electronic money itself, but the amount corresponding to the item value of the sales proceeds is determined in a cycle according to the agreement between the member store and the electronic payment service. Money will be transferred to your bank account. Electronic payments may include methods such as revolving payment and credit card payments that enable purchases of a larger amount than the charge balance at the time of purchase.

2 and 3 are sequence diagrams illustrating the general flow of electronic payment. There may be two patterns, pattern 1 and pattern 2, in electronic payment.

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 using an optical reading function (S1). The store code image 60 includes information on a store URL (Uniform Resource Locator). This store URL is the domain of the electronic payment service added with information that can identify the store, and is associated with member store IDs, store IDs, etc. in the payment server 100 (described later). The payment application 20 transmits 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 later) from the member store ID and store ID corresponding to the store URL, obtains the member store name and store name information (S3), and sends the information to the payment application 20 (S4). . The user inputs the payment amount into the user terminal device 10 on the screen on which the member store name and 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 notification (information for displaying the 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 step for the user to input the payment amount is omitted. For example, since the payment application 20 causes the display unit to display a screen in which the payment amount has been input, S5 described above is omitted. When the user confirms the amount and performs a predetermined operation, first payment information including the payment amount is transmitted to the payment server 100. Information on the member store name and store name may be included and displayed on the payment completion screen.

In the case of pattern 2 (hereinafter referred to as store scan) shown in FIG. sends a request to issue 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 sends it to the payment application 20 (S13). The payment application 20 displays a code image, such as a QR code or barcode, generated based on the one-time code (S14). The user holds up (presents) the display surface of the user terminal device 10 to the first store terminal device 50, and the first store terminal device 50 decodes the code image using an optical reading function and acquires a one-time code ( S15). Then, the first store terminal device 50 generates payment information including a one-time code, payment amount, member store ID, store ID, etc., and transmits it to the payment server 100 (S16). Information on the payment amount is obtained in advance by barcode reading, manual input, etc. 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). Then, the payment server 100 transmits a payment completion notification to the payment application 20 (S18), and the payment application 20 displays a payment completion screen (S19).

Note that electronic payment may be performed using only one of the above patterns. Moreover, the "account ID" explained in FIG. 2 may be other information (for example, a telephone number) that can be used as user identification information. Furthermore, the 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 that case, the payment server 100 identifies the user corresponding to the account ID instead of identifying the user corresponding to the one-time code.

[Payment server]
FIG. 4 is a configuration diagram of the payment server 100. The payment server 100 includes, for example, a communication section 110, a login state management section 120, a content provision section 122, a payment processing section 124, an information processing section 126, a first management section 128, and a second management section 130. Equipped with. 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 are hardware (circuit parts) such as LSI (Large Scale Integration), ASIC (Application Specific Integrated Circuit), FPGA (Field-Programmable Gate Array), and GPU (Graphics Processing Unit). (including circuitry), or may be realized by collaboration between 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 device such as a DVD or CD-ROM. It may be stored in a medium (non-transitory storage medium), and installed in the storage device by loading the storage medium into a drive device. Note that a part of the processing executed by the payment application 20 may be executed by the payment server 100, and a part of the processing executed by the payment server 100 may be executed by the payment application 20. Some of the functional configurations included in 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 a device different from the payment server 100. In this embodiment, as an example, the first management section 128 and the second management section 130 will be described as being included in the payment server 100.

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

The communication unit 110 is a communication interface for connecting to the network NW. Communication unit 110 is, for example, a network interface card.

The login state management unit 120 manages the login state of each user. For example, the login state management unit 120 allows login based on the phone number and password input by the user, or transitions the state from the login state to the logout state based on the user's logout operation. .

The content providing unit 122 has, for example, the function of a web server, and provides the user terminal device 10 with information (content and interface screens) for displaying various screens of the electronic payment service. The content providing unit 122 reads necessary content from the payment content information 174 as appropriate and provides it to the user terminal device 10. The user terminal device 10 receives various inputs from 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.

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.

The information processing unit 126 searches for information managed in the user information 172 and determines whether desired information is managed. Details of the processing by the first management section 128 and the second management section 130 will be described later.

FIG. 5 is a diagram showing an example of the contents of the user information 172. User information 172 is an example of user registration information. User information 172 includes, for example, user URL, account ID, phone number, password, email address, user ID, name/address/date of birth, registration date, charge balance, bank account, credit card number, Information such as other service cooperation information, radio wave authentication settings, carrier payment settings, chat friend list, charging history information, payment history information, chat history information, etc. are associated with each other. When registering for a new electronic payment service, it is mandatory to register a phone number and password. The account ID is issued to the user by the payment server 100, and the user ID is an ID that can be arbitrarily set (or does not need to be set) by the user. 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 arbitrarily by the user. Hereinafter, the user instance (electronic payment account) to which this information is associated will be referred to as an account. The user URL is used for remittance processing between users. The registration date is the date the user registered with the electronic payment service (the date the account was created).

The charge balance is information indicating the balance of electronic money set by the user transferring money to the account in advance. Methods of remittance include remittance from an ATM (Automatic Teller Machine) of a designated business (bank), remittance from a registered bank account, etc. The bank account and credit card number are each information about a bank account or credit card number (account number, card number) that can be used to deposit money into the electronic payment service. The other service cooperation information is the login ID of another service (for example, operated by an operator belonging to the same business group) that cooperates with the electronic payment service. Radio wave authentication settings are setting information when performing authentication through communication with a specific communication carrier. The carrier payment setting is setting information for transferring at least a part of the payment using the electronic payment service to the communication carrier. The chat friend list is a list of other users with whom you can chat in the chat function provided by the electronic payment service. The charging history information is a history of the user increasing the charging balance by remitting money to the electronic payment service in advance. The payment history information is information that shows details of the payments made by the user (date and time, store ID of the store where the purchase was made, payment amount, etc.) for each payment. Chat history information is a history of the contents of chats conducted by users.

FIG. 6 is a diagram showing an example of the contents of the affiliated store/store information 176. The store information 176 includes, for example, a first table 176A in which store URLs are associated with affiliate store IDs and store IDs, and a second table in which affiliate store names and sales proceeds (described above) are associated with affiliate store IDs. It includes a table 176B and a third table 176C in which store names are associated with store IDs. In addition to this information, the member store/store information 176 may include information such as the member store or store category, store location, payment pattern, and the like.

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

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

[Processing overview]
The payment server 100 collects information from other services (service server 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. Through 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 utilize the provided information to accept applications. For example, since the user's information can be prefilled in the input field based on the aggregated information, the number of prefills is expanded. Prefilling means that user information is input into the input field in advance without depending on the user's operation. Furthermore, the payment server 100 can perform various analyzes using the aggregated information to realize marketing optimization.

Furthermore, the payment server 100 provides services for one or both of the results of identity verification (so-called eKYC; electronic Know Your Customer) performed at the start of a predetermined transaction in the payment service and the information provided by the user for identity verification. It can be provided to the server 200. Thereby, the service server 200 can omit the need to newly verify the user's identity or receive the same information.

FIG. 8 is a conceptual diagram (part 2) of the process. For example, when using an electronic payment service, the user provides customer information to the electronic payment service, and also provides the electronic payment service with documents for identity verification and images of the required appearance. do. In the electronic payment service, the user's identity is verified using the provided information, and the user can now use the electronic payment service. Identity verification is a process of checking 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 taken of the user). For example, if the information input by the user matches the information on the driver's license, which is an identification document, and the image of the driver's license matches the appearance of the captured image, the identification 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 of a My Number card.

When the identity verification is completed, the payment server 100 acquires information indicating that the identity verification has been completed. After that, if the user wishes to use deferred payment, asset management, or banking services provided in the electronic payment service, it is necessary to separately apply for use of these services.

For example, if the process of this embodiment is not performed, the user provides the service server 200 with documents for inputting customer information, identity verification, and images of required appearance when applying for each service. However, each service server 200 needs to perform examination, authentication, etc. In this way, inputting information and providing information when applying for each service places a heavy burden on the user. Further, there is also a problem for the service provider because users are more likely to leave the service midway through the application process.

Therefore, in the present embodiment, the payment server 100 provides user information and authentication results for user identification to other service servers 200, so that the user does not have to provide information for each service. to assist us in making our Services available to you. This will be explained in detail below.

[Explanation of the functional configuration of the first management section (information provision section) and the second management section (acquisition section)]
FIG. 9 is a diagram for explaining the functional configurations of the first management section 128 and the second management section 130. The first management unit 128 provides user information and information managed by the payment server 100 (for example, authentication results for identity verification) 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 the user's information necessary for the application, and acquires information corresponding to the request from the first management unit 128.

The second management unit 130 receives information provided by a user via the service server 200 and information managed by the service server 200 from the service server 200, and acquires this information. The second management unit 130 causes the storage unit 170 to store the provided information. For example, when receiving information from a predetermined 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 is an interface that functions as an API (Application Programming Interface).

For example, the second management unit 130 acquires the information acquired by the asset management service server 200, and the first management unit 128 transmits the information acquired by the asset management service server 200 to the bank service server 200. It is possible to provide This allows the payment server 100 to serve as a hub for different services, allowing the services to share information obtained from each service. The above processing corresponds to the second mini-application that operates in the electronic payment application and provides other services by using the second information acquired by the acquisition unit (information acquired by the asset management service server 200). This is an example of a process of ``provided to a second service server (for example, a bank service server)'' that

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 payment application 20 and payment server 100. The 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 made. In the example of FIG. 10, for example, it is shown that the identity verification process has been completed. The confirmation date and time is the date and time when the identity was verified. The verification method is information indicating the document used for identity verification. The document is, for example, a driver's license or a My Number card. The confirming entity is the entity that has confirmed the identity. In the example of FIG. 10, the identity verification is performed by the administrator of the electronic payment service.

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 on an interface screen displayed on the display unit of the user terminal device 10 by the mini app 30 and the service server 200.

As described above, the type of information IF1 (first information) and the type of information IF2 (second information) may be determined in advance or may be dynamically changed. For example, the user information held by the payment server 100 may be set as information IF1, and other information may be set as information IF2. For example, the user's name, attributes, contact information, and place of work may be determined as information IF1, and other information may be determined as information IF2. In this case, regardless of whether the payment server 100 holds the information IF2 or not, the mini app 30 displays the interface screen (for example, the interface screen IM7 in FIG. 13 described later or the interface screen IM10 in FIG. ), and the information input by the user may be used as the information IF2. Further, if the payment server 100 holds the information IF2, the payment application 20 may display an interface screen including the information IF2 on the display section of the user terminal device 10 and request the user to confirm the information. .

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.

[Interface image including the 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 app 30 included in the payment app 20. The mini app 30 is, for example, an app using the payment app 20 as a platform. The mini-application 30 is, for example, an application program developed to run within the payment application 20 by a service provider who provides the service of the service server 200. The service provider develops the mini-application 30 by referring to an SDK (Software Development Kit), which is a program, technical documents, etc. for application development provided by the administrator of the payment application 20. The mini app 30 is, for example, an app that operates while the payment app 20 is activated. For example, part or all of the mini-app 30 may be installed when the payment application 20 is installed, or some or all of the mini-app 30 may be installed from the service server 200 corresponding to the mini-app 30. .

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 startup button for starting the mini-app 30. For example, the content providing unit 122 causes the payment application 20 to display an interface image IM1, which will be described later.

FIG. 12 is a diagram showing an example of the interface image IM1. The interface screen IM1 (an example of a first interface screen) is content provided in the electronic payment service, and includes information on QR codes (registered trademarks) and barcodes used in electronic payments, and services related to various electronic payments. The area AR1 of the interface image IM1 includes one or more buttons for starting the mini app 30. When the start button B1 is operated, the bank mini-app 30 is started. For example, the mini app 30 cooperates with a bank's service server 200 to provide services to the user.

[Processing related to the use of mini apps (Part 1)]
FIG. 13 is a diagram for explaining the process when opening a bank account using the mini app 30. In response to the user's operation, the mini app 30 cooperates with the service server 200 to display the interface screen IM2 (another example of the first interface screen) on the display unit. When the button for opening a bank account on the interface screen IM2 (for example, B2 or B3 in FIG. 13) is operated, the information processing unit 126 of the payment server 100 acquires information indicating that the above operation has been performed. Then, it is determined whether information such as the user's name, attributes (for example, date of birth, nationality, occupation, etc.), contact information, workplace, etc., is registered in the user information 172. These pieces of information are information acquired or managed by the payment server 100. Note that 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 "application button". Further, button B1 in FIG. 12 is another example of a "start button" or an "application button". For example, if button B1 in FIG. 12 is operated to start processing an application to use a service, button B1 may be used as a "start button" or "application button."

For example, if the user's name, attributes, contact information, and work information are not registered (if 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 of registered information are omitted). The interface screens IM3, IM4, IM5, and IM6 are examples of "second interface screens."

The interface screen IM3 is a screen for the user to input their name, the interface screen IM4 is a screen for the user to input attributes, and the interface screen IM5 is a screen for the user to input contact information. The interface screen IM6 is a screen for the user to input his/her place of work. For example, information is displayed indicating that the information input on the interface screen is registered in the user information 172 of the electronic payment service and is also used for the mini app 30 (other services). For example, information such as ``This information will be registered in the user information of the electronic payment service and will also be used for the mini app'' is displayed. When a predetermined button is operated, the user is deemed to have given permission for the input information to be used by the mini app 30.

If screening or authentication is required for information input by the user or information provided by the user, the payment server 100 and payment application 20 display an interface screen (not shown) for screening and authentication. For example, an interface screen for attaching or taking an image of a driver's license, My Number card, or the person in question is provided. When an image is attached to the interface screen and sent to the payment server 100, predetermined examination and authentication are performed in the payment server 100, and processing is performed according to the results of the examination and authentication. For example, when the examination or authentication is positive, the information used for the examination or authentication and the results of the examination or authentication are registered in the user information 172, and when the examination or authentication is negative, the payment server 100 Ask the user to provide other information. Please note that screening and certification may require a certain amount of time. If it takes time, the user may end the input here, wait for the review, and restart the input after the review, or if the service that provides the mini app 30 allows it, the user may wait for the review. You may proceed with inputting information other than waiting.

After acquiring the predetermined information, the payment server 100 stores the acquired information in the storage unit 170 in association with the user identification information of the user information 172, 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 predetermined information, or may provide the acquired information to the service server 200 in response to a request from the service server 200. You can. The mini app 30 and the service server 200 display the interface screen IM7 on the display unit. The interface screen IM7 is information necessary for the service provided by the service server 200. For example, this information is required by a service administrator when a user applies for a service. This information is information set in advance for each service, and is, for example, information that is not registered in the user information 172.

When the service server 200 acquires the information necessary for the service, the service server 200 and the mini app 30 display the 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 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 at predetermined positions, as described above. to be displayed. This allows the user to check his or her own information.

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

In response to the user's operation, the mini app 30 cooperates with the service server 200 to display the interface screen IM9 on the display unit. When the button for inputting customer information on the interface screen IM9 is operated, the payment server 100 skips the process of acquiring information, and the mini app 30 and the service server 200 input the information necessary for using the service. An interface screen IM10 for obtaining (my number) is displayed on the display unit. The interface screen IM10 is an example of a "third interface screen." Note that if the payment server 100 holds the above-mentioned necessary information, the payment server 100 provides the necessary information to the service server 200.

When the service server 200 acquires the information necessary for the service, the service server 200 and the mini app 30 share the information acquired by the payment server 100 and the information acquired by the service server 200, similar to the interface screen IM8 in FIG. An interface screen IM11 including content in which information is placed at a predetermined position is displayed on the display unit. Thereby, the user can confirm information such as name and attributes inputted at the start of a predetermined transaction of the payment service, or confirm information inputted at the start of a predetermined transaction of the service. Processing for modifying this information will be described later.

In addition, if multiple types of information IF1 (for example, user's name, attributes, contact information, and workplace information) are not stored in the user information 172, the payment server 100 can provide information on the unstored types of information IF1. An interface screen for allowing the user to input IF1 is displayed on the display unit, and in the user information 172, the information IF1 input on the interface screen is registered in association with the user's identification information, and the information IF1 is registered as the user's identification information. A plurality of correlated types of information IF1 are provided to the service server 200. Thereby, even if the payment server 100 does not store a part of the information IF1, it can acquire a part of the information IF1 and provide the information IF1 to the service server 200.

Note that even if the information IF1 is stored in the storage unit 170, the payment server 100 displays an interface screen on the display unit of the user terminal device 10 for prompting the user to confirm the stored information IF1. It may be displayed. This interface screen is prefilled with, for example, user information IF1 stored in the storage unit 170. For example, if some of the information IF1 is not stored in the payment server 100, the payment server 10 displays an interface screen on the display section of the user terminal device 10 for prompting input of the unstored information IF1. At the same time, an interface screen for prompting confirmation of the stored information IF1 may be displayed on the display unit of the user terminal device 10 with the stored information IF1 prefilled. For example, if the user's name is not stored, the payment server 100 displays the interface screen IM3 on the user terminal device 10, and if other information IF1 is stored, the stored information IF1 is prefilled. The interface screens IM4 to IM6 may be displayed on the display unit of the user terminal device 10.

The above information IF1 (first information) may be information that satisfies predetermined criteria. The predetermined criteria are, for example, criteria required when applying for a service. For example, the name may be registered in kanji, hiragana, or katakana, or the address may be registered. If the payment server 100 stores information IF1 (first information) that does not meet the predetermined criteria, the payment server 100 displays the interface screen prefilled with this information (for example, the interface screen IM3-6, etc.) on the user terminal device 10. The user may request that the information be corrected so that it satisfies predetermined criteria.

[Sequence diagram for using mini apps]
FIG. 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. Identification information for identifying users is shared between the service system and the payment system.

First, when the user starts the mini app 30 through the operation of the payment app 20 and performs an operation to make a predetermined application provided by the service system, the service system provides the user's information to the payment system. (S50). The payment system searches the user information 172 (S52) and sends the search results to the service system (S54). For example, if the payment server 100 holds information (first information, information IF1) to be acquired or managed by the payment server 100, it provides this information to the service system.

If the payment server 100 does not hold the information to be acquired or managed by the payment server 100, the payment system executes processing for inputting information (for example, providing an interface screen) (S56). Next, the payment system provides the input information to the service system (S58). Further, the input information is registered in association with the user identification information of the user information 172.

Next, the service system executes processing 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 provided user information 172 in association with the user's identification information (S64). Note that the processes of S62 and S64 may be omitted, or the information for which the user has given consent to share the information with the payment system may be provided to the payment system. Further, depending on the type of service system, it may be determined whether to omit the processing in S62 and S64.

As described above, the service system can use the information obtained or managed by the payment server 100 to perform processing related to the user's use of the service. FIG. 17 is a conceptual diagram of information sharing. For example, when a user is logged in to the payment application 20 and the user starts a transaction in another service, the service server 200 stores the information entered at the start of a predetermined transaction in the payment service, the identity verification form, and the user's physical appearance. Using captured images, etc., it is possible to conduct examinations and procedures for starting transactions.

Thereby, the service server 200 can reduce the load for acquiring information. Furthermore, since the user does not have to input the same information, the burden on the user is also reduced.

In the above description, the information acquired by the payment server 100 is provided to the service server 200. However, in addition to (or instead of) the information obtained by the payment server 100, the result of the identity verification in the payment server 100 may be provided to the service server 200. You can. FIG. 18 is a conceptual diagram of providing an identity verification result. For example, when a user is logged in to the payment application 20 and the user starts a transaction in another service, the service server 200 collects information such as the result of the identity verification (so-called eKYC) performed at the start of a predetermined transaction in the payment service, etc. The examination results and the like are provided to the service server 200. The service server 200 can perform examinations and procedures for starting transactions using or referring to the provided identity verification results and other examination results.

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

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

As mentioned above, when the user information acquired by the payment system or the user information acquired by the service system is modified, the payment system will display an interface screen and execute processing for modifying the information, and The user information 172 is updated (the first information is updated). 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 when providing information to other services, it is necessary to update the updated information. can provide information. This process includes the following: "After the first information has been updated, if a start button for starting the second service included in the first interface screen is operated, the control unit This is an example of a process of "providing the changed first information to a second service server corresponding to a second mini-app 30 that operates in an application and provides a second service."

Note that if an operation is performed on the interface screen IM11 for the mini app 30 and the service server 200 acquired on the interface screen IM10 to modify the information (second information) necessary for using the service, the payment server 100 And the payment application 20 does not provide an interface screen for modification, but instead provides an interface screen (“fifth An example of "interface screen") is displayed on the display unit.

[Sequence diagram regarding information modification]
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 the user performs an operation to modify information on the interface screen IM11, the service system transmits information indicating that the modification operation has been performed to the payment system (S100). Next, the payment system executes correction processing (S102). For example, an interface screen for inputting information to be corrected may be provided, or information input or provided by the user may be reviewed or authenticated.

Next, the payment server 100 updates the registered information in the user information 172 of the user to information corresponding to the correction (S104). As a result, the information updated according to the correction is registered in the user information 172 of the user. Next, the payment system provides the revised information to the service system (S106). Next, the service system causes the display unit to display an interface screen that includes information that reflects the modification (S108). For example, when 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.

As mentioned above, when a user's information is modified through an operation on the interface screen provided by the service system, the payment system performs processing according to this operation, accepts the modification, and processes the user's user information according to the modification. 172 is updated. Thereby, the payment server 100 can acquire and hold the latest information, and can provide the latest information to other services.

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

For example, when the user is logged in to use the payment application 20 (condition 2), the interface screen is displayed on the display section, and the application button for applying for the use of other services included in the interface screen is operated. , if the user's usage of the electronic payment service satisfies 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., condition 1, condition 5), The service server 200 provides completion information indicating that identity verification has been completed to the service server 200 that provides other services to the user in cooperation with the mini-app 30 that operates in the payment application 20 and provides other services. If the button B1 is operated and the set conditions are not met or the user's identity verification is not completed, the service server 200 is instructed to proceed with the processing related to the application, and the service server 200 is instructed to at least temporarily suspend the application. let

When proceeding with the processing related to the application, the payment server 100 executes the processing described above with reference to FIGS. 13 to 15 and the like. For example, depending on the information held, the payment server 100 causes the payment application 20 to display an interface screen for information input (first information input), or causes the mini app 30 to display information input (second information input). Display the interface screen for.

The payment server 100 also displays an application button or a first application button for applying to use the first service included in the interface screen displayed on the display unit while the user is logged in to use the payment application 20. When the operation button to start using the service is operated, an interface screen for performing authentication using the biometric authentication function installed in the user terminal device 10 of the user is displayed on the display section, and the user interface When biometric authentication (condition 6) is established in response to an operation on the screen, an interface screen corresponding to the operation is displayed on the display unit. That is, when biometric authentication is successful, use of a predetermined service provided by the service server 200 is permitted.

(Condition 1) The administrator of the electronic payment service has performed a predetermined confirmation regarding the user, and the predetermined confirmation has been completed. For example, the confirmation items that are performed at the beginning of using the electronic payment service must be completed. For example, if a predetermined confirmation has been completed, a flag indicating whether or not the user's identity has been verified is added to the identification information of the user in the user information 172, and this flag is shared to facilitate payment. The server 100 or the service server 200 can determine whether condition 1 is satisfied (see FIG. 10).

(Condition 2) The user must be logged in to the payment application 20. This is because by logging into the payment application 20, the mini-app 30 becomes available, and the mini-app 30 can be used to apply for a service.

(Condition 3) User 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 provide the user's information to the service server 200 has been obtained from the user.

(Condition 4) The service is capable of acquiring the date and time of identity verification of the target user and information on the verification method via the second management unit 130 (for example, API). For example, the service is capable of acquiring the confirmation date and time and confirmation method of personal identification managed by the payment server 100 as shown in FIG. 10 described above. For example, the service can acquire the above information by cooperating with the second management unit 130.

(Condition 5) The entity confirming the transaction is the administrator of the electronic payment service. Transaction confirmation is confirmation for the use of electronic payment services. The condition is that the subject of this confirmation is the administrator of the electronic payment service.

(Condition 6) The electronic payment service performs predetermined authentication at the time of a specific transaction using the mini app 30. This will be described later (see FIGS. 22 and 23).

(Condition 7) In the electronic payment service, the user is not a user who has conducted a transaction that is suspected of impersonation or a transaction with a customer who is suspected of being impersonated. For example, the payment server 100 uses predetermined criteria to identify users who meet the above conditions, and executes suspend processing for the identified users. Suspend processing means suspending or stopping the use of electronic payment services and related services by a specified user.

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

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

FIG. 22 is a flowchart showing an example of the flow of authentication processing. First, the payment application 20 determines whether an operation for performing a specific transaction has been performed on the mini application 30 (S200). When the operation is performed, the payment application 20 causes the display unit to display an interface screen requesting predetermined authentication (S202). The predetermined 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, this is authentication for unlocking the user terminal device 10. Authentication may be, for example, biometric authentication or authentication using a password. Biometric authentication is, for example, authentication using face authentication, fingerprints, iris, or the like. The biometric information used for authentication is information registered by the user using the functions of the user terminal device 10.

Next, the user terminal device 10 determines whether or not authentication is successful (S204). If the authentication is successful, the mini app 30 and the service server 200 provide the service (S206). For example, it continues processing for starting a transaction with a user, or starts a transaction. If the authentication is not successful, the mini app 30 and the service server 200 do not provide any service, and one routine of this process ends.

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

For example, assuming that the above authentication is not used, the user may send 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, etc. to the payment server 100 or the service. It is necessary to provide the information to the server 200. On the other hand, in the present embodiment, since authentication is performed as described above, the above processing is omitted, thereby improving convenience for the user.

In addition, in the above process, it was explained that authentication is performed when applying to use the service, but in addition to (or in place of) this, authentication is performed when starting to use the service after the application is completed. Authentication may be performed each time (however, after authentication, authentication is omitted for a certain period of time). This improves security.

According to the first embodiment described above, the payment server 100 executes appropriate processing according to the retained information or the result of identity verification. As a result, the user can 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, user convenience is improved and the processing load on the service server 200 is reduced.

<Second embodiment>
The second embodiment will be described below. In the second embodiment, information indicating risks related to transactions with the user is associated with user identification information in the user information, and this information is provided to the service server 200. Hereinafter, differences from the first embodiment will be mainly explained.

FIG. 24 is a diagram showing 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."

The first acquisition unit 132 acquires user information on one or both of the usage mode of the electronic payment service by the user and the information regarding the user provided by the user in order to use the electronic payment service. The usage mode is, for example, the user's usage history of the electronic payment service, such as the payment amount and information on the store where the payment was made. Information regarding the user is information provided by the user to the electronic payment service when applying for use of the electronic payment service. For example, it is the information IF1 in FIG. 10 mentioned above.

The second acquisition unit 134 acquires communication information that is one or both of information regarding the device that the user is using to use the electronic payment service and information regarding the network that the user is using. The information regarding the device is information such as information on the type of device of the user terminal device 10 and an IP address (Internet Protocol Address). The information regarding the network includes information on the Internet service provider that the user terminal device 10 is accessing, information regarding the network used for communication, and the like. For example, these pieces of information are information acquired by the payment application 20 and provided to the payment server 100.

The flag generation unit 136 derives the reliability of the user based on the user information and communication information. The flag generation unit 136 generates a risk flag according to the reliability, or derives a score according to the reliability, for example. This information is provided to the service server 200. For example, the second management unit 130 provides the service server 200 with information indicating reliability, user information 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, if a user operates an application button for applying for the use of another service included in the interface screen displayed on the display unit while logged in to use the payment application 20, the second management The unit 130 may provide the service server 200 with information indicating reliability, user information, and information indicating the result of identity verification in response to a request from the service server 200.

The flag generation unit 136 sets the flag based on, for example, user information and communication information, as well as conditions associated with the user (conditions based on user information) and conditions not associated with the user (conditions based on communication information). be done. FIG. 25 is a diagram for explaining conditions under which flags are set. The conditions associated with the user include, for example, that the user satisfies a predetermined condition, that a condition regarding the user's use of the electronic payment service is satisfied, and that there is a deficiency in the information managed by the payment server 100.

A user satisfying a predetermined condition means that the user is registered in the list in advance. For example, high-risk users are registered in this list. Satisfying the conditions regarding the manner in which the user uses the electronic payment service means, for example, that the electronic payment service is being used in a preset manner, such as making high-value payments a predetermined number of times or more. Inadequacies in information include, for example, inconsistencies in the information (for example, the prefecture and city of the address do not match) or in the necessary information (for example, the necessary information is missing). etc.

Conditions that are not linked to users include, for example, access from a preset device, access from a preset IP address, and access via a preset Internet service provider. be. For example, if a device, IP address, Internet service provider, etc. that are estimated to be high risk is used, the risk is presumed to be high.

The flag generation unit 136 sets a flag when the user meets the above-described conditions for setting the 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, it provides the service server 200 with a flag in association with the user information. Thereby, the service server 200 can recognize that the target user is a high-risk user, and can determine whether or not to provide a service in consideration of the recognition result.

Note that in the above example, a flag is given to a high-risk user, but instead of this, a flag may be given depending on the height of the risk. For example, a flag may be assigned depending on the level of risk, such as a high risk flag, medium risk flag, or low risk flag. Moreover, instead of the flag, a score indicating high or low risk may be provided. The flag generation unit 136 derives a score with reference to the criteria based on the conditions described above, and associates the derived score with the user's identification information.

FIG. 26 is a diagram showing an example of the contents of the user information 172A according to the second embodiment. In addition to the information described in the user information 172, the user information 172A includes a risk flag associated with the user's identification information.

Further, for example, the flag generation unit 136 may add a flag to the user's identification information according to the risk from predetermined types of flags including a gray flag, a black flag, and a white flag. A black flag is a flag that is set for a user who meets a condition that is not associated with a user. Further, a black flag may be set to a user who satisfies a predetermined condition among conditions associated with the user. The black flag is a flag indicating that the reliability is less than the second threshold.

Gray flags are used for users whose user information satisfies predetermined conditions (for example, a user who satisfies the conditions related to electronic payment or there is a flaw in the information) among the conditions that are associated with the user, and whose user information does not meet the conditions that do not correspond to the user. This is the flag that is set. The gray flag is a flag indicating that the reliability is less than the first threshold and greater than or equal to the second threshold.

A white flag is given to a user who does not meet the conditions for linking to a user and the conditions for not linking to a user.

For example, when a white flag user performs an operation to apply for the use of the mini app 30 service, the payment server 100 allows the user to use the service without going through the same procedures as a gray flag user, which will be described later. Can be done.

For example, when a gray flag user performs an operation to apply for the use of the mini-app 30 service, the payment server 100 requests the user to re-perform the identity verification performed in the electronic payment service. For example, the payment server 100 causes the display unit to display an interface screen for re-verifying the user's identity. Note that this interface screen may be displayed by the service server 200 that has acquired the gray flag.

For example, when a Black Flag user performs an operation to apply for the use of the service of the mini app 30, the payment server 100 causes the display unit to display an interface screen that includes information indicating that the service cannot be used. Note that this interface screen may be displayed by the service server 200 that has acquired the black flag.

According to the second embodiment described above, the payment server 100 generates information regarding the user's risk and provides the generated information to the service server 200. Thereby, the service server 200 can refer to the acquired information indicating the risk and determine whether to provide the service to the user. As a result, decisions regarding service provision can be made more accurately.

<Other examples (1)>
In the above example, when the 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. Alternatively (in addition to this), information may be shared when the user terminal device 10 of the user accesses the service server 200 without using the mini app 30.

FIG. 27 is a diagram for explaining the processing of other example (1). For example, the user terminal device 10 accesses the bank's service server 200 without going through the mini app 30, and the user is trying to open a bank account. For example, when an operation is performed to open a bank account on the interface screen provided by the service server 200, the service server 200 prompts the user to log in to the electronic payment service and connect the electronic payment service and the bank's service server 200. Inquire whether to link or not. When the user selects cooperation and performs the prescribed operations to log in and enter the user identification information and password used in the electronic payment service, the bank's service server 200 processes the payment from the payment server 100. The user information managed by the server 100 and the result of identity verification are acquired. The bank's service server 200 can proceed with the process of opening a bank account by using the acquired information and the result of identity verification.

As described above, the user can have his/her own information held in the payment server 100 used in another service server 200 even without using the mini app 30, which improves user convenience. The processing load on the service server 200 is reduced.

<Other examples (2)>
When the payment server 100 updates the information associated with the user's identification information in the user information 172 in response to the user's operation, the payment server 100 provides information indicating the update or the contents of the update to the predetermined service server 200. You can. For example, if a user updates his or her address on the interface screen provided by the payment server 100 while applying to open a bank account, information indicating that the address has been updated may be sent to a credit card, for example. It may also be provided to the company's service server 200 (predetermined service server 200). For example, since it is necessary to obtain the latest information regarding credit card credit, payment, etc., when information is updated in applications for other services, etc., the payment server 100 provides information indicating that the update has been made and The updated content is provided to the credit card company's service server 200.

As described above, when the user's information is updated, the payment server 100 provides information regarding the update to other service servers 200, so that the service server 200 and the payment server 100 can maintain the latest information. Can be done. Furthermore, since the user does not need to update information for all services, convenience for the user is improved.

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

As described above, when user information is updated in the service server 200, the payment server 100 can maintain the latest information by acquiring information regarding the update from the service server 200.

Although the mode for implementing the present invention has been described above using embodiments, the present invention is not limited to these embodiments in any way, and various modifications and substitutions can be made without departing from the gist of the present invention. can be added.

10 User terminal device 20 Payment application 30 Mini application 50 First store terminal device 60 Store code image 70 Second store terminal device 100 Payment server 121 Service information acquisition section 122 Content provision section 124 Payment processing section 126 Information processing section 128 First Management unit 130 Second management unit 132 First acquisition unit 134 Second acquisition unit 136 Flag generation unit 170 Storage unit 172 User information 174 Payment content information

Claims (16)

A service management device that provides a service,
A button for starting the first service included in the first interface screen displayed on the display unit is operated while the user is logged in to use a service application that provides the service, and If the first information is not stored in a storage device managed by the service among the information necessary to receive the service including first information and second information, the first information is input to the user. Display on the display section a second interface screen for
When the button is operated and the first information among the information necessary to receive the service is stored in the storage device, the first information that operates in the service application and provides the first service. comprising a control unit that executes processing for displaying on the display unit a third interface screen for allowing the user to input the second information into the mini app;
Service management device. When the user performs a correction operation to correct the first information on a fourth interface screen including the first information and the second information displayed on the display unit by the first mini-app,
The control unit causes a display unit to display an interface screen for changing the first information in response to the modification operation.
The service management device according to claim 1. The control unit is configured to perform processing based on information input on an interface screen for changing the first information and authentication information used to authenticate the input information provided to the user in response to the modification operation. and changing the first information;
The service management device according to claim 2. If a button for starting a second service included in the first interface screen is operated after the first information is updated,
The control unit provides the changed first information to a second service server corresponding to a second mini-app that operates in the service application and provides a second service.
The service management device according to claim 3. When the user performs a correction operation to correct the second information on a fourth interface screen including the first information and the second information displayed on the display unit by the first mini-app,
The control unit does not display an interface screen for changing the first information on the display unit,
the first mini-app causes a display unit to display a fifth interface screen for changing the second information in response to the modification operation;
The service management device according to claim 2. The control unit includes:
Operation of a button for starting the first service included in the first interface screen displayed on the display unit while the user is logged in to use the service application or a button for starting the service. If the operation button for starting the use of the first service is operated after the process for receiving the service is completed in accordance with the above, the authentication using the biometric authentication function installed in the user's terminal device is Display the interface screen for execution on the display,
When biometric authentication is established in response to a user's operation on the interface screen, displaying on a display unit an interface screen for proceeding with processing according to the operation;
The service management device according to any one of claims 1 to 5. further comprising an information providing unit that provides the first information input to the second interface screen to a first service server corresponding to the first mini-app;
The service management device according to any one of claims 1 to 5. The information providing unit provides the first service server with an authentication result for identity verification obtained based on the information for identity verification obtained from the user's terminal device and the first information.
The service management device according to claim 7. The first information includes a plurality of types of information,
The control unit includes:
When the button is operated and the first information of the plurality of types is not stored in the storage device, the second information for causing the user to input the first information of the type not stored in the storage device Display the interface screen on the display,
registering the first information input on the second interface screen in the storage device in association with identification information of the user;
The information providing unit provides the first service server with the plurality of types of first information associated with the user's identification information.
The service management device according to claim 7. A service management device according to claim 8;
a first service server corresponding to the first mini-app that starts providing a service to the user based on the first information and the authentication result;
A service management system equipped with further comprising an acquisition unit that acquires the second information from a first service server corresponding to the first mini-app;
A service management device according to any one of claims 1 to 5. further comprising an information providing unit that provides the second information acquired by the acquisition unit to a second service server corresponding to a second mini-app that operates in the service application and provides other services;
The service management device according to claim 11. The service is an electronic payment service,
The service application is an electronic payment application that provides electronic payment services.
The service management device according to any one of claims 1 to 5. A service app that provides services,
to the computer,
Displaying the first interface screen on the display unit while the user is logged in to use the service application;
A button for starting another service included in the first interface screen is operated, and the first information among the information necessary to receive the provision of the service including the first information and the second information is If the first information is not stored in a storage device managed by the service, displaying a second interface screen on the display unit for allowing the user to input the first information;
When the button is operated and the first information among the information necessary to receive the service is stored in the storage device, the mini-app that runs in the service app and provides the other service. executing a process for displaying a second interface screen on the display unit for allowing the user to input the second information;
Service app. A service management method for providing a service, the method comprising:
The computer is
A button for starting the first service included in the first interface screen displayed on the display unit is operated while the user is logged in to use a service application that provides the service, and If the first information is not stored in a storage device managed by the service among the information necessary to receive the service including first information and second information, the first information is input to the user. Display on the display section a second interface screen for
When the button is operated and the first information among the information necessary to receive the service is stored in the storage device, the first information that operates in the service application and provides the first service. executing a process for displaying on the display unit a third interface screen for allowing the user to input the second information into the mini app;
Service management methods. A program that provides a service,
to the computer,
A button for starting the first service included in the first interface screen displayed on the display unit is operated while the user is logged in to use a service application that provides the service, and If the first information is not stored in a storage device managed by the service among the information necessary to receive the service including first information and second information, the first information is input to the user. a process of displaying a second interface screen on the display unit for the purpose of
When the button is operated and the first information among the information necessary to receive the service is stored in the storage device, the first information that operates in the service application and provides the first service. a process for displaying on a display unit a third interface screen for causing a user to input the second information into the mini app;
A program to run.

Images