JP2018181309A - Transaction information provision system, server device, node device and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a system for sharing a system among a plurality of financial institutions and collectively transmitting transaction information of the financial institutions to a user. SOLUTION: A plurality of node devices 102 are managed by different financial institutions, and a means for holding user transaction information in a financial institution that manages itself, a means for holding user transaction information in a financial institution that does not manage itself, and a server. A node receiving means of a first acquisition request for user transaction information having transaction accounts in a plurality of financial institutions from the device, a means of reading transaction information corresponding to the received first acquisition request from a holding means, and a server device for transaction information. It has a node transmission means for transmitting to. The server device 101 provides a server receiving means for receiving a second acquisition request for transaction information from the user terminal 151, an acquisition means for acquiring transaction information in response to the second acquisition request from the node device, and transaction information to the user terminal 151. It has a server transmission means for transmission. The server transmission means transmits user transaction information of two or more financial institutions. [Selection diagram] FIG. 1A

Description

  The present invention relates to a transaction information providing system, a server device, a node device and a program for providing a business entity with transaction information provided by a plurality of financial institutions.

  BACKGROUND Conventionally, there has been known a system capable of accessing a website provided by a financial institution such as a bank and viewing financial transaction information provided by the financial institution and the status of account transfer.

  Such browsing service via the Internet is highly convenient, but when provided from a plurality of institutions, it is necessary to access each service separately, and access to each web site becomes troublesome. According to Patent Document 1, when a user who accesses a website on a financial institution side such as a bank desires to buy and sell financial products, a session with a user terminal can be made from a web server on the bank side via a web server on the bank side. A technology for automatically switching to the web server side is disclosed.

Unexamined-Japanese-Patent No. 2006-215904

  By the way, a business owner (also referred to simply as a user) may receive the provision of similar services (e.g., account transfers etc.) from a plurality of financial institutions, and when viewing information of the services, a plurality of financial institutions It is desirable to be able to receive the status of the service collectively.

  Although the technology disclosed in the above-mentioned Patent Document 1 facilitates switching of services by a plurality of financial institutions, it has not considered providing services by a plurality of financial institutions collectively.

  In addition, since the system that supports the services of financial institutions needs to achieve high levels of confidentiality maintenance and reduction of risks to system failures, each financial institution constructs its own system, resulting in high system construction cost. And can not but bear the operating costs.

  That is, a system that can share systems by multiple financial institutions to reduce maintenance and operation burdens, and can provide users with transaction information provided by multiple financial institutions in a batch, can be used by both financial institutions and users. It is useful.

  This invention is made in view of the said subject, The objective is to share a system with several financial institutions, and implement | achieves the technique which can provide collectively the transaction information provided from several financial institutions to a user. is there.

  In order to solve this problem, for example, the transaction information providing system of the present invention has the following configuration. That is, in a transaction information providing system including a plurality of node devices, a server device, and a user terminal, the plurality of node devices are a plurality of node devices managed by different financial institutions, respectively, and the plurality of nodes Each of the devices includes holding means for holding both the user's transaction information at the financial institution managing itself and the user's transaction information at the financial institution not managing itself, and a plurality of server devices from the server device. Node receiving means for receiving a first acquisition request for transaction information of a user having a trading account in any one of financial institutions, and transaction information according to the first acquisition request received by the node receiving means Means for reading out the information from the holding means, and the transaction information about the user read out by the Server transmission means for transmitting to the server device, the server device receiving the second acquisition request for the transaction information of the user from the user terminal of the user, and the server reception means Acquisition means for acquiring transaction information according to the second acquisition request from at least one of the plurality of node devices using the first acquisition request in response to receiving the second acquisition request And server transmission means for transmitting, as a response, the transaction information corresponding to the acquired second acquisition request to the user terminal, wherein the server transmission means performs the process in at least two or more financial institutions. The response including the transaction information of the user is transmitted to the user terminal.

  According to the present invention, a system can be shared by a plurality of financial institutions, and transaction information provided by a plurality of financial institutions can be collectively provided to a user.

, The figure explaining the outline of the transaction information offer system concerning the embodiment of the present invention A block diagram showing a hardware configuration of a server device, a node device, and a client device according to the present embodiment A figure explaining an example of functional composition of a server apparatus, a node apparatus, and a client apparatus concerning this embodiment Flow chart showing a series of operations of the server apparatus 101 for displaying account transfer data by the user and registering new account transfer data Diagram showing an example of a login screen and menu screen displayed on the user's client device Diagram showing an example of an account transfer processing list and an account transfer item list displayed on a user's client device Diagram showing an example of a new request registration screen displayed on the user's client device A flowchart describing a series of operations of the server apparatus 101 for downloading of bank transfer data by a financial institution and registration of processing result data Diagram showing an example of a management screen login and management menu displayed on a client device of a financial institution A diagram showing an example of a managed target account transfer processing list displayed on a client device of a financial institution and a lock screen Diagram showing an example of processing result upload displayed on a client device of a financial institution A diagram showing an example of a current matching table output screen displayed on a client device of a financial institution and an example of a current matching table A diagram showing a configuration example of a transaction information providing system according to another embodiment

(Embodiment 1)
Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the drawings.

(System configuration and operation outline)
FIG. 1A is a diagram for explaining a transaction information providing system as an example of an information processing system according to the present embodiment. Note that one or more server devices, client devices and node devices constituting the transaction information providing system shown in FIG. 1A may be realized by independent physical hardware, or may be virtually implemented by executing software. May be realized by a virtual machine realized by When these devices are realized virtually, a plurality of virtual machines may be executed on one hardware or may be realized respectively on different hardware. Also, at least one of these devices may be realized using two or more hardware.

(Summary of system and its operation)
The server device 101 includes a client device 151 managed by a business operator (user), a client device 161 managed by a financial institution (including a business operator engaged in financial business), a node device 102 configuring a P2P network on a block chain, The node device 103 intervenes with the node device 103, transmits and receives necessary data to and from the node device, and sends back data according to the request from the client device. In the following example, it is assumed that the user has a trading account at a plurality of financial institutions.

  The node devices 102 and 103 are each a computer managed by a specific financial institution. The node devices configure nodes on the P2P network that form a block chain, and each holds a distributed ledger in the block chain. Each node device operates software that provides a block chain service such as Hyperledger Fabric, etc., in order to realize management of the distributed ledger by the block chain. In the present embodiment, the account transfer data is recorded in the dispersion register of the block chain, and is shared by the dispersion registers possessed by a plurality of node devices. That is, the dispersion ledger of the node device 102 managed by the financial institution B1 holds both account transfer data of the user at the financial institution B2 and account transfer data of the user at another financial institution (for example, the financial institution B2). It can be done. However, the node device 102 can control encryption / decryption of data in the dispersion register using an encryption key of each financial institution managed by a management server (not shown) or the node device. Therefore, even if data of another financial institution is held in the dispersion ledger of the node device 102, the financial institution B1 can be prevented from viewing account transfer data of the other financial institution.

  The client device 151 is a user terminal used by a business operator (user) U1 who outsources the account transfer business to a financial institution, and is, for example, a personal computer. For example, it is assumed that the user U1 has entrusted the account transfer business to the financial institution B1 and the financial institution B2 and manages the client apparatus 151. In this case, the user U1 newly registers account transfer data of the user U1 in the consigning financial institution B1 and B2 via the client device 151, or browses account transfer data of the user U1 already registered. You can do it. The client device 152 is managed by, for example, a user (operator) U2 different from U1, and transmits and receives account transfer data of the user U2 similarly to the client device 151.

  The client device 161 is a user terminal used by a financial institution, and is, for example, a personal computer. For example, it is assumed that the financial institution B1 manages the client device 161. In this case, the financial institution B1 can download the debit data on the block chain via the client device 161. Further, the downloaded account transfer data can be input to a centralized management system (not shown in FIG. 1) separately present in each financial institution, and the account transfer process can be actually executed. Further, the financial institution B1 can register the result of the account transfer process performed by the central management system as processing result data in the block chain via the client device 161. The client device 162 is managed by, for example, a financial institution B2 different from the financial institution B1, and transmits and receives account transfer data relating to the financial institution B2 similarly to the client device 161.

  Next, an overview of the operation of the system in the case where a user views account transfer data and registers new account transfer data will be described. When the server apparatus 101 receives access from the client apparatus 151 handled by the user U1, the server apparatus 101 acquires the account transfer data already registered by the user U1 from the node apparatus on the block chain for a plurality of financial institutions (B1 and B2). Then, a web page displaying a part of the account transfer data of the user U1 (e.g., the account transfer data 171) and a button for new registration of data is transmitted to the client apparatus 151. The account transfer data 171 includes account transfer data of the user U1 at the financial institutions B1 and B2.

  The user U1 can register new account transfer data of the user U1 in the financial institution by pressing the web page new registration button on the client device 151. For example, the client device 151 transmits the new registration data 172 to the server device 101. The new registration data 172 includes, for example, account transfer data related to the financial institution B1 for the user U1. When receiving the new registration data from the client device 151, the server device 101 transmits the new registration data to the node device 102 in order to register the new registration data in the distribution register on the block chain. The node device 102 writes the received new registration data in the block on the block chain.

  The newly registered data written in the block on the block chain by the node device 102 becomes consensus acquired if the validity is confirmed by the processing of the consensus algorithm executed on the block chain. The data that has become consensus acquired is then recorded in the distribution ledger that each node device (including the node device 103) on the block chain has. That is, the new registration data is held in the respective dispersion registers of the node device 102 managed by the financial institution B1 and the node device 103 managed by the financial institution B2.

  Thereafter, the server device 101 acquires a part of the account transfer data including the newly acquired registration data on which consensus acquisition has been completed from the node device 102, and uses the web page displaying the account transfer data and the data registration button as a client. Send to device 151. In this case, the debit data includes the newly registered February 24 process.

  The server apparatus 101 performs the same process as the process described above even for an operation performed by the user U 2 using the client apparatus 152. For example, the server device 101 reads out the account transfer data of the user U 2 from the dispersion register on the block chain via the node device 103 and displays the data as the account transfer data 173. Further, the new registration data 174 of U 2 is recorded in the dispersion register of the node device 103 via the node device 103. That is, the new registration data 174 of U2 is recorded in the dispersion register of the node devices 102 and 103 on the block chain.

  Next, an outline of the operation of the system when the financial institution downloads the account transfer data of a plurality of users recorded in the distribution ledger on the block chain will be described. When receiving the access from the client device 161 managed by the financial institution B1, the server device 101 requests the node device 102 managed by the financial institution B1 to acquire account transfer data (to be processed by the financial institution B1). Send. The node device 102 sends, to the server device 101, account transfer data accessible to the financial institution B1 (that is, account transfer data to be managed by the financial institution B1). The account transfer data returned from the node device 102 includes account transfer data of a plurality of users that have not been processed by the central management system of the financial institution B1. The server device 101 collectively transmits the unprocessed data (for example, the account transfer data 175) for the plurality of users to the client device 161. The client device 162 can also download unprocessed account transfer data (for example, the account transfer data 176) to be processed by the financial institution B2 over a plurality of users.

  Further, with reference to FIG. 1B, an outline of the operation of the system in the case of uploading processing result data onto a block chain which has completed the processing of account transfer by the centralized management system of the financial institution will be described.

  When the server apparatus 101 receives access from the client apparatus 161 managed by the financial institution B1, the server apparatus 101 acquires account transfer data relating to the financial institution B1 from the node apparatus 102 on the block chain. Then, the financial institution B1 transmits, to the client device 161, a web page displaying a part of the account transfer data to be processed (for example, the account transfer data 181) and a button for uploading the processing result data. When the processing result data registration button displayed on the web page is pressed, the client device 161 transmits processing result data (for example, the account transfer data 182) output from the central management system to the server device 101.

  The server device 101 transmits the processing result data received from the client device 161 to the node device 102 on the block chain and records the data as a block. The recorded processing result data becomes consensus acquired if the legitimacy is confirmed by the processing of the consensus algorithm executed on the block chain. The processing result data that has become consensus acquired is recorded in the distribution register of each node device (including the node device 103) on the block chain.

  The server apparatus 101 also transmits unprocessed account transfer data 183 to the client apparatus 162 for the account transfer data of the financial institution B2 as in the case of the financial institution B1. Then, when the account transfer data (184) processed by the central management system of the financial institution B2 is received, the account transfer data is registered in the block chain via the node device 103.

  On the other hand, when the server device 101 receives a request from the client device 151, it acquires account transfer data including processing result data for which consensus acquisition has been completed from the node device 102, and transmits the data (account transfer data 185) to the client device 151. Send to At this time, the bank transfer data acquired by the server apparatus 101 from the node apparatus includes process result data newly registered by the financial institution B1 and the financial institution B2. As described above, according to the transaction information providing system according to the present embodiment, the system can be shared by a plurality of financial institutions, and the user can collectively acquire the account transfer data of the financial institution consigning the account transfer. .

(Configuration of Server Device 101)
Next, with reference to FIG. 2A and FIG. 3, a functional configuration example of the server apparatus 101 will be described.

  The CPU 201 implements the function of the server device 101 in the transaction information providing system shown in FIG. 1 by executing a program stored in the ROM 202 or the storage device 207.

  The program includes a web application for operating the server apparatus 101 as a web application server. The web application, as shown at 301 in FIG. 3, for example, a login module 302 that processes user login, a data transmission / reception module 303 that controls transmission / reception of data with the client device 151 or the client device 161, a list of account transfer data It includes a list display module 304 that provides a display function. The web application also includes a block chain client module 305 that communicates with the node devices 102 to 103 forming the block chain and operates as a client of the block chain.

  The ROM 202 includes a non-volatile memory such as a semiconductor memory, and stores programs executed by the CPU 201, setting values of the server apparatus 101, and the like. The RAM 203 includes, for example, a volatile memory such as an SDRAM, and temporarily stores calculation results and the like by the CPU 201.

  The communication device 206 transmits and receives commands and data between the client device 151 and the client device 161 and the node devices 102 to 103. The communication device 206 exchanges data with the client device 151 by communication compliant with, for example, HTTPS. Also, the communication device 206 exchanges data with the node devices 102 to 103 by communication based on, for example, the gRPC protocol. The storage device 207 includes, for example, a semiconductor memory such as an SSD, and a magnetic disk such as an HDD, and stores data necessary for the operation of the web application.

(Configuration of node devices 102 and 103)
The functional configuration example of the node device 102 and the node device 103 is the same as the functional configuration example of the server device 101 except that the program operated in the server device 101 is different. The node device 102 and the node device 103 include a CPU 211, a ROM 212, a RAM 213, a communication device 216, and a storage device 217. The program executed by the CPU 211 of the node device includes a service program for realizing a block chain, and, for example, Hyperledger Fabric operates. The service program writes account transfer data in the dispersion register book held by the storage device 217 of each node device, the account transfer data write module 311, the account transfer data read module 312 reading data from the register, access by the user or financial institution And an access control module 313 that controls the user according to the access authority. Further, the block chain service 314 executes processing such as execution of a consensus algorithm performed when adding a transaction, synchronization of distributed register data among node devices, and the like. The storage device 217 holds the data of the dispersion register which is written and read out by the execution of the service program, and the account transfer data is recorded in the dispersion register. The account transfer data is stored in blocks of a predetermined size and sequentially recorded in the distribution register.

(Configuration of Client Device 151)
Next, a functional configuration example of the client device 151 will be described with reference to FIG.

  The CPU 251 implements the function of the client device 151 in the transaction information providing system shown in FIG. 1 by executing a program stored in the ROM 252 or the storage device 257. The program includes a web browser 320 for operating the client device 151 as a web client. The web browser 320 transmits and receives data such as account transfer data to and from the server apparatus 101.

  The ROM 252 includes a non-volatile memory such as a semiconductor memory, and stores programs executed by the CPU 251, setting values of the client apparatus 151, and the like. The RAM 253 includes, for example, a volatile memory such as an SDRAM, and temporarily stores calculation results and the like by the CPU 251.

  The input device 254 includes, for example, a keyboard, a mouse, and a touch panel, and enables operation of screen transition of the web browser and selection of a file to be uploaded. The communication device 256 exchanges commands and data with the server device 101.

(Configuration of Client Device 161)
Furthermore, with reference to FIG. 2 (B) and FIG. 3, the function structural example of the client apparatus 161 is demonstrated. The CPU 261 implements the function of the client device 161 in the transaction information providing system shown in FIG. 1 by executing a program stored in the ROM 262 or the storage device 267. The program includes a web browser 330 for operating the client device 161 as a web client. The web browser 330 transmits and receives data such as account transfer data and processing result data to and from the server apparatus 101. Also, the program may include a cooperative application for exchanging account transfer data and processing result data with the company central management system 350. The company central management system 350 actually executes the process of debit based on the input debit data, and outputs process result data indicating the execution result. The other configuration of the client device 161 is the same as the configuration of the client device 151 described above, and thus the description thereof is omitted.

(A series of operations for displaying account transfer data and registering new account transfer data)
Next, with reference to FIG. 4, a series of operations of the server apparatus 101 for displaying account transfer data and registering new account transfer data by the user (business company) will be described. In the following description, the operator operating the client apparatus is referred to as the operator.

  Further, in this process, the operator selects “Account Transfer” on the menu screen (for example, FIG. 5B) after logging in on the login screen (for example, FIG. 5A) on the client device 151 in advance. It starts from the moment. That is, when the operator logs in, the correct combination of identification information and password specifying the user and the operator is input and logged in, and the menu screen is displayed when the server apparatus 101 confirms the legitimacy. It shall be. For example, in the example of FIG. 5A, the user (business operator) is identified by the company number, and the operator is identified by the user ID. As the password, other information such as biometrics may be used as long as it is information for confirming the legitimacy of the user or the operator.

  In step S41, the server apparatus 101 acquires information related to the account transfer process list from the node apparatus (for example, the node apparatus 102), and then transmits it to the client apparatus 151 as a web page of the account transfer process list (for example, FIG. 6A). Send. More specifically, in order to obtain information from the node device, the server device 101 causes the node device to specify, for example, information specifying the user (here, company number), and a predetermined range representing the range of account transfer data to be obtained. Send a request for acquisition of account transfer data by specifying the period of At this time, the server device 101 may obtain information from one specific node device, or may obtain information for each financial institution from each of the node devices managed by the financial institution whose user has a trading account. Good. When recording transaction information, a node device (for example, the node device 102) generates metadata for search that enables search of encrypted data in the dispersion ledger, and stores the metadata in the dispersion ledger together with the transaction information. Good. For example, when data is held in the key value store, the search metadata may correspond to the key part and the transaction information may correspond to the value part. For example, the CPU 211 of the node device 102 acquires transaction information corresponding to the search request from the server device 101 using the search metadata by executing the service program. Further, the node device 102 holds, in the storage device 217, for example, a table in which information identifying the user, a financial institution where the user has a trading account is associated in advance, and an encryption key of each financial institution. The CPU 211 of the node device 102 specifies the financial institution associated with the user using the table by executing the service program, acquires the encryption key of the financial institution, and uses the acquired encryption key to transfer funds in the distributed ledger. Decrypt the data.

  The server apparatus 101 is a web page that displays acquired account transfer data when it receives a response from the node apparatus 102, and the detailed account information acquisition, selective download, deletion, etc. of individual account transfer data. Create a web page that can be operated. As shown in FIG. 6A, the account transfer data displayed on the web page includes information such as the consignment financial institution, the number of items to be subjected to the account transfer, the total amount, the processing status, and the like. When the user who is the target of this process consigns account transfers to a plurality of financial institutions, the account transfer processing list includes account transfer data of a plurality of financial institutions.

  "Processing status" indicates the processing status of the account transfer data by the financial institution. For example, "open" the situation where the user newly registered debit data in the block chain, and the financial institution is locked so that the debit data can not be changed to actually execute debit by the central management system The state is expressed as "in process". Furthermore, a state in which the debit is actually executed by the central management system is represented as “processed”, and a state in which the user approves the unprocessed debit data is represented as “approved”.

  When the node device (for example, the node device 102) receives an acquisition request for information related to the account transfer processing list, the node device (for example, node device 102) acquires the encryption key of the financial institution associated with the user from the management server (not shown) or the node device itself. Decrypt the account transfer data of the distribution ledger using the acquired encryption key, and read out the account transfer data of the designated range.

  In S42, the server apparatus 101 receives, from the client apparatus 151, a request corresponding to the operation on the web page of the account transfer process list, and determines the content of the request. The server apparatus 101 proceeds to S43 if the content of the request is the display of the account transfer details list, and proceeds to S44 if the content of the request is the new request registration.

  In S43, the server apparatus 101 obtains more detailed information from the node apparatus for one of the account transfer data displayed in the account transfer process list, and creates a web page displaying the account transfer details list. Do. More specifically, for example, the server device 101 transmits, to the node device 102, information identifying the designated account transfer data to the node device 102, and the server device 101 transmits the detailed information associated with the corresponding account transfer data. Get account transfer data. For example, as shown in FIG. 6 (B), the display of the account transfer details list displays the account transfer data selected in the account transfer processing list and a plurality of account transfer data associated with the selected account transfer data. Do. After transmitting the web page of the account transfer details list to the client device 151, the server device 101 ends this series of processing.

  In S44, the server apparatus 101 creates, for example, a web page for new request registration shown in FIG. 7 and transmits it to the client apparatus 151. In the new request registration page, the operator can select, for example, a file in which the account transfer data is recorded in the CSV format as the new registration data to be registered in the block chain. When the operator presses the “upload” button, the client device transmits the file to the server device 101.

  In S45, when the server apparatus 101 receives the new registration data from the client apparatus 151, the server apparatus 101 makes an addition request for causing the node apparatus 102 to add the content of the data. The server apparatus 101 transmits an addition request for adding new registration data to a node apparatus (for example, the node apparatus 102) together with information for specifying a user. When the node device 102 receives a request for adding transaction information from the server device 101, the node device 102 writes account transfer data encrypted using the encryption key of the financial institution associated with the user in the distribution register. For example, the CPU 211 of the node device 102 specifies the financial institution associated with the user using the above-mentioned table by executing the service program, acquires the encryption key of the financial institution, and uses the encryption key to transfer the account transfer data Encrypt At this time, the CPU 211 of the node device 102 may generate search metadata for making it possible to search the encrypted data of the dispersion register by executing the service program, and store the metadata in the dispersion register together with the transaction information.

  In the block chain, a node (for example, the node device 102) to which a transaction is added generates data (that is, a signature) obtained by encrypting the transaction using a private key managed by itself, and adds it to the transaction. If the other node device confirms the legitimacy of the signature using the public key of the node device to which the transaction is added, tampering of the transaction is prevented. Further, falsification of the data block is prevented by calculating the hash of the data block to which the plurality of transactions are added and storing the hash in the adjacent data block.

  Further, in the present embodiment, for example, since the PBFT (Practical Byzantine Fault Tolerance) method is adopted as the block chain consensus algorithm, the consensus algorithm is executed at high speed as compared with the case of adopting the method such as Proof of Work. Can. As a result, since the recording of the debit data into the dispersion register is completed more quickly, after the debit data is registered in the block chain, the debit data after registration can be displayed more quickly.

  When the registration of the new registration data by the node device 102 is completed, the server device 101 ends the series of processes.

(A series of operations for downloading bank transfer data and registering processing result data by a financial institution)
Next, with reference to FIG. 8, a series of operations of the server apparatus 101 regarding downloading of account transfer data and registration of processing result data by a financial institution will be described.

  In this process, after the operator of the financial institution logs in in advance with the management screen login (for example, FIG. 9A) in the client device 161, “Account” is displayed on the management menu screen (for example, FIG. 9B). Start from the point when you select "Transfer". That is, it is assumed that when the operator logs in, he / she logs in by inputting a correct combination of identification information and a password specifying the financial institution and the operator, and displays the menu screen. For example, in the example of FIG. 9A, a financial institution is specified by a company number, and an operator is specified by a user ID. Similar to the example described with reference to FIG. 4, as the password, other information such as biometrics may be used as long as it is information for confirming the legitimacy of the user or the operator.

  In S81, the server apparatus 101 acquires information related to the account transfer processing list from the node apparatus (for example, the node apparatus 102) managed by the financial institution, and then the management target account transfer processing list (for example, FIG. 10A). It is transmitted to the client device 161 as a web page. The server apparatus 101 specifies, for example, identification information (here, a company number) for specifying a financial institution, a predetermined period representing the range of account transfer data to be acquired, etc. Send acquisition request.

  When the node device (for example, the node device 102) receives an acquisition request for information related to the management target account transfer processing list, the node device (for example, the node device 102) decrypts the data of the dispersion ledger using the encryption key associated with this financial institution Read out the account transfer data in the specified range.

  The server apparatus 101 is a web page that displays acquired account transfer data when it receives a response from the node apparatus 102, and the detailed account information acquisition, selective download, deletion, etc. of individual account transfer data. Create a web page that can be operated. As shown in FIG. 10A, the account transfer data displayed on the web page includes information such as the name of the consignor, the account number to be subjected to the account transfer, the number, the processing status, and the like. The bank transfer processing list includes bank transfer data of a plurality of entrustees (ie, users).

  In S82, the server apparatus 101 receives, from the client apparatus 161, a request corresponding to the user operation on the web page of the management target account transfer processing list, and determines the content of the request. The server apparatus 101 proceeds to S83 if the content of the request is the display of the lock screen, and proceeds to S84 if the content of the request is the result upload.

  In S83, the server apparatus 101 creates a web page of a lock screen (FIG. 10 (B)) on which a specific target date for locking account transfer data can be specified, and transmits it to the client apparatus 161. In S84, when the server apparatus 101 receives from the client apparatus 161 a request for batch lock specifying a lock target date, the server apparatus 101 requests the node apparatus 102 not to update account transfer data of the specified lock target day. . The node device 102 changes, for example, information indicating the processing status of the account transfer data to the locked state, and controls so that the account transfer data of the processing status having this locked state can not be updated.

  In S85, when the server apparatus 101 receives a request for batch downloading of locked account transfer data from the client apparatus 161, the server apparatus 101 acquires, from the node apparatus 102, account transfer data whose processing status is in a locked state. The server apparatus 101 transmits the acquired account transfer data to the client apparatus 161, for example, in a file format such as a CSV format. When the transmission of the file is completed, the server device 101 ends this series of operations.

  In step S86, when the server apparatus 101 receives the processing result upload request from the client apparatus 151, the server apparatus 101 generates a web page of the processing result upload screen (for example, FIG. 11) and transmits the web page to the client apparatus 161.

  In S87, when the server apparatus 101 receives the processing result data from the client apparatus 161, the server apparatus 101 makes an addition request for causing the node apparatus 102 to add the content of the data. The server apparatus 101 transmits processing result data and an addition request for adding the processing result data to a node apparatus (for example, the node apparatus 102) managed by the financial institution of the transmission source. The node device 102 writes account transfer data encrypted using the encryption key of the financial institution in the distribution register. Thereby, the processing status of the account transfer data included in the result processing data becomes processed. After that, the server device 101 ends the series of processes related to this process.

  As described above, a plurality of node devices managed by different financial institutions respectively hold both the user's account transfer data at their own financial institution and the user's account transfer data at other financial institutions. I did it. Furthermore, upon receipt of a request for acquisition of account transfer data from the client device of the user, account transfer data of the user at a plurality of financial institutions is transmitted to the client device. By doing this, a plurality of financial institutions can share the system (the operational burden per financial institution can be reduced), and the account transfer data provided by each financial institution can be collectively provided to the user. Will be able to offer. Also, each piece of account transfer data is encrypted using the encryption key of each financial institution when it is written to the distribution register. By doing this, even when a plurality of financial institutions share the system, it is possible not to disclose their information to other financial institutions.

  In the embodiment described above, the account transfer data is used as an example of the transaction information. However, the above-described system can be applied to other information of the user in the financial institution. In addition, the example of using Hyperledger Fabric as a block chain basis for sharing account transfer data of a plurality of financial institutions has been described. However, other block chain infrastructures may be used as long as financial institution's account transfer data can be distributed and shared to each node device without being disclosed to other financial institutions. Furthermore, block chains may not be used if the same can be realized.

(Other embodiments)
The embodiment described above may have a configuration for outputting the current match table in addition to the processing for the debit data. In the output example of the checking database in the present embodiment, transaction data (simply referred to as matching table data) related to the account of the checking account is displayed based on the information designated by the user (business company). The financial institution can record the collation table data in the block chain in the same manner as the processing result upload of the bank transfer data shown in the first embodiment. Therefore, the description of the process of registering the collation table data in the block chain is omitted, and the server apparatus 101 uses the coordinate table output screen (FIG. 12A) for setting the current collation table. A process from receiving the inquiry request from S. 151 to outputting the temporary matching table will be described.

  The server device 101 receives an inquiry request from the client device 151. The query request includes the bank name, account number, and query range (query start and query end) set in the temporary matching table output screen, so the server apparatus 101 specifies these parameters and It requests the device 102 to acquire information.

  When the node device (for example, the node device 102) receives a request for information acquisition from the server device 101, the node device (for example, the node device 102) decrypts the account transfer data of the dispersion account using the encryption key of the financial institution associated with the user. Read range transaction data.

  When the server device 101 acquires transaction data relating to a designated bank name, account number, etc. from the node device 102, the server device 101 uses a web page in the form of a temporary comparison table (for example, FIG. 12B) including transaction data as a client. Send to device 151. The transaction data displayed on the web page includes, as shown in FIG. 12B, the account number, the name of the store, and the like, the check number, the amount of the deposit and withdrawal, the balance, and the like.

  Also in this case, the transaction data relating to the current account can be managed in the distributed ledger shared by a plurality of financial institutions, and the user can easily acquire the current account match table of the plurality of financial institutions. In addition, by sharing the distributed ledger among multiple financial institutions, the risk of service suspension due to maintenance of confidentiality and system failure can be suppressed, and the burden of development costs and operation costs per financial institution can be reduced. .

  In the above embodiment, the transaction information providing system includes one server device 101, and the server device communicates with the client devices 151 to 152 and the client devices 161 to 162. However, the transaction information providing system may be configured to have a plurality of server devices having the same configuration as the server device 101, as shown in FIG. 13, for example. For example, the transaction information providing system includes three server devices 101, 105, and 106. The server device 101 communicates with the client device managed by the user and the node device 104 (or any node device), and the CPU executes processing relating to the display of the above-mentioned account transfer data and the registration of new account transfer data. Do. On the other hand, the server device 105 communicates between the client device 161 managed by the financial institution B1 and the node device 102, and by its CPU, downloading and processing result of account transfer data by the above-mentioned financial institution (for example, B1) Execute processing related to data registration. In addition, the server device 106 communicates between the client device 162 managed by the financial institution B2 and the node device 103, and the CPU causes the above-mentioned financial institution (for example, B2) to download the account transfer data and the processing result Execute processing of data registration. For example, the server apparatus 105 may be managed by the financial institution B1, and the server apparatus 106 may be managed by the financial institution B2. In this case, the server apparatus managed by each financial institution is paired with the node apparatus managed by the financial institution. Connected by 1.

  A web application that generates web pages such as the list of accounts to be managed (in the process of downloading account transfer data and registering the process result data by a financial institution) by separately providing the server device 105 and the server device 106 Makes it easy to make it unique for each financial institution. In this way, it becomes easy to appropriately allocate, for example, hardware resources necessary for each financial institution, and to customize display items such as a list of managed account transfer processes and display layout. In other words, while sharing the transaction information providing system among a plurality of financial institutions, it is possible to reflect the performance requirements, quality requirements, and usability of each of the financial institutions.

  Further, by separately providing the server apparatus 101 and the server apparatus 105, processing of displaying account transfer data and registering new account transfer data in the server apparatus, downloading account transfer data by a financial institution, and processing result data It is possible to distribute the load when executing the registration process simultaneously. For example, when a financial institution downloads a large amount of account transfer data related to the financial institution in order to process the account transfer data collectively, a process when the display request for the account transfer data is received from the client device 151 It is possible to suppress the decrease. Further, in the case where a server apparatus corresponding to each financial institution is provided as in the example shown in FIG. 13, the influence of the download processing by each financial institution from the download processing by another financial institution can be reduced.

  The example shown in FIG. 13 shows the case where the server apparatus 101, the server apparatus 105, and the server apparatus 106 are realized by separate hardware. That is, the operation of the server apparatus described with each server apparatus as an operation subject is realized by the CPU in each server apparatus executing a program recorded in the ROM. On the other hand, these server devices may be realized by a plurality of logical virtual machines. This logical plurality of virtual machines is generated by a program executed using one or more integral hardware resources (including a data center consisting of a plurality of devices having one or more CPUs / GPUs) May be done. In addition, it is possible to increase the computational resources required when the load on the server device increases.

  Further, in the above-described embodiment, the node devices 102 to 103 control the encryption and decryption of the data of the dispersion ledger, thereby controlling the plurality of financial institutions in the dispersion ledger of the node device managed by each financial institution. Added support for recording direct debit data. However, control of encryption and decryption of data may be controlled not only at the node device but also at the server device (or both the server device and the node device). For example, in the example of the system shown in FIG. 13, each CPU may execute encryption and decryption in each of the server apparatus 101 and the server apparatuses 105 to 106. For example, the server apparatus (for example, the server apparatus 105) encrypts the data received from the client apparatus by the CPU using the encryption key of the corresponding financial institution (for example, financial institution B1), and the node apparatus 102 (or other nodes) Device) sends an add request with the encrypted data. The node device 102 receives the encrypted data and writes the encrypted data in the distribution register of the storage device of the node device 102. In addition, when the server device 106 also receives data from the client device 162, the CPU encrypts it using the encryption key of the financial institution similarly associated, and transmits it along with the addition request to the node device 103. The node device 103 that has received the encrypted data records it in the distribution register of the storage device. By doing this, the load of encryption and decryption can be distributed.

  At this time, the server device 105 generates search metadata for enabling search of encrypted data of the dispersion register, and provides the metadata to the corresponding node device 102, and the node device 102 encrypts the search metadata. It may be recorded in the distribution register together with the The search metadata may include, for example, date and time, information specifying a financial institution, information specifying a user (for example, company number), etc. data that enables the node device to search encrypted data without decrypting each time. . The node device 102 may further encrypt and record the search metadata (decrypt and search the search metadata at the time of search). On the other hand, when reading data from the dispersion register, the node device 102 uses the search metadata and the like to read data corresponding to the request from the dispersion register by the CPU. Then, the read data is transmitted to the server device 105. Then, the server device 105 causes the CPU to decrypt the received data using the encryption key of the financial institution B1. The encryption key of the financial institution may be stored in the storage device of one of the server devices, for example, by one or more of the server devices, and may be provided to another server device, or each server device The encryption key of the necessary financial institution may be acquired from a specific key management server (not shown).

  Further, after the server apparatus 105 managed by the financial institution B1 encrypts the data received from the client apparatus 161 using the encryption key of the financial institution B1, the data is encrypted in the node apparatus 102 managed by the financial institution B1. Data may be received and decrypted with the encryption key of the financial institution B1, subjected to predetermined processing, encrypted again with the same encryption key, and recorded in the distribution register. At this time, the node device 102 temporarily decrypts the received data by the CPU, and executes processing according to the content of the received data using a control program (for example, smart contract) operating on the node device 102. At this time, the search metadata described above may be stored together in the distribution register of the storage device. At this time, the node device 102 receives, for example, the encryption key of the financial institution from the server device 105 in order to perform encryption and decryption using the encryption key of the financial institution B1, and the process of encryption and decryption ends. And the encryption key may be destroyed. Similarly, when the node device 102 reads data from the distribution register and transmits the data to the server device 105, the node device 102 may perform decryption and encryption.

  Furthermore, when the server apparatus 101 receives an acquisition request for the account transfer data recorded in the dispersion register from the client apparatus 151, the server apparatus 101 is one of the financial institutions (for example, financial institutions B1 and B2) associated with the user U1. Obtain an encryption key. At this time, the server apparatus 101 may store, for example, a table in which the information for identifying the user and the financial institution in which the user has a transaction account are associated in advance in the storage device 207, for example. In addition, the server device 101 transmits a request for acquiring bank transfer data to the node device 104 (or another node device), using a period of data to be searched, information of a financial institution to be searched as a search condition. The node device 104 or another node device performs a search according to the search condition using the search metadata, reads the encrypted account transfer data 185 from the dispersion register, and transmits the read data to the server device 101. Do. At this time, account transfer data acquired by the server device 101 from the node device includes data of the financial institution B1 and the financial institution B2. The server device 101 decrypts the account transfer data using the encryption key of the financial institution (for example, the financial institutions B1 and B2) linked to the user U1 described above, and transmits the decrypted account transfer data to the client device 151 Do. The node device may read out and decrypt the encrypted account transfer data meeting the predetermined condition, and may obtain the account transfer data satisfying the search condition by the control program. Even in this manner, the system can be shared by a plurality of financial institutions, and the user can collectively acquire the account transfer data of the financial institution that entrusts the account transfer.

  In the above-described embodiment, an example in which the transaction information is encrypted and decrypted using the key of the financial institution has been described, but the method of encryption and decryption is not limited to this. For example, the transaction information in the financial institution B1 may be encrypted using any encryption key A, and the encryption key A may be encrypted with the encryption key associated with the financial institution B1. When the transaction information is referred to, the encryption key A may be acquired using the encryption key associated with the financial institution B1, and the transaction information may be decrypted by the encryption key A. That is, the transaction information in the financial institution B1 is concealed so that it can be referred to using the encryption key of the financial institution B1, and can not be referred to from other financial institutions.

DESCRIPTION OF SYMBOLS 101 ... Server apparatus, 102 ... Node apparatus, 103 ... Node apparatus, 151, 152 ... Client apparatus, 161, 162 ... Client apparatus

Claims (19)

A transaction information providing system including a plurality of node devices, a server device, and a user terminal, comprising:
The plurality of node devices are a plurality of node devices respectively managed by different financial institutions, and each of the plurality of node devices is
Holding means for holding both the user's transaction information at the financial institution that manages itself and the user's transaction information at the financial institution that does not manage itself;
Node receiving means for receiving, from the server device, a first acquisition request for transaction information of a user who has a transaction account at any one of a plurality of financial institutions;
Reading means for reading from the holding means transaction information corresponding to the first acquisition request received by the node receiving means;
Node transmission means for transmitting the transaction information about the user read by the reading means to the server device;
The server device is
Server receiving means for receiving a second acquisition request for transaction information of the user from the user terminal of the user;
Using the first acquisition request, the transaction information corresponding to the second acquisition request from at least one of the plurality of node devices in response to the reception of the second acquisition request by the server reception means Acquisition means for acquiring
Server transmission means for transmitting, as a response, the transaction information according to the acquired second acquisition request to the user terminal,
The system for providing transaction information, wherein the server transmission unit transmits the response including the transaction information of the user at at least two or more financial institutions to the user terminal.   The claim is characterized in that the holding means holds both the transaction information of the user at the financial institution that manages it and the transaction information of the user at the financial institution that does not manage itself by the block chain. The transaction information providing system according to Item 1. Each of the plurality of node devices further includes processing means for processing transaction information of the user,
The processing means conceals the transaction information of the user at the first financial institution so that it can be referred to using the encryption key assigned to the first financial institution, and the transaction of the user at the second financial institution Conceal the information so that it can be referred to using the encryption key assigned to the second financial institution,
2. The information processing apparatus according to claim 1, wherein the holding unit holds transaction information of the user at the first financial institution and transaction information of the user at the second financial institution, which are concealed by the processing unit. The transaction information provision system described in 2. When the processing means receives the first acquisition request from the server device, and the user of the user terminal has a transaction account at the first financial institution and the second financial institution, the first financial The user's transaction information in the first financial institution, which can be concealed so as to be referred to, is decrypted using an encryption key assigned to the institution, and is referenced using the encryption key assigned to the second financial institution. Decrypt the user's transaction information at said second financial institution, possibly concealed;
4. The transaction information providing system according to claim 3, wherein the node transmission unit transmits the transaction information about the user decrypted by the processing unit to the server device. The server device further adds the transaction information held by the node device to at least one of the plurality of node devices in response to the server reception unit receiving additional transaction information from the user terminal. Have additional request means for sending an additional request to add transaction information of
The holding unit of the plurality of node devices adds transaction information relating to the addition request to transaction information held by the node device in response to reception of the addition request. The transaction information providing system according to any one of to 4. The server reception means further receives, from a second user terminal managed by a predetermined financial institution, transaction information whose transaction status has been changed,
The addition request unit further transmits the node information to at least one of the plurality of node devices in response to reception of the transaction information whose transaction state has been changed from the second user terminal by the server reception unit. The system for providing transaction information according to claim 5, further comprising transmitting an additional request to add the transaction information whose status has been changed to the transaction information held by the device.   The transaction information in which the status of the transaction has been changed is transaction information in which the status of the transaction has been changed by processing the transaction in the central management system of the predetermined financial institution. Transaction information provision system described. The server receiving means further receives an acquisition request for transaction information of the predetermined financial institution from a second user terminal managed by the predetermined financial institution,
The acquisition means receives, in response to the acquisition request for the transaction information from the second user terminal by the server reception means, the transaction information corresponding to the acquisition request among the transaction information pertaining to the predetermined financial institution. The transaction information providing system according to any one of claims 1 to 5, characterized in that it is acquired.   The server device further includes lock request means for requesting the plurality of node devices not to change the content of predetermined transaction information among the transaction information held by each of the plurality of node devices. The system for providing transaction information according to claim 8. The server device further comprises processing means for processing transaction information of the user,
The processing means conceals the transaction information of the user at the first financial institution so that it can be referred to using the encryption key assigned to the first financial institution, and the transaction of the user at the second financial institution Conceal the information so that it can be referred to using the encryption key assigned to the second financial institution,
The server transmission means further comprises: transaction information of a user at the first financial institution and a transaction of a user at the second financial institution concealed by the server apparatus in at least one of the plurality of node devices The system for providing transaction information according to claim 1 or 2, which transmits information. The transaction information providing system further includes a second server device managed by a predetermined financial institution different from the server device,
The second server device is
A second server receiving unit that receives transaction information whose status has been changed from the second user terminal managed by the predetermined financial institution;
In the node device managed by the predetermined financial institution of the plurality of node devices in response to the second server receiving means receiving the transaction information in which the state of the transaction has been changed, the node device The additional request means for transmitting an additional request to add the changed transaction information of the status of the transaction to the transaction information held by the device;
The storage unit of each of the plurality of node devices adds transaction information related to the addition request to transaction information held by the node device in response to reception of the addition request. The transaction information providing system according to any one of Items 1, 2 and 10. The second server device further includes
The second server receiving means can refer to the transaction information using the encryption key assigned to the predetermined financial institution in response to the reception of the transaction information in which the status of the transaction has been changed. The system for providing transaction information according to claim 11, comprising: second processing means for concealing.   The transaction information providing system according to any one of claims 1 to 12, wherein the transaction information is account transfer information. A plurality of node devices each managed by a different financial institution, each of the user's transaction information at the financial institution managing itself and the user's transaction information at the financial institution not managing itself. A server device in communication with a plurality of node devices configured to be held, comprising:
Receiving means for receiving an acquisition request for transaction information of the user from a user terminal of a user having a transaction account at any one of a plurality of financial institutions;
Acquisition means for acquiring transaction information corresponding to the acquisition request from at least one of the plurality of node devices in response to receiving the acquisition request;
And transmitting means for transmitting, as a response, the transaction information corresponding to the acquired acquisition request to the user terminal,
The server apparatus, wherein the transmission means transmits the response including transaction information of the user at at least two or more financial institutions to the user terminal. A plurality of node devices each managed by a different financial institution, each of the user's transaction information at the financial institution managing itself and the user's transaction information at the financial institution not managing itself. A control method of a server device in communication with a plurality of node devices configured to be held, comprising:
Receiving means for receiving an acquisition request for transaction information of the user from a user terminal of a user having a transaction account at any one of a plurality of financial institutions;
Obtaining the transaction information according to the acquisition request from at least one of the plurality of node devices in response to the reception of the acquisition request;
And transmitting, as a response, the transaction information according to the acquired acquisition request to the user terminal,
And transmitting the response including the transaction information of the user at at least two or more financial institutions to the user terminal.   The program for functioning a computer as each means of the server apparatus of Claim 14. A plurality of node devices each managed by a different financial institution, each of the user's transaction information at the financial institution managing itself and the user's transaction information at the financial institution not managing itself. In response to receiving an acquisition request for transaction information of a plurality of node devices configured to be held and a user terminal of a user having a transaction account at any one of the plurality of financial institutions, A server device that acquires transaction information according to the acquisition request from at least one of the plurality of node devices, and transmits a response including transaction information of the user at at least two or more financial institutions to the user terminal; The node device in a system having
Holding means that each holds both the user's transaction information at the financial institution that manages itself and the user's transaction information at the financial institution that does not manage itself;
A receiving unit configured to receive an acquisition request for transaction information on the user from the server device;
Reading means for reading from the holding means transaction information corresponding to the acquisition request received by the receiving means;
And transmitting means for transmitting the transaction information about the user read by the reading means to the server device. A plurality of node devices each managed by a different financial institution, each of the user's transaction information at the financial institution managing itself and the user's transaction information at the financial institution not managing itself. In response to receiving an acquisition request for transaction information of a plurality of node devices configured to be held and a user terminal of a user having a transaction account at any one of the plurality of financial institutions, A server device that acquires transaction information according to the acquisition request from at least one of the plurality of node devices, and transmits a response including transaction information of the user at at least two or more financial institutions to the user terminal; A control method of the node device in a system including
Each holding means holds both the user's transaction information at the financial institution that manages itself and the user's transaction information at the financial institution that does not manage itself;
Receiving means for receiving from the server device a request for obtaining transaction information for the user;
Reading out transaction information corresponding to the received acquisition request from the held transaction information;
And transmitting the transaction information about the read user to the server device.   A program for causing a computer to function as each means of the node device according to claim 17.