JP6710737B2 - Payment system and payment method - Google Patents

Description

The present invention relates to a settlement system and a settlement method for settlement of transactions between orderers.

Blockchain technology utilizing a peer-to-peer network is being used for payment and the like (see Non-Patent Document 1, for example). In the technology described in Non-Patent Document 1, a mechanism that enables the instant sharing/payment of contract information as unalterable data is considered without utilizing a blockchain to newly construct a large-scale payment system. ing. In this blockchain technology, the ordered records are continuously managed by a distributed ledger, thereby preventing retrospective change of data in the block.

In addition, block chain technology may be used to prevent falsification of virtual currency used in online transactions (see, for example, Patent Document 1). In this technique, balance information based on contract information is recorded in a distributed ledger as a group connected by a block chain.

In addition, a technique for supporting a transaction using a distributed blockchain computing system including a plurality of computing nodes is also under consideration (for example, see Patent Document 2). In this technique, the exchange stores purchase orders and multiple digital wallets associated with different clients. The computer system receives a new data trade request to be added to the purchase order. Matches between data transaction requests are identified and hashes associated with the digital wallets associated with the individual data transaction requests are generated. The trading partner receives the hash of the counterparty along with information about the match, and each party has the blockchain transaction added to the blockchain. Monitor the blockchain to determine if both matches have been added to the blockchain.

Further, a payment support system and a payment support method for supporting payment are provided by using a base system capable of confirming the legitimacy of debt record information using the distributed ledger technology (for example, see Patent Document 3). .. This technology uses a basic system that is connected to a payer terminal and a payer financial institution server and can confirm the validity of information by a distributed ledger technology such as a blockchain. The payer terminal acquires the payment method selection information for the creditor from the debtor, records the debt record information of the selected payment method in the distributed ledger, and stores it in the payer financial institution server according to the selected payment method. Notify issue of debt record information. The payer financial institution server confirms the distributed ledger, records the approval information of the debt record information in the distributed ledger, processes the payment to the creditor based on the payment method, and records the revocation information of the debt record information in the distributed ledger. Record.

JP, 2016-151802, A Japanese Patent Publication No. 2018-515833 Japanese Patent No. 6363254

Mizuho Bank, Ltd., “Implementing a verification experiment aimed at improving the settlement process efficiency of securities transactions that cross borders”, March 8, 2016, [online], Mizuho Bank, Ltd., [September 9, 2018 Date search], internet <https://www.mizuhobank.co.jp/release/pdf/20160308release_jp.pdf>

For a large number of contracts and settlements such as stocks, transactions can be collated and settled by a large system investment. However, in securities trading, there are transactions with a small number of daily contract settlements. Even in such securities transactions, a system equivalent to stocks is required for transaction verification, DVP settlement, etc. for secure and efficient settlement. However, when the number of transactions is small, the system investment per transaction becomes large.

A settlement system that solves the above problem includes a clearing organization system in which an exchange system connected to an orderer system is connected via a basic system that can confirm the validity of information by a distributed ledger. Then, the exchange system acquires contracted order information recorded in the distributed ledger, and specifies the contracted order information by matching the acquired order information, and the unconfirmed order information. With respect to, the revocation information is recorded in the distributed ledger, and the clearing agency system performs settlement based on the contracted order information.

According to the present invention, it is possible to support an efficient transaction, that is, a series of processes from contract to settlement, by using an information sharing technology using a distributed ledger and a basic system capable of confirming the validity of information.

The system schematic of this embodiment. Explanatory drawing of a hardware structural example. It is explanatory drawing of each system of this embodiment, (a) is a user system, (b) is an exchange system, (c) is a settlement account management institution system, (d) is explanatory drawing of a clearing institution system. It is explanatory drawing of the information recorded on a distributed ledger in this embodiment, (a) is order information, (b) is contract completion information, (c) is revocation information, (d) is approval request information, (e) ) Is settlement approval information, (f) is settlement advance notice information, and (g) is an explanatory diagram of settlement completion information. Explanatory drawing of the processing procedure of this embodiment. Explanatory drawing of the processing procedure of this embodiment. Explanatory drawing of the processing procedure of this embodiment.

Hereinafter, an embodiment in which a payment system and a payment method are embodied will be described with reference to FIGS. 1 to 7. In the present embodiment, an order is placed for a security issue, and settlement of a trade that has been executed is supported. This settlement includes DVP settlement and the like and settlement by a clearing house. In the following, it is assumed that DVP settlement is performed, but the present invention may be applied to other settlements.
As shown in FIG. 1, in the present embodiment, a user system 10, an exchange system 20, a settlement account management institution system 30, and a clearing institution system 40 connected to the distributed ledger D1 are used. In the present embodiment, it is assumed that the basic system that can confirm the validity of the record of transaction settlement information by the block chain is used to support the transaction and settlement. The block chain technology is not limited to the above as long as the distributed ledger D1 (distributed ledger) that holds the same data in a plurality of nodes connected to the network is used. The transaction settlement information electronically records information about orders, contracts, and settlements of financial institutions, and the transaction settlement information is recorded in the distributed ledger D1 and fixed by the block chain technology. Further, unlike so-called virtual currency, the recording itself does not complete the settlement, but merely records information about ordering to settlement. In the present embodiment, settlement is completed for the first time by a method approved or determined based on a contract between parties involved in transaction settlement information (establishment of a debt-debt relationship).

The user system 10 to the clearing organization system 40 are connected by a peer-to-peer network. This peer-to-peer is one of the architectures for communicating between a large number of systems, and is a base system of a communication system in which peers communicate with each other. For example, a block chain method can be used to prevent falsification of information. In the blockchain method, “blocks” that are a collection of “transaction records” are added sequentially in a “chain” fashion. Each block that constitutes the block chain is composed of a "header" that contains information about the block and the immediately preceding block, and a "transaction" that records a list of transactions performed within a certain time. In the blockchain, since all transaction records from the past are recorded, if it is attempted to make a fraud, it is necessary to rewrite all the blocks after the fraud, which makes the computation load large and falsification difficult. Then, each system connected to the peer-to-peer network will share the information transmitted by one peer in a distributed manner.

Then, each of the user system 10 to the clearing house system 40 holds a distributed ledger D1 for storing information shared in the peer-to-peer network. When predetermined information is written in the distributed ledger D1 of one system, the same distributed information is written in the distributed ledger D1 owned by all other systems by the peer-to-peer network.

(Example of hardware configuration)
FIG. 2 is a hardware configuration example of the information processing device H10 that functions as the user system 10 to the clearing organization system 40 and the like.

The information processing device H10 includes a communication device H11, an input device H12, a display device H13, a storage unit H14, and a processor H15. Note that this hardware configuration is an example, and other hardware may be included.

The communication device H11 is an interface that establishes a communication path with another device and transmits/receives data, and is, for example, a network interface card or a wireless interface.

The input device H12 is a device that receives an input from a user or the like, and is, for example, a mouse or a keyboard. The display device H13 is a display, a touch panel, or the like that displays various information.

The storage unit H14 is a storage device (for example, the information storage unit M2) that stores data and various programs for executing various functions of the user system 10 to the clearing organization system 40. For example, the storage unit H14 stores the information shown in the information storage unit M2. Examples of the storage unit H14 include a ROM, a RAM, a hard disk, and the like.

The processor H15 controls each process in the user system 10 to the clearing organization system 40 (for example, the process in the ledger management unit M1) using the programs and data stored in the storage unit H14. Examples of the processor H15 include CPU and MPU. The processor H15 expands a program stored in a ROM or the like into a RAM and executes various processes corresponding to various processes. For example, when the application program of the user system 10 to the clearing organization system 40 is activated, the processor H15 operates a process that executes each process shown in FIGS. 5 and 6 described later.

The processor H15 is not limited to performing software processing for all the processing executed by itself. For example, the processor H15 may include a dedicated hardware circuit (for example, an application specific integrated circuit: ASIC) that performs a hardware process for at least a part of the process executed by itself. That is, the processor H15 includes (1) one or more processors that operate according to a computer program (software), (2) one or more dedicated hardware circuits that execute at least a part of various processes, or ( 3) A combination of them can be configured as a circuit including. The processor includes a CPU and memories such as RAM and ROM, and the memory stores program codes or instructions configured to cause the CPU to perform processing. Memory or computer readable media includes any available media that can be accessed by a general purpose or special purpose computer.

(Functions of each information processing device)
As shown in FIG. 3, each of the user system 10 to the clearing organization system 40 includes a ledger management unit M1 and an information storage unit M2. The ledger management unit M1 writes the information written in the information storage unit M2 of its own system into the distributed ledger D1 of the information storage unit M2 of another system connected to the peer-to-peer network.

The user system 10 shown in FIG. 3A is a computer system used by an orderer of a buy order or a sell order. The user system 10 includes a control unit 11. The control unit 11 generates order information according to the input of the orderer and transmits it to the exchange system 20.

The exchange system 20 illustrated in FIG. 3B is a computer system of an exchange that acquires order information (buying order, selling order) of each orderer and manages the execution of orders whose order conditions match. The exchange system 20 includes a transaction management unit 21, a participant information storage unit 22, and a transaction information storage unit 24.

The transaction management unit 21 performs a process of matching a sell order and a buy order for each issue and establishing a contract. For this reason, the transaction management unit 21 holds a predetermined rule for the condition for establishing a contract. As a rule, for example, the timing (every hour, every day) at which a contract is fulfilled, or a condition for specifying an order to be fulfilled when a plurality of identical orders are recorded on the distributed ledger D1 (time priority or lottery, etc.) ).
In addition, when the orderer holds an account in another settlement account management institution, the transaction management unit 21 makes a settlement approval request.

In the participant information storage unit 22, participant management information for managing the participants of the exchange is recorded. The participant code and the holding account are recorded in the participant management information.
In the participant code data area, data regarding an identifier for identifying a participant (orderer) of the exchange is recorded.

In the holding account data area, data regarding an identifier for specifying the account of the settlement account management institution of this participant is recorded. When the participant himself/herself is a clearing account management institution, data regarding an identifier for specifying the account of the clearing account management institution of the participant itself is recorded. In addition, when an account is held in another settlement account management institution, data relating to another settlement account management institution and an identifier for identifying the account is recorded.

The transaction information storage unit 24 records transaction management information executed based on the order information. In the transaction management information, transaction code, contract date, brand, buy orderer, sell orderer, contracted amount, and quantity information are recorded.

Data relating to an identifier for identifying each order is recorded in the transaction code data area.
In the trade date data area, data regarding the date and time when the contract is established is recorded.

In the issue data area, data relating to an identifier for identifying a trade object (security issue) that has been executed is recorded.

In the buy orderer and sell orderer data areas, data relating to identifiers for identifying the buy orderer and the sell orderer of the brand of the trade that has been executed are recorded.
In the contracted amount data area, data on the contracted amount of transaction is recorded.
In the quantity data area, data relating to the executed trade quantity is recorded.

The settlement account management institution system 30 shown in FIG. 3C is a computer system of a financial institution that manages the account of each orderer. The settlement account management system 30 includes an account management unit 31 and an account information storage unit 32.
The account management unit 31 executes processing for managing the orderer's account. In this embodiment, in response to an approval request from the exchange system 20, it is confirmed that the orderer's account has a balance, and then the payment is approved.

The account information storage unit 32 records account management information for managing the account held by the orderer in the settlement account management institution. A participant code, an account identifier, a balance, and a deposit/withdrawal history are recorded in this account management information.

In the participant code data area, data regarding an identifier for identifying a participant (orderer) of the exchange is recorded.
In the account identifier data area, data regarding an identifier for identifying the participant's account is recorded.
Data relating to the balance of this account is recorded in the balance data area.
In the deposit/withdrawal history data area, history information on deposits/withdrawals to/from this account is recorded.

The clearing organization system 40 shown in FIG. 3D is a computer system of a clearing organization (CCP: Central Counterparty) that clears settlement between orderers based on the transaction information acquired from the exchange. A clearing account management institution, etc. participates in the clearing at the clearing institution. Even if the orderer is the clearing account management organization, he/she will participate in this clearing. The clearing organization system 40 includes a clearing management unit 41 and a payment information storage unit 42.

The clearing management unit 41 performs settlement (DVP settlement in the present embodiment) for a transaction performed on the exchange system 20. Then, the clearing management unit 41 generates clearing schedule information based on the netting and records it in the distributed ledger D1.

In the payment information storage unit 42, payment schedule information in which netting is performed on the trades that have been executed is recorded. The settlement schedule information includes information on the scheduled settlement date, the settlement account management organization, the issue, the scheduled settlement amount, and the scheduled settlement amount.

In the scheduled settlement date data area, data relating to the scheduled date for DVP settlement is recorded.
In the settlement account management institution data area, data regarding an identifier for identifying the settlement account management institution is recorded.

In the issue data area, data relating to an identifier for identifying a trade object (security issue) that has been executed is recorded.
Data relating to the quantity of securities scheduled to be settled and the planned payment amount are recorded in the respective data areas of the planned settlement quantity and the planned payment amount.

(Information recorded in the distributed ledger)
As shown in FIG. 4, order information 510, contract establishment information 520, revocation information 530, approval request information 540, settlement approval information 550, settlement notice information 560, and settlement completion information 570 are recorded in the distributed ledger D1.

As shown in FIG. 4A, the order information 510 includes information on the issue number, brand, trade identifier, orderer, limit price, and quantity. This order information 510 is encrypted with a key that can be decrypted by a person involved in the main transaction (the user system 10 to the clearing organization system 40 etc.), if necessary.

Data relating to an identifier for specifying an order for trading is recorded in the issue number data area. In the embodiment, this issue number is used as an identifier for specifying a series of information recorded in the distributed ledger D1.
Data relating to an identifier for identifying the securities to be traded is recorded in the issue data area.

A flag for identifying "sale" or "buy" is recorded in the trade identifier data area.
In the orderer data area, data regarding an identifier for identifying the orderer of this order is recorded.

In the limit data area, data relating to the desired transaction price of this issue is recorded.
In the quantity data area, data relating to the desired trading quantity of this issue is recorded.

As shown in FIG. 4B, the contract establishment information 520 includes information about the issue number, brand, buy orderer, sell orderer, contracted amount, and quantity. The contract establishment information 520 is encrypted with a key that can be decrypted by a person involved in the transaction (user system 10 to clearing organization system 40, etc.) as necessary.
In the issue number data area, data relating to an identifier for identifying the executed transaction is recorded. Here, the issue numbers of the buy order and the sell order (for example, the issue number of the order information 510) are included.
Data relating to an identifier for identifying the securities to be traded is recorded in the issue data area.

In each of the data areas of the buy orderer and the sell orderer, data relating to an identifier for identifying the buy orderer and the sell orderer of the executed order is recorded.
In the respective data areas of the contracted amount and the quantity, data relating to the contracted amount and the quantity of the contracted transaction are recorded.

As shown in FIG. 4C, the revocation information 530 includes an issue number and information regarding order revocation. This revocation information 530 is encrypted by a key that can be decrypted by a person involved in the main transaction (user system 10 to clearing organization system 40 etc.), if necessary.
In the issue number data area, data relating to an identifier (for example, the issue number of the order information 510) for specifying an order for trading is recorded.
A flag indicating that this order has not been contracted with another order is recorded in the order expiration data area.

As shown in FIG. 4D, the approval request information 540 includes information on the issue number, brand, trade identifier, orderer, contract amount, quantity, and settlement account management institution. The approval request information 540 is encrypted with a key that can be decrypted by a person involved in the main transaction (the user system 10 to the clearing organization system 40 etc.) if necessary.

In the issue number data area, data relating to an identifier (for example, the issue number of the order information 510) for identifying the executed transaction is recorded.
In the brand data area, data relating to an identifier for identifying the contract to be traded is recorded.

In the trade identifier data area, a flag for identifying “sale” or “buy” of the contracted trade object is recorded.
In the orderer data area, data regarding an identifier for identifying an orderer who is a participant of this exchange is recorded.
In the respective data areas of the contracted amount and the quantity, data relating to the contracted amount and the quantity of the contracted transaction are recorded.
In the settlement account management institution data area, data relating to an identifier for identifying a settlement account management institution that the orderer holds an account and requesting transaction approval is recorded.

As shown in FIG. 4E, the settlement approval information 550 includes information on the issue number, brand, trade identifier, orderer, settlement account management organization, and approval result. The settlement approval information 550 is encrypted by a key that can be decrypted by a person involved in the main transaction (the user system 10 to the clearing organization system 40 etc.) if necessary.

In the issue number data area, data relating to an identifier (for example, the issue number of the order information 510) for identifying the executed transaction is recorded.
In the brand data area, data relating to an identifier for identifying the contract to be traded is recorded.

In the trade identifier data area, a flag for identifying “sale” or “buy” of the contracted trade object is recorded.
In the orderer data area, data regarding an identifier for identifying an orderer who is a participant of this exchange is recorded.

In the settlement account management institution data area, data regarding an identifier for identifying the settlement account management institution that has approved the transaction is recorded.
A flag for identifying the result of transaction approval is recorded in the approval result data area.

As shown in FIG. 4F, the settlement advance notice information 560 includes information on the issue number, the settlement target person, the scheduled settlement date and time, and the settlement contents. The settlement advance notice information 560 is encrypted with a key that can be decrypted by a person involved in the main transaction (the user system 10 to the clearing organization system 40, etc.) as necessary.
In the issue number data area, data relating to an identifier for specifying a settlement advance notice is recorded.
Data relating to an identifier for identifying a payment target person is recorded in the payment target person data area. Here, the persons to be settled are the orderer and the settlement account management organization (including the case where the participant is the settlement account management organization).

In the scheduled payment date/time data area, data relating to the date and time of payment is recorded.
The contents of the payment target are recorded in the payment contents data area. For example, regarding the orderer's transaction, the total (quantity) of each issue and the total transaction amount are recorded. Regarding the settlement account management institution, the cumulative total (quantity) of each issue and cumulative total of transaction amount are recorded.

As shown in FIG. 4G, the settlement completion information 570 includes an issue number and information regarding settlement completion. This settlement completion information 570 is encrypted with a key that can be decrypted by a person involved in the main transaction (user system 10 to clearing organization system 40, etc.), if necessary.
In the issue number data area, data relating to an identifier for specifying a settlement advance notice is recorded.
In the settlement completion data area, a flag indicating that the DVP settlement regarding the settlement notice is completed is recorded.

(Transaction processing)
Next, the transaction processing will be described with reference to FIGS. Here, for example, as the order information 510 to the payment completion information 570, a colored coin based on an open asset protocol using a block chain is used.

First, as shown in FIG. 5, the user system 10 executes order information registration processing (step S1-1). Specifically, the sell orderer and the buy orderer use the user system 10 to create order information. This order information includes information on the brand, a trade identifier indicating “sell” or “buy”, a limit price, and a quantity. When the order instruction is input, the control unit 11 records the order information 510 and the information storage unit M2. In this case, the ledger management unit M1 writes the order information 510 in the distributed ledger D1 of the information storage unit M2 of the other system connected to the peer-to-peer network.
As shown in FIG. 7, it is assumed that the order information 510 of sell orders s1 to s4 and buy orders b1 to b3 is recorded in the distributed ledger D1.

Next, the exchange system 20 executes a matching process (step S1-2). Specifically, the transaction management unit 21 of the exchange system 20 does not associate the contract establishment information 520 and the revocation information 530 with the issue number in the order information 510 recorded in the distributed ledger D1, and can execute the contract. The order information 510 is specified. Then, the transaction management unit 21 matches the limit price of the buy order and the sell order of the same brand with respect to the order information 510 of each brand, based on a predetermined rule (condition for executing contract execution). Then, the transaction management unit 21 searches for a buy order and a sell order that can be contracted according to the limit price.

Next, the exchange system 20 executes a determination process as to whether or not the contract is established (step S1-3). Specifically, the transaction management unit 21 of the exchange system 20 determines that a contract has been established when a buy order and a sell order that can be contracted can be specified.

When it is determined that the contract has been established (“YES” in step S1-3), the exchange system 20 executes the contract establishment registration process (step S1-4). Specifically, the transaction management unit 21 of the exchange system 20 generates transaction management information based on the order information and records the transaction management information in the transaction information storage unit 24 when there is an executed order. Then, the transaction management unit 21 generates the contract establishment information 520 to which the issue number is given based on the issue numbers of the sell order and the buy order in which the transaction is completed. The contract establishment information 520 includes data on the issue number, the brand of the trade that has been executed, the purchase orderer, the sell orderer, the contracted amount, and the quantity. Then, the ledger management unit M1 of the exchange system 20 records the contract establishment information 520 in the distributed ledger D1 of the information storage unit M2. In this case, the ledger management unit M1 writes the contract establishment information 520 to the distributed ledger D1 of the information storage unit M2 of the other system connected to the peer-to-peer network.

As shown in FIG. 7, it is assumed that a "sale order s1 and buy order b3", a "sale order s2 and buy order b1", and a "sale order s4 and buy order b2" are fulfilled. In this case, the contract establishment information 520 is recorded for each contract establishment in the distributed ledger D1.

On the other hand, when there is no contractable order and it is determined that the contract has not been established (“NO” in step S1-3), the exchange system 20 skips the contract establishment registration process (step S1-4).

Next, the exchange system 20 executes a revocation registration process for orders other than contracted orders (step S1-5). Specifically, the transaction management unit 21 of the exchange system 20 identifies the order information 510 that has not been fulfilled in the order information 510 recorded in the distributed ledger D1. Then, the transaction management unit 21 generates revocation information 530 in which the specified issue number of the order information 510 is recorded, and records the revocation information 530 in the distributed ledger D1 of the information storage unit M2. In this case, the ledger management unit M1 writes the revocation information 530 to the distributed ledger D1 of the information storage unit M2 of the other system connected to the peer-to-peer network.

Next, as shown in FIG. 6, the exchange system 20 executes a determination process as to whether or not another settlement account management institution is registered (step S2-1). Specifically, the transaction management unit 21 of the exchange system 20 uses the participant information storage unit 22 to specify the settlement account management institution of the orderer (participant) that has been contracted. In this case, there are cases where the participant himself/herself is a settlement account management institution and cases where the participant is a settlement account management institution user who holds an account of another settlement account management institution. When other settlement account management institution information is recorded in the participant management information of at least one orderer, it is determined that another settlement account management institution is registered.

If it is determined that another settlement account management institution is registered (“YES” in step S2-1), the exchange system 20 executes approval request processing (step S2-2). Specifically, the transaction management unit 21 of the exchange system 20 uses the participant information storage unit 22 to specify the account held by the orderer in another settlement account management institution. Then, the transaction management unit 21 generates approval request information 540 for requesting approval of the payment to the other specified payment account management institution. This approval request information 540 includes data relating to the issue number, brand, trade identifier, orderer, contracted amount, quantity, and settlement account management institution. Then, the ledger management unit M1 of the exchange system 20 records the approval request information 540 in the distributed ledger D1 of the information storage unit M2. In this case, the ledger management unit M1 writes the approval request information 540 in the distributed ledger D1 of the information storage unit M2 of the other system connected to the peer-to-peer network.
On the other hand, when determining that there is no registration of another settlement account management institution (“NO” in step S2-1), the exchange system 20 skips the approval request process (step S2-2).

Next, the exchange system 20 executes a determination process as to whether the orderer is a settlement account management institution (step S2-3). Specifically, the transaction management unit 21 of the exchange system 20 uses the participant information storage unit 22 to search for an orderer for whom another settlement account management institution is not registered. When the orderer who has not been registered with another settlement account management institution can be specified, the orderer (participant) himself/herself determines that it is the settlement account management institution.

When the orderer determines that it is the settlement account management institution (“YES” in step S2-3), the exchange system 20 executes an automatic approval process (step S2-4). Specifically, the transaction management unit 21 of the exchange system 20 determines that the orderer (participant) himself can make payment, and generates the payment approval information 550 of automatic approval. Then, the transaction management unit 21 records the settlement approval information 550 in the distributed ledger D1 of the information storage unit M2. In this case, the ledger management unit M1 writes the settlement approval information 550 in the distributed ledger D1 of the information storage unit M2 of the other system connected to the peer-to-peer network.
On the other hand, when it is determined that all the orderers are not the settlement account management institution (“NO” in step S2-3), the exchange system 20 skips the automatic approval process (step S2-4).

The payment account management institution system 30 that has acquired the approval request information 540 executes a payment approval process (step S2-5). Specifically, the account management unit 31 of the settlement account management institution system 30 identifies the orderer's account in the account information storage unit 32 using the approval request information 540 recorded in the distributed ledger D1. Next, the account management unit 31 generates the settlement approval information 550 when the orderer's account balance allows settlement. Then, the ledger management unit M1 of the settlement account management institution system 30 records the settlement approval information 550 in the distributed ledger D1 of the information storage unit M2. In this case, the ledger management unit M1 writes the settlement approval information 550 in the distributed ledger D1 of the information storage unit M2 of the other system connected to the peer-to-peer network.

As shown in FIG. 7, “sale order s1”, “sale order s2”, “buy order b1”, and “buy order b2” are assumed to use a settlement account management institution other than an exchange. In this case, the settlement approval information 550 for each contract is recorded in the distributed ledger D1.

Next, the clearing organization system 40 executes the aggregation process using the distributed ledger D1 (step S2-6). Specifically, the clearing management unit 41 of the clearing organization system 40 uses the payment approval recorded in the distributed ledger D1 to total the transaction contents of the approved (including automatic approval) payment account management organization. Here, the contracted amount and the total contracted amount are totaled for each brand.

Next, the clearinghouse system 40 executes a settlement advance notice process using the distributed ledger D1 (step S2-7). Specifically, the clearing management unit 41 of the clearing organization system 40 collects the contracted amount and contracted amount (contracted amount, contracted amount) for each participant (orderer or settlement account management institution) of the clearing institution. The settlement advance notice information 560 including "" is generated. The ledger management unit M1 of the clearing organization system 40 records the settlement advance notice information 560 in the distributed ledger D1 of the information storage unit M2. In this case, the ledger management unit M1 writes the settlement advance notice information 560 in the distributed ledger D1 of the information storage unit M2 of the other system connected to the peer-to-peer network.

As shown in FIG. 7, the settlement advance notice information 560 is recorded in the distributed ledger D1 for each participant in the clearing organization and the settlement account management organization.

Next, the clearinghouse system 40 executes a DVP settlement process (step S2-8). Specifically, the clearing management unit 41 of the clearing organization system 40 performs the DVP payment when the scheduled payment date and time of the payment announcement information 560 is reached.

Next, the clearing organization system 40 executes a payment completion registration process (step S2-9). Specifically, the clearing management unit 41 of the clearing organization system 40 generates payment completion information 570. Then, the ledger management unit M1 of the clearing organization system 40 records the settlement completion information 570 in the distributed ledger D1 of the information storage unit M2. In this case, the ledger management unit M1 writes the payment completion information 570 in the distributed ledger D1 of the information storage unit M2 of the other system connected to the peer-to-peer network.
As shown in FIG. 7, the payment completion information 570 corresponding to the payment advance information 560 is recorded in the distributed ledger D1.

According to this embodiment, the following effects can be obtained.
(1) In this embodiment, order information 510, contract establishment information 520, revocation information 530, approval request information 540, settlement approval information 550, settlement notice information 560, and settlement completion information 570 are recorded in the distributed ledger D1. Thereby, the person involved in the transaction can confirm the transaction content and transaction status. Then, the distributed ledger D1 using the block chain uses the information sharing technology by the distributed ledger and the tampering prevention technology of the record by the block chain and the like, the contents of the record are unchanged, and the collation of the record is easy, It can support quick and efficient securities transactions, that is, a series of processing from execution to settlement.

(2) In the present embodiment, the user system 10 executes order information registration processing (step S1-1). The exchange system 20 also executes a matching process (step S1-2) and a determination process (step S1-3) as to whether or not a contract is established. Then, when it is determined that there is an order that can be executed (in the case of “YES” in step S1-3), the exchange system 20 executes the contract establishment registration process (step S1-4). As a result, among a plurality of orders for a particular issue, orders that meet the conditions can be executed based on a predetermined rule, and the orders can be completed.

(3) In the present embodiment, the exchange system 20 executes a revocation registration process for orders other than contracted orders (step S1-5). As a result, the order information 510 that could not be filled can be revoked on the distributed ledger to complete the order.

(4) In the present embodiment, when it is determined that another settlement account management institution is registered (“YES” in step S2-1), the exchange system 20 executes approval request processing (step S2). -2). Then, the settlement account management institution system 30 executes settlement approval processing (step S2-5). As a result, even when the orderer's account is managed outside the exchange, the settlement procedure can be advanced based on the approval recorded in the distributed ledger D1.

(5) In the present embodiment, when the orderer determines that it is a settlement account management institution (“YES” in step S2-3), the exchange system 20 executes an automatic approval process (step S2-4). .. As a result, when the orderer is the settlement account management organization, the settlement procedure can proceed based on the approval recorded in the distributed ledger D1.

(6) In the present embodiment, the clearing organization system 40 uses the distributed ledger D1 for aggregation processing (step S2-6), the distributed ledger D1 for settlement advance notice processing (step S2-7), and DVP settlement processing (step S2-6). Execute S2-8). As a result, the individual transactions can be aggregated and efficiently settled.

This embodiment can be modified and implemented as follows. The present embodiment and the following modified examples can be implemented in combination with each other within a technically consistent range.
In the above embodiment, the case where the open asset protocol (colored coin) that uses the block chain of Bitcoin is used as the order information 510 to the payment completion information 570 is assumed. The information recorded in the distributed ledger D1 is not limited to colored coins. It is possible to use a basic system, which is a distributed ledger D1 other than bitcoin, and whose main purpose is to have a role/function other than currency.

In the above embodiment, the order information 510 to the payment completion information 570 are recorded in the distributed ledger D1. The information recorded in the distributed ledger D1 is not limited to these.
-In the said embodiment, the clearing organization system 40 performs the totalization process (step S2-6) using the distributed ledger D1, and the settlement advance notice process (step S2-7) using the distributed ledger D1. Here, information linking the contracted transaction information and the settlement notice collected for each settlement account management institution may be recorded in the distributed ledger D1.
In the above-described embodiment, the clearing organization system 40 performs the aggregation process using the distributed ledger D1 (step S2-6), the settlement advance notice process on the distributed ledger D1 (step S2-7), and the DVP settlement process (step S2-8). To execute. In this case, each participant may check the contents of the settlement notice and record the settlement notice approval information in the distributed ledger D1. In this case, the clearinghouse system 40 executes the DVP settlement process based on the settlement advance notice approval information (step S2-8).

-In the above-mentioned embodiment, exchange system 20 performs contract establishment registration processing (Step S1-4). In this case, the transaction management unit 21 generates the contract completion information 520 to which the issue number is given based on the issue numbers of the sell order and the buy order in which the contract is established. Here, the information associating the contract establishment information 520 and each order information 510 is not limited to the issue number. For example, the contract establishment information 520 may include the issue number of each order information 510.
Further, the contract establishment information 520 may be generated for each order information 510. In this case, the issue number of the order information of the counterparty who made the transaction is recorded in the agreement establishment information 520.
In the above embodiment, the information recorded in the distributed ledger D1 is encrypted with a key that can be decrypted by the parties involved in the main transaction, if necessary. The necessity of encryption may be made according to the network and information. For example, in the case of a closed type (private type) network used only by parties concerned, encryption is not necessary.
In the above embodiment, the issue number of the order information 510 or the like is used as an identifier for identifying a series of information recorded in the distributed ledger D1. The issue number of the order information 510 is not limited as long as it is an identifier that can specify a series of information.

10... User system, 11... Control unit, 20... Exchange system, 21... Transaction management unit, 22... Participant information storage unit, 24... Transaction information storage unit, 30... Settlement account management institution system, 31... Account management unit , 32... Account information storage unit, 40... Clearing agency system, 41... Clearing management unit, 42... Settlement information storage unit, D1... Distributed ledger, M1... Ledger management unit, M2... Information storage unit.

Claims (6)

The exchange system connected to the orderer system is a payment system including a clearing organization system connected via a base system that can confirm the validity of information by a distributed ledger,
The exchange system is
Acquired order information that can be filled and recorded in the distributed ledger,
By matching the acquired order information, the contracted order information is specified,
For the unfilled order information, record the revocation information in the distributed ledger,
When it is determined that the orderer of the contracted order information is a settlement account management institution, the settlement authorization information for performing settlement using the account of the settlement account management institution is recorded in the distributed ledger,
The clearing system is
A payment system, wherein payment is performed based on the contracted order information. The exchange system connected to the orderer system is a payment system including a clearing organization system connected via a base system that can confirm the validity of information by a distributed ledger,
The exchange system is
Acquired order information that can be filled and recorded in the distributed ledger,
By matching the acquired order information, the contracted order information is specified,
For the unfilled order information, record the revocation information in the distributed ledger,
If at least one of the orderer and the contractor of the contracted order information determines that it is a settlement account management institution user who has registered other than himself as a settlement account management institution, the settlement account management institution user Send an approval request to the settlement account management system of
The clearing system is
A settlement system, wherein when settlement approval information of the settlement account management institution system is recorded in the distributed ledger, settlement is performed based on the contracted order information. The clearing system is
Based on the contracted order information, record a payment notice in the distributed ledger,
Payment system according to claim 1 or 2, characterized in that to settle after the payment notice. The settlement system according to claim 3 , wherein the clearing agency system aggregates the transaction amount for each trader of the contracted order information and gives the settlement notice. A method in which an exchange system connected to an orderer system supports payment by using a payment system including a clearing organization system connected via a base system that can confirm the validity of information by a distributed ledger,
The exchange system is
Acquired order information that can be filled and recorded in the distributed ledger,
By matching the acquired order information, the contracted order information is specified,
For the unfilled order information, record the revocation information in the distributed ledger,
When it is determined that the orderer of the contracted order information is a settlement account management institution, the settlement authorization information for performing settlement using the account of the settlement account management institution is recorded in the distributed ledger,
The clearing system is
A payment method, wherein payment is made based on the contracted order information. A method in which an exchange system connected to an orderer system supports payment by using a payment system including a clearing organization system connected via a base system that can confirm the validity of information by a distributed ledger,
The exchange system is
Acquired order information that can be filled and recorded in the distributed ledger,
By matching the acquired order information, the contracted order information is specified,
For the unfilled order information, record the revocation information in the distributed ledger,
If at least one of the orderer and the contractor of the contracted order information determines that it is a settlement account management institution user who has registered other than himself as a settlement account management institution, the settlement account management institution user Send an approval request to the settlement account management system of
The clearing system is
A settlement method comprising performing settlement based on the contracted order information when settlement approval information of the settlement account management institution system is recorded in the distributed ledger.

Images