JP7399672B2 - financial institution system - Google Patents

Description

Application of Article 30, Paragraph 2 of the Patent Act SBI Sumishin Net Bank was assigned the right to obtain a patent for the invention by the inventors Hiroyoshi Fujiwara and Yusuke Yakubo at 1:00 p.m. on October 5, 2018. Co., Ltd. ordered its employees to send VeriTrans Co., Ltd. the specifications for the financial institution system invented by Hiroyoshi Fujiwara and Yusuke Yakubo by e-mail at 7:20 p.m. on October 5, 2018. that it was sent.

The present invention relates to a financial institution system using API (Application Programming Interface).

In recent years, the field of FinTech, which combines information technology and financial services, such as transferring money using smartphones, has been attracting attention. In the field of FinTech, API (Application Programming Interface) is known as a program that allows parties other than banks to connect to a bank's system and use its functions. Open APIs are known that provide APIs to banks and authorize access to banking systems based on user consent.

Patent Document 1 discloses an example of an open API system that allows a user to grant access authority to a banking system to a FinTech provider in order to access the user's bank account information and provide the user with various services. An invention has been proposed that improves the method of issuing access tokens for accessing the banking system employed in the above system.

JP2018-49667A

Using open APIs, banks may provide APIs to businesses to provide financial services. This financial service includes, for example, a product sales/service providing company that sells products or provides services to users such as consumers, and the purchase price of the product when the user purchases a product or receives a service. There is a system in which the user makes a payment (i.e., settlement) using a bank account held at the bank.

In this case, the bank must identify what kind of financial services (e.g., instant account transfer, balance inquiry, transfer inquiry, etc.) each product sales/service provider provides, and the API that specifies each financial service. For each product sales and service provider, it becomes necessary to create a structure for each financial service provided, which places a heavy burden on banks.

This invention is intended for financial institutions that provide various financial services such as banks, securities companies, insurance companies, virtual currency exchange operators, etc., when they provide financial services using APIs. The purpose is to propose a financial institution system that reduces the burden on the financial institution system side, which institutions manage in order to provide financial services.

[1]
A product/service provider that sells products or provides services to users such as consumers receives an API from a financial institution and, based on the user's authorization, uses the user account information held by the financial institution. A financial institution system used to execute financial service functions using the API,
An intermediate handler ID issued by the financial institution system as an identifier for identifying the intermediate handler for each intermediate handler intervening between the product/service provider and the financial institution; The combination of the financial service function by the API and the product/service provider that the financial institution system has received a request for execution from the product/service provider, which is issued in association with each intermediate handler ID. A financial institution system equipped with scope information, which is an identifying identifier, and an intermediate handler information management processing unit that manages scope information.

[2]
A product/service provider that sells products or provides services to users such as consumers receives an API from a financial institution and, based on the user's authorization, uses the user account information held by the financial institution. A computer program used to execute a financial service function using the API,
computer,
For each intermediate handler intervening between the product/service provider and the financial institution, an intermediate handler ID issued by a financial institution system managed by the financial institution as an identifier for identifying the intermediate handler. , the financial service function by the API and the product/service that the financial institution system has received a request for execution from the product/service provider, which the financial institution system has issued in association with each intermediate handler ID; A computer program that functions as an intermediate handler information management processing unit that manages scope information, which is an identifier that specifies a combination with a provider.

[3]
A product/service provider that sells products or provides services to users such as consumers receives an API from a financial institution and, based on the user's authorization, uses the user account information held by the financial institution. In contrast, in a financial institution system used to execute a financial service function using the API, the financial service function using the API that the financial institution system has received a request for execution from the product/service provider, and the product/service A scope issuance method that issues scope information that is an identifier that identifies a combination with a provider,
For each intermediate handler intervening between the product/service provider and the financial institution, the intermediate handler may receive an intermediate handler ID issued by the financial institution system as an identifier for identifying the intermediate handler. An intermediate handler ID issuance processing step for issuing an intermediate handler ID to the intermediate handler terminal to be used;
A scope issuance method, comprising: a scope information issuance processing step in which the financial institution system issues the scope information linked to each intermediate handler ID to the intermediate handler terminal.

According to the present invention, it is possible to provide a financial institution system that reduces the technical burden on the financial institution side when providing financial service functions using API to product sales and service providing companies.

1 is a diagram illustrating an example of the configuration of a system that combines the financial institution system of the present invention and other terminals. FIG. 2 is a conceptual diagram of provision of financial service functions by API using the financial institution system of the present invention. 1 is a diagram showing an example of the configuration of a financial institution system of the present invention. It is a figure showing an example of an input screen of authentication information displayed on a user terminal. FIG. 2 is a diagram illustrating an example of the configuration of an intermediate agent terminal connected to the financial institution system of the present invention. (a) to (c) are diagrams showing details of a part of the configuration of the intermediate handler terminal shown in FIG. 5; (a) It is a diagram showing an example of information stored in a product/service provider DB provided in an intermediate handling terminal. (b) is a diagram showing an example of information stored in an access token DB included in an intermediate handler terminal. It is a flow diagram showing an example of processing of the financial institution system of the present invention. 9 is a flow diagram illustrating an example of processing subsequent to FIG. 8. FIG.

Hereinafter, an example of an embodiment of the present invention will be described with reference to the accompanying drawings.

In the present invention, a product/service provider who sells products or provides services to users such as consumers receives an API from a financial institution, and based on the user's authorization, the financial institution provides an API. The present invention includes a financial institution system used to execute financial service functions using the API on user account information, a method executed by the system, and a computer program for executing the same on a computer.

The financial institutions are entities that provide various financial services, such as banks, securities companies, insurance companies, virtual currency exchange operators, and the like.

In this embodiment, a product/service provider who sells products or provides services to users such as consumers receives an API from a financial institution, and based on the user's authorization, the financial institution An example of a financial institution system used to execute a financial service function using the API for the account information of the user will be described.

In the embodiment shown in FIG. 1, a financial institution system 1 managed by a financial institution that provides various conventionally known financial services includes user terminals 2 used by a plurality of users, and products used by a plurality of product/service providers.・Service provider terminal 3, intermediary terminal 4 used by multiple intermediaries intervening between product/service providers and financial institutions, an Internet communication network, and a wireless communication network specified by wireless communication standards. They are communicably connected via a communication network 5 such as .

In this embodiment, the product/service provider is, for example, a product sales company that sells products through electronic commerce or the like, or a service provider that provides various services.

In this embodiment, the user is a consumer or user who purchases a product from a product sales company or receives a service from a service provider company. If the person using the financial institution system 1 of this embodiment is a securities company, insurance company, virtual currency exchange operator, etc., the products and services handled and provided by the product and service provider, and the users, It will correspond to each one.

The intermediate handler is the intermediate handler, when the product/service provider receives an API from the financial institution and, based on the user's authorization, performs financial processing using the API against the account information of the user stored in the financial institution. A person who intervenes between the product/service provider and the financial institution when performing a service function. For example, it is a company that handles payments on behalf of users when they wish to pay product purchase prices and service charges to product/service providers through their own financial institution accounts.

In this embodiment, as shown in FIG. 2, the financial institution issues an intermediate handler ID as an identifier for identifying the intermediate handler for each intermediate handler via the financial institution system 1. In addition, the financial institution that manages the financial institution system 1 receives scope information, which is an identifier that specifies the combination of the financial service function that the financial institution that manages the financial institution system 1 is requested to perform from the product/service provider, and the product/service provider. , are issued via the financial institution system 1 in association with each intermediate handler ID.

The financial service functions that the financial institution that manages the financial institution system 1 receives execution requests from product/service providers include various financial service functions using APIs (hereinafter referred to as "API-based financial service functions" in this specification and drawings). ``Financial Service Functions'' shall be referred to as ``API Functions''). Examples of the API function include a reference API such as a balance inquiry of a financial institution account in the user's account information, and an update API such as a payment instruction to a financial institution account in the user's account information. If the person using the financial institution system 1 of this embodiment is a securities company, an insurance company, a virtual currency exchange business, etc., the API functions will correspond to each.

[User terminal configuration]
The user terminal 2 is a computer such as a personal computer, a smartphone, a tablet terminal, a mobile phone, a smart speaker, etc. used by a plurality of users.

The user terminal 2 is communicably connected to the financial institution system 1, the product/service provider terminal 3, and the intermediate handler terminal 4 via the communication network 5.

Although not shown, the user terminal 2 includes an arithmetic processing section that is composed of a CPU and performs various data processing and calculations, a storage section such as a memory that stores various data, and an information output section such as a liquid crystal display and a speaker. , an information input section such as a touch panel and a microphone, and a communication section that sends and receives various data. The specific configurations of the information output section and the information input section employed differ depending on the type of user terminal 2.

The storage unit of the user terminal 2 stores processing operations related to API functions such as product purchase price payment (settlement), service purchase price payment (settlement), balance inquiry, transfer inquiry, etc. using the financial institution system 1 of this embodiment. A computer program for controlling the processing unit by the arithmetic processing unit is stored. By executing this computer program, each function of the user terminal 2 is realized, such as the function of granting the product/service provider terminal 3 access authority to the account information of the user registered with the financial institution. be done.

[Configuration of product/service provider terminal]
The product/service provider terminal 3 is a computer such as a server used by a product/service provider who is a product sales company that sells products through electronic commerce or the like or a service provider company that provides various services.

The product/service provider terminal 3 is communicably connected to the financial institution system 1, the user terminal 2, and the intermediate agent terminal 4 via the communication network 5.

Although not shown in the figure, the product/service provider terminal 3 includes an arithmetic processing section that is composed of a CPU and performs processing and calculations on various data, a storage section such as a memory and hard disk that stores various data, and a storage section that stores various data such as a memory and a hard disk. A communication unit that performs transmission and reception.

The storage unit of the product/service provider terminal 3 stores information such as product purchase price payment (settlement), service purchase price payment (settlement), balance inquiry, and transfer inquiry executed by the user using the financial institution system 1 of this embodiment. A computer program for controlling processing operations related to API functions such as , etc., by an arithmetic processing unit is stored. By executing this computer program, each function provided by the product/service provider terminal 3, for example, a function of using a payment instruction service for a financial institution account based on the account information of the user using an API provided by the financial institution; etc. are realized.

[Financial institution system configuration]
The financial institution system 1 is a system composed of various servers managed by a financial institution. In this embodiment, the financial institution system 1 is a system composed of a web system 7, an API control system 8, and an accounting system 9, as shown in FIG. Although not shown, a system may be constructed in which the functions within the Web system 7 and the functions within the API control system 8 are provided in the same system without intervening the communication network 10.

1. Configuration of Web System The Web system 7 is configured with one or more Web servers. In the illustrated embodiment, the web system 7 is communicably connected to the user terminal 2 and the intermediate handler terminal 4 via the communication network 5, and is connected to the API control system 8 via the communication network 10 such as a leased line. and the accounting system 9, respectively, so as to be communicable. Although not shown, a load distribution device may be provided to distribute the load on the Web server due to concentration of accesses from the user terminals 2 and intermediate handler terminals 4.

The web system 7 shown in FIG. 3 includes an information transmitting/receiving section 12, a control section 13, an intermediate handler information management processing section 14, a first confirmation processing section 17, an authentication processing section 18, and an authorization code sending processing section 19. .

The information transmitting/receiving unit 12 transmits and receives information to and from the user terminal 2, intermediate handler terminal 4, API control system 8, and accounting system 9, respectively.

The control unit 13 controls information processing performed by each processing unit included in the Web system 7 using arithmetic processing units such as a CPU and a RAM.

The intermediate handler information management processing section 14 includes an intermediate handler ID issuing processing section 15 and a scope information issuing processing section 16. The intermediate handler information management processing unit 14 manages the following information.

・Intermediate handler ID
The intermediate handler ID is issued by a financial institution via the financial institution system 1, and is an identifier for identifying each intermediate handler. The intermediate handler ID is issued by the intermediate handler ID issuing processing unit 15 and notified to the intermediate handler terminal 4. For example, an intermediate handler ID consisting of a different character string for each financial institution as shown in FIG. The notification is sent to each intermediate handler terminal 4 used by the person. The intermediate handler ID is registered in an intermediate handler ID database 22 provided in the API control system 8, which will be described later (hereinafter, "database" will be referred to as "DB" in this specification and drawings).

-Scope information Scope information is an identifier that identifies the combination of the API function that the financial institution that manages the financial institution system 1 has received a request for execution from the product/service provider, and the product/service provider. A financial institution issues scope information in association with each intermediate handler ID via the API system 1. The scope information is issued by the scope information issuing processing unit 16 and notified to the intermediate handler terminal 4. For example, the characters shown in FIG. 7(a) for the combination of the API function provided by each financial institution and the product/service provider who uses the financial institution system 1 by requesting the execution of the API function. One piece of scope information consisting of a column is issued by the scope information issue processing unit 16 and notified to the intermediate handler terminal 4. This scope information is registered in a scope DB 23 included in the API control system 8, which will be described later.

・Intermediate handler secret The intermediary handler secret indicates that the access to the financial institution system 1 received from the intermediate handler having the intermediate handler ID via the intermediate handler terminal 4 used by the intermediate handler is legitimate. This is information that proves something. This intermediate handler secret is registered in the intermediate handler IDDB 22, which will be described later.

The first confirmation processing section 17 performs a process of confirming that the intermediate handler ID and scope information obtained by the information transmitting/receiving section 12, which is an information obtaining section, are legitimate.

In this embodiment, when the intermediate handler terminal 4 requests the financial institution system 1 for an access token issuance request, which will be described later, the intermediate handler terminal 4 transfers information from the product/service provider terminal 3 to the user terminal 2. A user ID that identifies the user and a session identifier between the user terminal 2 and the product/service provider terminal 3 are acquired.

The intermediate handler terminal 4 identifies scope information and an intermediate handler ID, which is a combination of API functions and product/service providers, based on the acquired user ID and session identifier, and displays the specified scope information and intermediate handler ID. Send the ID to the web system 7.

The authentication processing unit 18 transmits information from the product/service provider terminal 3 via the intermediate handler terminal 4 to the user terminal 2 used by the user related to the scope information confirmed by the first confirmation processing unit 17. Authentication information for permitting a request to issue an access token for the product/service provider terminal 3 to access the financial institution system 1 via the intermediate handler terminal 4, which is made to the financial institution system 1 via the intermediate handler terminal 4. prompt for input. In this case, the information transmitting/receiving unit 12, which is an information transmitting unit, transmits intermediate handler information indicating the intermediate handler linked to the intermediate handler ID, the API function linked to the scope information, and the API function linked to the scope information. Combination information indicating a combination with the product/service provider that receives the function is transmitted to the user terminal, and this information is displayed on the user terminal. Then, authentication processing is performed based on the authentication information acquired from the user terminal 2.

In this embodiment, as shown in FIG. A message indicating that you would like to use the "Account Transfer Function, Identity Verification Function" is displayed on the user terminal 2, and you must also enter your login ID and password, and the product/service provider "Hanamaru Shokai" will be contacted by the intermediate handler "Net Settlement Co., Ltd." The user is prompted to choose whether or not to allow the use of the API function ``○△□ instant account transfer function and identity verification function provided by online banks.'' The user inputs a predetermined login ID and password, and selects permission or rejection. The authentication processing unit 18 authenticates the login ID and the password by referring to a user DB 33 included in the accounting system 9, which will be described later, which stores information about the user.

The authorization code sending processing unit 19 performs a process of sending an authorization code issued by the API control system 8, which will be described later, to the intermediate handler terminal 4.

2. Configuration of API Control System The API control system 8 is configured of one or more API control servers. The API control system 8 is communicably connected to the user terminal 2 and the intermediate handler terminal 4 via the communication network 5, and is communicably connected to the web system 7 and the accounting system 9 via the communication network 10 such as a dedicated line. Connected for communication. Although not shown, a load distribution device may be provided in order to distribute the load on the API control server due to concentration of accesses from the user terminals 2 and intermediate handler terminals 4.

The API control system 8 shown in FIG. 3 includes an information transmitting/receiving section 20, a control section 21, an intermediate handler ID DB 22, a scope DB 23, an access token DB 24, an authorization code issuance processing section 25, a second confirmation processing section 26, and an access token issuance processing section. 27, an access token sending processing section 28, a third confirmation processing section 29, and an API function execution completion information sending processing section 30.

The information transmitting/receiving unit 20 transmits and receives information to and from the user terminal 2, intermediate handler terminal 4, web system 7, and accounting system 9, respectively.

The control unit 21 controls information processing performed by each processing unit included in the API control system 8 using arithmetic processing units such as a CPU and a RAM.

The intermediate handler ID DB 22 stores the above-mentioned intermediate handler ID and intermediate handler secret.

The scope DB 23 stores the above-mentioned scope information.

The access token DB 24 stores an authorization code issued by an authorization code issuing processing unit 25, which will be described later, and an access token and refresh token issued by an access token issuing processing unit 27, which will be described later. The access token is a token linked to the authorization code confirmed by the second confirmation processing unit 26 described later, and is valid for the combination of the intermediate handler ID and the scope information related to the authorization code. This is a token that identifies the user and authorizes the product/service provider to use the API function via the intermediate handler terminal 4. For example, an access token consisting of a character string as shown in FIG. 7(b) is stored. Further, the access token shown in FIG. 7(b) has a first expiration date (access token expiration date) for accessing the financial institution system 1. The refresh token is a token linked to the authorization code confirmed by the second confirmation processing unit 26 described later, and is valid for the combination of the intermediate handler ID and the scope information related to the authorization code. and a token that authorizes the intermediary handler to be granted a new token having the same function as the access token by re-accessing the financial institution system 1 after the first expiration date has elapsed. be. For example, a refresh token consisting of a character string as shown in FIG. 7(b) is stored. Further, a second expiration date (refresh token expiration date) for accessing the financial institution system 1 is set in the refresh token shown in FIG. 7(b).

The authorization code issuance processing unit 25 performs a process of issuing an authorization code that is linked to the user ID that identifies the user who has been authenticated by the authentication processing unit 18, the intermediate handler ID, and the scope information. . In this embodiment, the authentication processing unit 18 of the web system 7 successfully authenticates the login ID and the password, and the user allows the product/service provider to use the API function through the intermediate handler. In this case, the authorization code issuance processing unit 25 uses the scope information and the intermediate handler ID acquired during the confirmation processing by the first confirmation processing unit 17 of the Web system 7, and the authentication processing by the authentication processing unit 18. An authorization code is issued that is linked to the user ID obtained at the time. The authorization code is sent to the intermediate handler terminal 4 by the authorization code sending processing section 19 of the Web system 7. At this time, the intermediate handler ID and the scope information linked to the authorization code may be sent.

The second confirmation processing unit 26 confirms that the intermediate handler ID, the scope information, the authorization code, and the intermediate handler secret acquired from the intermediate handler terminal 4 are legitimate. Perform processing. In this embodiment, after the intermediate handler terminal 4 acquires the authorization code, the intermediate handler ID related to the issuance of the authorization code, and the scope information from the web system 7, the acquired authorization code, the intermediate handler The ID, the scope information, and the intermediate handler secret that has been previously set in association with the intermediate handler ID are sent to the API control system 8 to request issuance of an access token. The second confirmation processing unit 26 of the API control system 8 determines whether the acquired authorization code is information stored in the access token DB 24 and whether the intermediate handler ID and the intermediate handler secret are the intermediate handler ID DB 22. It is confirmed whether the scope information is information stored in the scope DB 23.

The access token issuance processing section 27 performs a process of issuing the above-mentioned access token linked to the authorization code that has been confirmed by the second confirmation processing section 26.

In addition, the access token issuance processing unit 27 issues a refresh token with a second expiration date set for re-accessing the financial institution system 1 after the first expiration date for accessing the financial institution system 1 has passed. Perform the processing to do.

In addition, the access token issuance processing unit 27 generates an access token having the same function as an access token used when the API function execution processing unit 34 of the banking system 9 (to be described later) executes the API function, and a refresh token linked thereto. Perform the process of issuing a new .

The access token sending processing unit 28 performs a process of sending the access token and the refresh token issued by the access token issuing processing unit 27 to the intermediate handler terminal 4. At this time, the intermediate handler ID and the scope information linked to the access token may be sent.

The third confirmation processing unit 29 performs processing to confirm that the intermediate handler ID, the scope information, and the access token acquired from the intermediate handler terminal 4 are legitimate. In this embodiment, when the product/service provider terminal 3 requests the financial institution system 1 to execute the above-described API function, the intermediate handler terminal 4 receives the user ID from the product/service provider terminal 3. , obtains a financial institution ID that identifies the financial institution related to the API function. The intermediate handler terminal 4 specifies the intermediate handler ID, the scope information, and the access token based on the acquired user ID and the financial institution ID, and sends them to the financial institution system 1. The third confirmation processing unit 29 of the API control system 8 determines whether the acquired intermediate handler ID is information stored in the intermediate handler ID DB 22 and whether the scope information is information stored in the scope DB 23. It is checked whether the access token is the information stored in the access token DB 24.

The API function execution completion information transmission processing unit 30 sends processing completion information indicating that the execution of the API function related to the execution request from the product/service provider terminal 3 performed in the accounting system 9, which will be described later, to the intermediate handler. Performs processing to send to terminal 4. In this embodiment, after the API function execution processing unit 34 of the accounting system 9, which will be described later, executes the API function related to the execution request from the product/service provider terminal 3, the execution result is sent to the API control system 8. The API function execution completion information sending processing unit 30 sends the execution result to the intermediate handler terminal 4, and the intermediate handler terminal 4 sends the execution result to the user terminal 2 via the product/service provider terminal 3. Send.

3. Configuration of Accounting System The accounting system 9 is composed of a financial institution server that performs one or more accounting processes. The accounting system 9 is communicably connected to the Web system 7 and the API control system 8 via a communication network 10 such as a dedicated line.

The accounting system 9 shown in FIG. 3 includes an EAI (Enterprise Application Interration) 31, a product/service provider DB 32, a user DB 33, and an API function execution processing unit 34. Although not shown, the system may be configured such that the user DB 33 is located in the Web system 7 and the product/service provider DB 32 is located in the API control system 8.

The EAI 31 is a system that integrates and links applications between the Web system 7 and the API control system 8.

The product/service provider DB 32 stores information about the product/service provider related to the product/service provider terminal 3 connected to the financial institution system 1.

The user DB 33 stores information regarding the user, such as user account information such as the user's bank account, the user ID, and the password.

The API function execution processing unit 34 uses the intermediate handler ID confirmed by the third confirmation processing unit 29 of the API control system 8, the access token, and the scope information to identify the ID using the access token. The API function specified by the scope information is executed in the financial institution account of the user account information linked to the user ID.

[Configuration of intermediate handler terminal]
The intermediate agent terminal 4 is a computer such as a server used by the intermediate agent interposed between the product/service provider and the financial institution.

The intermediate handler terminal 4 is communicably connected to the financial institution system 1, the user terminal 2, and the product/service provider terminal 3 via the communication network 5.

The intermediate handler terminal 4 shown in FIG. 5 includes an information transmitting/receiving section 35, a control section 36, an information registration processing section 37, a storage section 38, an access token issuance request management processing section 39, and an API function execution request management processing section 40. There is.

The information transmitting and receiving unit 35 transmits and receives information to and from the financial institution system 1, the user terminal 2, and the product/service provider terminal 3, respectively.

The control unit 36 controls information processing performed by each processing unit included in the intermediate handling terminal 4 using arithmetic processing units such as a CPU and a RAM.

The information registration processing unit 37 performs a process of registering various information sent from the financial institution system 1 in a DB included in a storage unit 38, which will be described later.

The storage unit 38 includes a product/service provider DB 41 and an access token DB 42. The product/service provider DB 41 includes information identifying the product/service provider related to the product/service provider terminal 3 connected to the intermediate handler terminal 4, and information as shown in FIG. 7(a). , the intermediate handler ID issued by the Web system 7 and the scope information are stored. As shown in FIG. 7(b), the access token DB 42 stores the access token and refresh token issued by the API control system 8 for each scope information.

The access token issuance request management processing unit 39 includes a product/service provider information confirmation processing unit 43, a financial institution list creation/sending processing unit 44, an intermediate handler ID/scope information identification processing unit 45, and an intermediate handler ID/scope information processing unit 45. It includes a sending processing section 46, an access token issuance request processing section 47, and an access token issuance completion information sending processing section 48.

The product/service provider information confirmation processing unit 43 receives the user ID that identifies the user associated with the user terminal 2 from the user terminal 2 via the product/service provider terminal 3, and the user terminal 2 and product/service provision information. A process is performed to check whether the product/service provider associated with the session identifier is stored in the product/service provider DB 41.

The financial institution list creation/sending processing section 44 creates a list of the financial institutions with which the product/service provider confirmed by the product/service provider information confirmation processing section 43 has a contract, and the created financial institution list. The process of sending the data to the user terminal 2 is performed. For example, when the product/service provider confirmation processing unit 43 confirms the product/service provider "Hanamaru Shokai" from the product/service provider DB 41 shown in FIG. 7(a), the financial institution list is created. - The sending processing unit 44 creates a list of financial institutions "〇△□Bank" and "△△Bank" with which the product/service provider "Hanamaru Shokai" has a contract, and sends the created financial institution list to the user. It is sent to the user terminal 2 along with the ID and the session identifier.

The financial institution list is displayed or audibly output on the user terminal 2. The user selects a financial institution necessary for the access token issuance process.

The intermediate handler ID/scope information identification processing unit 45 identifies the intermediate handler ID and scope information associated with the combination of the financial institution selected by the user terminal 2 and the product/service provider associated with the session identifier. from the product/service provider DB 41. For example, if the user selects "〇△□ Bank" from a list of financial institutions "〇△□ Bank" and "△△ Bank" with which the product/service provider "Hanamaru Shokai" has a contract, The intermediate handler ID/scope information identification processing unit 45 manages the product/service provider management numbers “1” and “2” from the product/service provider DB 41 shown in FIG. 7(a). Specify the intermediate handler ID and scope information.

The intermediate handler ID/scope information sending processing unit 46 performs a process of sending the intermediate handler ID and the scope information specified by the intermediate handler ID/scope information specifying unit 45 to the financial institution system 1. In the financial institution system 1, the first confirmation processing unit 17 of the Web system 7 performs the above-described confirmation process.

After acquiring the authorization code from the authorization code sending processor 19 of the web system 7, the access token issuance request processing unit 47 obtains the acquired authorization code, the intermediate handler ID associated with the authorization code, and the scope information, A process is performed in which the intermediate handler secret, which is set in advance in association with the intermediate handler ID, is sent to the financial institution system 1 to request issuance of an access token. In the financial institution system 1, the second confirmation processing unit 26 of the API control system 8 performs the above-described confirmation process.

After acquiring the access token and the refresh token from the access token transmission processing unit 28 of the API control system 8, the access token issuance completion information transmission processing unit 48 transmits processing completion information indicating that the issuance of the access token has been completed. Processing for sending to the product/service provider terminal 3 is performed.

In addition, at this time, the information registration processing unit 37 performs a process of registering the obtained access token and the refresh token in the access token DB 42 by associating them with the user ID as a key, as shown in FIG. 7(b). conduct.

The product/service provider terminal 3 records predetermined registration completion information in the storage section of the product/service provider terminal 3 and sends the information to the user terminal 2.

The API function execution request management processing section 40 includes a product/service provider information identification processing section 49, an intermediate handler ID identification processing section 50, a scope information identification processing section 51, an access token identification processing section 52, and an API function execution request processing section. 53, an API function execution completion information sending processing section 54 is provided.

The product/service provider information identification processing unit 49 includes the user ID that identifies the user associated with the user terminal 2 acquired from the user terminal 2 via the product/service provider terminal 3, and the product/service provider information. A process is performed to identify the product/service provider from the product/service provider DB 41 based on the financial institution ID related to the API function to be used.

The intermediate handler ID identification processing unit 50 performs a process of identifying an intermediate handler ID linked to the product/service provider identified by the product/service provider information identification processing unit 49 from the product/service provider DB 41. I do.

The scope information identification processing unit 51 performs a process of identifying scope information linked to the product/service provider identified by the product/service provider information identification processing unit 49 from the product/service provider DB 41 .

The access token identification processing unit 52 links the user ID to the user ID based on the intermediate handler ID identified by the intermediate handler ID identification processing unit 50 and the scope information identified by the scope information identification processing unit 51. A process of specifying an access token from the access token DB 42 is performed.

The API function execution request processing unit 53 sends the specified intermediate handler ID, the scope information, and the access token to the financial institution system 1, and performs a process of requesting execution of the API function related to the scope information. . In the financial institution system 1, the third confirmation processing unit 29 of the API control system 8 performs the above-described processing.

The API function execution completion information sending processing unit 54 sends processing completion information indicating that the execution of the API function related to the execution request from the product/service provider terminal 3 in the accounting system 9 has been completed, or in the accounting system 9. The user account information associated with the user ID obtained by executing the API function related to the execution request from the product/service provider terminal 3 is obtained from the API control system 8, and the processing completion information or the Processing for sending user account information to the product/service provider terminal 3 is performed.

At this time, the information registration processing section 37 obtains the latest access token and refresh token from the access token issuing processing section 27 and the access token sending processing section 28 of the API control system 8, and stores them in the access token DB 42. Update information.

The product/service provider terminal 3 sends predetermined API execution completion information to the user terminal 2.

In this way, in the financial institution system 1 of this embodiment, one intermediate handler ID that identifies the intermediate handler is issued to each of the plurality of intermediate handler terminals 3, and the API functions to be executed and The system issues a plurality of pieces of scope information that specify the combination with the product/service provider to be used, in association with the intermediate handler ID.

Therefore, unlike in the past, it is no longer necessary to issue, register, and manage a client ID that identifies the product/service provider for each product/service provider and API function to be executed, and multiple product/service provider terminals 3 and the financial institution system 1, the financial institution only needs to set up the network with the intermediary agent terminal 4, so the technical burden on the financial institution is significantly reduced.

[Processing flow using financial institution system]
An example of the processing flow of this embodiment will be described with reference to FIGS. 4 and 7 to 9. In this processing flow, the financial institution is ``〇△□ Bank'', the product/service provider that receives API functions from ``〇△□ Bank'' is ``Hanamaru Shokai'', and the user pays the product purchase price and service fee. When you try to make a payment by paying a product or service provider through your own bank account, you use "Net Settlement Co., Ltd.", a company that handles the payment as an intermediate handler, and use the API function as "instant account". "Transfer and identity verification."

1. Initial registration flow (S101)
A user who purchases a product from "Hanamaru Shokai" must pay for the product purchased from "Hanamaru Shokai" via the user's bank account (i.e., use the API function "Immediate account transfer and identity verification") ), the user accesses the "Hanamaru Shokai" product/service provider terminal 3 via the user terminal 2 and informs that he/she desires initial registration for this purpose.

(S102)
The product/service provider terminal 3 assigns a user ID to identify the accessing user, and also assigns a session identifier between the user terminal 2 and the intermediate handler terminal 4, and sends these to the accessing user terminal 2. and prompts redirection to the intermediate handler terminal 4. The user terminal 2 redirects to the intermediate handler terminal 4 based on the acquired information.

(S103)
In the intermediate handler terminal 4, the product/service provider information confirmation processing unit 43 checks whether the product/service provider “Hanamaru Shokai” related to the acquired session identifier is stored in the product/service provider DB 41. Perform the processing to do.

(S104)
When the product/service provider confirmation processing unit 43 confirms the product/service provider “Hanamaru Shokai” from the product/service provider DB 41 shown in FIG. 7(a), a list of financial institutions is created and sent. The processing unit 44 creates a list of financial institutions "〇△□Bank" and "△△Bank" with which the product/service provider "Hanamaru Shokai" has a contract to use the API function "Immediate account transfer and identity verification". Then, the created financial institution list is sent to the user terminal 2 along with the user ID and the session identifier. The financial institution list is displayed on the user terminal 2.

(S105)
The user uses the user terminal 2 to select the financial institution ``〇△□Bank'' that uses the API function ``Immediate account transfer and identity verification,'' and transmits the selection to the intermediate handler terminal 4.

(S106, S107)
In the intermediate handler terminal 4, the intermediate handler ID/scope information identification processing unit 45 selects the product/service provider management number “1” from the product/service provider DB 41 shown in FIG. 7(a). Identify the managed intermediate handler ID and scope information. It also provides a session identifier between the user terminal 2 and the Web system 7, conveys these to the user terminal 2 accessing it, and prompts redirection to the Web system 7 in the financial institution system 1. The user terminal 2 redirects to the web system 7 of the financial institution system 1 based on the acquired information.

(S108)
In the Web system 7 of the financial institution system 1, the first confirmation processing unit 17 refers to the information stored in the intermediate handler ID DB 22 and scope DB 23 provided in the API control system 8, and uses the acquired intermediate handler ID. It is confirmed from the combination of the information and the scope information that these are legitimate.

(S109)
When the first confirmation processing unit 17 confirms that the device is genuine, the authentication processing unit 18 issues an access token for the product/service provider terminal 3 to access the financial institution system 1. The user terminal 2 is prompted to input authentication information for permitting the request. In this case, the information transmitting/receiving unit 12 of the Web system 7 transmits the intermediate handler information indicating the intermediate handler "Net Settlement Co., Ltd." linked to the intermediate handler ID, and the intermediate handler information linked to the scope information. Combination information indicating the combination of the API function "Immediate account transfer and identity verification" and the product/service provider "Hanamaru Shokai" that receives the provision of the API function is transmitted to the user terminal. The user terminal 2 has a message indicating that the product/service provider "Hanamaru Shokai" wishes to use the API function "Immediate account transfer and identity verification" through the intermediate handler "Net Settlement Co., Ltd." as shown in Figure 4. Enter a message, login ID, and password, and allow the product/service provider "Hanamaru Shokai" to use the API function "instant account transfer and identity verification" through the intermediate handler "Net Settlement Co., Ltd." Encourage the user to choose whether or not to do so. The user inputs a predetermined login ID and password, and selects permission or rejection.

(S110, S111)
When authentication information is input from the user terminal 2, the authentication processing unit 18 refers to information about the user stored in the user DB 33 included in the accounting system 9, and authenticates the login ID and password. I do.

(S112)
After the authentication processing unit 18 performs authentication, the authorization code issuance processing unit 25 stores the user ID that identifies the user who has been authenticated by the authentication processing unit 18, the intermediate handler ID, and the scope information. Issue an authorization code linked to.
The authorization code issued by the authorization code issuing processing unit 25 is transmitted to the user terminal 2 by the authorization code sending processing unit 19 of the web system 7 together with the intermediate handler ID and the scope information linked to the authorization code, and the user terminal 2 to the intermediate handler terminal 4.

(S113)
In the intermediate handler terminal 4 that has been redirected from the user terminal 2, the access token issuance request processing unit 47 stores the acquired authorization code, the intermediate handler ID, the scope information, and the intermediate handler ID in advance. The intermediary handler secret that is linked and set (the access to the banking system 1 received from the intermediary handler with the intermediary handler ID via the intermediary handler terminal 4 used by the intermediary handler is legitimate) information proving that there is) is transmitted to the financial institution system 1.

(S114)
In the financial institution system 1 that has acquired the authorization code, the intermediate handler ID, the scope information, and the intermediate handler secret from the intermediate handler terminal 4, the second confirmation processing unit 26 A process is performed to confirm that the intermediate handler ID, the scope information, the authorization code, and the intermediate handler secret acquired from the user terminal 4 are genuine.

(S115)
When the second confirmation processing unit 26 confirms that the authentication code is genuine, the access token issuing processing unit 27 issues an access token linked to the authorization code.
Furthermore, the access token issuance processing unit 27 issues a refresh token in which a second expiration date for accessing the financial institution system 1 is set after the first expiration date for accessing the financial institution system 1 has passed. Perform processing.
The access token and refresh token issued by the access token issuing processing unit 27 are transmitted to the intermediate handling person terminal 4 by the access token sending processing unit 28 along with the intermediate handling person ID and the scope information that are linked to the access token. be done.
Alternatively, the access token and refresh token issued by the access token issuing processing unit 27 are transmitted to the user terminal 2 by the access token sending processing unit 28 together with the intermediate handler ID and the scope information that are linked to the access token. and may be redirected from the user terminal 2 to the intermediate handler terminal 4.

(S116)
In the intermediate handler terminal 4, the information registration processing unit 37 performs a process of registering the acquired access token and the refresh token in the access token DB 42 by associating them with the user ID as a key.

(S117)
After the registration is completed, the access token issuance completion information sending processing unit 48 sends processing completion information indicating that the issuance of the access token has been completed to the user terminal 2, and also sends the information to the product/service provider terminal. You will be redirected to 3.

(S118)
The product/service provider terminal 3 that has received the redirect from the user terminal 2 records that the initial registration has been completed by the user using the user terminal 2, and sends a notification to the user terminal 2 that the initial registration procedure has been completed. .

2. Payment flow for product/service purchase amount (S201)
If a user who has purchased a product from Hanamaru Shokai, a product/service provider for whom initial registration has been completed, wishes to pay for the purchase using the financial service function for which processing has been registered, the user may accesses the product/service provider terminal 3 of "Hanamaru Shokai" and makes a request to that effect.

(S202)
The product/service provider terminal 3 of Hanamaru Shokai, which has received a request from the user terminal 2, sends information identifying the user, the bank designated by the user, and information regarding the requested financial service function. It is sent to the intermediate handler terminal 4 of the intermediate handler "Net Settlement Co., Ltd.".

(S203, S204)
At the intermediate handler terminal 4 of the intermediate handler "Net Settlement Co., Ltd." which receives a request from the product/service provider terminal 3, the product/service provider information identification processing unit 49 acquires information from the product/service provider terminal 3. The product/service provider is identified from the product/service provider DB 41 based on the user ID that identifies the user who has provided the service, and the financial institution ID related to the API function used by the product/service provider. Perform the processing to do.
The intermediate handler ID identification processing unit 50 performs a process of identifying an intermediate handler ID linked to the product/service provider identified by the product/service provider information identification processing unit 49 from the product/service provider DB 41. I do.
The scope information identification processing unit 51 performs a process of identifying scope information linked to the product/service provider identified by the product/service provider information identification processing unit 49 from the product/service provider DB 41 .
The access token identification processing unit 52 links the user ID to the user ID based on the intermediate handler ID identified by the intermediate handler ID identification processing unit 50 and the scope information identified by the scope information identification processing unit 51. A process of specifying an access token from the access token DB 42 is performed.
The API function execution request processing unit 53 sends the specified intermediate handler ID, the scope information, and the access token to the financial institution system 1 of the specified financial institution, and executes the API function related to the scope information. Performs processing that requests execution.

(S205)
In the financial institution system 1 that has acquired the above information from the intermediate handler terminal 4 of the intermediate handler "Net Settlement Co., Ltd.", the third confirmation processing unit 29 acquires the scope information, the intermediate handler ID, and the access information. Performs processing to confirm that the token is legitimate.

(S206)
If the third confirmation processing unit 29 confirms that the information is legitimate, the API function execution processing unit 34 uses the scope information that has been confirmed by the third confirmation processing unit 29, Based on the intermediate handler ID and the access token, the API function specified by the scope information is executed with the bank account of the user account information linked to the user ID.

(S207)
When the API function is executed by the API function execution processing unit 34, the API function completion information sending unit 30 sends processing completion information indicating that the API function has been executed by the API function execution processing unit 34 to the intermediate handler terminal 4. Send to.
In addition, the access token issuance processing unit 27 generates a new access token having the same function as the access token used by the API function execution processing unit 34 of the banking system 9 to execute the API function, and a refresh token linked thereto. Perform the processing to issue to.

(S208, S209)
When the intermediate handler terminal 4 of the intermediate handler "Net Settlement Co., Ltd." acquires the above-mentioned processing completion information from the financial institution system 1, the API function execution completion information sending processing unit 54 records the above-mentioned processing completion information from the financial institution system 1. The process completion information or the user account information linked to the user ID obtained by executing the API function is sent to the product/service provider terminal 3 of the product/service provider "Hanamaru Shokai".
The product/service provider terminal 3 of the product/service provider "Hanamaru Shokai", which has acquired the above-mentioned processing completion information etc. from the intermediate handler terminal 4, records the fact and notifies the user terminal 2 of the processing result. do.
Further, in the intermediate handler terminal 4, the information registration processing unit 37 stores the acquired access token and refresh token in the access token DB 42, and updates the information.

(S210)
Predetermined API function execution completion information is displayed on the user terminal.

1 Financial institution system 2 User terminal 3 Product/service provider terminal 4 Intermediate handler terminal 5, 10 Communication network 7 Web system 8 API control system 9 Accounting system 12 Information transmission/reception unit 13 Control unit 14 Intermediate handler information management processing unit 15 Intermediate handler ID issuing processing unit 16 Scope information issuing processing unit 17 First confirmation processing unit 18 Authentication processing unit 19 Authorization code sending processing unit 20 Information transmission/reception unit 21 Control unit 22 Intermediate handler IDDB
23 Scope DB
24 Access token DB
25 Authorization code issuing processing section 26 Second confirmation processing section 27 Access token issuing processing section 28 Access token sending processing section 29 Third confirmation processing section 30 API function execution completion information sending processing section 31 EAI
32 Product/Service Provider DB
33 User DB
34 API function execution processing section 35 Information transmission/reception section 36 Control section 37 Information registration processing section 38 Storage section 39 Access token issuance request management processing section 40 API function execution request management processing section 41 Product/service provider DB
42 Access token DB
43 Product/service provider information confirmation processing unit 44 Financial institution list creation/sending processing unit 45 Intermediate handler ID/scope information identification processing unit 46 Intermediate handler ID/scope information sending processing unit 47 Access token issuance request processing unit 48 Access Token issue completion information transmission processing unit 49 Product/service provider information identification processing unit 50 Intermediate handler ID identification processing unit 51 Scope information identification processing unit 52 Access token identification processing unit 53 API function execution request processing unit 54 API function execution completion information Sending processing section

Claims (16)

A product/service provider that sells products or provides services to users such as consumers receives an API from a financial institution and, based on the user's authorization, uses the user account information held by the financial institution. A financial institution system used to execute financial service functions using the API,
An intermediate handler ID issued by the financial institution system as an identifier for identifying the intermediate handler for each intermediate handler intervening between the product/service provider and the financial institution; The combination of the financial service function by the API and the product/service provider that the financial institution system has received a request for execution from the product/service provider, which is issued in association with each intermediate handler ID. A financial institution system equipped with scope information, which is an identifying identifier, and an intermediate handler information management processing unit that manages scope information. The intermediate handler information management processing unit further manages an intermediate handler secret, which is information that proves that access from the intermediate handler having the intermediate handler ID to the financial institution system is legitimate. The financial institution system according to claim 1. a first confirmation processing unit that confirms that the intermediate handler ID and the scope information obtained by the information acquisition unit are genuine based on the combination;
From the product/service provider terminal used by the product/service provider to the financial institution system with respect to the user terminal used by the user related to the scope information confirmed by the first confirmation processing unit prompting the product/service provider terminal to input authentication information for permitting a request for issuance of an access token for accessing the financial institution system, and the authentication information obtained from the user terminal; an authentication processing unit that performs authentication processing based on;
an authorization code issuance processing unit that issues an authorization code that is linked to a user ID that identifies the user who has been authenticated by the authentication processing unit, the intermediate handler ID, and the scope information;
The financial institution system according to claim 1 or 2, further comprising: an authorization code sending processing unit that sends the authorization code to an intermediate handler terminal used by the intermediate handler. Providing the product/service from the product/service provider terminal to the financial institution system with respect to the user terminal used by the user related to the scope information confirmed by the first confirmation processing unit. Indicates the intermediate handler linked to the intermediate handler ID when prompting the user terminal to input authentication information for permitting a request for issuance of an access token for accessing the financial institution system. Claim 3 further comprising: an information transmitter that causes the user terminal to display combination information indicating a combination of intermediary handler information, the financial service function by the API linked to the scope information, and the product/service provider. Financial institution system listed. The access to the financial institution system from the intermediate handler who has the intermediate handler ID, the scope information, the authorization code, and the intermediate handler ID acquired by the information acquisition unit is legitimate. a second confirmation processing unit that confirms that the intermediate handler secret, which is the information that proves the information, is genuine;
an access token issuance processing unit that issues an access token linked to the authorization code that has been confirmed by the second confirmation processing unit;
an access token sending processing unit that sends out the access token issued by the access token issuing processing unit;
a third confirmation processing unit that confirms that the intermediate handler ID, the scope information, and the access token acquired by the information acquisition unit are legitimate;
Based on the scope information confirmed by the third confirmation processing unit and the access token, the scope is determined in the financial institution account of the user account information linked to the user ID specified by the access token. an API function execution processing unit that executes a financial service function using the API specified in the information;
5. The financial institution system according to claim 4, further comprising: an API function execution completion information sending unit that sends processing completion information indicating that the financial service function using the API has been executed by the API function execution processing unit. The access to the financial institution system from the intermediate handler who has the intermediate handler ID, the scope information, the authorization code, and the intermediate handler ID acquired by the information acquisition unit is legitimate. a second confirmation processing unit that confirms that the intermediate handler secret, which is the information that proves the information, is genuine;
further comprising: an access token issuance processing unit that issues an access token linked to the authorization code that has been confirmed by the second confirmation processing unit;
The access token has a first expiration date set for accessing the financial institution system,
When issuing the access token, the access token issuance processing unit issues a refresh token in which a second expiration date is set for access to the financial institution system after the first expiration date has elapsed. The financial institution system described in item 3 or 4 . an intermediate handler ID issuing processing unit that issues the intermediate handler ID to an intermediate handler terminal used by the intermediate handler;
The financial institution system according to any one of claims 1 to 6, further comprising: a scope information issuance processing unit that issues the scope information to the intermediate handler terminal. A product/service provider that sells products or provides services to users such as consumers receives an API from a financial institution and, based on the user's authorization, uses the user account information held by the financial institution. A computer program used to execute a financial service function using the API,
computer,
For each intermediate handler intervening between the product/service provider and the financial institution, an intermediate handler ID issued by a financial institution system managed by the financial institution as an identifier for identifying the intermediate handler. , the financial service function by the API and the product/service that the financial institution system has received a request for execution from the product/service provider, which the financial institution system has issued in association with each intermediate handler ID; A computer program that functions as an intermediate handler information management processing unit that manages scope information, which is an identifier that specifies a combination with a provider. The intermediate handler information management processing unit further manages an intermediate handler secret that is information that proves that access to the financial institution system from the intermediate handler having the intermediate handler ID is legitimate. 9. The computer program according to claim 8, which functions to perform the following functions. computer, and
a first confirmation processing unit that confirms that the intermediate handler ID and the scope information obtained by the information acquisition unit are genuine based on the combination;
From the product/service provider terminal used by the product/service provider to the financial institution system with respect to the user terminal used by the user related to the scope information confirmed by the first confirmation processing unit prompting the product/service provider terminal to input authentication information for permitting a request for issuance of an access token for accessing the financial institution system, and the authentication information obtained from the user terminal; an authentication processing unit that performs authentication processing based on;
an authorization code issuance processing unit that issues an authorization code that is linked to a user ID that identifies the user who has been authenticated by the authentication processing unit, the intermediate handler ID, and the scope information;
The computer program according to claim 8 or 9, which functions as an authorization code sending processing unit that sends the authorization code to an intermediate handler terminal used by the intermediate handler. computer, and
Providing the product/service from the product/service provider terminal to the financial institution system with respect to the user terminal used by the user related to the scope information confirmed by the first confirmation processing unit. Indicates the intermediate handler linked to the intermediate handler ID when prompting the user terminal to input authentication information for permitting a request for issuance of an access token for accessing the financial institution system. 10. Functions as an information transmitter that causes the user terminal to display intermediate handler information, combination information indicating a combination of the financial service function by the API linked to the scope information, and the product/service provider. The computer program described. computer, and
The access to the financial institution system from the intermediate handler who has the intermediate handler ID, the scope information, the authorization code, and the intermediate handler ID acquired by the information acquisition unit is legitimate. a second confirmation processing unit that confirms that the intermediate handler secret, which is the information that proves the information, is genuine;
an access token issuance processing unit that issues an access token linked to the authorization code that has been confirmed by the second confirmation processing unit;
an access token sending processing unit that sends out the access token issued by the access token issuing processing unit;
a third confirmation processing unit that confirms that the intermediate handler ID, the scope information, and the access token acquired by the information acquisition unit are legitimate;
Based on the scope information confirmed by the third confirmation processing unit and the access token, the scope is determined in the financial institution account of the user account information linked to the user ID specified by the access token. an API function execution processing unit that executes a financial service function using the API specified in the information;
12. The computer program according to claim 11, which functions as an API function execution completion information sending unit that sends processing completion information indicating that the financial service function using the API has been executed in the API function execution processing unit. computer, and
The access to the financial institution system from the intermediate handler who has the intermediate handler ID, the scope information, the authorization code, and the intermediate handler ID acquired by the information acquisition unit is legitimate. a second confirmation processing unit that confirms that the intermediate handler secret, which is the information that proves the information, is genuine;
functioning as an access token issuing processing unit that issues an access token linked to the authorization code that has been confirmed by the second confirmation processing unit;
The access token has a first expiration date set for accessing the financial institution system,
When issuing the access token, the access token issuance processing unit is configured to issue a refresh token with a second expiration date set for access to the financial institution system after the first expiration date has elapsed. The computer program according to claim 10 or 11 . computer, and
an intermediate handler ID issuing processing unit that issues the intermediate handler ID to an intermediate handler terminal used by the intermediate handler;
The computer program according to any one of claims 8 to 13, which functions as a scope information issuance processing unit that issues the scope information to the intermediate handler terminal. A product/service provider that sells products or provides services to users such as consumers receives an API from a financial institution and, based on the user's authorization, uses the user account information held by the financial institution. In contrast, in a financial institution system used to execute a financial service function using the API, the financial service function using the API that the financial institution system has received a request for execution from the product/service provider, and the product/service A scope issuance method that issues scope information that is an identifier that identifies a combination with a provider,
For each intermediate handler intervening between the product/service provider and the financial institution, the intermediate handler may receive an intermediate handler ID issued by the financial institution system as an identifier for identifying the intermediate handler. An intermediate handler ID issuance processing step for issuing an intermediate handler ID to the intermediate handler terminal to be used;
A scope issuance method, comprising: a scope information issuance processing step in which the financial institution system issues the scope information linked to each intermediate handler ID to the intermediate handler terminal. A computer program for causing a computer to execute the method according to claim 15.

Images