JP6218979B1 - Financial transaction method and system using blockchain - Google Patents

Abstract

Although blockchain (BC) is actively used in the financial field, actual financial transactions are not performed just by transferring value on BC. At present, a person in charge at a financial institution operates an account system by referring to the recorded contents of BC to transfer funds between actual accounts. Therefore, even if the transaction on BC is high, a human error may occur in the actual transaction. In conjunction with a transaction using a BC, a billing operation is executed using a computing system, and the correctness of the transaction is determined by matching the execution result with the recorded content of the BC. [Selection] Figure 3

Description

  The present invention relates to a financial transaction method and system using a block chain. More specifically, it is possible to determine whether the transaction is correct or not by executing an accounting operation using a computing system in conjunction with a transaction using the block chain, and matching the execution result with the recorded contents of the block chain. A method and system capable of

  Currently, transactions using Internet banking have become widespread, but problems such as unauthorized money transfers have occurred. On the other hand, blockchain (hereinafter referred to as “BC”), which makes it difficult to falsify transaction data by ensuring the reliability of transactions with a third party, is actively used in the financial field due to its high security. It has become. At present, when BC is used in the financial field, electronic value indicating money (for example, bit coin) is transferred on BC.

  However, just a value transfer on BC does not mean that an actual financial transaction has been performed. For example, even if a transaction is performed on BC, funds are not transferred between actual accounts at a financial institution at that stage. If funds are transferred, it is assumed that a person in charge at the financial institution operates the accounting system with reference to the recorded contents of the BC. Therefore, even if the transaction on BC is high, a human error may occur in an actual transaction. Also, it can be said that there is a problem in terms of transparency of actual transactions (it cannot be said that there is no possibility of unauthorized operation).

  The present invention has been made in view of such problems, and the object of the present invention is to provide a transaction method and system that eliminates human error and ensures transaction transparency in financial transactions using BC. There is to build. On the other hand, it is considered that safety and transparency can be further improved by realizing a series of processes in a financial transaction using BC with a smart contract that is difficult to falsify and whose processing contents are disclosed.

In order to achieve such an object, the present invention is a computer that executes a billing operation in conjunction with a financial transaction using a block chain (BC), wherein the computer is a first computer,
Receiving transaction data indicating the contents of the financial transaction from a second computer participating in the BC network (BC-NW);
Based on the transaction data, it is configured to perform an accounting operation for a remittance account corresponding to a remittance address on BC and a receiving account corresponding to a receiving address on BC. And

In the first computer described in the previous paragraph, receiving the transaction data
Monitoring the second computer at regular intervals to obtain the transaction data, or
The second computer executes the financial transaction, and receives the transaction data transmitted to the first computer.

Further, the first computer described in the preceding paragraph receives again the transaction data corresponding to the executed account-related operation from the second computer after the account-related operation is executed,
In order to confirm that the transaction has been normally executed based on the transaction content on the BC, the transaction data received again and the execution result data of the account system operation are further matched. And

And in the first computer according to the preceding paragraph, the second computer executes the financial transaction and receives the transaction data transmitted to the first computer,
Receiving the transaction data indicating the contents of the financial transaction, executing the account system operation based on the transaction data, and after executing the account system operation, the transaction data corresponding to the executed account system operation Is received again, and at least one of matching the transaction data received again and the execution result data is smart contracted.

In another embodiment, the present invention is a method executed by a first computer that executes an accounting operation in conjunction with a financial transaction using a block chain (BC).
The first computer receiving transaction data indicating the contents of the financial transaction from a second computer participating in a BC network (BC-NW);
The first computer performs a billing operation on a remittance account corresponding to a remittance address on BC and a receiving account corresponding to a receiving address on BC based on the transaction data. When,
It is provided with.

Furthermore, in yet another embodiment of the present invention, there is provided a computer program that is executed by a first computer that executes a billing operation in conjunction with a financial transaction using a block chain (BC). When executed by the first computer,
Receiving transaction data indicating the contents of the financial transaction from a second computer participating in a BC network (BC-NW);
The first computer performs a billing operation on a remittance account corresponding to a remittance address on BC and a receiving account corresponding to a receiving address on BC based on the transaction data. And causing the first computer to execute.

  As described above, according to the present invention, a transaction operation is executed using a computing system in conjunction with a transaction using BC, and the transaction result is verified by matching the execution result with the recorded content of BC. Determine. Thereby, the transaction which ensured safety | security and transparency can be performed, without performing human operation.

1 is a diagram illustrating an overall configuration of a system according to an embodiment of the present invention. It is a figure which shows the structure of the transaction management terminal of the system which concerns on one Embodiment of this invention. It is a flowchart which shows BC interlocking | linkage processing which concerns on one Embodiment of this invention. It is a flowchart which shows the BC-account system matching process which concerns on one Embodiment of this invention. It is a figure which shows the data stored in the transaction data storage part which concerns on one Embodiment of this invention. It is a figure which shows the data stored in the transaction status data storage part which concerns on one Embodiment of this invention. It is a figure which shows the data stored in the execution result data storage part which concerns on one Embodiment of this invention. It is a figure which shows the data stored in the account data storage part which concerns on one Embodiment of this invention.

  Hereinafter, a system according to an embodiment of the present invention will be described in detail with reference to the accompanying drawings. FIG. 1 is a diagram showing an overall configuration of a system according to an embodiment of the present invention. In FIG. 1, a transaction management terminal 100 and a billing system server 105 managed by a financial institution A are configured to communicate with each other via a network 101 (for example, an intranet). Further, the transaction management terminal 100 is configured to communicate with the person in charge terminal 104 via the network 101 in order to perform a BC transaction. Further, the transaction management terminal 100 performs a BC transaction through the network 102 (for example, the Internet) via a customer terminal 103 and a person in charge terminal 106 of another financial institution B (hereinafter referred to as “other institution terminal and 106”). )).

  The transaction management terminal 100 is a terminal used by a transaction person in the financial institution A. The person in charge of the transaction participates in the block chain network (hereinafter referred to as “BC-NW”) via the transaction management terminal 100 and performs a transaction (for example, a loan transaction) with the customer.

  The customer terminal 103 is a terminal used by a customer who makes a transaction with the financial institution A. The customer participates in the BC-NW via the customer terminal 103 and conducts a transaction with the financial institution A (non-substitution pattern).

  The person-in-charge terminal 104 is also a terminal used by a person in charge of transaction in the financial institution A. For example, when the customer does not have the customer terminal 103 that participated in the BC-NW, the person in charge of the transaction participates in the BC-NW via the person-in-charge terminal 104 and conducts the transaction on behalf (the financial institution substitution pattern). ). Thereby, even if it is a customer who does not have the customer terminal 103 which participated in BC-NW, it can transact with the financial institution A (transaction management terminal 100) on BC.

  The other institution terminal 106 is a terminal used by a person in charge of transaction at another financial institution B. For example, if the customer has an account with another financial institution B and the customer does not have the customer terminal 103 that participated in the BC-NW, the person in charge of the transaction at the other financial institution B can connect via the other institution terminal 106. Participate in BC-NW and conduct transactions with financial institution A on behalf (another institution substitution pattern).

  The transaction management terminal 100 monitors the recorded contents (transaction data) on the BC, and executes an account operation on the account server 105 based on the transaction data (for example, an application program interface on the account server 105) (API) is called, and the transfer process to the account of the loan transaction customer is executed). The content recorded on the BC that is the monitoring target (and hence the account-related operation execution target) is based on the exchange between users on the BC corresponding to the financial institution and the customer. Specific examples of the exchange include the patterns described above. Further, the transaction management terminal 100 collates the execution result of the accounting operation and the recorded content (transaction data) on the BC, and determines whether the transaction is correct. Transaction management terminal 100 may be a server computer in consideration of stable operation.

  Next, the configuration of the transaction management terminal 100 will be described in detail. FIG. 2 is a diagram showing a configuration of a transaction management terminal of the system according to one embodiment of the present invention. In FIG. 2, only a necessary configuration is shown assuming a single computing system. However, in another embodiment, each process executed by the transaction management terminal 100 is distributed among a plurality of computers. It may also be a distributed computing system configured to execute. The transaction management terminal 100 includes a CPU 110, a RAM 111, an input device 112, an output device 113, a communication control device 114, and a storage device 116 that are connected to each other via a system bus 115. The storage device 116 is configured by a nonvolatile storage medium (ROM, HDD, or the like), and includes a program storage area that stores a software program related to the transfer process and a data storage area that stores data handled by the software program. . Each processing unit in the program storage area described later is actually an independent software program, its routine, component, and the like, and is stored in the storage device 116. Each processing unit is called from the storage device 116 by the CPU 110 at the time of execution and is expanded in the work area of the RAM 111, so that each function can be performed while appropriately accessing a database or the like.

  The software program stored in the program storage area in the storage device 116 of FIG. 2 includes an interlocking processing unit 120 and a matching processing unit 121 when only those related to the present invention are listed. These processing units are executed by the CPU 110.

  The data storage area in the storage device 116 of FIG. 2 includes a transaction data storage unit 130, a transaction state data storage unit 131, and an execution result data storage unit 132 when only those related to the present invention are listed. Both are fixed storage areas secured in the storage device 116.

  Next, the function of each processing unit stored in the storage device 116 in FIG. 2 will be described. The linkage processing unit 120 in FIG. 2 monitors a transaction on a BC with a customer. When there is a transaction, the linkage processing unit 120 acquires the transaction data and stores it in the transaction data storage unit 130. Further, the linkage processing unit 120 executes a transaction based on the acquired transaction data (strictly, the account processing operation is transmitted to the account server 105 and the account server 105 performs the account operation. Executed). When executing the transaction, the linkage processing unit 120 searches the transaction state data storage unit 131 and determines whether the target transaction has already been executed (if the transaction has already been executed, the transaction is not executed again. ). When a billing operation is executed by the billing server 105, the linkage processing unit 120 receives the execution result data transmitted from the billing server 105 and stores it in the execution result data storage unit 132.

  The match processing unit 121 in FIG. 2 acquires transaction data on the BC and matches the execution result data received from the accounting server 105 to determine whether the transaction is correct. When it is determined that the transaction has not been executed normally, the matching processing unit 121 executes error processing.

  Next, data stored in each storage unit of the storage device 116 in FIG. 2 will be described. The transaction data storage unit 130 in FIG. 2 stores data relating to the contents of transactions performed on the BC. FIG. 5 is a diagram illustrating transaction data stored in the transaction data storage unit 130 according to an embodiment of the present invention.

  The transaction data in FIG. 5 includes “transaction ID” uniquely indicating a BC transaction, “remittance address” and “recipient address” uniquely indicating a remittance user and a recipient user on BC, and a transaction on BC. A “transaction amount” indicating an amount, an “interest rate” indicating an interest rate when the transaction is a loan, an “execution date” indicating a transaction execution date, and the like can be stored.

  The transaction data in FIG. 5 is transaction data managed by user terminals participating in the BC-NW, including the transaction management terminal 100 and the customer terminal 103. In the present invention, since BC transactions between financial institutions and customers are targeted, it is assumed that transaction data on the transaction management terminal 100 is monitored. However, naturally, the transaction data of another terminal participating in the BC-NW can also be monitored.

  The transaction status data storage unit 131 in FIG. 2 stores data relating to the transaction (accounting operation) executed in conjunction with the BC transaction and the execution status of the reconciliation process. FIG. 6 is a diagram showing transaction state data stored in the transaction state data storage unit 131 according to an embodiment of the present invention.

  The transaction status data in FIG. 6 stores a “transaction ID” uniquely indicating a BC transaction and a “transaction status” indicating an execution status of a transaction (account system operation) executed in conjunction with the BC transaction. be able to.

  The transaction status data in FIG. 6 is transaction data that is created before execution of the accounting operation and is updated according to the execution status of each process. “Transaction ID” in FIG. 6 is “transaction ID” in transaction data (FIG. 5), and transaction state data and transaction data can be associated with each other. In the “transaction status” in FIG. 6, a numerical value (for example, 1: account-related operation is being executed) indicating the account-related operation for the BC transaction, and the execution status of the reconciliation process between the execution result of the account-related operation and the recorded content on the BC. 2: Account processing operation completed, 3: Matching process in progress, 4: Matching process performed, 9: Matching process failed ...) can be set. It should be noted that there is no target record itself in the transaction status data before execution of the accounting operation. Therefore, when there is no target record in the transaction status data, it can be determined that the accounting operation has not been executed yet.

  The execution result data storage unit 132 in FIG. 2 stores data related to the execution result of a transaction (accounting operation) executed in conjunction with the BC transaction. FIG. 7 is a diagram showing execution result data stored in the execution result data storage unit 132 according to an embodiment of the present invention.

  The execution result data in FIG. 7 includes a “transaction ID” that uniquely indicates a BC transaction, an “execution result” that indicates an execution result of an account operation, and a “remittance” that uniquely indicates a remittance user and a receiver user on BC. Side address "and" recipient side address "," remittance side account "and" recipient side account "that uniquely indicate the remittance side account and the receiving side account that executed the account operations, and" transaction amount "that indicates the executed transaction amount The “interest rate” indicating the interest rate when the transaction is a loan, the “execution date” indicating the execution date of the transaction, and the like can be stored.

  The execution result data in FIG. 7 is transaction data created after execution of the accounting operation. “Transaction ID” in FIG. 7 is “transaction ID” in transaction data (FIG. 5), and execution result data and transaction data can be associated with each other. In the “execution result” in FIG. 7, a numerical value (for example, 1: success, 9: failure...) Indicating the execution result of the account operation executed in conjunction with the BC transaction can be set. In the example of FIG. 7, the “remittance side account” and the “reception side account” are “financial institution code”, “branch code”, “account type”, and “account number” in account data (FIG. 8) described later. A combined value is set, whereby each account can be uniquely indicated.

  In FIG. 7, according to the “remittance address” and “recipient address”, “remittance account”, and “reception account”, the remittance and reception users on the BC and the account of each user in the financial institution Can be associated with each other. As a result, in conjunction with the transaction on the BC from the “send-side address” to the “receive-side address”, the account operation from the “send-side account” to the “receiver-side account” can be executed. The execution result data indicates the contents based on the execution of the accounting operation. For this reason, if the accounting operation is not executed based on the transaction contents on the BC due to some problem, the contents of the execution result data do not match the contents recorded on the BC (failure of matching).

  Next, the account data of the contract customer in the financial institution stored in the account data storage unit of the account server 105 or a server computer (not shown) of another financial institution will be described. FIG. 8 is a diagram showing account data stored in the account data storage unit according to the embodiment of the present invention.

  The account data in FIG. 8 includes a “financial institution code” that uniquely indicates the financial institution that provides the contract account, a “financial institution name” that indicates the name, and a “branch code” that uniquely indicates the branch of the financial institution. "Branch name" indicating the name, "Account type" indicating the account type (subject) of the contract account, "Account number" indicating the account number of the contract account, "Account name" indicating the account name of the contract account, and The “deposit amount” indicating the current deposit amount of the contract account can be stored.

  Account data is master data registered by a financial institution when a contract customer opens an account. The contract account is uniquely identified by “financial institution code”, “branch code”, “account type”, and “account number”. In the “account type”, a numerical value indicating the account type (for example, 1: normal deposit, 2: current account,...) Can be set. Further, although the account data in FIG. 8 is described assuming a real account, in another embodiment, the present invention can be realized by a virtual account.

  Next, with reference to the flowchart of FIG. 3 and the data of FIGS. 5-8, the BC interlocking process according to an embodiment of the present invention will be described along the flow. FIG. 3 is a flowchart showing the BC interlocking process according to the embodiment of the present invention. In this process, the transaction management terminal 100 executes an accounting operation on the accounting server 105 based on the transaction data on the BC by using a transaction on the BC as a trigger when the transaction management terminal 100 confirms the transaction on the BC between the financial institution and the customer. It is.

  First, the linkage processing unit 120 of the transaction management terminal 100 monitors transactions on the BC between the transaction management terminal 100 (financial institution) and the customer terminal 103, the person in charge terminal 104, or the other institution terminal 106 (customer) ( Step S301). For example, when a BC transaction is performed, a newly created record content (block) is monitored at a certain period, and the occurrence of a transaction record (transaction data) between the transaction management terminal 100 and the customer terminal 103 is confirmed. Is. The monitoring destination is, for example, the transaction management terminal 100, but, of course, another terminal participating in the BC-NW can be monitored. In another embodiment, the transaction management terminal 100 does not monitor, but notifies the transaction management terminal 100 every time a customer terminal 103 participating in the BC-NW executes a transaction on BC ( For example, transaction data can be transmitted). Note that a series of processes from a transaction on the BC between the transaction management terminal 100 and the customer terminal 103 to a notification to the transaction management terminal 100 can be realized by a smart contract.

  In step S301, when the occurrence of transaction records (transaction data) between the transaction management terminal 100 and the customer terminal 103 cannot be confirmed, the process proceeds to the No route in step S302, and the monitoring in step S301 is executed again. On the other hand, when the generation of transaction data can be confirmed, the process proceeds to the Yes route in step S302, and the interlocking processing unit 120 acquires (receives) the transaction data (FIG. 5) from the user terminals participating in the BC-NW. (Step S303) and stored in the transaction data storage unit 130 (step S304). In another embodiment in the above-described step S301 (embodiment in which the transaction management terminal 100 is not monitored and a notification is received from the customer terminal 103 participating in the BC-NW, etc.), the interlocking process is performed as in step S303. Step S304 and the subsequent steps are executed when the unit 120 receives transaction data from the customer terminal 103 or the like as a trigger.

  Next, in order to determine whether the transaction (accounting operation) to be executed in conjunction with the transaction data (FIG. 5) received in step S303 has already been executed, the linkage processing unit 120 determines the transaction status data ( 6) is searched (step S305). More specifically, the transaction state data storage unit 131 is searched using the “transaction ID” of the transaction data as a search key, and the presence or absence of the target record is confirmed. If there is a target record in the transaction status data, since the accounting operation has already been executed, the process proceeds to No route in step S306, and this process ends.

  On the other hand, if there is no target record in the transaction status data, the process proceeds to the Yes route in step S306, and the interlocking processing unit 120 creates transaction status data (FIG. 6) and stores it in the transaction status data storage unit 131 (step). S307). At this time, “1” (during account system operation execution) is set as the “transaction state” of the transaction state data.

  Next, the linkage processing unit 120 executes a transaction (accounting operation) based on the transaction data (FIG. 5) received in step S303 (step S308). More specifically, funds of “transaction amount” are transferred to each account corresponding to “remittance address” and “reception address” of transaction data. This is an operation performed on the account data (FIG. 8) by the account server 105 in accordance with a request from the interlock processing unit 120 of the transaction management terminal 100. The accounts corresponding to the “remittance address” and the “reception address” are specified by having the correspondence relationship in advance as mapping data (not shown) in the transaction management terminal 100 or the account server 105. Can do.

  In step S <b> 308, when the account operation in the account server 105 is executed, the account server 105 transmits the execution result data (FIG. 7) to the transaction management terminal 100. The transmitted execution result data is received by the linkage processing unit 120 (step S309) and stored in the execution result data storage unit 132 (step S310).

  Next, the accounting server 105 updates the “transaction status” of the transaction status data (FIG. 6) stored in the transaction status data storage unit 131 to “2” (accounting operation has been executed) (step S311). After step S311, the process ends.

  Next, with reference to the flowchart of FIG. 4 and the data of FIGS. 5-7, the BC interlocking process according to an embodiment of the present invention will be described along the flow. FIG. 4 is a flowchart showing a BC-accounting system reconciliation process according to an embodiment of the present invention. In this process, the transaction management terminal 100 collates the content of the executed transaction (accounting operation) with the recorded content on the BC, and determines whether the transaction has been executed normally.

  First, the matching processing unit 121 of the transaction management terminal 100 monitors the execution of the transaction (accounting operation) by monitoring the execution result data (FIG. 7) (step S401). For example, the execution result data storage unit 132 is monitored at a certain period, and the occurrence of a new record of the execution result data (that is, the execution of step S310) is confirmed. Moreover, in another embodiment, this process can also be performed as a series of processes following execution of step S310 or step S311 without monitoring execution result data by the matching processing unit 121.

  If the execution of the transaction (accounting operation) cannot be confirmed in step S401, the process proceeds to the No route in step S402, and the monitoring in step S401 is executed again. On the other hand, if the execution of the transaction can be confirmed, the process proceeds to a Yes route in step S402, and the matching processing unit 121 determines whether or not the account operation has been successfully executed (step S403). Specifically, it is determined whether the “execution result” of the execution result data (FIG. 7) indicates “1” (success) or “9” (failure). When the transaction is not executed normally (when “execution result” = “9”), the process proceeds to the No route in step S403, and the matching processing unit 121 executes error processing (step S409), and this process ends. To do. The error processing here is, for example, error notification to the terminal used by the administrator.

  On the other hand, when the transaction is executed normally (when “execution result” = “1”), the process proceeds to the Yes route in step S403, and the matching processing unit 121 stores the transaction state data stored in the transaction state data storage unit 131. The “transaction state” in FIG. 6 is updated to “3” (matching process is being executed) (step S404). This is to prevent double execution of the matching process.

  Next, the matching processing unit 121 acquires (receives) transaction data (FIG. 5) on the BC corresponding to the execution result data (FIG. 7) again from the user terminals participating in the BC-NW (step S405). ).

  Next, the matching processing unit 121 matches the transaction data acquired in step S405 (FIG. 5) and the corresponding execution result data (FIG. 7) (step S406). Thereby, based on the transaction content on BC, it can be determined whether transaction (account system operation) was normally performed. For example, if there is a discrepancy between the transaction data that is the recorded content on the BC and the corresponding execution result data, this indicates that the transaction has not been executed normally based on the transaction content on the BC. means. When the transaction is not normally executed, the process proceeds to the No route in Step S407, and the matching processing unit 121 executes an error process (Step S409), and this process ends. The error processing here means, for example, updating “transaction status” in the transaction status data (FIG. 6) to “9” (match processing failure) in addition to error notification to the terminal used by the administrator. It is.

  On the other hand, when the transaction is normally executed based on the transaction content on the BC, the process proceeds to the Yes route in step S407, and the matching processing unit 121 sets the “transaction state” in the transaction state data (FIG. 6) to “4” ( (Matching process has been executed) is updated (step S408). After step S408, this process ends.

  In another embodiment, each of the interlocking process in FIG. 3 and the matching process in FIG. 4 can be realized by a smart contract. In still another embodiment, a series of processes from the interlocking process to the matching process can be realized by a smart contract. In addition, a series of processes from the transaction on the BC between the transaction management terminal 100 and the customer terminal 103 to the interlocking process and the matching process can be realized by a smart contract. In addition, when smartly converting the interlocking process and / or the reconciliation process, not only the transaction data (FIG. 5) but also the transaction state data (FIG. 6) and the execution result data (FIG. 7) participate in the BC-NW. It can also be managed by a user terminal. In this way, by making a flow-oriented process into a smart contract, the safety and transparency of financial transactions can be further enhanced.

  As described above, according to the present invention, in conjunction with a financial transaction using BC, the account system operation is executed using the computing system, and the correctness of the transaction is determined by matching the execution result with the recorded content of the BC. To do. Thereby, the transaction which ensured safety | security and transparency can be performed, without performing human operation.

Claims (6)

A computer that executes an accounting operation in conjunction with a financial transaction using a block chain (BC), wherein the computer is a first computer,
Receiving transaction data indicating the contents of the financial transaction from a second computer participating in the BC network (BC-NW);
Based on the transaction data, it is configured to perform an accounting operation for a remittance account corresponding to a remittance address on BC and a receiving account corresponding to a receiving address on BC. And computer. Receiving the transaction data includes
Monitoring the second computer at regular intervals to obtain the transaction data, or
The computer according to claim 1, comprising: executing the financial transaction by the second computer and receiving the transaction data transmitted to the first computer. After the account-related operation is executed, transaction data corresponding to the executed account-related operation is received again from the second computer,
In order to confirm that the transaction has been normally executed based on the transaction content on the BC, the transaction data received again and the execution result data of the account system operation are further matched. The computer according to claim 2. The second computer executes the financial transaction and receives the transaction data transmitted to the first computer;
Receiving the transaction data indicating the contents of the financial transaction, executing the account system operation based on the transaction data, and after executing the account system operation, the transaction data corresponding to the executed account system operation The computer according to claim 3, wherein at least one of receiving the transaction data again and matching the transaction data received again with the execution result data is smart contracted. A method executed by a first computer that performs an accounting operation in conjunction with a financial transaction using a block chain (BC), the method comprising:
The first computer receiving transaction data indicating the contents of the financial transaction from a second computer participating in a BC network (BC-NW);
The first computer performs a billing operation on a remittance account corresponding to a remittance address on BC and a receiving account corresponding to a receiving address on BC based on the transaction data. When,
A method characterized by comprising: A computer program that is executed by a first computer that executes a billing operation in conjunction with a financial transaction using a block chain (BC), the computer program being executed by the first computer,
Receiving transaction data indicating the contents of the financial transaction from a second computer terminal participating in a BC network (BC-NW);
The first computer performs a billing operation on a remittance account corresponding to a remittance address on BC and a receiving account corresponding to a receiving address on BC based on the transaction data. A computer program that causes the first computer to execute.

Images