JP7663538B2 - Information processing program, information processing device, and information processing method - Google Patents

Description

The present invention relates to an information processing program, an information processing device, and an information processing method.

Conventionally, there is known a technique for issuing a token to a payment application (hereinafter referred to as a "payment app") installed on a device, and using the token to make a payment in the payment app. For example, Patent Literature 1 describes that a token is issued to a payment app installed on a user's device, and a store terminal reads a payment code generated based on the token, thereby making a payment based on the payment app.

There is also known a technique for authenticating a device or a user using an authentication application (hereinafter referred to as an "authentication app") installed on the device. Such payment apps and/or authentication apps (hereinafter referred to as "payment/authentication apps") are generally used for dedicated purposes in order to ensure a certain level of security.

Patent No. 6986176

Various applications, including but not limited to payment/authentication apps, are installed on user devices. For example, applications optimized for various services (hereinafter referred to as "service apps"), such as online services that provide virtual reality (VR) spaces or metaverse spaces, are becoming more widely used. In order to improve the satisfaction of users who use such service apps (e.g., building experiences in VR spaces or metaverse spaces), it is expected that the use of a payment function and/or authentication function will be required when the service app provides a service.

However, if an attempt is made to link a service app with a payment/authentication app in order to improve the satisfaction of users who use the service app, there is a risk that a certain level of security required of the payment/authentication app cannot be guaranteed.

This disclosure has been made in light of these circumstances, and one of its objectives is to provide an information processing program, an information processing system, and an information processing method that can improve the satisfaction of users who use service apps while ensuring a certain level of security.

An information processing program according to one aspect of the present disclosure causes a computer to function as an acquisition unit that acquires an issuance request requesting that a token and/or electronic certificate used in a first application provided by a first operator be issued to a second application provided by a second operator, a verification unit that verifies the identity of a user of the first application and a user of the second application in response to the issuance request, and a provision unit that provides the token and/or the electronic certificate issued by the first operator to the second application based on a result of the verification of identity.

An information processing device according to another aspect of the present disclosure includes an acquisition unit that acquires an issuance request requesting that a token and/or an electronic certificate used in a first application provided by a first business be issued to a second application provided by a second business, a verification unit that verifies the identity of a user of the first application and a user of the second application in response to the issuance request, and a provision unit that provides the token and/or the electronic certificate issued by the first business to the second application based on a result of the verification of the identity.

An information processing method of an information processing device according to another aspect of the present disclosure includes the steps of: acquiring an issuance request for issuing a token and/or an electronic certificate used in a first application provided by a first business operator to a second application provided by a second business operator; verifying the identity of a user of the first application and a user of the second application in response to the issuance request; and providing the token and/or the electronic certificate issued by the first business operator to the second application based on the result of the verification of the identity.

According to one aspect of the present disclosure, it is possible to improve the satisfaction of users who use service apps while ensuring a certain level of security.

1 is a diagram showing a schematic configuration of an information processing system 1 according to an embodiment of the present invention. FIG. 2 is a diagram illustrating an example of a collaboration model according to the embodiment. 1 is a diagram illustrating an example of a physical configuration of each device in an information processing system 1 according to an embodiment of the present invention. FIG. 1 is a diagram illustrating an example of a functional configuration of an information processing system 1 according to an embodiment of the present invention. FIG. 2 is a diagram illustrating an example of an operation of the information processing system 1 according to the present embodiment. FIG. 11 is a diagram illustrating another example of the operation of the information processing system 1 according to the present embodiment.

Below, an information processing system according to one embodiment of the present invention will be described in detail with reference to the drawings. In addition, in the following description of the drawings, identical or similar parts are denoted by identical or similar reference numerals.

Furthermore, in the following, the first application and the second application are respectively a payment/authentication app and a service app, but this is merely an example and is not limited thereto. Furthermore, the first business is a payment business and/or authentication business, and the second business is a service business, but this is merely an example and is not limited thereto. Furthermore, confirmation information regarding a user of the payment/authentication app is shown as an example of first confirmation information regarding a user of the first application, but is not limited thereto. Furthermore, confirmation information regarding a user of the service app is shown as an example of second confirmation information regarding a user of the second application, but is not limited thereto.

(overview)
1 is a diagram showing an overview of an information processing system according to the present embodiment. As shown in FIG. 1, the information processing system 1 includes a terminal 10, a payment/authentication provider device 20, a service provider device 30, an inter-application cooperation device 40, and a network 50.

The terminal 10 is a terminal on which a payment/authentication app and/or a service app is installed and used by a user. The terminal 10 is, for example, a smartphone, a tablet, a personal computer, a game console, VR (Virtual Reality) goggles, a VR headset, etc. The payment/authentication app and/or a service app is installed on the terminal 10. Note that the payment/authentication app and the service app may be installed on different terminals 10, or may be installed on the same terminal 10.

The payment/authentication business device 20 is an information processing device of a payment business and/or authentication business, and provides a payment/authentication app. The payment business is, for example, a credit card company, a financial institution, etc. The authentication business is, for example, a credit card company, a financial institution, a certification body, etc. The payment/authentication business device 20 is not limited to one information processing device, and may be composed of multiple information processing devices.

The payment/authentication app is an application that has a payment function and/or a user authentication function. For example, a payment is performed by the payment business operator based on a token issued by the payment/authentication business operator device 20 to the payment/authentication app. Also, authentication by the authentication business operator may be performed based on a digital certificate issued by the payment/authentication business operator device 20 to the payment/authentication app.

The service provider device 30 is an information processing device of a service provider, and provides a service app. The service provider is, for example, a game company, a company providing a VR space, a company providing a metaverse space, etc. The service provider device 30 is not limited to one information processing device, and may be composed of multiple information processing devices.

Service apps are applications optimized for various services, such as online services that provide VR and metaverse spaces.

The inter-application cooperation device 40 is an information processing device used for cooperation between a payment/authentication application and a service application. The inter-application cooperation device 40 provides a token and/or an electronic certificate (hereinafter referred to as "token/certificate") issued by a payment/authentication business operator to the service application. The inter-application cooperation device 40 is not limited to one information processing device, and may be composed of multiple information processing devices.

The inter-application linkage device 40 has an interface with a payment/authentication application installed on the terminal 10 (hereinafter referred to as the "payment/authentication application I/F") and an interface with a service application installed on the terminal 10 (hereinafter referred to as the "service application I/F"). The payment/authentication application I/F and the service application I/F are, for example, APIs (Application Programming Interfaces) and may be used for calling functions, providing SDKs (Software Development Kits), etc.

The network 50 is a wireless and/or wired network that connects at least two of the terminal 10, the payment/authentication provider device 20, the service provider device 30, and the inter-application linkage device 40.

The inter-application cooperation device 40 also has a connection interface with the payment/authentication provider device 20 (hereinafter referred to as the "payment/authentication provider I/F") and a connection interface with the service provider device 30 (hereinafter referred to as the "service provider I/F"). The inter-application cooperation device 40 transmits and receives data to and from the payment/authentication provider device 20 via the payment/authentication provider I/F, and transmits and receives data to and from the service provider device 30 via the service provider I/F. The payment/authentication provider I/F and the service provider I/F may be, for example, an API.

Figure 2 is a diagram showing an example of a collaboration model according to this embodiment. Note that in Figure 2, the payment/authentication app and the service app are installed on the same terminal 10, but this is not limited thereto, and they may be installed on different terminals 10. Note that the order of steps S101 and S102 may be reversed.

In the collaboration model shown in FIG. 2, when a service provided to a user by a service app requires payment and/or authentication, the inter-app collaboration device 40 verifies the identity of the user of the payment/authentication app and the user of the service app in response to a token/certificate issuance request from either the payment/authentication app or the service app, and provides the service app with a token/certificate issued by the payment/authentication business based on the result of the identity verification.

Specifically, in step S101 of FIG. 2, in response to a token/certificate issuance request from either the payment/authentication app or the service app to the service app, a user verification process is performed between the payment/authentication business device 20, the payment/authentication app, and the user via the inter-application linkage device 40. In the verification process, the inter-application linkage device 40 obtains verification information related to the user of the payment/authentication app (hereinafter referred to as "payment/authentication user verification information").

In step S102, in response to the issuance request, a user verification process is performed between the service provider device 30, the service app, and the user via the inter-app linkage device 40. In the verification process, the inter-app linkage device 40 obtains verification information regarding the user of the service app (hereinafter referred to as "service user verification information") from the service provider device 30.

Here, the user verification process in step S101 is a process for verifying that the user is a legitimate user of the payment/authentication app. Also, the user verification process in step S102 is a process for verifying that the user is a legitimate user of the service app. The user verification process in steps S101 and S102 may be (1) a high level (hereinafter referred to as "high level") identity verification as required by the Criminal Proceeds Transfer Prevention Act, and/or (2) a lower level identity verification than the high level identity verification. (1) In the high level identity verification, for example, identity verification may be performed using at least two of knowledge information (for example, a password, a PIN code, or a secret question, etc.), possession information (for example, SIM card information, a hard token, or an IC card, etc.), and biometric information (for example, a face, a fingerprint, a vein, a voiceprint, etc.). Note that the high level identity verification may be called identity authentication. (2) In the low level identity verification, for example, identity verification using knowledge information may be performed. Alternatively, the method may be a method of simply verifying the identity of a user by comparing user information stored in a customer database held by a service provider, financial institution, payment provider, public institution, or other provider with information provided by the user, and if they match, verifying the identity of the user. For example, a low level of identity verification may be performed between the payment/authentication provider device 20 and the payment/authentication app, and a high level of identity verification (identity authentication) may be performed between the payment/authentication app and the user. Similarly, a low level of identity verification may be performed between the service provider device 30 and the service app, and a high level of identity verification (identity authentication) may be performed between the service app and the user.

In step S103, the inter-application cooperation device 40 verifies the identity of the user of the payment/authentication application and the user of the service application based on the payment/authentication user confirmation information acquired in step S101 and the service user confirmation information acquired in step S102. If the identity of the user of the payment/authentication application and the user of the service application is verified, in step S104, the inter-application cooperation device 40 provides the token/certificate issued by the payment/authentication business device 20 to the service application.

In step S105, a service is provided to the user by the service app that has acquired the token/certificate issued by the payment/authentication provider device 20. In order to provide the service to the user, the service app may use the acquired token to perform payment-related processing with the payment/authentication provider device 20. In addition, the service app may use the acquired digital certificate to perform authentication-related processing with the payment/authentication provider device 20.

In this way, in the information processing system 1 according to this embodiment, when the use of a payment function and/or authentication function is required when a service is provided by a service app, the identity of the user of the payment/authentication app and the user of the service app is verified, and then a token/certificate for the payment/authentication app is issued to the service app from the payment/authentication business device 20. This makes it possible to link tokens/certificates between the payment/authentication app and the service app while ensuring a certain level of security, thereby improving the satisfaction of users who use the service app.

(composition)
Next, the physical configuration and the functional configuration of the information processing system 1 according to this embodiment will be described.
<Physical configuration>
3 is a diagram showing an example of a physical configuration of each device in the information processing system 1 according to the present embodiment. Each device in the information processing system 1 (e.g., the terminal 10, the payment/authentication provider device 20, the service provider device 30, and the inter-application cooperation device 40) includes a processor 101, a storage unit 102, a transmission/reception unit 103, and an input/output unit 104.

The processor 101 is, for example, a CPU (Central Processing Unit) and controls each device in the information processing system 1. The processor 101 may execute various processes described in this embodiment by reading and executing a program from the storage unit 102. Each device in the information processing system 1 may be configured with one or more processors 101. Furthermore, each of the devices may be referred to as a computer.

The storage unit 102 is composed of storage such as a memory, a hard disk drive (HDD) and/or a solid state drive (SSD). The storage unit 102 may store various information necessary for the processor 101 to execute processing (e.g., a program executed by the processor 101, etc.).

The transmitting/receiving unit 103 is a device that communicates via the network 50, and may include, for example, a network card, a communication module, a chip, an antenna, etc. The transmitting/receiving unit 103 may include a transmitting unit that transmits various information via the network 50, and/or a receiving unit that receives various information via the network 50.

The input/output unit 104 includes an input unit such as a keyboard, a touch panel, a mouse, and/or a microphone, an output unit such as a display and/or a speaker, and an imaging unit such as a camera. The input unit accepts input of various information from a user. The output unit may also include a display unit that displays various information for the user.

The physical configuration described above is merely one example. Each device in the information processing system 1 may omit some of the hardware shown in FIG. 3, or may include hardware not shown in FIG. 3. In addition, the hardware shown in FIG. 3 may be configured from one or more chips.

<Functional configuration>
FIG. 4 is a diagram showing an example of a functional configuration of the terminal 10 and the inter-application cooperation device 40 according to the present embodiment.
<Device>
As shown in Fig. 4, terminal 10 includes payment/authentication application unit 11 that performs various processes provided by a payment/authentication application and service application unit 12 that performs various processes provided by a service application. The function of payment/authentication application unit 11 is realized by processor 101 of terminal 10 executing a program of a payment/authentication application stored in storage unit 102 of terminal 10. The function of service application unit 12 is realized by processor 101 of terminal 10 executing a program of a service application stored in storage unit 102 of terminal 10. When a payment/authentication application and a service application are installed in different terminals 10, each terminal 10 may include either payment/authentication application unit 11 or service application unit 12.

As shown in FIG. 4, the payment/authentication application unit 11 includes an issuance request unit 111 and a user confirmation unit 112. Note that the issuance request unit 111 may be omitted if an issuance request unit 121 is provided in the service application unit 12 described later.

The issuance request unit 111 may request the inter-application cooperation device 40 to issue a token/certificate used in the payment/authentication application unit 11 to the service application unit 12. For example, in response to reception of an input from a user by the input/output unit 104, the issuance request unit 111 may cause the transmission/reception unit 103 to transmit an issuance request for the token/certificate to the inter-application cooperation device 40.

The issuance request may include at least one of information related to the payment/authentication app (hereinafter referred to as "payment/authentication app information"), information related to the service app to which the token/certificate is to be issued (hereinafter referred to as "service app information"), and information related to the token/certificate (hereinafter referred to as "token/certificate information"). The issuance request may also include identification information of the user of the payment/authentication app (hereinafter referred to as "payment/authentication user ID").

The payment/authentication app information may include, for example, at least one of identification information of the payment/authentication app (hereinafter referred to as the "payment/authentication app ID") and identification information of the payment/authentication business that provides the payment/authentication app (hereinafter referred to as the "payment/authentication business ID").

The service app information may also include, for example, at least one of identification information of the service app (hereinafter referred to as the "service app ID") and identification information of the service provider that provides the service app (hereinafter referred to as the "service provider ID").

The token/certificate information may include, for example, at least one of token identification information (hereinafter referred to as "token ID"), electronic certificate identification information (hereinafter referred to as "certificate ID"), and type information. The type information may indicate whether issuance of a token or an electronic certificate is requested, or may indicate that issuance of both a token and an electronic certificate is requested.

The user verification unit 112 performs verification processing of the user of the payment/authentication app. Specifically, the user verification unit 112 performs verification processing of the user of the payment/authentication app between the payment/authentication provider device 20 in response to a verification request from the inter-application cooperation device 40. For example, the user verification unit 112 may perform verification processing of the user of the payment/authentication app between the payment/authentication provider device 20 in the verification processing.

On the other hand, the service application unit 12 includes an issuance request unit 121, a user confirmation unit 122, an acquisition unit 123, and a service unit 124. Note that the issuance request unit 121 may be omitted if the issuance request unit 111 is provided in the payment/authentication application unit 11.

The issuance request unit 121 may request the inter-application linkage device 40 to issue a token/certificate used in the payment/authentication application unit 11 to the service application unit 12. For example, the issuance request unit 121 may cause the transmission/reception unit 103 to transmit an issuance request for the token/certificate to the inter-application linkage device 40 in response to reception of an input from a user by the input/output unit 104. The issuance request is as described for the issuance request unit 111. The issuance request by the issuance request unit 121 may include identification information of the user of the service application (hereinafter referred to as "service user ID").

The user confirmation unit 122 performs a confirmation process of the user of the service app. Specifically, the user confirmation unit 122 performs a confirmation process of the user of the service app between the service provider device 30 in response to a confirmation request from the inter-app cooperation device 40. For example, the user confirmation unit 122 may perform a confirmation process of the user of the service app between the service provider device 30 in the confirmation process.

The acquisition unit 123 acquires the token/certificate issued by the payment/authentication business operator device 20 in response to an issuance request from the issuance request unit 111 or the issuance request unit 121. Specifically, the acquisition unit 123 may acquire the token/certificate received from the inter-application cooperation device 40 by the transmission/reception unit 103.

The service unit 124 provides a service to the user. Specifically, the service unit 124 provides the service to the user using the token/certificate acquired by the acquisition unit 123. For example, in order to provide the service, the service unit 124 may perform a payment-related process with the payment/authentication provider device 20 using the token acquired by the acquisition unit 123. In addition, in order to provide the service, the service unit 124 may perform an authentication-related process with the payment/authentication provider device 20 using the electronic certificate acquired by the acquisition unit 123.

<Inter-app linking device>
4, the inter-application cooperation device 40 includes an acquisition unit 41, a user confirmation unit 42, a verification unit 43, and a provision unit 44. Note that the processor 101 of the inter-application cooperation device 40 executes a program stored in the storage unit 102 of the inter-application cooperation device 40, thereby realizing at least some of the functions of the acquisition unit 41, the user confirmation unit 42, the verification unit 43, and the provision unit 44 described later.

The acquisition unit 41 acquires an issuance request that requests that a token/certificate used in a payment/authentication app provided by the payment/authentication business device 20 be issued to a service app provided by the service provider device 30. Specifically, the acquisition unit 41 acquires an issuance request from the terminal 10 that is received by the transmission/reception unit 103 of the inter-application cooperation device 40. The issuance request may be one requested by either the issuance request unit 111 or the issuance request unit 121.

The user verification unit 42 performs verification processing of the user of the payment/authentication app installed on the terminal 10 and the user of the service app in response to the issuance request acquired by the acquisition unit 41. Specifically, the user verification unit 42 may acquire payment/authentication user verification information from the payment/authentication business device 20 in the verification processing of the user of the payment/authentication app. The user verification unit 42 may also acquire service user verification information from the service business device 30 in the verification processing of the user of the service app.

Here, the payment/authentication user confirmation information may include at least one of the confirmation result of the user of the payment/authentication app and the attribute information of the user. The user attribute information may include, for example, at least one of the user's name, telephone number, email address, date of birth, postal code, gender, age, and, if the user is a corporation, the company name, trade name, and representative name. Furthermore, the service user confirmation information may include at least one of the confirmation result of the user of the service app and the attribute information of the user.

The user verification unit 42 determines the payment/authentication business device 20 to connect to based on the payment/authentication app information (e.g., payment/authentication app ID or payment/authentication business ID) included in the issuance request. The user verification unit 42 may transmit a request for verification processing of the user of the payment/authentication app (hereinafter referred to as a "payment/authentication user verification request") to the payment/authentication business device 20 via the transmission/reception unit 103, and receive payment/authentication user verification information from the payment/authentication business device 20 via the transmission/reception unit 103 in response to the payment/authentication user verification request.

When the issuance request acquired by the acquisition unit 41 includes the payment/authentication user ID (i.e., when the payment/authentication user ID is linked), the user confirmation unit 42 may include the payment/authentication user ID in a payment/authentication user confirmation request to the payment/authentication business. Based on the payment/authentication user ID, the payment/authentication business device 20 may perform a confirmation process for the user of the payment/authentication app.

On the other hand, if the issuance request acquired by the acquisition unit 41 does not include the above-mentioned payment/authentication user ID (i.e., if the payment/authentication user ID is not linked), the user confirmation unit 42 may acquire the payment/authentication user ID from the payment/authentication application unit 11 of the terminal 10 and include the payment/authentication user ID in a payment/authentication user confirmation request to the payment/authentication business device 20. Based on the payment/authentication user ID, the payment/authentication business device 20 may perform a confirmation process for the user of the payment/authentication application.

The user verification unit 42 also determines the service provider device 30 to connect to based on the service app information (e.g., service app ID or service provider ID) included in the issuance request. The user verification unit 42 may transmit a request for verification processing of the user of the service app (hereinafter referred to as a "service user verification request") to the service provider device 30 via the transmission/reception unit 103, and may receive service user verification information from the service provider device 30 via the transmission/reception unit 103 in response to the service user verification request.

When the issuance request acquired by the acquisition unit 41 includes the service user ID (i.e., when the service user ID is linked), the user confirmation unit 42 may include the service user ID in a service user confirmation request to the service provider. Based on the service user ID, the service provider device 30 may perform a process of confirming the user of the service app.

On the other hand, if the issuance request acquired by the acquisition unit 41 does not include the above-mentioned service user ID (i.e., if the service user ID is not linked), the user confirmation unit 42 may acquire the service user ID from the service app unit 12 of the terminal 10 and include the service user ID in the service user confirmation request to the service provider device 30. Based on the service user ID, the service provider device 30 may perform a process of confirming the user of the service app.

The verification unit 43 verifies the identity of the user of the payment/authentication app and the user of the service app in response to the issuance request acquired by the acquisition unit 41. Specifically, the verification unit 43 may verify the identity based on the payment/authentication user confirmation information acquired by the user confirmation unit 42 (e.g., the confirmation result of the user of the payment/authentication app and at least one of the attribute information of the user) and the service user confirmation information (e.g., the confirmation result of the user of the service app and at least one of the attribute information of the user).

For example, the verification unit 43 may compare the verification results of the user of the payment/authentication app with the verification results of the user of the service app to verify the identity of the user of the payment/authentication app and the user of the service app. If the user verified by the payment/authentication business device 20 and the user verified by the service business device match, the verification unit 43 may determine that the user of the payment/authentication app and the user of the service app are the same.

The verification unit 43 may also verify the identity of the user of the payment/authentication app and the user of the service app by comparing attribute information of the user of the payment/authentication app and attribute information of the user of the service app. When the user indicated by the attribute information acquired from the payment/authentication business device 20 and the user indicated by the attribute information acquired from the service business device match, the verification unit 43 may determine that the user of the payment/authentication app and the user of the service app are the same.

If the user of the payment/authentication app and the user of the service app are not the same, the verification unit 43 may transmit error information via the transmission/reception unit 103 to the app that requested the issuance of the token/certificate (the payment/authentication app unit 11 or the service app unit 12). Based on the error information, the terminal 10 may notify the user of the app that requested the issuance of the token/certificate that the issuance process of the token/certificate has been stopped. For example, the terminal 10 may output information indicating the stop of the issuance process to the input/output unit 104 (for example, display on the display unit). In addition, the error information may be transmitted to the payment/authentication business device 20 and/or the service business device 30.

If the user of the payment/authentication app and the user of the service app are the same, the verification unit 43 may instruct the provision unit 44 to provide the token/certificate to the service app.

The providing unit 44 provides the service app with a token/certificate issued by the payment/authentication business based on the verification result of the verification unit 43 of the identity of the user of the payment/authentication app and the user of the service app.

Specifically, when the verification unit 43 verifies the identity of the payment/authentication app user and the service app user, the provision unit 44 transmits a token/certificate issuance request to the payment/authentication business device 20 via the transmission/reception unit 103. The issuance request transmitted to the payment/authentication business may be based on at least one of the payment/authentication app information, the service app information, and the token/certificate information included in the issuance request from the payment/authentication app unit 11 or the service app unit 12 (it may include at least one of the payment/authentication app information, the service app information, and the token/certificate information).

For example, the providing unit 44 may send an issuance request for either a token or an electronic certificate, or an issuance request for both a token and an electronic certificate to the payment/authentication business device 20 based on type information included in the issuance request from the payment/authentication application unit 11 or the service application unit 12.

(Operation)
The operation of the information processing system 1 according to this embodiment will be described with reference to Figures 5 and 6. Note that in Figures 5 and 6, the payment/authentication application and the service application are installed in the same terminal 10, but this is not limited, and they may be installed in different terminals 10. That is, in Figures 5 and 6, the same terminal 10 is equipped with both the payment/authentication application unit 11 and the service application unit 12, but this is not limited, and it goes without saying that the system can operate in the same way even if one terminal 10 is equipped with the payment/authentication application unit 11 and the other terminal 10 is equipped with the service application unit 12.

Figure 5 is a diagram showing an example of the operation of the information processing system 1 according to this embodiment. Figure 5 illustrates a case in which the payment/authentication application unit 11 of the terminal 10 accepts a token/certificate issuance request for the service application unit 12 of the terminal 10.

Note that some steps in FIG. 5 may be omitted, steps not shown may be added, and the order of at least two steps may be changed and/or performed in parallel. For example, steps S203 to S205 and steps S206 to S208 in FIG. 5 may be performed in parallel, or steps S206 to S208 may be performed before steps S203 to S205.

In step S201, the payment/authentication application unit 11 accepts a token/certificate issuance request for the service application unit 12 input by the user via the input/output unit 104.

In step S202, the payment/authentication application unit 11 transmits the issuance request acquired in step S201 to the inter-application cooperation device 40 via the transmission/reception unit 103.

In step S203, the inter-application cooperation device 40 transmits the payment/authentication user confirmation request to the payment/authentication business device 20 in response to the issuance request received in step S202. As described above, the payment/authentication user confirmation request may include a payment/authentication user ID, which may be included in the issuance request in step S202, or may be obtained from the payment/authentication application unit 11 in response to a request (not shown) from the inter-application cooperation device 40.

In step S204, the payment/authentication business device 20 performs a process of verifying the user of the payment/authentication app with the payment/authentication application unit 11 in response to the payment/authentication user verification request from the inter-application cooperation device 40. Specifically, the payment/authentication business device 20 may perform a process of verifying the user with the payment/authentication application unit 11 based on the payment/authentication user ID included in the authentication/payment user verification request. For example, the payment/authentication business device 20 may obtain attribute information of a user identified by the payment/authentication user ID and transmit the attribute information to the terminal 10. The payment/authentication application unit 11 matches the attribute information with information about the user input to the payment/authentication application unit 11 (hereinafter referred to as "user information"). The user information may be, for example, at least one of knowledge information (e.g., user ID, password), biometric information (e.g., captured image of the user, fingerprint, etc.) and possession information (e.g., SIM card number stored in the terminal 10) input to the payment/authentication application. The user information may be input on an input screen that the payment/authentication application unit 11 causes to be displayed on the display unit, may be captured by an imaging unit activated by the payment/authentication application unit 11, or may be acquired through the payment/authentication application unit 11. If the payment/authentication application unit 11 finds a match between the attribute information and the user information, the operation proceeds to step S205, and if the match does not find a match, the operation may end.

In step S205, the inter-application cooperation device 40 receives payment/authentication user confirmation information based on the result of the confirmation process in step S204 from the payment/authentication business device 20. The payment/authentication user confirmation information may include at least one of the user confirmation result in step S204 and attribute information of the user.

In step S206, the inter-application cooperation device 40 transmits the above-mentioned service user confirmation request to the service provider device 30 in response to the issuance request received in step S202. As described above, the service user confirmation request may include a service user ID, which may be included in the issuance request in step S202, or may be obtained from the service application unit 12 in response to a request (not shown) from the inter-application cooperation device 40.

In step S207, the service provider device 30 performs a process of confirming the user of the service app with the service app unit 12 in response to the service user confirmation request from the inter-application cooperation device 40. Specifically, the service provider device 30 may perform a process of confirming the user with the service app unit 12 based on the service user ID included in the service user confirmation request. For example, the service provider device 30 may acquire attribute information of the user identified by the service user ID and transmit the attribute information to the terminal 10. The service app unit 12 matches the attribute information with the user information input to the service app unit 12. The user information may be, for example, at least one of knowledge information (e.g., user ID, password), biometric information (e.g., captured image of the user, fingerprint, etc.), and possession information (e.g., SIM card number stored in the terminal 10) input to the service app. The user information may be input on an input screen that the service app unit 12 displays on the display unit, may be captured by an imaging unit activated by the service app unit 12, or may be acquired through the service app unit 12. If the service application unit 12 finds a match between the attribute information and the user information, the operation proceeds to step S208, and if the match does not find a match, the operation may end.

In step S208, the inter-application cooperation device 40 receives service user confirmation information based on the result of the confirmation process in step S207 from the service provider device 30. The service user confirmation information may include at least one of the result of the user confirmation in step S207 and attribute information of the user.

In step S209, the inter-application cooperation device 40 verifies the identity of the user of the payment/authentication application and the user of the service application based on the payment/authentication user confirmation information received in step S205 and the service user confirmation information received in step S208. For example, if a positive confirmation result is input by the user in steps S204 and S207 and the users match, the inter-application cooperation device 40 may determine that the user of the payment/authentication application and the user of the service application are the same.

In step S210, if the identity of the payment/authentication app user and the service app user is verified, the inter-application linkage device 40 transmits a token/certificate issuance request to the payment/authentication business device 20. The issuance request in step S210 may be based on at least one of the payment/authentication app information, service app information, and token/certificate information included in the issuance request in step S202 (and may include at least one of the payment/authentication app information, service app information, and token/certificate information). For example, the issuance request in step S210 may request issuance of either a token or an electronic certificate, or both a token and an electronic certificate, based on type information included in the issuance request in step S202.

In step S211, the inter-application linkage device 40 receives the token/certificate sent by the payment/authentication business device 20 in response to the issuance request in step S210.

In step S212, the inter-application cooperation device 40 provides the token/certificate received from the payment/authentication business device 20 in step S211 to the service application unit 12. The service application unit 12 receives the token/certificate via the transmission/reception unit 103.

In step S213, the service application unit 12 provides a service to the user using the token/certificate provided by the inter-application cooperation device 40 in step S212. For example, the service application unit 12 may provide the user with a service that requires payment by performing a process related to payment with the payment/authentication provider device 20 using the provided token. The service application unit 12 may also provide the user with a service that requires authentication by performing a process related to authentication with the payment/authentication provider device 20 using the provided electronic certificate.

Figure 6 is a diagram showing another example of the operation of the information processing system 1 according to this embodiment. Figure 6 illustrates a case in which the service application unit 12 of the terminal 10 accepts a request to issue a token/certificate for a payment/authentication application for itself. Note that Figure 6 focuses on the differences from Figure 5, and similar points will not be described repeatedly.

As shown in FIG. 6, in step S301, the service application unit 12 receives a request for issuing a token/certificate for a payment/authentication application to the service application unit 12, the request being input by the user via the input/output unit 104.

In step S302, the service application unit 12 transmits the issuance request acquired in step S301 to the inter-application cooperation device 40 via the transmission/reception unit 103. Steps S303 to S313 are similar to steps S203 to S213 in FIG. 5.

As described above, in the information processing system 1 according to this embodiment, when the use of a payment function and/or authentication function is required when a service is provided by a service app, the identity of the user of the payment/authentication app and the user of the service app is verified, and then a token/certificate for the payment/authentication app is issued to the service app from the payment/authentication business device 20. Therefore, while ensuring a certain level of security, it is possible to link tokens/certificates between the payment/authentication app and the service app, thereby contributing to the satisfaction of users who use the service app.

Other Embodiments
The above-described embodiments are intended to facilitate understanding of the present invention, and are not intended to limit the present invention. The elements of the embodiments, as well as their arrangements, materials, conditions, shapes, sizes, etc., are not limited to those shown as examples and can be changed as appropriate. In addition, configurations shown in different embodiments can be partially substituted or combined with each other.

1...information processing system, 10...terminal, 20...payment/authentication provider device, 30...service provider device, 40...inter-application linkage device, 50...network, 11...authentication application unit, 12...service application unit, 41...acquisition unit, 42...user confirmation unit, 43...verification unit, 44...provision unit, 111...issuance request unit, 112...user confirmation unit, 121...issuance request unit, 122...user confirmation unit, 123...acquisition unit, 124...service unit, 101...processor, 102...storage unit, 103...transmission/reception unit, 104...input/output unit,

Claims (6)

Computer,
an acquisition unit that acquires an issuance request for requesting that a token and/or a digital certificate used in a first application provided by a first business be issued to a second application provided by a second business;
a verification unit that verifies the identity of the user of the first application and the user of the second application in response to the issuance request;
a providing unit that receives the token and/or the electronic certificate from a first business operator device that is an information processing device of the first business operator based on a result of the verification of the identity, and provides the token and/or the electronic certificate to the second application, the token and/or the electronic certificate being issued by the first business operator device, based on the result of the verification of the identity;
An information processing program that functions as a a user confirmation unit that, in response to the issuance request, acquires first confirmation information related to a user of the first application from the first business operator device , and acquires second confirmation information related to the user of the second application from a second business operator device that is an information processing device of the second business operator;
The verification unit verifies the identity based on the first confirmation information and the second confirmation information.
The information processing program according to claim 1. the providing unit, when the identity is verified by the verifying unit, requests the first business operator device to issue the token and/or the electronic certificate, receives the token and/or the electronic certificate issued by the first business operator device in response to the request from the first business operator device , and provides the token and/or the electronic certificate to the second application.
3. The information processing program according to claim 2. The acquisition unit acquires the issuance request from the first application or the second application.
4. The information processing program according to claim 1. an acquisition unit that acquires an issuance request for requesting that a token and/or a digital certificate used in a first application provided by a first business be issued to a second application provided by a second business;
a verification unit that verifies the identity of the user of the first application and the user of the second application in response to the issuance request;
a providing unit that receives the token and/or the electronic certificate from a first business device that is an information processing device of the first business based on a result of the verification of the identity, and provides the token and/or the electronic certificate to the second application, the token and/or the electronic certificate being issued by the first business device ;
An information processing device comprising: obtaining an issuance request for issuing a token and/or a digital certificate for use in a first application provided by a first business operator to a second application provided by a second business operator;
In response to the issuance request, verifying the identity of the first application user and the second application user;
receiving , based on a result of the verification of the identity, the token and/or the electronic certificate issued by a first business device, which is an information processing device of the first business device , from the first business device and providing the token and/or the electronic certificate to the second application;
The information processing method of the information processing device having the above configuration.

Images