JP7280420B1 - Payment management device, payment management system, payment management method, and program - Google Patents

Abstract

An object of the present invention is to improve user convenience. A first interface screen is displayed on a display unit while a user is logged in to use an electronic payment application, and an application button for applying for use of other services included in the first interface screen is provided. When the user's use of the electronic payment service satisfies the conditions set in the electronic payment service and the identity of the user has been verified in the electronic payment service, the mini-app is linked to provide the user with other services. to the service server that provides the personal 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. Alternatively, a settlement management device comprising a control unit that causes a service server to at least temporarily suspend an application when user identification has not been completed. [Selection drawing] Fig. 4

Description

The present invention relates to a payment management device, a payment management system, an electronic payment application, a payment management method, and a program.

2. Description of the Related Art Conventionally, in electronic commerce, there is known a system that performs electronic authentication for personal identification and performs electronic payment based on the electronic authentication (see, for example, Patent Document 1).

Japanese Patent Application Laid-Open No. 2002-123726

However, in some cases, the above devices are not convenient for users or service providers.

The present invention has been made in consideration of such circumstances, and provides a payment management device, a payment management system, an electronic payment application, a payment management method, and a program that can improve user convenience. is one of the purposes.

One aspect of the present invention is a payment management apparatus that provides an electronic payment service, in which a first interface screen is displayed on a display unit while a user is logged in to use an electronic payment application; An application button for applying for use of another service included in the interface screen is operated, the usage mode of the electronic payment service by the user satisfies the conditions set in the electronic payment service, and the When the identity verification of the user is completed, the said identity verification is completed to the service server that provides the said other service to the said user in cooperation with the mini app that operates in the said electronic payment application and provides the said other service. and instructing the service server to proceed with the processing related to the application, the application button is operated, the set conditions are not satisfied, or the identity of the user is confirmed. is not completed, the settlement management apparatus includes a control unit that causes the service server to at least temporarily stop the application.

ADVANTAGE OF THE INVENTION According to one aspect of the present invention, it is possible to provide a payment management device, a payment management system, an electronic payment application, a payment management method, and a program that can improve user convenience.

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

A settlement management device, a settlement management system, an electronic settlement application, a settlement management method, and a program according to the present invention will be described below with reference to the drawings. An information processing apparatus, an information processing method, and a program will be described below with reference to the drawings.

A service management device is realized by one or more processors. A service management device that provides a service, the service of 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. 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 When a second interface screen for allowing the user to input information 1 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 ( For example, a content providing unit). The above services are arbitrary services such as electronic payment services, chat applications, and social network services, for example. In the following description, as an example, an electronic payment service will be described.

The first information is, for example, information acquired by the user inputting information on an interface screen provided by the electronic payment application. The second information is, for example, information acquired 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 using the service of a mini-app different from the first mini-app. The second information is, for example, information required for using the service of the first mini app. The first interface screen may be any screen that includes a button for starting the service of the service. The first interface screen may be a screen provided by an electronic payment application, or may be a screen provided by a mini-application. The button for starting the service of the first service is a button operated to start using the service. It is a button corresponding to an operation that triggers use. The button for starting the service can also be called an application button for applying for the service.

The processing for displaying the third interface screen on the display means displaying the third interface screen on the display in cooperation with the first mini-app or the service server corresponding to the first mini-app. For example, the control unit instructs the first Mini appli or the service server to display the third interface screen.

A payment management device for providing an electronic payment service, wherein a first interface screen is displayed on a display unit while a user is logged in to use an electronic payment application; An application button for applying for use of the service is operated, the user's use of the electronic payment service satisfies the conditions set in the electronic payment service, and the identity verification of the user is completed in the electronic payment service. If so, a completion indicating that the identity verification has been completed to the service server that provides the other service to the user in cooperation with the mini app that operates in the electronic payment application and provides the other service. If information is provided, the service server is instructed to proceed with the processing related to the application, the application button is operated, and the set conditions are not satisfied, or the identity verification of the user is not completed, A control unit is provided for causing the service server to at least temporarily suspend the application.

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 is. Temporarily suspending means, for example, displaying an interface screen on the display unit indicating that the payment application, payment server, mini-application, or service server cannot use the service; It is to provide information indicating that processing, examination, etc. is necessary.

The information processing apparatus comprises: a first acquisition unit that acquires user information of one or both of a user's usage mode of the electronic payment service and information about the user provided by the user to use the electronic payment service; 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 the second embodiment).

<First embodiment>
[Electronic payment service]
FIG. 1 is a diagram showing an example of a configuration for realizing an electronic payment service. An electronic payment service is implemented centering on the payment server 100 . The settlement 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), wireless base stations, provider devices, and the like. Hereinafter, the service servers 200-1 to 200-3 will be referred to as service servers 200 when not distinguished from each other. 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 smart phone 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, 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, and operates in cooperation with the payment server 100 to provide electronic payment services to the user. The payment application 20 controls a camera, a communication device, a touch panel, and the like.

The first store terminal device 50 is installed, for example, in a store. The first store terminal device 50 is a computer device having at least a product price acquisition function, an optical reading function, a program execution function, and a communication function. The first store terminal device 50 includes a so-called POS (Point of Sale) device, and the POS device may realize the product price acquisition function and the optical reading function. The store code image 60 is placed in a store and is a code image such as a QR code (registered trademark) printed on a medium such as paper or plastic. Note that the store code image 60 may be displayed on a display placed in the store (a display of a terminal device such as a smart phone may be used).

The second store terminal device 70 is used by the member store operator. The second store terminal device 70 is a smart phone, a tablet terminal, a personal computer, or the like. A member store interface 72 operates on the second store terminal device 70 . The merchant interface 72 may be a merchant application or a browser. The member store interface 72 accepts coupon settings and the like from the member store operator and transmits them to the settlement server 100 . The second store terminal device 70, which is a smartphone, has a function of displaying a code image corresponding to the store code image and reading a 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 this case, payment information is transmitted from the POS device to the payment server 100 via the member store server. In the following explanation, it is assumed that the payment information is transmitted from the first store terminal device 50 without distinguishing between them. 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 sales proceeds of the affiliated store. For example, the item value of the sales proceeds of the member store is not used as electronic money per se, but the amount corresponding to the item value of the sales proceeds is calculated in a cycle according to the agreement between the member store and the electronic payment service. transferred to a bank account. Electronic payment may include those that enable purchase of a larger amount than the charge balance at the time of purchase by methods such as revolving payment and credit payment.

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

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 shop code image 60 by the optical reading function (S1). The store code image 60 includes store URL (Uniform Resource Locator) information. The store URL is a domain of the electronic payment service to which information that can identify the store is added, and is associated with the member store ID, the store ID, and the like in the settlement server 100 (described later). The payment application 20 transmits the first payment information including the store URL and the account ID to the payment server 100 (S2). The payment server 100 retrieves store information (described later) from the member store ID and store ID corresponding to the store URL, acquires the member store name and store name information (S3), and transmits them to the settlement application 20 (S4). . The user inputs the settlement amount into the user terminal device 10 on the screen displaying the member store name and store name (S5). Then, the user terminal device 10 generates second payment information including at least the payment amount, and transmits the second payment information to the payment server 100 (S6). The payment server 100 completes electronic payment as described above based on the received second payment information (S7). The payment server 100 then transmits a payment completion notification (information for displaying a payment completion screen) to the payment application 20 (S8), and the payment application 20 displays the payment completion screen (S9). Note that the store code image 60 may include not only the store URL but also the payment amount information. In this case, the procedure for the user to input the settlement amount is omitted. For example, since the payment application 20 causes the display unit to display a screen in which the payment amount is input, the above S5 is omitted. When the user confirms the amount and performs a predetermined operation, the first payment information including the payment amount is transmitted to the payment server 100 . Information on the name of the member store and the name of the store 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. 3, the payment application 20 transmits a one-time code (corresponding to user identification information) issuance request to the settlement server 100 (S11). The payment server 100 generates a one-time code (S12) and transmits it to the payment application 20 (S13). The payment application 20 displays a code image such as a QR code or 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 shop terminal device 50, and the first shop terminal device 50 decodes the code image by the optical reading function and acquires the one-time code ( S15). The first store terminal device 50 then generates payment information including the one-time code, payment amount, member store ID, store ID, etc., and transmits the payment information to the payment server 100 (S16). The information on the payment amount is acquired in advance by reading a bar code, manually inputting it, or the like. The payment server 100 identifies the user corresponding to the one-time code based on the received information, and completes the electronic payment as described above (S17). The payment server 100 then transmits a payment completion notification to the payment application 20 (S18), and the payment application 20 displays a payment completion screen (S19).

It should be noted that electronic payment may be performed using only one of the above patterns. Also, the "account ID" described in FIG. 2 may be other information (such as a telephone number) that can be used as user identification information. Alternatively, the issuance of the 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 settlement server 100 identifies the user corresponding to the account ID instead of identifying the user corresponding to the one-time code.

[Settlement server]
FIG. 4 is a configuration diagram of the settlement server 100. As shown in FIG. The payment server 100 includes, for example, a communication unit 110, a login status management unit 120, a content provision unit 122, a payment processing unit 124, an information processing unit 126, a first management unit 128, and a second management unit 130. Prepare. Components other than communication unit 110 and storage unit 170 are implemented by, for example, a hardware processor such as a CPU executing a program (software). Some or all of these components are hardware (circuit part; circuitry) or by cooperation of software and hardware. The program may be stored in advance in a storage device (a storage device with a non-transitory storage medium) such as a HDD (Hard Disk Drive) or flash memory, or may be stored in a removable storage 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 the drive device. Part of the processing executed by the payment application 20 may be executed by the payment server 100 , and 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 the settlement server 100 may be included in other devices. For example, the first manager 128 and the second manager 130 may be included in another device different from the settlement server 100 . In this embodiment, as an example, the first management unit 128 and the second management unit 130 are described as being included in the settlement 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 settlement server 100 via a network. The storage unit 170 stores information such as user information 172, payment content information 174, member store/store information 176, and the like.

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

The login status management unit 120 manages the login status of each user. For example, the login state management unit 120 permits login based on the telephone number and password input by the user, and 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, a function of a web server, and provides the user terminal device 10 with information (contents and interface screens) for displaying various screens of the electronic payment service. The content providing unit 122 appropriately reads necessary content from the payment content information 174 and provides it to the user terminal device 10 . The user terminal device 10 accepts various inputs from the user while the content is being reproduced by the payment application 20 , and transmits the above-described payment information and the like to the payment server 100 .

The payment processing unit 124 performs payment processing based on the payment information transmitted from the user terminal device 10 or the first shop 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 or not desired information is managed. Details of the processing of the first management unit 128 and the second management unit 130 will be described later.

FIG. 5 is a diagram showing an example of the contents of the user information 172. As shown in FIG. The 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 setting, carrier payment setting, chat friend list, charge history information, payment history information, chat history information, etc. are associated with each other. When registering for the electronic payment service, it is mandatory to register a phone number and password. The account ID is issued to the user by the settlement server 100, and the user ID is an ID that can be set arbitrarily by the user (does not need to be set). In addition, information other than the user URL, account ID, telephone number, password, registration date, charge balance, charge history information, and settlement history information can be arbitrarily set by the user. Hereinafter, a user instance (electronic settlement account) associated with these pieces of information will be referred to as an account. The user URL is used for remittance processing between users. The registration date is the date when the user registers for the electronic payment service (the date when the account is 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 trader (bank), remittance from a registered bank account, and the like. Each of the bank account and credit card number is information (account number, card number) of a bank account or credit card number that can deposit money into the electronic payment service. Other service cooperation information is a login ID or the like of another service that cooperates with the electronic payment service (for example, is operated by an operator belonging to the same business group). Radio wave authentication setting is setting information when performing authentication by communication with a specific communication carrier. The carrier payment setting is setting information for transferring at least part of the payment using the electronic payment service to payment to the communication carrier. The chat friend list is a list of other users who are chat partners in the chat function provided by the electronic payment service. The charge history information is a history of the user's advance remittance to the electronic payment service to increase the charge balance. The payment history information is information indicating details of payments made by the user (date and time, shop ID of the shop where the purchase was made, payment amount, etc.) for each payment. The 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 member store/store information 176. As shown in FIG. The store information 176 includes, for example, a first table 176A in which member store IDs and store IDs are associated with store URLs, and a second table 176A in which member store names and sales proceeds (described above) are associated with member store IDs. It includes a table 176B and a third table 176C in which store IDs are associated with store names. The member store/store information 176 may include, in addition to this information, information such as the category of the member store or store, the location of the store, and the payment pattern.

The information processing section 126 manages various types of 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 services according to, for example, the user's operation of the mini-appli 30, which will be described later.

[Overview of processing]
The settlement server 100 collects information from other services (service server 200), aggregates and manages the collected information. The settlement server 100 provides other services with part or all of the aggregated information. FIG. 7 is a conceptual diagram (part 1) of processing. Through this processing, for example, when a user applies for a service as described later, the settlement server 100 provides information to the service. The service can accept applications with the help of the information provided. For example, since the user's input fields can be pre-filled with user information based on the aggregated information, pre-filling is expanded. Pre-filling means that user information is previously entered in input fields without depending on the user's operation. In addition, the settlement server 100 can perform various analyzes using the aggregated information and realize optimization of marketing.

Furthermore, the payment server 100 serves one or both of the result 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 server 200 . As a result, the service server 200 can omit performing new identity verification and receiving 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 facial features. do. In the electronic payment service, identity verification is performed using the provided information, and the user can use the electronic payment service. Identity verification is a process of confirming whether or not the information input by the user matches the information for identity verification provided by the user (for example, identity verification documents or images taken by the user). For example, when the information entered by the user matches the information on the driver's license, which is the identity verification document, and the image of the driver's license matches the appearance of the captured image, the identity verification is completed. Personal identification may be automatically performed by computer processing, or part or all of the process may be performed by staff. Also, public personal authentication may be used for personal identification. For example, personal identification may be performed using electronic information on a My Number card.

When the identity verification is completed, the settlement server 100 acquires information indicating that the identity verification has been completed. After that, when the user wants to use postpayment, asset management, and bank services, which are services provided in the electronic payment service, it is necessary to separately apply for the use of these services.

For example, if the processing of the present embodiment is not performed, the user provides the service server 200 with the customer information input, the document for identity verification, and the image of the required facial features when applying for each service. However, the service server 200 needs to perform examination, authentication, and the like. Thus, inputting information and providing information when applying for each service imposes a heavy burden on the user. Moreover, there is a problem on the side of the service provider, because the user is likely to withdraw in the middle of the application.

Therefore, in the present embodiment, the settlement server 100 provides the user information, the authentication result of personal identification, etc. to the other service servers 200, so that the user can to help make the service available. A specific description will be given below.

[Description of Functional Configuration of First Management Unit (Information Providing Unit) and Second Management Unit (Acquisition Unit)]
FIG. 9 is a diagram for explaining the functional configuration of the first management unit 128 and the second management unit 130. As shown in FIG. The first management unit 128 provides user information and information managed by the settlement server 100 (for example, authentication results of personal identification) in response to a request from the service server 200 . For example, when a user applies for a service, the service server 200 requests the payment server 100 to provide user information required for application, and obtains information according to the request from the first management unit 128 .

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

For example, the second management unit 130 acquires 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 As a result, the settlement server 100 serves as a hub for different services, and information obtained from each service can be shared among the services. The above processing is performed by "corresponding the second information (information acquired by the asset management service server 200) acquired by the acquisition unit to a second mini-application that operates in the electronic payment application and provides other services." This is an example of the process of "providing to a second service server (for example, a service server of a bank)".

FIG. 10 is a diagram showing an example of information registered by the second management unit 130. As shown in FIG. This information is information included in the user information 172, for example. 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. A status is information indicating whether or not a predetermined confirmation has been made. The example of FIG. 10 indicates, for example, that the identity verification process has been completed. The confirmation date and time is the date and time when the identity is confirmed. A confirmation method is information indicating a document used for personal identification. The document is, for example, a driver's license or my number card. The confirmation subject is the subject who has performed identity verification. In the example of FIG. 10, identity verification is performed by the administrator of the electronic payment service.

Information IF2 is information (information registered by second management unit 130) provided by mini-application 30 and service server 200, which will be described later. The information IF2 is, for example, information input by the user to 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 changed dynamically. For example, the user information held by the settlement server 100 may be the information IF1, and other information may be the information IF2. For example, the user's name, attributes, contact information, and place of work may be defined as information IF1, and other information may be defined as information IF2. In this case, regardless of whether the payment server 100 holds the information IF2 or not, the mini-application 30 displays an interface screen (for example, an interface screen IM7 in FIG. 13 or an interface screen IM10 in FIG. 15, which will be described later) to the user. ) may be provided, and the information input by the user may be used as the information IF2. Further, when the payment server 100 holds the information IF2, the payment application 20 may display an interface screen including the information IF2 on the display unit 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 a launch button that launches a mini app]
A payment application includes one or more mini applications 30 . FIG. 11 shows a mini app 30 included in the payment app 20. As shown in FIG. The mini-application 30 is, for example, an application that uses the payment application 20 as a platform. The mini-application 30 is, for example, an application program developed by a service provider that provides the service of the service server 200 to operate within the payment application 20 . The service provider develops the mini-application 30 by referring to an SDK (Software Development Kit), which is an application development program and technical documents 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 running. For example, when the payment application 20 is installed, some or all of the mini applications 30 may be installed, or some or all of the mini applications 30 may be installed from the service server 200 corresponding to the mini applications 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 an activation button for activating 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 QR codes (registered trademark) and barcodes used in the electronic payment, and information on services related to various electronic payments. Area AR1 of interface image IM1 includes one or more buttons for starting mini appli 30 . When the activation button B1 is operated, the mini application 30 of the bank is activated. The mini-appli 30 provides services to users in cooperation with, for example, a bank's service server 200 .

[Processing related to the use of mini apps (Part 1)]
FIG. 13 is a diagram for explaining the process of opening a bank account using the mini-application 30. As shown in FIG. 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 (for example, B2 or B3 in FIG. 13) on the interface screen IM2 is operated, the information processing section 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, place of work, 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 section 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". Also, the button B1 in FIG. 12 is another example of the 'start button' or 'application button'. For example, when the button B1 in FIG. 12 is operated to start the process of applying for use of the service, the button B1 may be the "start button" or the "application button."

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

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

If the information input by the user or the information provided by the user requires examination or authentication, the payment server 100 and the payment application 20 display an interface screen (not shown) for examination or authentication. For example, a driver's license, a My Number card, and an interface screen for attaching or capturing an image of the person himself/herself are provided. When an image is attached to the interface screen and sent to the payment server 100, the payment server 100 performs predetermined examination and authentication, and processes are performed according to the results of the examination and authentication. For example, if the examination or authentication is positive, the information used for the examination or authentication and the result of the examination or authentication are registered in the user information 172, and if the examination or authentication is negative, the payment server 100 Ask the user for other information. It may take a certain amount of time for examination and certification. If it takes time, the user may stop inputting here, wait for review, and resume input after review. You may proceed with inputting information other than waiting.

After the settlement server 100 acquires the predetermined information, it associates the acquired information with the identification information of the user of the user information 172 , stores the acquired information in the storage unit 170 , and provides the stored information to the service server 200 . The settlement 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. may Mini appli 30 and service server 200 display interface screen IM7 on the display unit. The interface screen IM7 is information necessary for the service provided by the service server 200. FIG. For example, it is information required by a service manager when a user applies for a service. This information is information preset for each service, and is, for example, information that is not registered in the user information 172 .

When service server 200 acquires the information necessary for the service, service server 200 and mini appli 30 display 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-application 30 and the service server 200 display the interface screen IM8 containing the information obtained by the settlement server 100 and the information obtained by the service server 200 at predetermined positions as described above. to display. This allows the user to confirm his/her own information.

[Processing related to the use of mini-apps (Part 2)]
FIG. 15 is a diagram for explaining the processing when applying for use of a predetermined service using the mini app 30. As shown in FIG. In this process, it is assumed that the user's name, attributes, contact information, and office 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-application 30 cooperates with the service server 200 to display the interface screen IM9 on the display unit. When a button for inputting customer information on interface screen IM9 is operated, settlement server 100 omits the process of acquiring information, and mini-application 30 and service server 200 receive information necessary for using the service. The interface screen IM10 for acquiring (my number) is displayed on the display unit. The interface screen IM10 is an example of a "third interface screen". If the payment server 100 holds the necessary information, the payment server 100 provides the service server 200 with the necessary information.

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 with the information acquired by the service server 200, similar to the interface screen IM8 in FIG. The interface screen IM11 including the content in which the information is arranged at a predetermined position is displayed on the display unit. As a result, the user can confirm the information such as the name and attributes input at the start of a predetermined transaction of the payment service, or confirm the information input at the start of the predetermined transaction of the service. Processing for correcting these pieces of information will be described later.

If a plurality of types of information IF1 (for example, the user's name, attributes, contact information, and work place information) are not stored in the user information 172, the settlement server 100 stores the types of information that are not stored. 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 to the interface screen is registered in association with the user identification information, and registered as the user identification information. The service server 200 is provided with a plurality of associated types of information IF1. Thereby, even if the settlement server 100 does not store the part of the information IF1, it can acquire the part of the information IF1 and provide the service server 200 with the information IF1.

Note that even if the information IF1 is stored in the storage unit 170, the settlement server 100 displays an interface screen on the display unit of the user terminal device 10 to prompt the user to confirm the stored information IF1. may be displayed. This interface screen is prefilled with user information IF1 stored in the storage unit 170, for example. For example, if part of the information IF1 is not stored in the payment server 100, the payment server 10 displays an interface screen on the display unit of the user terminal device 10 to prompt the user to input the information IF1 that is not stored. In addition to the display, an interface screen for prompting confirmation of the stored information IF1 may be displayed on the display unit of the user terminal device 10 in a state in which the stored information IF1 is prefilled. For example, if the user's name is not stored, the payment server 100 causes the user terminal device 10 to display the interface screen IM3, and if other information IF1 is stored, the stored information IF1 is prefilled. interface screens IM4 to IM6 may be displayed on the display unit of the user terminal device 10. FIG.

The above information IF1 (first information) may be information that satisfies a predetermined criterion. 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 street address may be registered. If the settlement server 100 stores information IF1 (first information) that does not meet the predetermined criteria, the user terminal device 10 displays the interface screen (for example, the interface screen IM3-6) prefilled with this information. may be displayed on the display unit and the information may be requested to be corrected so as to satisfy a predetermined standard.

[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 activates the mini-appli 30 through the operation of the payment application 20 and performs an operation for making a predetermined application provided by the service system, the service system sends the user's information to the payment system. (S50). The settlement system searches the user information 172 (S52) and transmits the search result to the service system (S54). For example, when the payment server 100 holds information (first information, information IF1) for the payment server 100 to acquire or manage, the information is provided to the service system.

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

Next, the service system executes processing for prompting the user to input information required by the service (S60). Next, the service system provides the entered information to the settlement system (S62). Next, the payment system registers the provided user information 172 in association with the identification information of the user (S64). Note that the processing of S62 and S64 may be omitted, or information with the user's consent to sharing information with the payment system may be provided to the payment system. Further, whether or not to omit the processing of S62 and S64 may be determined according to the type of service system.

As described above, the service system can use the information obtained and managed by the payment server 100 to process the user's use of services. FIG. 17 is a conceptual diagram of information sharing. For example, while the user is logged into the payment application 20, when the user starts a transaction for another service, the service server 200 receives the information input at the start of a predetermined transaction for the payment service, the personal identification document, and the user's physical appearance. By using captured images, it is possible to perform examinations and procedures for the start of transactions.

Thereby, the service server 200 can reduce the load for acquiring information. Moreover, since the user does not need to input the same information, the user's load is reduced.

In the above description, the information acquired by the settlement server 100 is provided to the service server 200, but in addition (or instead), the result of identity verification by the settlement server 100 is provided to the service server 200. may FIG. 18 is a conceptual diagram of providing a result of identity verification. For example, while the user is logged in to the payment application 20, when the user starts a transaction for another service, the service server 200 receives the result of identity verification performed at the start of a predetermined transaction for the payment service (so-called eKYC), and other It provides the service server 200 with the results of examination and the like. The service server 200 can use or refer to the provided personal identification results and other examination results to conduct examinations and procedures for starting transactions.

[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 for correcting information on the interface screen IM11 (input content confirmation screen), the payment application 20 and the payment server 100 display 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 personal identification information needs to be updated in order to edit user information, an update button for updating, and the like. Updating the identity verification information means, for example, updating information associated with user identification information managed by the settlement server 100 . For example, it is necessary to carry out identity verification processing such as sending an image of a driver's license again.

For example, when editing an e-mail address, an interface screen IM13 for inputting the e-mail address is displayed by a predetermined operation, and when the e-mail address is edited and a predetermined operation is performed, the screen transitions to the interface screen IM14. An authentication e-mail is sent to the entered 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 described above, when the user information acquired by the payment system or the user information acquired by the service system is corrected, the payment system executes the interface screen and processing for correcting the information, and the user's use update the person information 172 (update the first information); In this way, the settlement system updates the user information 172 of the user and newly registers the updated information in the user information 172. Therefore, when providing information to other services, the correction is reflected. can provide information. This process is performed as follows: "When the start button for starting the service of the second service included in the first interface screen is operated after the first information is updated, the control unit This is an example of the process of providing the changed first information to the second service server corresponding to the second mini app 30 that runs in the app and provides the second service.

Note that if an operation for correcting the information (second information) necessary for the service server 200 to use the service acquired on the interface screen IM10 is performed on the interface screen IM11, the settlement server 100 And the payment application 20 does not provide an interface screen for correction, but displays an interface screen ("5th interface screen”) is displayed on the display unit.

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

Next, the settlement 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. The payment system then provides the corrected information to the service system (S106). Next, the service system causes the display unit to display an interface screen including information reflecting the correction (S108). For example, when the address is changed, the interface screen IM11 displays an interface screen in which the address before the change is corrected to the address after the change.

As described above, when user information is modified by an operation on the interface screen provided by the service system, the payment system performs processing according to this operation to accept the modification, and the user's user information 172 update. Thereby, the settlement 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 the conditions for using the mini app 30 to apply for services provided by the service system. For example, part or all of conditions 1 to 8 are conditions for applying using information managed in the above-described payment service.

For example, while the user is logged in to use the payment application 20 (Condition 2), an interface screen is displayed on the display unit, and an application button for applying for use of another service included in the interface screen is operated. , when the user's use of the electronic payment service satisfies the conditions set in the electronic payment service (for example, condition 7) and the user's identity verification is completed in the electronic payment service (for example, conditions 1 and 5); The service server 200, which operates in the payment application 20 and provides other services in cooperation with the mini-application 30, provides the service server 200 with completion information indicating that the personal identification has been completed. If the button B1 is operated and the set conditions are not satisfied or the identity verification of the user is not completed, the service server 200 stops the application at least temporarily. Let

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

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

(Condition 1) The administrator of the electronic payment service has performed predetermined confirmation of the user, and the predetermined confirmation has been completed. For example, the confirmations made at the start of using the electronic payment service have been completed. For example, when a predetermined confirmation has been completed, a flag indicating whether or not the identification information of the user in the user information 172 has been verified is added. The server 100 or service server 200 can determine whether condition 1 is satisfied (see FIG. 10).

(Condition 2) Log in to the payment application 20 . This is because logging in to the payment application 20 enables the use of the mini-application 30, and the mini-application 30 can be used to apply for services.

(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 settlement server 100 by cooperating with the second management unit 130 using user identification information as a key (see FIG. 9 described above). It is assumed that the consent to provide the user's information to the service server 200 has been obtained from the user.

(Condition 4) The service must be able to acquire the identity verification date and time of the target user and information on the verification method via the second management unit 130 (for example, API). For example, the service can acquire the confirmation date and time and the confirmation method of personal identification managed by the settlement 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 subject of transaction confirmation must be the administrator of the electronic payment service. A transaction confirmation is a confirmation for the use of an electronic payment service. The subject of this confirmation must be 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 application 30 . This will be described later (see FIGS. 22 and 23).

(Condition 7) In the electronic payment service, the user must not be a user who is suspected of being impersonated or a user who is suspected of being a fraudulent customer. For example, the settlement server 100 uses predetermined criteria to identify users who satisfy the above conditions, and suspends the identified users. Suspend processing means suspending or suspending use of an electronic payment service or related services by a specified user.

(Condition 8) The user must not meet the use prohibition conditions. Whether or not the use prohibition condition is satisfied is determined based on information associated with the user identification information of the user information 172, for example. Usage prohibition conditions are, for example, various conditions such as preset users.

[Description on (Condition 6)]
The payment server 100 operates a button or a service start 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 payment application 20. When the operation button for starting the use of the first service is operated after the processing for receiving the provision of the service is completed (for example, after the application is completed) in response to the operation of the button for An interface screen for executing authentication by the biometric authentication function installed in the user terminal device 10 is displayed on the display unit, and when biometric authentication is established according to the user's operation on the interface screen, the biometric authentication is performed according to the operation. An interface screen for proceeding with processing 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 illustrating an example of the flow of authentication processing. First, the payment application 20 determines whether or not 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). Predetermined authentication is, for example, authentication realized by a function installed in the user terminal device 10 (for example, an OS (Operating System) or an application program). For example, 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 the authentication has been established (S204). If authentication is successful, mini-application 30 and service server 200 provide the service (S206). For example, it continues processing for starting a transaction with the user or starts a transaction. If authentication is not established, mini-application 30 and service server 200 do not provide services, and one routine of this process ends.

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

For example, assuming that the above authentication is not used, the user can send images of the driver's license taken from multiple angles, an image of the back of the driver's license, an image of the person's face, etc. to the payment server 100 or the service. must be provided 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 the above processing, authentication is described as being performed when applying for use of the service. 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 settlement server 100 holds and executes appropriate processing according to the 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 service to the user by utilizing the information managed by the settlement 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>
A second embodiment will be described below. In the second embodiment, the identification information of the user in the user information is associated with information indicating risks associated with transactions with the user, and this information is provided to the service server 200 . The following description will focus on differences from the first embodiment.

FIG. 24 is a diagram showing part of the functional configuration of the payment server 100A of the second embodiment. The settlement 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 settlement server 100 of the first embodiment. Some of these functional configurations may be included in other devices. The settlement server 100A is an example of an "information processing device."

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

The second acquisition unit 134 acquires communication information, which is one or both of information on the device used by the user in using the electronic payment service and information on the network used by the user. The information about the device is information such as the type of the device of the user terminal device 10 and the IP address (Internet Protocol Address). Information about the network includes information about the Internet service provider accessed by the user terminal device 10, information about 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 generator 136 derives user reliability based on the user information and the communication information. The flag generating unit 136 generates, for example, risk flags according to reliability and derives scores according to reliability. These pieces of information are provided to the service server 200 . For example, in response to a request from the service server 200, the second management unit 130 provides the service server 200 with information indicating reliability, user information held by the settlement server 100, and information indicating the result of identity verification. For example, in a state in which the user is logged in to use the payment application 20, when an application button for applying for use of another service included in the interface screen displayed on the display unit is operated, the second management In response to a request from the service server 200, the unit 130 may provide the service server 200 with information indicating reliability, user information, and information indicating the result of identity verification.

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

A user who satisfies a predetermined condition means that the user is pre-registered in the list. For example, this list contains high-risk users. Satisfaction of the user's usage pattern of the electronic payment service means that the electronic payment service is used in a preset usage pattern, such as, for example, making high-value payments more than a predetermined number of times. Insufficient information means, for example, inconsistency in information (e.g. inconsistency between address prefecture and city) or incompleteness in necessary information (e.g. lack of necessary information) and so on.

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

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

In the above example, a flag is given to a high-risk user, but instead of this, a flag corresponding to the level of risk may be given. For example, a flag corresponding to the level of risk, such as a high risk flag, medium risk flag, or low risk flag, may be assigned. Also, instead of the flag, a score indicating high or low risk may be given. The flag generating unit 136 refers to the criteria based on the conditions described above, derives the score, and associates the derived score with the identification information of the user.

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

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

The gray flag indicates that the user information satisfies a predetermined condition among the conditions associated with the user (for example, the user who meets the conditions related to electronic payment or the information is incomplete), and the user who does not correspond to the conditions not associated with the user Flags to be set. A 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 user-related conditions and the user-unrelated conditions.

For example, when a white flag user performs an operation to apply for the use of the service of the mini-appli 30, the settlement server 100 allows the user to use the service without following the procedures for a gray flag user, which will be described later. can be done.

For example, when a gray-flagged user performs an operation to apply for the service of the mini app 30, the payment server 100 requests the user to re-confirm the identity of the user, which is performed in the electronic payment service. For example, the settlement server 100 causes the display unit to display an interface screen for performing identity verification again. 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 using the service of the mini app 30, the settlement server 100 causes the display unit to display an interface screen containing 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 settlement server 100 generates information regarding user risk and provides the generated information to the service server 200 . Accordingly, the service server 200 can refer to the acquired risk information and determine whether to provide the service to the user. As a result, more accurate determination regarding service provision is made.

<Other examples (1)>
In the above example, the information held in the payment server 100 is shared with the service server 200 when the user operates the mini-application 30 while logged in to the payment application 20. 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 another example (1). For example, the user terminal device 10 accesses the service server 200 of the bank without going through the mini application 30, and the user attempts to open a bank account. For example, when an operation for opening a bank account is performed on an interface screen provided by the service server 200, the service server 200 prompts the user to log in to the electronic payment service and connect the electronic payment service and the bank service server 200. Inquires whether or not to link When the user selects to cooperate and performs a predetermined operation to log in, or enters user identification information and a password used in the electronic payment service, the bank service server 200 receives payment from the payment server 100. User information and the result of personal identification managed by the server 100 are acquired. The bank 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, even if the user does not use the mini-application 30, the user's information held by the settlement server 100 can be used by another service server 200, which increases the user's convenience. and the processing load of the service server 200 is reduced.

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

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

<Other examples (3)>
When the user updates the user information on the interface screen provided by the service server 200 and the service server 200 updates the user information, the service server 200 notifies the settlement server 100 that the user information has been updated. You may provide information and update content to indicate. The settlement server 100 may update the user information in the user information 172 based on this information. Furthermore, the settlement server 100 may provide the other service server 200 with information indicating that it has been updated and the content of the update.

As described above, when the user's information is updated in the service server 200, the settlement server 100 can retain the latest information by acquiring the update-related information from the service server 200. FIG.

As described above, the mode for carrying out the present invention has been described using the embodiments, but the present invention is not limited to such embodiments at all, and various modifications and replacements can be made without departing from the scope of the present invention. can be added.

10 User terminal device 20 Settlement application 30 Mini app 50 First store terminal device 60 Store code image 70 Second store terminal device 100 Settlement server 121 Service information acquisition unit 122 Content providing unit 124 Settlement processing unit 126 Information processing unit 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 Settlement content information

Claims (13)

A payment management device that provides an electronic payment service,
The application button for applying for the use of other services included in the first interface screen displayed on the display unit of the terminal device is operated while the user is logged in to use the electronic payment application, and the user When the usage mode of the electronic payment service satisfies the conditions set in the electronic payment service and the identification of the user has been completed in the electronic payment service, the electronic payment application operates to perform the other service. Completion information indicating that the personal identification has been completed is provided to the service server that provides the other service to the user in cooperation with the provided mini app, and the service server proceeds with the processing related to the application. indicate that
a control unit that causes the service server to at least temporarily stop the application when the application button is operated and the set conditions are not satisfied or the identity verification of the user is not completed;
A payment management device. The control unit
An application button for applying for the use of the first service included in the first interface screen displayed on the display unit while the user is logged in to use the electronic payment application, or the use of the first service. When the operation button for starting is operated, an interface screen for executing authentication by the biometric authentication function installed in the user's terminal device is displayed on the display unit,
When biometric authentication is established according to the user's operation on the interface screen, displaying on the display unit an interface screen for proceeding with the process according to the operation;
The settlement management device according to claim 1. The control unit provides the user's identification information to a service server corresponding to the mini app, and shares the user's identification information.
The settlement management device according to claim 1. Completion information indicating completion of the identity verification corresponding to the shared user identification information stored in a storage unit, date and time information indicating the date and time when the identity verification was completed, and a method of indicating the identity verification method further comprising an information providing unit that acquires information and provides the acquired completion information, date and time information, and method information to the service server;
The settlement management device according to claim 3. In the case of facilitating the above application,
The control unit provides the first service, which is the other service, when the first information among the information required for the application including the first information and the second information is stored in the storage device. executing processing for displaying on the display unit a third interface screen for prompting the user to input the second information to the mini app;
The first information is 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 information required to use the service of the first mini-app.
The settlement management device according to any one of claims 1 to 3. In the case of facilitating the above application,
The control unit displays an interface screen for prompting a user to input the first information when the first information among the information required for the application including the first information and the second information is not stored in the storage device. display in the department,
The first information is information required to use the service of the first mini-app that provides the first service, which is the other service, and to use the service of the mini-app that is different from the first mini-app. ,
The second information is information required to use the service of the first mini-app.
The settlement management device according to any one of claims 1 to 3. further comprising an information providing unit that provides the first information input to the interface screen to the first service server corresponding to the first mini app;
The settlement management device according to claim 6. The information providing unit provides the first service server with information for identity verification obtained from the terminal device of the user and an authentication result for identity verification obtained based on the first information.
The settlement management device according to claim 7. The payment management device according to claim 8;
The service server that starts providing a service to the user based on the first information and the authentication result,
Payment management system. further comprising an acquisition unit that acquires the second information from a first service server corresponding to the first mini-app that provides the first service, which is the other service;
The settlement management device according to claim 5. further comprising an information providing unit that provides the second information obtained by the obtaining unit to a second service server corresponding to the second mini app that provides the other service;
The settlement management device according to claim 10. A payment management method for providing an electronic payment service, comprising:
the computer
The application button for applying for the use of other services included in the first interface screen displayed on the display unit of the terminal device is operated while the user is logged in to use the electronic payment application, and the user When the usage mode of the electronic payment service satisfies the conditions set in the electronic payment service and the identification of the user has been completed in the electronic payment service, the electronic payment application operates to perform the other service. Providing completion information indicating that the personal identification has been completed to a service server that provides the other service to the user in cooperation with the provided mini app, and prompting the service server to make the application. direct,
If the application button is operated and the set conditions are not met, or if the identity verification of the user is not completed, the service server does not promote the application;
Payment management method. A program for providing electronic payment services,
to the computer,
The application button for applying for the use of other services included in the first interface screen displayed on the display unit of the terminal device is operated while the user is logged in to use the electronic payment application, and the user When the usage mode of the electronic payment service satisfies the conditions set in the electronic payment service and the identification of the user has been completed in the electronic payment service, the electronic payment application operates to perform the other service. Completion information indicating that the personal identification has been completed is provided to the service server that provides the other service to the user in cooperation with the provided mini app, and the service server proceeds with the processing related to the application. and
a process of causing the service server to at least temporarily suspend the application when the application button is operated and the set conditions are not satisfied or the identity verification of the user is not completed;
program to run.

Images