JP7598349B2 - PROGRAM, INFORMATION PROCESSING APPARATUS, AND INFORMATION PROCESSING METHOD - Google Patents

Description

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

When a transaction or service is provided, some verification of the user may be performed, such as whether the user is the authentic user or not, and the reliability of the user. Patent Document 1 discloses a technology for verifying the user in electronic commerce by matching fingerprints, voice, etc.

JP 2001-043276 A

Building a mechanism to verify users for each system used for transactions or to provide services would impose a heavy burden on system construction.

The present invention aims to provide technology that reduces the burden of building a system that has a mechanism for verifying users.

A program according to one embodiment causes a computer to execute an information processing method including receiving, via a communication unit, authentication information of a user input via a terminal device to request the provision of a first service by a first operator to the user, and transmitting, via the communication unit, to a second server device that provides an interface for the use of the first service, a result of confirmation regarding the user based on a comparison result between attribute information of the user indicated by the authentication information and attribute information of the user stored in a first server device for the use of a second service provided by a second operator.

An information processing device according to one embodiment has a control unit and a communication unit, and the control unit receives, via the communication unit, authentication information of the user input via a terminal device to request the provision of a first service by a first operator to the user, and transmits, via the communication unit, a result of confirmation regarding the user based on a comparison between attribute information of the user indicated by the authentication information and attribute information of the user stored in a first server device for use of a second service provided by a second operator, to a second server device that provides an interface for use of the first service.

An information processing method according to one embodiment includes receiving, via a communication unit, authentication information of a user input via a terminal device to request the provision of a first service by a first operator to the user, and transmitting, via the communication unit, a result of confirmation regarding the user based on a comparison result between attribute information of the user indicated by the authentication information and attribute information of the user stored in a first server device for use of a second service provided by a second operator, to a second server device providing an interface for use of the first service.

The present invention provides a technology that reduces the burden of building a system that has a mechanism for verifying users.

FIG. 1 is a conceptual diagram for explaining an overview of an exemplary system in one embodiment. FIG. 1 is a conceptual diagram for explaining an overview of an exemplary system in one embodiment. FIG. 1 is a conceptual diagram for explaining an overview of an exemplary system in one embodiment. FIG. 1 is a conceptual diagram for explaining an overview of an exemplary system in one embodiment. FIG. 1 is a conceptual diagram illustrating an example of a system configuration according to an embodiment. FIG. 2 is a block diagram illustrating an example of a functional configuration of a server device according to an embodiment. FIG. 1 is a sequence diagram for explaining an overview of an exemplary process performed by a system in one embodiment. FIG. 2 is a block diagram illustrating an example of a functional configuration of a control unit according to an embodiment. FIG. 2 is a sequence diagram illustrating an example of a hardware configuration of a computer according to an embodiment.

A system according to one embodiment of the present invention will be described in detail with reference to the drawings. However, the embodiment described below is merely an example, and is not intended to exclude the application of various modifications or techniques not specifically described below. In other words, the present invention can be implemented by modifying it in various ways or combining the various embodiments without departing from the spirit of the invention. In addition, in the description of the drawings below, identical or similar parts are denoted by the same or similar reference numerals.

[System Overview]
An overview of an exemplary system according to this embodiment and a use example will be described with reference to FIG. 1. The system 1 has an interface function (service interface function) for using a service provided by another system (in the example of FIG. 1, an open banking service provided by a bank system) and a function (external trust function) for performing user-related confirmation using user attribute information stored in the other system. The user-related confirmation may include, for example, confirmation that the user is the person in question or is trustworthy. In this embodiment, the user-related confirmation is also referred to as user confirmation.

Open banking services are services that enable operations such as referencing bank account information or transferring funds within a bank account via an API (Application Programming Interface). The external trust function enables user verification using user attribute information registered in the bank system.

The service interface function and the external trust function of the system 1 function as follows, for example. First, a user who wishes to transfer funds in a bank account performs user authentication by inputting a user ID and a password through the system of a customer front provider, which is a payment service provider or a funds transfer service provider, and then performs an instruction to transfer funds in the account (account instruction) (S11). The service interface function of the system 1 receives the account instruction through the system of the customer front provider (S12) and transmits a user confirmation request to the external trust function (S13). In response to receiving the user confirmation request, the external trust function of the system 1 presents the user with a user interface that accepts authentication information for user confirmation, and receives the authentication information from the user (S14). The external trust function of the system 1 compares the attribute information indicated by the authentication information received from the user (or the attribute information obtained from the database of the system 1 based on the authentication information) with the user attribute information stored in the bank system (S15). The external trust function performs user confirmation through the comparison. The result of the user confirmation may be stored as a confirmation history in the database of the system 1. The external trust function transmits the result of the user authentication to the service interface function (S16). The result of the user authentication may be transmitted in the form of an electronic certificate (or an electronic signature; the same applies to the following description). In response to receiving a result indicating that the user authentication was successful in S16, the service interface function transmits an instruction corresponding to the account instruction received in S12 to the bank system (S17), whereby the account instruction is executed in the bank system.

Thus, according to system 1 of this embodiment, even if the bank system itself does not have a user verification function, the bank system can perform the user verification in order to provide open banking services to users. In other words, by using the already-constructed system 1, the bank can reduce the construction load of a system having the user verification mechanism while enabling user verification to be performed.

In FIG. 1, an account instruction is sent from the customer front provider to the service interface function (S12), and a user verification request is sent from the service interface function to the external trust function, but this flow is not limited to this. For example, a user verification request may be sent from the customer front provider to the external trust function before the account instruction is sent from the customer front provider to the service interface function.

With reference to FIG. 1, an example has been described in which system 1 works in conjunction with a bank system to provide an interface function for using open banking services, but this is not limited thereto, and system 1 may also work in conjunction with the systems of other financial institutions (financial business operators) including card operators or money transfer operators, etc., to provide an interface function for using other financial transaction services.

With reference to Figures 2 to 4, an example will be described in which the system 1 according to this embodiment provides an interface function for using services other than financial services, such as open banking services.

The system 1 shown in FIG. 2 has a service interface function and an external trust function, similar to the example shown in FIG. 1. The service interface function functions as an interface for executing a process for establishing some kind of contract with a user through the system (i.e., processing of a contract service). The establishment of the contract may be, for example, the establishment of a credit card subscription contract between a user and a credit card company, or the establishment of a gym membership contract between a user and a gym company.

In the example shown in FIG. 2, first, a user who wishes to conclude a contract with a certain business performs user authentication via the customer front provider's system, and then requests a contract application (S21). The service interface function of system 1 receives the contract application via the customer front provider's system (S22) and transmits a user verification request to the external trust function (S13). Thereafter, as in the example described with reference to FIG. 1, the external trust function performs the processes of receiving authentication information (S14), matching attributes (S15), and transmitting the verification result (S16). In response to receiving a result indicating that the user verification was successful in S16, the service interface function executes a process for concluding a contract corresponding to the contract application received in S22 (S27). The process for concluding a contract may include a process of signing a contract, or a process of registering the contract applicant in a database as a contractor.

In the example shown in Figure 2, a business (e.g., a credit card business or a sports gym business) can use user attribute information registered in another business's system, such as a bank system, to verify the user while ensuring authenticity and auditability.

The system 1 shown in FIG. 3 has a service interface function and an external trust function, similar to the example shown in FIG. 1. The service interface function functions as an interface for a digital data provider (an entity that provides digital data) to execute a process (i.e., a rights management service process) for transferring or setting rights (e.g., ownership) related to digital data to a user. The digital data may be, for example, video content or music content.

In the example shown in FIG. 3, first, a user who wishes to acquire ownership of digital data provided by a digital data provider performs user authentication via the system of the digital data provider, and then requests rights registration (S31). The service interface function of the system 1 receives the request for rights registration via the system of the customer front provider (S32), and transmits a user verification request to the external trust function (S13). Thereafter, as in the example described with reference to FIG. 1, the external trust function performs the processes of receiving authentication information (S14), attribute matching (S15), and transmitting the verification result (S16). Also, in the example shown in FIG. 3, in addition to receiving authentication information for user verification of the user who wishes to acquire ownership of the digital data in S14, the external trust function receives authentication information from the digital data provider via the terminal device for user verification with the digital data provider as the user. In S15, the external trust function compares the attribute information of the digital data provider indicated by the authentication information with the corresponding attribute information received from the bank system. The external trust function performs user verification of the digital data provider through the comparison. The external trust function transmits the results of the two user confirmations to the service interface function. In response to receiving a result indicating that the two user confirmations were successful in S16, the service interface function executes a process for registering the ownership of the digital data corresponding to the right registration request received in S32 to the corresponding user (S37). Note that the digital data provider and the business (digital data right management business) that manages the transfer of ownership of the digital data or the registration of the settings may be the same or different.

According to the example shown in FIG. 3, a digital data provider or a digital data rights management business can use user attribute information registered in the system of another business, such as a bank system, to verify the user while ensuring authenticity and auditability. In other words, according to this embodiment, it is possible to perform processes such as user verification or registration of transfer or setting of rights related to digital data using a simple mechanism without using technologies such as blockchain technology or NFT (Non-Fungible Token).

The system 1 shown in FIG. 4 has a service interface function and an external trust function, similar to the example shown in FIG. 1. The service interface function functions as an interface for executing processing for recording transaction history between multiple parties, including individuals or businesses (i.e., processing of transaction history service). The above transactions include, for example, transactions of objects for which traceability is required. The objects for which traceability is required may be, for example, electric vehicle batteries (EV batteries). The service interface function is provided, for example, by an institution that provides traceability services. The customer front provider is also, for example, an institution that provides traceability services, but may also be another institution or business.

In the example shown in FIG. 4, first, a business (user) such as an automobile factory, an automobile parts store, a car dealer, or a used car dealer, which performs processes such as installation, collection, and repair of an EV battery, which is an object requiring traceability, performs user authentication via the business's system, and then requests information registration regarding the collection (transfer) of the EV battery (S41). The service interface function of the system 1 receives the request for information registration of the transfer via the customer front provider's system (S42), and transmits a business (user) confirmation request to the external trust function (S13). Thereafter, as in the example described with reference to FIG. 1, the external trust function performs processes of receiving authentication information (S14), matching attributes (S15), and transmitting the confirmation result (S16). In response to receiving a result indicating that the user confirmation was successful in S16, the service interface function executes a process for registering information on the transfer of the EV battery corresponding to the request for information registration of the transfer received in S42 (S47). The process for registering the transfer information includes, for example, storing information indicating that the ownership of the EV battery has been transferred from the user to an auto parts store in a system that tracks the ownership of the EV battery.

The system for tracking ownership of EV batteries may store and manage information regarding the purchase, installation, trade-in, resale, disposal, or repair of EV batteries. Furthermore, the above-mentioned automobile factories, automobile parts stores, or used car dealerships of EV batteries are businesses that participate in the tracking activities by the system for tracking ownership of EV batteries, and may include other businesses. Furthermore, users of system 1 may include end users of EV batteries in addition to businesses such as automobile factories, automobile parts stores, car dealerships, or used car dealerships.

According to the example shown in FIG. 4, a person participating in an activity of tracking a certain object or an institution managing the activity can use user attribute information registered in the system of another business operator, such as a bank system, to perform user verification while ensuring authenticity and auditability. In other words, according to this embodiment, user verification or object traceability can be achieved with a simple mechanism without using technologies such as blockchain technology or NFT (Non-Fungible Token).

[System Configuration]
An example of the configuration of the system 1 in this embodiment will be described with reference to Fig. 5. The system 1 includes server devices 10 (10a, 10b) and a terminal device 20. The devices are configured to be able to communicate with each other via a network N.

The server device 10 is an information processing device such as a server computer. The server device 10 may be configured as one information processing device (or computer; the same applies below), or may be configured as multiple information processing devices using cloud computing technology or distributed computing technology, etc.

The terminal device 20 is configured as an information processing device such as a personal computer, a mobile device, or a dedicated terminal. The terminal device 20 may be configured to be able to communicate with a server device 10 configured using cloud computing technology.

The network N is composed of a wireless network or a wired network. The network N may include any network, such as the Internet, a mobile communication network, or a LAN (Local Area Network).

System 1 communicates with and processes external systems or devices. For example, system 1 may communicate with and process a bank system 2 or a customer front provider's server device 3 (customer front provider's system), but the external systems or devices with which system 1 communicates are not limited to these.

In the example shown in FIG. 5, the system 1 is configured to include two server devices 10 and one terminal device 20, but the number of devices included in the system 1 is not limited to this, and the system 1 may include any number of devices. For example, the system 1 may include three or more server devices 10, or may include two or more terminal devices 20. Note that in the following description, at least a portion of the processing described as processing by either the server device 10 or the terminal device 20 may be executed by the other device. For example, a portion of the processing described as processing by the server device 10 may be executed by the terminal device 20, and a portion of the processing described as processing by the terminal device 20 may be executed by the server device 10.

[Functional configuration]
6, the functions of the server device 10 will be described. The server device 10 (10a, 10b) has, as main functional components, a communication unit 11 (11a, 11b), a database 12 (12a, 12b), and a control unit 13 (13a, 13b).

The server device 10 may have other functional configurations possessed by information processing devices such as general information processing devices or dedicated devices. The functional configuration of the server device 10 is realized by cooperation between a computer program (software) and hardware, for example, when a control device such as a CPU (Central Processing Unit) possessed by the server device 10 reads and executes a computer program stored in a storage device.

The communication unit 11 receives and transmits various information through communication with an external device. The database 12 stores various information including information received by the communication unit 11, information required for processing by the server device 10, or information generated by the server device 10. The control unit 13 controls the processing of various functions executed by the server device 10.

[Processing flow]
7, an example of a processing flow in the system 1, the bank system 2, and the server device 3 will be described. Each processing step described below is realized by cooperation between a computer program (software) and hardware, for example, when a control unit of the server device 10 and the terminal device 20 reads and executes a computer program stored in a storage unit.

In the following description, it is assumed that server device 10a has the above-mentioned service interface function and server device 10b has the above-mentioned external trust function, but this is not limited to this.

First, the terminal device 20 displays, for example, a web page provided by the server device 3 on the display unit, and transmits a user authentication request including a user ID and password to the server device 3 in response to a user input on the web page (S71). The server device 3 authenticates the user based on the received user ID and password (S72), and transmits the result of the user authentication to the terminal device 20.

If the user authentication in step S72 is successful, the terminal device 20 transmits a service provision request to the server device 3 in response to an operation input by the user (S73). The service (first service) may be, for example, the above-mentioned open banking service, contract service, rights management service, or transaction history service.

The service provision request received by server device 3 is sent to server device 10a (S74) and then to server device 10b (S75).

Then, the display on the display unit of the terminal device 20 is redirected from the web page provided by the server device 3 to the web page provided by the server device 10b. In response to the user's operation input on the redirected web page displayed on the display unit of the terminal device 20, the terminal device 20 transmits the user confirmation request to the server device 10b (S76).

The method of sending the user confirmation request to the server device 10b is not limited to a method using redirection, and any method can be used. For example, the user confirmation request may be sent from the terminal device 20 to the server device 10a in response to a user operation, and then sent from the server device 10a to the server device 10b.

In response to receiving the user verification request in step S76, the server device 10b requests the bank system 2 to transmit attribute information of the user (S77). In response to receiving the request, the bank system 2 transmits the corresponding user attribute information to the server device 10b (S78). The user attribute information may include, for example, at least a portion of the user's bank account number, customer name (name, corporate name, trade name, etc.), family name, employee name, address, location, telephone number, email address, date of birth, gender, etc.

The server device 10b compares (or collates) the user attribute information included in the user confirmation request received in step S76 (or the user attribute information acquired from the database of the server device 10b in response to the receipt of the user confirmation request) with the user attribute information received from the bank system 2 in step S78 (S79). The comparison (comparison or collation) may be performed by the bank system 2. That is, the user attribute information included in the user confirmation request received in step S76 may be transmitted to the bank system 2, and the bank system 2 may compare the attribute information received from the server device 10b with the attribute information stored in the bank system 2 and transmit the comparison result to the server device 10b. If it is determined that the attribute information matches as a result of the collation, the server device 10b transmits a user confirmation result indicating that the user confirmation was successful to the server device 10a (S80). Note that in step S80, the server device 10b may generate an electronic certificate indicating the user confirmation result and transmit the electronic certificate to the server device 10a.

In response to receiving the user confirmation result indicating that the user confirmation was successful in step S80, the server device 10a calls the service corresponding to the service provision request received in step S74 (S81). For example, if the service is an open banking service, the server device 10a may execute an API call to the bank system 2 for an operation such as referencing bank account information or transferring funds in the bank account.

Among the processes shown in FIG. 7, at least a part of the processes performed by the server device 10b is embodied as processes performed by the communication unit 11b, the database 12b, and the control unit 13b as follows. That is, the communication unit 11b receives a user confirmation request including the user's authentication information input via the terminal device 20 to request the provision of the first service to the user (S76). The first service provided by the first business operator may be, for example, an open banking service provided by the bank, a credit card contract service (contract act) provided by a credit card business operator, a rights management service provided by a digital data rights management business operator, or a transaction history management service provided by a transaction history management business operator. After that, the control unit 13b transmits the result of user confirmation based on the result of matching between the user's attribute information indicated by the authentication information received by the communication unit 11b and the user's attribute information stored in the server device (first server device) of the bank system 2 for the use of the second service provided by a business operator (second business operator) to the server device 10a providing an interface for the use of the first service via the communication unit 11b (S80).

The authentication information may be received via communication unit 11b after the user has been successfully authenticated by a customer front provider (third business operator) that provides the first service by way of an intermediary.

The customer front provider (third business) may be, for example, a payment service provider or a funds transfer service provider. A funds transfer service provider is, for example, a business that provides a service of transferring funds between bank accounts in response to a request from a user.

The user attribute information stored in the first server device for use of the second service provided by the second operator is, for example, but not limited to, user information of a bank service (second service) provided by a bank (second operator). The user attribute information stored for use of the second service provided by the second operator may be, for example, user information of a credit card service (second service) provided by a credit card operator (second operator), or user information of a mobile phone service (second service) provided by a communication carrier (second operator). In addition, the user attribute information stored for use of the second service provided by the second operator may be, for example, user attribute information stored in a ledger of a public institution (for example, user attribute information stored in a server device of an administrative institution that provides administrative services such as a local government or the government).

The user attribute information indicated by the authentication information received by the communication unit 11b may be included in the authentication information, or may be attribute information previously stored in the database 12b as attribute information corresponding to the authentication information.

As described above, according to the system 1 of this embodiment, even if the bank system 2 itself does not have a user verification function, the bank system 2 can perform the user verification in order to provide the open banking service to the user. In other words, by using the already-constructed system 1, the bank can reduce the construction load of a system having the user verification mechanism while enabling user verification to be performed.

Regarding the transmission of the user confirmation result from server device 10b to server device 10a in step S80, control unit 13b may generate an electronic certificate indicating the user confirmation result, and communication unit 11b may transmit the electronic certificate to server device 10a.

The first business through which the service provision is mediated by the customer front provider (third business) may be the same business as the second business that provides the user's attribute information in step S78 for the purpose of matching the attribute information, or it may be a different business.

For example, in the above, the first entity is a financial institution (including, for example, a bank, a credit card company, or a funds transfer company), a digital data rights management company, or a transaction history management company, and the second entity is a bank, a credit card company, a communications carrier, or a public institution.

[Detailed function configuration]
Examples of various functions executed by the control unit 13b of the server device 10b will be described in more detail with reference to Fig. 8. As shown in Fig. 8, the functions executed by the control unit 13b include, for example, an attribute inquiry function 131, an electronic signature/electronic certificate issuance function 132, a function for service providers 133, and a notarization/audit function 134. The control unit 13b may further execute functions other than those described above, or may not execute some of the functions described above.

(A) Attribute inquiry function 131
The attribute inquiry function 131 has functions related to financial institution information inquiry, financial institution information master, user identity verification, and user authentication, which will be described next.

(A-1) Financial Institution Information Inquiry This is a function for inquiring of financial institutions (such as banks or card companies) about attribute information on users (whether individuals or corporations) who are customers of the financial institution. For example, the control unit 13b may call an API for attribute information inquiry provided by the financial institution to obtain the user's attribute information. The user's attribute information may include, for example, at least a part of the user's bank account number, customer name (name, corporate name, trade name, etc.), family name, employee name, address, location, telephone number, email address, date of birth, gender, etc. In order to call the API for attribute information inquiry, a part of the above attribute information may be used as a key, or another identifier may be used.

(A-2) Financial Institution Information Master This is a function to acquire user attribute information stored in a financial institution, and store and manage the information as master information of the financial institution's user attribute information in the database 12b of the server device 10b. The financial institution's user attribute information is used for the above-mentioned collation of attribute information. Acquisition of user attribute information stored in a financial institution may be performed at a predetermined timing via a dedicated line or the like.

(A-3) User Identity Verification This is a function for performing identity verification of a user. In this embodiment, identity verification may be identity verification under the Criminal Proceeds Transfer Prevention Act. The control unit 13b compares the user's attribute information included in the identity verification request received from the server device 10a (or the user's attribute information acquired from the database of the server device 10b in response to the receipt of the identity verification request) with the user's attribute information received from the financial institution. If the result of the comparison shows that the attribute information matches or there is no contradiction between the two, the control unit 13b judges that the user's identity verification has been successful. If the attribute information does not match or there is a contradiction between the two, the user's identity verification is judged to have failed. For the identity verification of a user, eKYC may be performed, or identity verification may be performed using a digital copy of an official certificate (e.g., a driver's license or a passport). The identity verification of a user may be performed each time a service provision request is received from the terminal device 20 via a customer front provider, or may be performed at another timing.

(A-4) User Authentication This is a function for performing user authentication. The authentication of the user may be performed, for example, after (A-3) user identity verification. The authentication of the user may be based on a user ID and a password, may be two-factor authentication, may be FIDO (Fast Identity Online) authentication, or may be another authentication method.

(B) Digital signature/digital certificate issuing function 132
The digital signature/digital certificate issuing function 132 has the functions of accepting a digital certificate issuance request, querying attributes and obtaining the results, issuing a digital signature/digital certificate, and recording the signature/certificate history, which will be described next.

(B-1) Receiving a request for issuing an electronic certificate This is a function for receiving a request for issuing an electronic signature and an electronic certificate from the above-mentioned service interface function (server device 10a). For example, the control unit 13b receives an electronic certificate issuance request indicating the result of the above-mentioned user confirmation via the communication unit 11b. The control unit 13b may also receive a request for issuing an electronic certificate for information about the business providing the service (e.g., connection information, business information, etc.). The electronic certificate may include information about the target financial institution (if it is necessary to identify the financial institution), an electronic signature, or a timestamp.

(B-2) Attribute Inquiry/Result Acquisition This is a function for calling the attribute inquiry function 131 in response to the above-mentioned digital certificate issuance request acceptance, and obtaining the result of matching the user's attribute information by the attribute inquiry function 131.

(B-3) Issuance of electronic signature and electronic certificate If the result of matching the user's attribute information is successful, an electronic signature or electronic certificate indicating the user verification result is generated. The electronic signature or electronic certificate is generated in any format or by any method.

(B-4) Signature/Certificate History Recording This is a function for storing the above-mentioned user confirmation result, electronic signature or electronic certificate in the database 12b.

(C) Function for Service Providers 133
The service provider function 133 stores information about the service provider (e.g., a provider of an open banking service) in advance in the database 12b, and when a service provision request is received, determines whether the service provision request is legitimate based on the information.

Furthermore, the service provider function 133 provides the electronic signature or electronic certificate issued as described above to the service provider (or the server device 10a).

(D) Notarization and audit function 134
The notarization and audit function 134 has a function for verifying the electronic signature or electronic certificate issued and provided as described above. Specifically, by providing a verification tool such as a public key to the service provider, it becomes possible to support the service provider in verifying the electronic signature or electronic certificate.

The notarization and audit function 134 also functions as an interface that accepts a request to inquire about the user verification result, electronic signature, or electronic certificate stored in the database 12b. In response to the inquiry request, the user verification result, electronic signature, or electronic certificate stored in the database 12b is inquired.

[Hardware configuration]
9, an example of a hardware configuration of a computer 800 will be described in the case where the server device 10 and the terminal device 20 are realized by the computer 800. Note that the functions of each device can be realized by dividing them into a plurality of devices.

As shown in FIG. 9, the computer 800 includes a processor 801, a memory 803, a storage device 805, an input I/F unit 807, a data I/F unit 809, a communication I/F unit 811, and a display device 813. Although not shown, the computer 800 may also include various actuators (e.g., motors), a positioning module (e.g., a GPS module), or various sensors.

The processor 801 is a control unit that controls various processes in the computer 800 by executing programs stored in the memory 803.

The memory 803 is a storage medium such as a RAM (Random Access Memory). The memory 803 temporarily stores the program code of the program executed by the processor 801 and data required when the program is executed.

The storage device 805 is a non-volatile storage medium such as a hard disk drive (HDD) or a flash memory. The storage device 805 stores an operating system and various programs for implementing the above-mentioned configurations. The storage device 805 may be the same device as the memory 803.

The input I/F unit 807 is a device for receiving input from a user. Specific examples of the input I/F unit 807 include a keyboard, a mouse, a touch panel, various sensors, and a wearable device. The input I/F unit 807 may be connected to the computer 800 via an interface such as a USB (Universal Serial Bus).

The data I/F unit 809 is a device for inputting data from outside the computer 800. A specific example of the data I/F unit 809 is a drive device for reading data stored in various storage media. The data I/F unit 809 may be provided outside the computer 800. In that case, the data I/F unit 809 is connected to the computer 800 via an interface such as a USB.

The communication I/F unit 811 is a device for performing data communication via the Internet N, either wired or wirelessly, with devices external to the computer 800. The communication I/F unit 811 may be provided external to the computer 800. In that case, the communication I/F unit 811 is connected to the computer 800 via an interface such as a USB.

The display device 813 is a device for displaying various types of information. Specific examples of the display device 813 include a liquid crystal display, an organic EL (Electro-Luminescence) display, a display of a wearable device, and the like. The display device 813 may be provided outside the computer 800. In that case, the display device 813 is connected to the computer 800 via, for example, a display cable. In addition, when a touch panel is used as the input I/F unit 807, the display device 813 can be configured as an integral part of the input I/F unit 807.

[Modification]
The program for implementing the system 1 (or the server device 10, or the terminal device 20) in the above embodiment can be installed or loaded into a computer through various recording media such as optical disks such as CD-ROMs, magnetic disks, and semiconductor memories, or by downloading via a communication network, etc.

The present invention is not limited to the above-described embodiment, and can be embodied in various other forms without departing from the spirit of the present invention. The above-described embodiment is merely illustrative in all respects and should not be interpreted as being restrictive.

Reference Signs List 1 System 10 Server device 11 Communication unit 12 Database 13 Control unit 20 Terminal device 800 Computer

Claims (9)

On the computer,
receiving, via a communication unit, authentication information of a user input via a terminal device for requesting provision of a first service by a first carrier to the user;
transmitting, via the communication unit, a confirmation result regarding the user based on a comparison result between attribute information of the user indicated by the authentication information and attribute information of the user stored in a first server device for use of a second service provided by a second operator, to a second server device providing an interface for use of the first service;
Including,
The authentication information is received via the communication unit after the user is successfully authenticated by a third service provider that provides the first service provided by the first service provider.
A program for executing an information processing method. The program according to claim 1, wherein transmitting the confirmation result includes transmitting an electronic certificate indicating the confirmation result to the second server device via the communication unit. The service provided by the first business includes an open banking service;
the request includes a bank account transfer instruction;
The program according to claim 1. The program according to claim 1, wherein the first operator is the same operator as the second operator. The program according to claim 1, wherein the first business entity is a financial institution, a digital data rights verification service provider, or an electric vehicle battery tracking and management organization. The program according to claim 1, wherein the third business is a money transfer service business. The program according to claim 1, wherein the second business is a bank, a credit card business, a telecommunications carrier, or a public institution. An information processing device having a control unit and a communication unit,
receiving, via the communication unit, authentication information of the user input via a terminal device for requesting provision of a first service by a first carrier to the user;
transmitting, via the communication unit, a confirmation result regarding the user based on a comparison result between attribute information of the user indicated by the authentication information and attribute information of the user stored in a first server device for use of a second service provided by a second operator, to a second server device providing an interface for use of the first service ;
The authentication information is received via the communication unit after the user is successfully authenticated by a third service provider that provides the first service provided by the first service provider.
Information processing device. The computer
receiving, via a communication unit, authentication information of a user input via a terminal device for requesting provision of a first service by a first carrier to the user;
transmitting, via the communication unit, a confirmation result regarding the user based on a comparison result between attribute information of the user indicated by the authentication information and attribute information of the user stored in a first server device for use of a second service provided by a second operator, to a second server device providing an interface for use of the first service ;
The authentication information is received via the communication unit after the user is successfully authenticated by a third service provider that provides the first service provided by the first service provider.
Information processing methods.