JP6946256B2 - Payment system and payment method - Google Patents

Description

The present invention relates to a payment system and a payment method for settling a transaction.

Blockchain technology utilizing a peer-to-peer network is being used for payments and the like (see, for example, Non-Patent Document 1). In the technology described in Non-Patent Document 1, a mechanism is studied in which contract information can be instantly shared and settled as tamper-proof data without newly constructing a large-scale payment system by utilizing a blockchain. ing. This blockchain technology prevents retroactive changes in the data in a block by continuously managing the ordered records in a distributed ledger.

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

In addition, a technique for supporting transactions by using a distributed blockchain computing system including a plurality of computing nodes is also being studied (see, for example, Patent Document 2). In this technology, the exchange stores purchase orders and multiple digital wallets associated with different clients. The computer system receives new data transaction requests that are added to the purchase order. Matches between data transaction requests are identified and a hash associated with the digital wallet associated with the individual data transaction request is generated. The counterparty receives the counterparty's hash 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.

In addition, a payment support system and a payment support method for supporting payment by using a basic system that can confirm the validity of debt record information using distributed ledger technology are also being studied (for example, Patent Document 3). reference). This technology uses a basic system that is connected to the payer terminal and the payer financial institution server and can confirm the validity of information by distributed ledger technology such as blockchain. The payer terminal acquires payment method selection information from the debtor to the creditor, records the debt record information of the selected payment method in the distributed ledger, and sends it to the payer financial institution server according to the selected payment method. Notify the issuance 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 stores the revocation information of the debt record information in the distributed ledger. Record.

Japanese Unexamined Patent Publication No. 2016-151802 Special Table 2018-515833 Japanese Patent No. 6363254

Mizuho Bank, Ltd., "Implementing a Demonstration Experiment to Improve the Efficiency of Settlement Processes for Cross-Border Securities Transactions", March 8, 2016, [online], Mizuho Bank, Ltd., [September 9, 2018 Day search], Internet <https://www.mizuhobank.co.jp/release/pdf/20160308release_jp.pdf>

For example, in online transactions, the timing of product provision and payment does not always match. Therefore, an escrow service may be used in which a third party secures funds for payment and pays the funds to the other party based on predetermined conditions. However, if information cannot be efficiently shared with payers, recipients, and third parties, the procedure becomes complicated.

In the payment system that solves the above problems, the payer system of the payer in the transaction and the payer account of the payer and the payee who made the transaction and the financial institution system in which the payee account is opened are informationed by the distributed ledger. Use a payment system connected via a basic system that can confirm the validity of. Then, the payer system registers the withdrawal information in the distributed ledger based on the transaction contract, and the financial institution system in which the payer account is opened registers the approval information for the withdrawal information in the distributed ledger. The financial institution system that has registered and opened the beneficiary account confirms in the distributed ledger the information that satisfies the payment conditions of the withdrawal information, and based on the satisfaction of the payment conditions, the above is added to the beneficiary account. The payment process is executed based on the withdrawal information, and the financial institution system in which the payer account is opened records the transaction completion information regarding the withdrawal information in the distributed ledger.

According to the present invention, it is possible to support efficient 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 diagram of this embodiment. Explanatory drawing of hardware configuration example. An explanatory diagram of each system of the present embodiment, (a) is a payer system, (b) is a payee system, and (c) is an explanatory diagram of a financial institution system. It is explanatory drawing of the information recorded in the distributed ledger in this embodiment, (a) is a drawing information, (b) is approval information, (c) is payment information, (d) is settlement completion information, (e) Is an explanatory diagram of revocation information. The explanatory view of the processing procedure of this embodiment. Schematic diagram of the system of another embodiment. Explanatory drawing of information recorded in a distributed ledger in another embodiment. Explanatory drawing of the processing procedure of another embodiment.

(First Embodiment)
Hereinafter, an embodiment in which a payment system and a payment method are embodied will be described with reference to FIGS. 1 to 5. In the present embodiment, a transaction is performed between the payer and the beneficiary, and settlement of the transaction is supported. For example, the payer is the purchaser of the transaction object (commodity), and the recipient is the seller of this commodity.

As shown in FIG. 1, in the present embodiment, the payer system 10, the payee system 20, and the financial institution systems 30 and 40 connected to the distributed ledger D1 are used. In the present embodiment, it is assumed that the settlement is supported by using the basic system that can confirm the validity of the record of the transaction settlement information by the blockchain. It should be noted that the case where the distributed ledger D1 (distributed ledger) that holds the same data among a plurality of nodes connected to the network is used is not limited to the case where the blockchain technology is used. The transaction settlement information electronically records information related to the settlement of a financial institution, and the transaction settlement information is recorded in the distributed ledger D1 and fixed by the blockchain technology. Further, unlike the so-called virtual currency, the settlement itself is not completed by this record itself, and only the information related to the withdrawal-settlement is recorded. In the present embodiment, the settlement is completed only by the method approved or determined based on the contract between the parties involved in the transaction settlement information (establishment of the debt-credit relationship).

The payer system 10 to the financial institution 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 basic system of a communication method in which peers communicate with each other. For example, a blockchain method can be used to prevent falsification of information. In the blockchain method, "blocks" that summarize "transaction records" are sequentially added in the form of "chains". Each block that makes up a blockchain is composed of a "header" that contains information about that block and the previous block, and a "transaction" that records a list of transactions made within a certain period of time. In the blockchain, all transaction records from the past are recorded, so if an attempt is made to commit fraud, it is necessary to rewrite all blocks after fraud, which increases the calculation load and makes falsification difficult. Then, each system connected to the peer-to-peer network will distribute and share the information transmitted by one peer.

The payer system 10 to the financial institution system 40 each hold a distributed ledger D1 that stores 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 the other systems by the peer-to-peer network.

(Hardware configuration example)
FIG. 2 is a hardware configuration example of an information processing device H10 that functions as a payer system 10 to a financial institution 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 executes data transmission / reception, such as a network interface card or a wireless interface.

The input device H12 is a device that receives input from a user or the like, and is, for example, a mouse, a keyboard, or the like. 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, an information storage unit M2 described later) that stores data and various programs for executing various functions of the payer system 10 and the financial institution system 40. For example, the storage unit H14 stores the information shown in the information storage unit M2. An example of the storage unit H14 is a ROM, a RAM, a hard disk, or the like.

The processor H15 controls each process in the payer system 10 to the financial institution system 40 (for example, the process in the ledger management unit M1 described later) by using the program or data stored in the storage unit H14. Examples of the processor H15 include a CPU, an MPU, and the like. 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 payer system 10 to the financial institution system 40 is started, the processor H15 operates a process of executing each process shown in FIG. 5 described later.

The processor H15 is not limited to the one that performs software processing for all the processing executed by itself. For example, the processor H15 may include a dedicated hardware circuit (for example, an integrated circuit for a specific application: ASIC) that performs hardware processing for at least a part of the processing executed by the processor H15. That is, the processor H15 is (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) It can be configured as a circuitry including a combination thereof. The processor includes a CPU and a memory such as a RAM and a ROM, and the memory stores a program code or a command configured to cause the CPU to execute a process. Memory or computer-readable medium includes any available medium accessible by a general purpose or dedicated computer.

(Functions of each information processing device)
As shown in FIG. 3, the payer system 10, the payee system 20, the financial institution system 30, and 40 include a ledger management unit M1 and an information storage unit M2, respectively. 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 payer system 10 shown in FIG. 3A is a computer system used by the payer (purchaser of goods). The payer system 10 includes a control unit 11. The control unit 11 generates the drawing information according to the input of the payer and records it in the distributed ledger D1.

The payee system 20 shown in FIG. 3B is a computer system of a product seller who conducts a transaction with a payer. The payee system 20 includes a transaction management unit 21 and a transaction information storage unit 22.
The transaction management unit 21 performs a process of managing transactions with the payer.

The transaction information storage unit 22 records transaction management information regarding transactions with the payer. Information on the transaction code, transaction date and time, purchaser, and transaction details is recorded in this transaction management information.

In the transaction code data area, data regarding an identifier for identifying each transaction is recorded.
Data related to the date and time of the transaction are recorded in the transaction date / time data area.

In the purchaser data area, data for identifying the product purchaser (payer) who has made a transaction is recorded.
Data related to the product type and product quantity to be sold are recorded in the transaction content data area.

The financial institution systems 30 and 40 shown in FIG. 3C are computer systems of a financial institution that manage the accounts of customers (payers and payees) of the financial institution. The financial institution systems 30 and 40 include account management units 31 and 41 and account information storage units 32 and 42, respectively.

The account management units 31 and 41 execute a process of managing the customer's account. In the present embodiment, payment is approved after confirming that there is a balance in the payer's account according to the withdrawal information from the payee system 20.

Account management information for managing accounts opened in financial institutions is recorded in the account information storage units 32 and 42. In this account management information, an account identifier, an account holder, a balance, and a deposit / withdrawal history are recorded.

In the account identifier data area, data regarding an identifier for identifying an account opened in a financial institution is recorded.
In the account holder data area, data regarding an identifier for identifying the holder (payer or payee) of this account is recorded.

Data regarding the balance of this account is recorded in the balance data area.
In the deposit / withdrawal history data area, history information of deposits to / from this account and withdrawals from this account is recorded.

(Information recorded in the distributed ledger)
As shown in FIG. 4, the distributed ledger D1 records the withdrawal information 510, the approval information 520, the payment information 530, the settlement completion information 540, and the revocation information 550.

As shown in FIG. 4A, the withdrawal information 510 includes information on the issue number, transaction code, payer, payee, payer financial institution, payee financial institution, amount, and payment conditions. In the present embodiment, the drawing information 510 is encrypted with a key that can be decrypted by the parties involved in the transaction (payer system 10 to financial institution system 40, etc.), if necessary.

In the issue number data area, data relating to an identifier for identifying the drawing information 510 is recorded.
In the transaction code data area, data regarding an identifier for identifying a transaction between a payer and a payee is recorded. In the present embodiment, the transaction code is used to associate a series of information (drawing information 510 to revocation information 550) recorded in the distributed ledger D1.

In each of the payer and payee data areas, data regarding an identifier for identifying the payer and payee who made the transaction is recorded, respectively.
In each data area of the payer financial institution and the payee financial institution, data regarding an identifier for identifying the financial institution in which the payer and the payee have opened an account is recorded, respectively.

The monetary data area records data about the amount paid by the payer for the transaction.
The deposit condition data area records data regarding conditions for a financial institution to deposit money into a recipient's account based on a transaction contract between the payer and the recipient.

As shown in FIG. 4B, the approval information 520 includes information on the issue number, transaction code, payer financial institution, and approval result. In the present embodiment, the approval information 520 is also encrypted with a key that can be decrypted by the parties involved in the transaction (payer system 10 to financial institution system 40, etc.), if necessary.
In the issue number data area, data regarding an identifier for identifying the approval information 520 is recorded.

In the transaction code data area, data regarding an identifier for identifying a transaction between a payer and a payee is recorded.
In the payer financial institution data area, data regarding an identifier for identifying the financial institution in which the payer holds an account is recorded.

In the approval result data area, a flag for specifying the approval result for the withdrawal using the account is recorded.

As shown in FIG. 4C, the deposit information 530 includes an issue number, a transaction code, and information about the payee financial institution. In the present embodiment, the deposit information 530 is also encrypted with a key that can be decrypted by the parties involved in the transaction (payer system 10 to financial institution system 40, etc.), if necessary.
In the issue number data area, data regarding an identifier for identifying the deposit information 530 is recorded.
In the transaction code data area, data regarding an identifier for identifying a transaction to be drawn out is recorded.
In the beneficiary financial institution data area, data regarding an identifier for identifying the financial institution in which the beneficiary holds an account is recorded.

As shown in FIG. 4D, the settlement completion information 540 includes information regarding the issue number, transaction code, payment conditions, payer financial institution, and settlement completion. In the present embodiment, the settlement completion information 540 is also encrypted with a key that can be decrypted by the parties involved in the transaction (payer system 10 to financial institution system 40, etc.), if necessary.

In the issue number data area, data regarding an identifier for identifying the settlement completion information 540 is recorded.
In the transaction code data area, data regarding an identifier for identifying a transaction between a payer and a payee is recorded.

In the deposit condition data area, data related to the deposit condition in the withdrawal is recorded.
In the payer financial institution data area, data regarding an identifier for identifying the financial institution in which the payer holds an account is recorded.
A flag indicating that the payment has been completed is recorded in the payment completion data area.

As shown in FIG. 4 (e), the revocation information 550 includes information on the issue number, transaction code, payment conditions, payer financial institution, and revocation. In the present embodiment, the revocation information 550 is also encrypted with a key that can be decrypted by the parties involved in the transaction (payer system 10 to financial institution system 40, etc.), if necessary.

In the issue number data area, data regarding an identifier for identifying revocation information 550 is recorded.
In the transaction code data area, data regarding an identifier for identifying a transaction between a payer and a payee is recorded.

In the deposit condition data area, data related to the deposit condition in the withdrawal is recorded.
In the payer financial institution data area, data regarding an identifier for identifying the financial institution in which the payer holds an account is recorded.
A flag indicating revocation is recorded in the revocation data area.

(Transaction processing)
Next, the transaction process will be described with reference to FIG. Here, for example, as the withdrawal information 510 to the revocation information 550, colored coins by an open asset protocol using a blockchain are used.

As shown in FIG. 5, the payee system 20 executes the payment request processing (step S1-1). Specifically, a transaction is made between the payer system 10 and the payee system 20. For example, the payer system 10 accesses the payee system 20 and sends a purchase request for a desired product. In this case, the payee system 20 transmits a payment request including a transaction code and information about the payee financial institution to the payer system 10.

Next, the payer system 10 executes the drawing information registration process (step S1-2). Specifically, when a payment instruction is input by the payer, the control unit 11 of the payer system 10 creates the drawing information. This withdrawal information includes information about the issue number, transaction code, payer, payee, payer financial institution, payee financial institution, amount, and payment terms. Then, when the drawing instruction is input, the control unit 11 records the drawing information 510 in the information storage unit M2. In this case, the ledger management unit M1 writes the drawing information 510 in the distributed ledger D1 of the information storage unit M2 of the other system connected to the peer-to-peer network.

The financial institution system 30 of the payer financial institution recorded in the withdrawal information 510 executes the confirmation processing of the withdrawal information (step S1-3). Specifically, the account management unit 31 of the financial institution system 30 acquires the withdrawal information 510 recorded by the payer's financial institution without recording the settlement completion information 540 and the revocation information 550 in the distributed ledger D1. do. Then, the account management unit 31 identifies the payer's account in the account information storage unit 32 by using the payer information of the acquired withdrawal information 510. Then, the account management unit 31 compares the account balance of the payer with the amount of the withdrawal information 510.

Next, the financial institution system 30 of the payer financial institution executes the registration process of the approval information (step S1-4). Specifically, the account management unit 31 of the financial institution system 30 deducts the amount of the withdrawal information 510 from the payer's account when it is determined that the payment can be made based on the payer's account balance. Then, the account management unit 31 generates the approval information 520 including the issue number, the transaction code, and the information about the payer financial institution. Then, the ledger management unit M1 of the financial institution system 30 records the approval information 520 in the distributed ledger D1 of the information storage unit M2. In this case, the ledger management unit M1 writes the approval information 520 in the distributed ledger D1 of the information storage unit M2 of the other system connected to the peer-to-peer network. If the payer's account balance is lower than the amount of the withdrawal information 510 and it is determined that the payment cannot be made, the account management unit 31 sends a withdrawal prohibition notification to the payer. The payer who has obtained the non-drawing notice makes a deposit to his / her own account. In this case, the account management unit 31 determines that payment is possible using the account balance of the payer, and executes the subsequent processing.

Next, the financial institution system 40 of the beneficiary financial institution executes a determination process as to whether or not the approval information has been acquired (step S1-5). Specifically, the account management unit 41 confirms whether or not the approval information 520 in which the settlement completion information 540 and the revocation information 550 are recorded and the recipient financial institution information is recorded is registered in the distributed ledger D1. ..

If the approval information 520 has not been acquired (“NO” in step S1-5), the financial institution system 40 of the beneficiary financial institution waits for the acquisition of the approval information.
On the other hand, when the approval information 520 is acquired (when “YES” in step S1-5), the financial institution system 40 of the beneficiary financial institution executes the payment condition satisfaction determination process (step S1-6). Specifically, the account management unit 41 identifies the withdrawal information 510 recorded in the distributed ledger D1 by using the transaction code of the approval information 520. Then, the account management unit 41 acquires the payment conditions recorded in the withdrawal information 510. Next, the account management unit 31 determines whether the current situation satisfies the deposit conditions. For example, when the deposit date is set as the deposit condition, the current date and time and the deposit date are compared. If the deposit conditions are not satisfied, the account management unit 41 waits until the deposit conditions are satisfied.

When it is determined that the payment conditions are satisfied, the financial institution system 40 executes the payment information registration process (step S1-7). Specifically, the account management unit 41 deposits the amount of the withdrawal information 510 into the recipient's account. Then, the account management unit 41 generates the deposit information 530 including the issue number, the transaction code, and the information about the beneficiary financial institution. Then, the ledger management unit M1 of the financial institution system 30 records the deposit information 530 in the distributed ledger D1 of the information storage unit M2. In this case, the ledger management unit M1 writes the deposit information 530 in the distributed ledger D1 of the information storage unit M2 of the other system connected to the peer-to-peer network.

Next, the financial institution system 30 of the payer financial institution executes a determination process as to whether or not the payment information has been acquired (step S1-8). Specifically, the account management unit 31 confirms whether or not the payment information 530 in which the payment completion information 540 and the revocation information 550 are recorded and the payer financial institution information is recorded is registered in the distributed ledger D1. ..

When the payment information 530 is acquired (when “YES” in step S1-8), the financial institution system 30 of the payer financial institution executes the settlement completion information registration process (step S1-9). Specifically, the account management unit 31 generates payment completion information 540 including information on the issue number, transaction code, payer financial institution, and payment completion. Then, the ledger management unit M1 of the financial institution system 30 records the settlement completion information 540 in the distributed ledger D1 of the information storage unit M2. In this case, the ledger management unit M1 writes the settlement completion 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 the payment information 530 has not been acquired (when “NO” in step S1-8), the financial institution system 30 of the payer financial institution executes a determination process as to whether or not the payment conditions are valid (step). S1-10). Specifically, the account management unit 31 confirms whether or not the payment conditions of the withdrawal information 510 are valid in the distributed ledger D1. For example, if the withdrawal information 510 has a valid period set in the payment conditions, it is confirmed whether or not the valid period has been exceeded.

When it is determined that the payment condition is valid (when "YES" in step S1-10), the financial institution system 30 of the payer financial institution performs a determination process (step S1-8) as to whether or not the payment information has been acquired. continue.

On the other hand, if it is determined that the payment condition is not valid (“NO” in step S1-10), the financial institution system 30 of the payer financial institution executes the revocation process of the payment condition (step S1-11). Specifically, the account management unit 31 generates revocation information 550 including information on the issue number, transaction code, payment conditions, payer financial institution, and revocation. Then, the ledger management unit M1 of the financial institution system 30 records the revocation information 550 in the distributed ledger D1 of the information storage unit M2. In this case, the ledger management unit M1 writes the revocation information 550 in the distributed ledger D1 of the information storage unit M2 of the other system connected to the peer-to-peer network.

According to this embodiment, the following effects can be obtained.
(1-1) In the present embodiment, the withdrawal information 510, the approval information 520, the payment information 530, the settlement completion information 540, and the revocation information 550 are recorded in the distributed ledger D1. As a result, the parties involved in the transaction can confirm the transaction details and the transaction status. Then, by using the distributed ledger D1 using the blockchain, the contents of the record are unchanged and the collation of the records is easy by using the information sharing technology by the distributed ledger and the tampering prevention technology of the record by the blockchain or the like. It can support quick and efficient transaction settlement.

(1-2) In the present embodiment, the financial institution system 30 of the payer financial institution executes a confirmation process of drawing information (step S1-3) and a registration process of approval information (step S1-4). When the approval information 520 is acquired (when “YES” in step S1-5), the financial institution system 40 of the beneficiary financial institution executes the payment condition satisfaction determination process (step S1-6). As a result, payment can be made based on the approval information of the payer's financial institution.

When it is determined that the payment conditions are satisfied, the financial institution system 40 executes the payment information registration process (step S1-7). As a result, conditions for making a deposit can be set according to the transaction content.

(1-3) When the payment information 530 is acquired (when “YES” in step S1-8), the financial institution system 30 of the payer financial institution executes the registration process of the payment completion information (step S1-9). ). As a result, the withdrawal information can be completed based on the settlement completion information.

(1-4) In the present embodiment, when it is determined that the payment condition is not valid (when “NO” in step S1-10), the financial institution system 30 of the payer financial institution executes the revocation process of the payment condition. (Step S1-11). As a result, it is possible to invalidate the withdrawal information that could not be deposited.

(Second Embodiment)
Next, a second embodiment that embodies the payment system and the payment method will be described with reference to FIGS. 6 to 8. Since the second embodiment has only a configuration in which the payment conditions are changed, detailed description of the same parts will be omitted. In the first embodiment, the payment is made by satisfying the payment date set as the payment condition. In the second embodiment, the completion of delivery of the transaction (delivery corresponding item) is used as the payment condition.

As shown in FIG. 6, a delivery management system 50 is provided in the peer-to-peer network. Like the payer system 10 and the financial institution system 40, the delivery management system 50 is composed of an information processing device H10, and includes a ledger management unit M1 and an information storage unit M2.

Further, the delivery management system 50 includes a delivery management unit 51 and a delivery information storage unit 52.
The delivery management unit 51 manages the delivery status of the delivered goods.
The delivery information storage unit 52 records information on the delivery status with respect to the tracking number. In this delivery status, information that identifies the start of delivery of the delivery object, the passage of the relay base, and the completion of delivery is recorded.

Further, as shown in FIG. 7, delivery completion information 560 is recorded in the distributed ledger D1.
The delivery completion information 560 includes information on the issue number, transaction code, tracking number, delivery company, and delivery status. In the present embodiment, the delivery completion information 560 is also encrypted with a key that can be decrypted by the parties involved in the transaction (payer system 10 to delivery management system 50, etc.), if necessary.

In the issue number data area, data regarding an identifier for identifying the delivery completion information 560 is recorded.
In the transaction code data area, data regarding an identifier for identifying a transaction between a payer and a payee is recorded.

In the tracking number data area, information regarding an identifier for identifying a delivery target is recorded in the delivery company.
In the delivery company data area, data regarding an identifier for identifying the delivery company that delivers the delivery object is recorded.
Information that identifies the completion of delivery of the delivery object is recorded in the delivery status data area.

In the distributed ledger D1, the drawing information 510 to the revocation information 550 are also recorded in the same manner as in the first embodiment. In the present embodiment, in the withdrawal information 510, in addition to the issue number to the payment condition, information about the delivery company that delivers the transaction is recorded.

(Transaction processing)
Next, the transaction process will be described with reference to FIG.
Here, the payee system 20 executes the payment request processing in the same manner as in step S1-1 (step S2-1), and the payer system 10 performs the payment information registration processing in the same manner as in step S1-2. Execute (step S2-2). The financial institution system 30 of the payer financial institution executes the drawing information confirmation process (step S2-3) and the approval information registration process (step S2-4) in the same manner as in steps S1-3 and S1-4.

Next, the financial institution system 40 of the beneficiary financial institution executes a determination process as to whether or not the approval information has been acquired (step S2-5), as in step S1-5.
If the approval information 520 has not been acquired (“NO” in step S2-5), the financial institution system 40 of the beneficiary financial institution waits for the acquisition of the approval information.

On the other hand, when the approval information 520 is acquired (when “YES” in step S2-5), the financial institution system 40 of the beneficiary financial institution executes the payment condition satisfaction determination process as in step S1-6. (Step S2-6). Here, it is assumed that the delivery completion of the product is recorded as a payment condition and the delivery completion information has not been acquired yet.

In addition, the delivery management system 50 executes a determination process as to whether or not the approval information has been acquired (step S2-7). Specifically, the delivery management unit 51 of the delivery management system 50 registers the approval information 520 in which the settlement completion information 540 and the revocation information 550 are not recorded in the distributed ledger D1 and the recipient financial institution information is recorded. Check for the presence of.

If the approval information 520 has not been acquired (in the case of "NO" in step S2-7), the delivery management system 50 waits for the acquisition of the approval information.
On the other hand, when the approval information 520 is acquired (when "YES" in step S2-7), the delivery management system 50 executes the delivery instruction process (step S2-8). Specifically, the delivery management unit 51 outputs a delivery instruction for the delivery target to the terminal of the person in charge of the delivery company. Then, the delivery management unit 51 records the delivery status in the delivery information storage unit 52 when the tracking number printed on the delivery label of the delivery object is read at the time of delivery.

Then, the delivery management system 50 executes the registration process of the delivery completion information (step S2-9). Specifically, when the delivery management unit 51 of the delivery management system 50 records the delivery completion information as the delivery status associated with the tracking number in the delivery information storage unit 52, the issue number, the transaction code, the tracking number, Generates delivery completion information 560 including information on the delivery company and delivery status. Then, the ledger management unit M1 of the delivery management system 50 records the delivery completion information 560 in the distributed ledger D1 of the information storage unit M2. In this case, the ledger management unit M1 writes the delivery completion information 560 in the distributed ledger D1 of the information storage unit M2 of the other system connected to the peer-to-peer network.

The financial institution system 40 of the beneficiary financial institution executes a determination process as to whether or not the delivery completion information has been acquired (step S2-10). Specifically, the account management unit 41 confirms the delivery completion information 560 in which the settlement completion information 540 and the revocation information 550 are not recorded in the distributed ledger D1 and the delivery company information is recorded.

If the delivery completion information has not been acquired (“NO” in step S2-10), the financial institution system 40 of the recipient financial institution waits for the acquisition of the delivery completion information.
On the other hand, when the delivery completion information is acquired (when "YES" in step S2-10), the financial institution system 40 of the recipient financial institution determines that the payment conditions are satisfied, as in steps S1-6 and S1-7. The process (step S2-11) and the deposit information registration process (step S2-12) are executed.
Then, the financial institution system 30 of the payer financial institution executes the processes of steps S1-8 and subsequent steps.

According to this embodiment, the following effects can be obtained.
(2-1) In the present embodiment, when the approval information 520 is acquired (when “YES” in step S2-7), the delivery management system 50 executes the delivery instruction process (step S2-8). As a result, the product can be shipped based on the information recorded in the distributed ledger D1.

(2-2) In the present embodiment, the delivery management system 50 executes the registration process of the delivery completion information (step S2-9). As a result, the delivery status information of the product can be shared with the parties concerned by using the distributed ledger D1.

(2-3) In the present embodiment, when the delivery completion information is acquired (when "YES" in step S2-10), the delivery management system 50 performs the payment condition satisfaction determination process (step S2-11) and the payment. The information registration process (step S2-12) is executed. As a result, payment can be made based on the delivery status.

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 each of the above embodiments, it is assumed that the open asset protocol (colored coin) using the Bitcoin blockchain is used as the drawing information 510 to the delivery completion information 560. Each piece of information recorded in the distributed ledger D1 is not limited to colored coins. It is possible to use a basic system whose main purpose is to have a role / function other than currency by applying a distributed ledger D1 other than Bitcoin.

-In each of the above embodiments, the drawing information 510 to the delivery completion information 560 are recorded in the distributed ledger D1. The information recorded in the distributed ledger D1 is not limited to these.
-In each of the above embodiments, the information recorded in the distributed ledger D1 is encrypted with a key that can be decrypted by the parties involved in the transaction, if necessary. The need for encryption may be determined according to the network and information. For example, in the case of a closed (private) network used only by the parties concerned, encryption is not necessary.
-In each of the above embodiments, a transaction code is used as an identifier for identifying a series of information recorded in the distributed ledger D1. The identifier is not limited to the transaction code as long as it is an identifier that can identify a series of information, and for example, the issue number of the drawing information 510 may be used.
-In the second embodiment, when the delivery completion information is acquired (when "YES" in step S2-10), the delivery management system 50 performs the payment condition satisfaction determination process (step S2-11), and the payment information. Registration process (step S2-12) is executed. When the payment condition is information from a person other than a trader or a financial institution, the payment condition is not limited to the delivery completion information, and the information recorded in the distributed ledger D1 can be used as the payment condition.

10 ... Payer system, 11 ... Control unit, 20 ... Recipient system, 21 ... Control unit, 30, 40 ... Financial institution system, 31, 41 ... Account management department, 32, 42 ... Account information storage unit, 50 ... Delivery Management system, D1 ... distributed ledger, M1 ... ledger management unit, M2 ... information storage unit.

Claims (3)

Finance in which a payer's payer's account is opened between the payer's payer system in a transaction and the payer's payer's account that trades between the payer and the payee based on the transaction contract for the goods delivered by the carrier. A payment system in which an institutional system and a financial institutional system in which a payee's payee account is opened are connected via a basic system that can confirm the validity of information by a distributed ledger.
The payer system registers the withdrawal information including the transaction code in the distributed ledger based on the contract of the transaction.
The financial institution system in which the payer account is opened registers the approval information including the transaction code of the withdrawal information in the distributed ledger.
If the financial institution system in which the payer account is opened has a valid period set in the payment conditions of the withdrawal information and the valid period is exceeded, the revocation information including the transaction code of the withdrawal information is included. In the distributed ledger
The delivery management system of the delivery company confirms the approval information of the withdrawal information in which at least one of the settlement completion information including the transaction code and the revocation information is not recorded.
The delivery management system that performs the delivery processing of the product based on the approval information of the withdrawal information registers the delivery completion information including the transaction code of the withdrawal information in the distributed ledger for the product related to the contract. ,
The financial institution system in which the payee account is opened does not record at least one of the settlement completion information and the revocation information including the transaction code of the withdrawal information, and the delivery management system is used as a payment condition of the withdrawal information. With respect to the withdrawal information for which the registration of the delivery completion information in the distributed ledger is set, the satisfaction of the payment conditions is confirmed in the distributed ledger using the transaction code of the withdrawal information.
The financial institution system in which the payee account is opened executes a deposit process in the payee account based on the withdrawal information in response to the satisfaction of the deposit conditions.
A payment system characterized in that a financial institution system in which a payer account is opened records payment completion information including a transaction code of the withdrawal information in the distributed ledger. As a payment condition for the withdrawal information, the financial institution system in which the payer account is opened
Payment system according to claim 1, characterized in that the registration of approval information to the distributed register is set. Finance in which a payer's payer's account is opened between the payer's payer system in a transaction and the payer's payer's account that trades between the payer and the payee based on the transaction contract for the goods delivered by the carrier. It is a method to support payment by using a payment system that is connected to the institution system and the financial institution system where the payee's payee account is opened via a basic system that can confirm the validity of information by the distributed ledger. hand,
The payer system registers the withdrawal information including the transaction code in the distributed ledger based on the contract of the transaction.
The financial institution system in which the payer account is opened registers the approval information including the transaction code of the withdrawal information in the distributed ledger.
If the financial institution system in which the payer account is opened has a valid period set in the payment conditions of the withdrawal information and the valid period is exceeded, the revocation information including the transaction code of the withdrawal information is included. In the distributed ledger
The delivery management system of the delivery company confirms the approval information of the withdrawal information in which at least one of the settlement completion information including the transaction code and the revocation information is not recorded.
The delivery management system that performs the delivery processing of the product based on the approval information of the withdrawal information registers the delivery completion information including the transaction code of the withdrawal information in the distributed ledger for the product related to the contract. ,
The financial institution system in which the payee account is opened does not record at least one of the settlement completion information and the revocation information including the transaction code of the withdrawal information, and the delivery management system is used as a payment condition of the withdrawal information. With respect to the withdrawal information for which the registration of the delivery completion information in the distributed ledger is set, the satisfaction of the payment conditions is confirmed in the distributed ledger using the transaction code of the withdrawal information.
The financial institution system in which the beneficiary account is opened executes a payment process in the beneficiary account based on the withdrawal information in response to the satisfaction of the payment conditions.
A payment method characterized in that a financial institution system in which a payer account is opened records payment completion information including a transaction code of the withdrawal information in the distributed ledger.

Images