JP7410479B2 - Payment devices, payment methods and payment programs - Google Patents

Description

TECHNICAL FIELD The present invention relates to a payment device and the like that uses a blockchain to perform payments from a primary payer to a secondary payer under usage restrictions.

In recent years, decentralized networks using blockchain have been realized, making it possible to safely conduct transactions such as payments, certifications, and contracts on the network. By using blockchain, it is possible to safely and easily conduct proper transactions on a network without going through a third party, and it is thought that transactions using networks will increase in the future.

A technology using such blockchain-based virtual currency is disclosed in Patent Document 1, for example. The technology disclosed in Patent Document 1 is such that the national government or an authorized organization provides local governments such as prefectures or municipalities with part or all of the pensions to be paid to pensioners residing in the local government. The entrusted local government issues local currency to each pensioner via the local government's server computer, and each recipient receives the local currency. is received using an IC card or smartphone.

On the other hand, for example, for a subsidy provided by a local government to a local private company (primary payment), the company receiving the subsidy may make the primary payment to the person to whom the subsidy is paid (secondary payment recipient). It is prohibited to restrict the benefits only to the area under the jurisdiction of the local government where they were made, or to prohibit specific uses (e.g., food and beverage expenses, entertainment expenses) as the purpose of use (secondary payment purpose) of benefits provided by municipalities to individuals (primary payment). There are many situations where you want to realize a payment that satisfies the restriction when you want to do so.

As a technique for restricting the use of electronic money in relation to the above-mentioned payment restriction, the techniques shown in Patent Documents 2 and 3, for example, have been disclosed. In the technology shown in Patent Document 2, an in-store terminal performs payment by close proximity communication with a portable device used for payment of electronic value to be paid as consideration, and a product identification code acquisition unit identifies the product to be purchased. The device identification code acquisition unit acquires the device identification code of the portable device from the portable device, and the inquiry unit acquires the product identification code corresponding to the acquired device identification code from the portable device. The output unit inquires of the server whether the product with the given product identification code can be purchased, and if the server determines that the product is not purchasable, the output unit outputs information indicating that the product is not purchasable. It is something to do.

The technology shown in Patent Document 3 includes a balance information acquisition unit that acquires balance information from an electronic value storage means that stores balance information including the balance of electronic value and usage information of electronic value, and an increase/decrease amount value of electronic value. a payment information acquisition unit that acquires payment information including usage information; and a payment unit that executes payment processing to increase or decrease the electronic value stored in the means.

Japanese Patent Application Publication No. 2018-195224 International Publication No. 2017/056197 International Publication No. 2017/154331

However, none of the technologies disclosed in the above patent documents allow a primary payer to restrict payments by a secondary payer using blockchain technology. Furthermore, neither technology involves transferring money to a financial institution's account, assuming the security of blockchain-based payment processing.

The present invention makes it possible to realize a payment that reliably satisfies the usage restrictions by setting usage restrictions from the primary payer to the secondary payers on usage rights whose safety is ensured by blockchain. Provide payment devices, etc.

The payment device according to the present invention is transferred from a primary payer to a secondary payer, and when the secondary payer purchases a product and/or receives a service, the payment device has a usage right that can be exercised as payment to a provider. a usage right issuing means for issuing, a restriction information registration means for registering restriction information regarding usage restrictions of the usage right imposed by the primary payer on the secondary payer, and the usage satisfying the registered restriction information. a right-of-use exercise means for updating exercise information of the right of use when the right of use is exercised; and account information of the financial institution of the primary payer and the financial institution of the provider in response to the exercise of the right of use; and an account balance update means for issuing an update instruction to update the account information of the user, and at least the registration of the usage right and the update of the exercise information are managed on the blockchain.

As described above, in the payment device according to the present invention, the secondary payer can exercise the right to use, which is secured on the blockchain, while satisfying the restriction information registered by the primary payer at the time of issuance. Because money moves from the primary payer's financial institution account to the provider's financial institution account only when the First, it is possible to reliably realize payment according to the purpose of use desired by the primary payer.

Furthermore, since usage rights are managed on the blockchain, it is possible to exercise usage rights with safety and reliability.

FIG. 2 is a diagram showing the relationship between a primary payer, a secondary payer, and a provider who use the payment system according to the first embodiment. FIG. 1 is a system configuration diagram of a payment system according to a first embodiment. FIG. 2 is a functional block diagram showing a configuration related to new user registration in the payment system according to the first embodiment. 4 is a flowchart showing the new user registration process of FIG. 3. FIG. FIG. 2 is a functional block diagram showing a configuration related to system login in the payment system according to the first embodiment. 6 is a flowchart showing the system login process of FIG. 5. FIG. FIG. 2 is a functional block diagram showing a configuration related to primary payment in the payment system according to the first embodiment. 8 is a flowchart showing the primary payment process in FIG. 7; FIG. 2 is a functional block diagram showing a configuration related to secondary payment in the payment system according to the first embodiment. 10 is a first flowchart showing the secondary payment process of FIG. 9. FIG. 10 is a second flowchart showing the secondary payment process of FIG. 9. FIG. FIG. 3 is a diagram showing an example of data used in the payment system according to the first embodiment. FIG. 2 is a functional block diagram showing a configuration related to primary payment in a payment system according to a second embodiment. FIG. 2 is a functional block diagram showing a configuration related to secondary payment in a payment system according to a second embodiment. FIG. 7 is a functional block diagram showing a configuration related to new user registration in a payment system according to a third embodiment. FIG. 7 is a functional block diagram showing a configuration related to primary payment in a payment system according to a third embodiment. It is a figure showing an example of an account information storage part in a payment system concerning a 3rd embodiment. FIG. 3 is a functional block diagram showing a configuration related to secondary payment in a payment system according to a third embodiment.

(First embodiment of the present invention)
A payment system using a payment device according to this embodiment will be described with reference to FIGS. 1 to 12. The payment device according to this embodiment has a usage right that is transferred from a primary payer to a secondary payer, and is exercisable as payment to a provider when the secondary payer purchases a product and/or receives a service. In addition to managing the usage rights on the blockchain, restriction information regarding the usage restrictions of the usage rights is registered, and when the usage rights that satisfy this restriction information are exercised, the usage rights managed on the blockchain are registered. The exercise information is updated, and the primary payer's financial institution account information and the provider's financial institution account information are updated in accordance with the exercise of this usage right.

FIG. 1 is a diagram showing the relationship between a primary payer, a secondary payer, and a provider who use the payment system according to this embodiment. In Figure 1, the primary payer is a system user who makes a primary payment to a secondary payer, and gives the secondary payer the usage right (money equivalent to the primary payment amount from the primary payer's financial institution account). transfer the right to use). At this time, the usage amount and usage restrictions can be set for the usage rights to be transferred, and the amount information and restriction information are stored in association with the usage rights information. The restriction information includes, for example, information such as the person to whom the usage right is exercised, the date and time, and the deadline. A secondary payer is a system user who purchases goods or services from a provider and makes secondary payments for them, and who exercises the usage rights assigned by the primary payer. receive products and services from providers. The exercise of usage rights through secondary payments is only possible if the restrictions regarding the above-mentioned restriction information are met. When a usage right is exercised, money is transferred from the primary payer's financial institution account to the provider's financial institution account in an amount corresponding to the exercised usage right.

FIG. 2 is a system configuration diagram of the payment system according to this embodiment. The payment system 1 according to the present embodiment includes a user terminal 11 used by users such as primary payers and secondary payers, a payment management device 10 for managing and operating the entire system, and issuing and exercising usage rights. It is equipped with a blockchain 12, which is a distributed ledger for managing , and a financial system 13 of a financial institution in which primary payers and providers have accounts, and each component is connected for telecommunication.

Blockchain 12 is a distributed database constructed using distributed database technology and an editing history sharing processing mechanism for sharing the editing history of the distributed database. ). Furthermore, the blockchain 12 in this embodiment may include an execution unit that autonomously executes predetermined processing in a virtual machine configured on the blockchain 12. This execution means is called a smart contract in Ethereum, which is a type of blockchain. The virtual machine that executes the execution means is executed by a computer called a miner that provides computing resources to update the blockchain database, among a plurality of computers connected to the blockchain network. Mining is the process of running virtual machines using computational resources provided by miners to execute execution means and update blockchain databases.

Note that the blockchain 12 is not limited to those that have a processing mechanism that shares the editing history of a distributed database based on the characteristics of a one-way hash function, such as Ethereum and Bitcoin, but can also be edited using other mechanisms. A distributed database may be shared by having a processing mechanism that shares history.

In addition, the blockchain 12 is not limited to blockchains that have a mechanism for adding and updating data added to a distributed database as a block, such as Ethereum and Bitcoin, but also for adding and updating individual data as a block. It may be possible to have a mechanism for sequentially adding and updating information, a mechanism for adding and updating information irregularly, or a mechanism for adding and updating information in other forms.

Furthermore, the blockchain 12 is not limited to systems such as Ethereum and Bitcoin, in which data recorded on a distributed database is added as continuous one-dimensional data like a single chain. Adding data to multiple chains in parallel, adding data in a network, adding data in a 2D planar manner, adding data in multiple dimensions such as 3D, etc. It may be added in the form of .

The configuration and processing of the payment system according to this embodiment will be described in detail below. FIG. 3 is a functional block diagram showing the configuration related to new user registration in the payment system according to the present embodiment, FIG. 4 is a flowchart showing the new user registration process of FIG. 3, and FIG. 5 is the payment system according to the present embodiment. FIG. 6 is a flowchart showing the system login process of FIG. 5; FIG. 7 is a functional block diagram showing the configuration related to primary payment in the payment system according to the present embodiment; FIG. is a flowchart showing the primary payment process in FIG. 7, FIG. 9 is a functional block diagram showing the configuration related to secondary payment in the payment system according to this embodiment, and FIGS. 10 and 11 are flowcharts showing the secondary payment process in FIG. The flowchart shown in FIG. 12 is a diagram showing an example of data used in the payment system according to the present embodiment.

The functional block diagram shown in FIG. 3 implements a "new user registration" function. Although FIG. 3 only shows the processing unit related to the "new user registration" function, the payment management device 10 and blockchain 12 are also used to implement other functions and information management, etc., as will be described later. It also includes a processing section.

In FIG. 3, the user terminal 11 has an input/output unit 111 that accepts input from users (primary payer, secondary payer, provider, etc.) and presents information to the user, and an input/output unit 111 that receives input from users (primary payer, secondary payer, provider, etc.) and that communicates with the user via the Internet. and a web browser 112 for accessing the system (payment management device 10) on the cloud.

The payment management device 10 includes a new registration control unit 101 that controls new user registration processing based on information transmitted from the user terminal 11, and a new registration control unit 101 that controls the processing of new user registration based on information transmitted from the user terminal 11. A login information registration unit 102 registers information in a login information storage unit 103 (see FIG. 12(A)), and a new blockchain address (hereinafter referred to as BC address) and blockchain private key (hereinafter referred to as BC address) for the blockchain 12. A BC information acquisition unit 104 that requests the generation of a BC private key (hereinafter referred to as a BC private key) and receives the generated BC address and BC private key from the blockchain 12; The BC information registration unit 105 registers in the storage unit 106 (see FIG. 12(B)), and the account information storage unit 108 (see FIG. 12(C) )).

The blockchain 12 includes a BC information generation unit 121 that generates a new user's BC address and BC private key in response to a request from the BC information acquisition unit 104 and returns them to the BC information acquisition unit 104 as is.

FIG. 4 is a flowchart showing the process of "new user registration" realized by the configuration shown in FIG. A user ID, password, and account information are input to the input/output unit 111 of the user terminal 11, and the information is passed to the new registration control unit 101 via the Web browser 112 (S1). The new registration control unit 101 passes information on the user ID and password to the login information registration unit 102, and the login information registration unit 102 stores the user ID and password in the login information storage unit 103 shown in FIG. S2). The new registration control unit 101 passes user ID information to the BC information acquisition unit 104, and the BC information acquisition unit 104 requests the blockchain 12 to generate a BC address and a BC private key (S3). In the blockchain 12, the BC information generation unit 121 in the blockchain 12 generates a BC address and a BC private key corresponding to the user ID, and passes them to the BC information acquisition unit 104 (S4). The BC information acquisition unit 104 passes the associated user ID, BC address, and BC private key information to the BC information registration unit 105, and the BC information registration unit 105 stores the BC information shown in FIG. 12(B). The information of the user ID, BC address, and BC private key is stored in the unit 106 (S5). The new registration control unit 101 passes the user ID and account information to the account information registration unit 107, and the account information registration unit 107 stores the user ID and account information in the account information storage unit 108 shown in FIG. 12(C). S6). When the processes from S1 to S6 are completed normally, the new registration control unit 101 sends information to the effect that new user registration is completed to the user terminal 11 (S7), and the process ends. The user can confirm that new user registration has been completed using the Web browser 112 of the user terminal 11.

The functional block diagram shown in FIG. 5 implements a "system login" function. Although FIG. 5 shows only the processing section related to the "system login" function, the payment management device 10 also includes processing sections for realizing other functions, information management, and the like. Note that the configuration of the user terminal 11 is the same as that in FIG. 3.

The payment management device 10 includes a login control unit 201 that controls login processing based on information transmitted from the user terminal 11, and a login information storage unit 103 shown in FIG. The password confirmation unit 202 compares and confirms the registered information, and the session data storage unit 205 (see FIG. 12(D)) manages the login status of the user's user ID. It also includes a login session registration unit 204 for registering data.

FIG. 6 is a flowchart showing the "system login" process realized by the configuration shown in FIG. A user ID and password are input into the input/output unit 111 of the user terminal 11, and the information is passed to the login control unit 201 via the Web browser 112 (S1). The login control unit 201 passes the user ID and password information to the password confirmation unit 202, and the password confirmation unit 202 passes the password input in S1 and the input information in the login information storage unit 103 shown in FIG. 12(A). It is confirmed that the password corresponding to the user ID matches (S2). The password confirmation unit 202 passes the verification result to the login control unit 201 (S3). The login control unit 201 passes the input user ID to the login session registration unit 204, and the login session registration unit 204 creates a new session ID so that the session ID does not overlap in the session data storage unit 205 shown in FIG. 12(D). A session ID is generated and the user ID and session ID are stored in the session data storage unit 205 (S4). The login session registration unit 204 passes the generated session ID to the login control unit 201, and the login control unit 201 passes the session ID to the Web browser 112 of the user terminal 11 (S5). The web browser 112 stores the session ID in a cookie within the web browser, and notifies the user of login completion through the input/output unit 111 (S6).

The functional block diagram shown in FIG. 7 implements the "primary payment" function. Although FIG. 7 shows only the processing unit related to the “primary payment” function, the payment management device 10 and blockchain 12 also include processing units for realizing other functions and information management, etc. It is.

The configuration of the user terminal 11 is the same as in the case of FIG. 3, but in this primary payment process, the user terminal 11 is used by the primary payer. The information input by the primary payer to the input/output unit 111 includes the user ID of the secondary payer, the amount of the primary payment, and the restriction information of the secondary payment.

The payment management device 10 includes a primary payment control unit 301 that controls primary payment processing based on information transmitted from the user terminal 11, and session data shown in FIG. 12(D) based on the session ID from the user terminal 11. A login session confirmation unit 302 that confirms the login of the primary payer from the storage unit 205 and acquires the user ID of the primary payer from the session data storage unit 205 based on the session ID of the primary payer; ); an account balance confirmation unit 303 that accesses the financial institution's system to obtain account information of the primary payer based on the account information stored in the account information storage unit 108 shown in ) and confirms the account balance; The user ID of the primary payer, the user ID of the secondary payer, information on the amount of the primary payment, the BC private key of the primary payer stored in the BC information storage unit 106 shown in FIG. Based on the payer's BC address, generate a usage rights issue transaction containing the amount of the primary payment to the secondary payer's BC address, broadcast it to the blockchain 12, and receive the usage rights ID of the issued usage rights. Usage rights issuing unit 304 and usage rights issuing user registration unit 306 that registers the user ID of the primary payer in association with the usage rights ID issued to usage rights issuing user storage unit 305 (see FIG. 12(E)). and a restriction information registration unit 308 that registers secondary payment restriction information in a restriction information storage unit 307 (see FIG. 12(F)).

The blockchain 12 includes a usage rights registration unit 310 that registers usage rights in a usage rights storage unit 309 (see FIG. 12(G)) in response to transactions from the usage rights issuing unit 304.

FIG. 8 is a flowchart showing the "primary payment" process realized by the configuration shown in FIG. The primary payer inputs the user ID of the secondary payer, the amount of the primary payment, and the restriction information of the secondary payment into the input/output unit 111 of the user terminal 11, and the information is used to control the primary payment via the web browser 112. The information is passed to the department 301 (S1). At this time, the web browser 112 also passes the primary payer's session ID stored in the cookie of the web browser 112. The primary payment control unit 301 passes the session ID of the primary payer to the login session confirmation unit 302, and the login session confirmation unit 302 confirms the login of the primary payer from the session data storage unit 205 shown in FIG. 12(D). (S2). The login session confirmation unit 302 acquires the user ID of the primary payer based on the session ID of the primary payer, and passes it to the primary payment control unit 301 (S3).

The primary payment control unit 301 passes the user ID of the primary payer and the amount of the primary payment to the account balance confirmation unit 303, and the account balance confirmation unit 303 stores the primary payer's user ID and the amount of the primary payment from the account information storage unit 108 shown in FIG. The account information of the primary payer corresponding to the user ID is acquired (S4). The account balance confirmation unit 303 acquires the account balance of the primary payer from the financial institution based on the account information of the primary payer, confirms that the account balance is equal to or greater than the amount of the primary payment, and then sends the account balance to the primary payment control unit. The result is returned to 301 (S5).

The primary payment control unit 301 passes the primary payer's user ID, the secondary payer's user ID, and the amount of the primary payment to the usage right issuing unit 304. Based on the user ID of the secondary payer, the BC private key of the primary payer and the BC address of the secondary payer are acquired from the BC information storage unit 106 shown in FIG. 12(B) (S6). The usage right issuing unit 304 generates a usage rights issuing transaction including the secondary payer's BC address and the primary payment amount, signs it with the primary payer's BC private key, and broadcasts it to the blockchain 12 (S7). On the blockchain 12, the usage right registration unit 310 registers the issued usage right in the usage right storage unit 309 shown in FIG. 12(G). Then, the issued usage right is given a usage right ID on the blockchain 12 and sent back to the usage right issuing unit 304, and the usage right issuing unit 304 passes the usage right ID to the primary payment control unit 301 (S8 ).

The primary payment control unit 301 passes the usage right ID and the user ID of the primary payer to the usage rights issuing user registration unit 306, and the usage rights issuing user registration unit 306 stores the usage rights issuing user storage unit shown in FIG. 12(E). 305, the user ID of the primary payer is stored in association with the usage right ID (S9). The primary payment control unit 301 passes the usage right ID and secondary payment restriction information to the restriction information registration unit 308, and the restriction information registration unit 308 passes the usage right ID to the restriction information storage unit 307 shown in FIG. 12(F). Secondary payment restriction information is stored in association (S10). The primary payment control unit 301 notifies the user (primary payer) of the completion of the primary payment via the user terminal 11 (S11), and ends the process.

The functional block diagram shown in FIG. 9 implements the "secondary payment" function. Although FIG. 9 only shows the processing unit related to the “secondary payment” function, the payment management device 10 and blockchain 12 also include processing units for realizing other functions and information management. It is something.

The configuration of the user terminal 11 is the same as in the case of FIG. 3, but in this secondary payment process, the user terminal 11 is used by the secondary payer. The information inputted to the input/output unit 111 by the secondary payer includes the usage right ID of the usage right used for the secondary payment, the user ID of the provider, and the amount of the secondary payment.

The payment management device 10 has a secondary payment control unit 401 that controls secondary payment processing based on information transmitted from the user terminal 11, and based on the session ID from the user terminal 11, as shown in FIG. 12(D). a login session confirmation unit 302 that confirms the login of the secondary payer from the session data storage unit 205 and acquires the user ID of the secondary payer from the session data storage unit 205 based on the session ID of the secondary payer; , a restriction information confirmation unit 402 that checks whether the provider's user ID is not subject to secondary payment restrictions based on the restriction information stored in the restriction information storage unit 307 shown in FIG. 12 (E ), the license issuing user confirmation unit 404 acquires the user ID of the primary payer corresponding to the license ID from the license issuing user storage unit 305 shown in FIG. 12(C). an account balance confirmation unit 303 that obtains the account balance of the primary payer from the account information storage unit 108 shown in FIG. an account balance update unit 405 that moves and updates the amount of the secondary payment from the primary payer's account to the provider's account based on the user ID of the user; A usage rights update transaction including the ID and the usage rights balance after the secondary payment (usage rights balance - amount of secondary payment) is generated, and the usage rights update transaction that includes the usage rights balance after the secondary payment is generated, and the usage rights update transaction that includes the usage rights balance after the secondary payment is generated, and It also includes a usage right exercise unit 406 that signs with the payer's BC private key and broadcasts it to the blockchain 12 to update the usage right information.

The blockchain 12 includes a usage right confirmation unit that acquires the balance of usage rights from the usage right storage unit 309 shown in FIG. 407, a usage right updating unit 408 that updates the usage right balance in the usage right storage unit 309 shown in FIG. The usage right deletion section 409 deletes the usage right for which the value becomes 0 from the usage right storage section 309 shown in FIG. 12(G).

Note that the restriction information confirmation unit 402 may check whether the user ID registered as a “restrictor” in the restriction information storage unit 307 matches the user ID of the provider; It may be confirmed whether the user ID registered as a "person who is not a restricted person" matches the user ID of the provider. In addition, whether the exercise date and time restrictions are met, whether the exercise period is met, whether the exercise purpose is met, whether the exercise frequency is met, whether the exercise location is met, and the reason for exercising. You may also check whether the (objective) is met.

Further, the balance of usage rights that the usage rights balance confirmation unit 403 confirms is the balance that the secondary payer has (that can be paid to the provider). That is, when one secondary payer uses this system for one primary payer, the balance of usage rights confirmed by the usage rights balance confirmation unit 403 = balance of usage rights held by the secondary payer = This is the balance of the usage rights transferred by the primary payer. On the other hand, when one secondary payer uses this system for multiple primary payers, the balance of usage rights checked by the usage rights balance confirmation unit 403 = balance of usage rights held by the secondary payer = This is the total balance of usage rights transferred by the primary payer.

10 and 11 are flowcharts showing the "secondary payment" process realized by the configuration of FIG. 9. The secondary payer inputs the usage right ID, the provider's user ID, and the secondary payment amount into the input/output unit 111 of the user terminal 11, and the information is sent to the secondary payment control unit 401 via the web browser 112. (S1). At this time, the web browser 112 also passes the secondary payer's session ID stored in the cookie of the web browser 112. The secondary payment control unit 401 passes the session ID of the secondary payer to the login session confirmation unit 302, and the login session confirmation unit 302 logs in the secondary payer from the session data storage unit 205 shown in FIG. 12(D). Confirm (S2). The login session confirmation unit 302 acquires the user ID of the secondary payer based on the session ID of the secondary payer and passes it to the secondary payment control unit 401 (S3).

The secondary payment control unit 401 passes the usage right ID of the usage right used for secondary payment and the user ID of the provider to the restriction information confirmation unit 402, and the restriction information verification unit 402 uses the usage right ID as shown in FIG. 12 based on the usage right ID. Restriction information is acquired from the restriction information storage unit 307 shown in (F) (S4). The restriction information confirmation unit 402 checks the restriction information and the provider's user ID, confirms that the provider is not subject to secondary payment restrictions, and returns the result to the secondary payment control unit 401 (S5 ).

The secondary payment control unit 401 passes the usage right ID of the usage right used for secondary payment and the amount of the secondary payment to the usage right balance confirmation unit 403, and the usage right balance verification unit 403 uses the usage right ID. Information on the usage right balance is acquired from the blockchain 12 (S6). The usage right balance confirmation unit 403 checks that the usage right balance of the usage rights used for the secondary payment is equal to or greater than the amount of the secondary payment, and returns the result to the secondary payment control unit 401 (S7).

The secondary payment control unit 401 passes the usage right ID of the usage right used for secondary payment to the usage right issuing user confirmation unit 404, and the usage right issuing user verification unit 404 uses the usage right ID as shown in FIG. The user ID of the primary payer is obtained from the usage right issuing user storage unit 305 shown in E) and passed to the secondary payment control unit 401 (S8).

The secondary payment control unit 401 passes the user ID of the primary payer and the amount of the secondary payment to the account balance confirmation unit 303, and the account balance confirmation unit 303 receives the primary payment information from the account information storage unit 108 shown in FIG. 12(C). The account information of the primary payer corresponding to the payer's user ID is acquired (S9). The account balance confirmation unit 303 obtains the account balance of the primary payer from the financial institution based on the account information of the primary payer, confirms that the account balance is equal to or greater than the amount of the secondary payment, and performs the secondary payment. The result is returned to the control 401 (S10).

The secondary payment control unit 401 passes the primary payer's user ID, the provider's user ID, and the amount of the secondary payment to the account balance update unit 405. Based on the user ID of the person, the account information of the primary payer and the account information of the provider are acquired from the account information storage unit 108 shown in FIG. 12(C) (S11). The account balance update unit 405 operates the account balance of the financial institution based on the primary payer's account information and the provider's account information, and transfers the amount of the secondary payment from the primary payer's account to the provider's account. (S12).

The secondary payment control unit 401 passes the secondary payer's user ID, the usage right ID, and the amount of the secondary payment to the usage right exercise unit 406, and the usage right exercise unit 406 also receives the secondary payer's user ID. Then, the BC private key is acquired from the BC information storage unit 106 shown in FIG. 12(B) (S13). The usage right exercise unit 406 generates a usage right update transaction including the usage right ID of the usage right to be used for the secondary payment, the usage right balance after the secondary payment (usage right balance - the amount of the secondary payment), and It is signed with the payer's BC private key and broadcast to the blockchain 12 (S14). On the blockchain 12, the usage right updating unit 408 updates the usage right balance in the usage right storage unit 309 shown in FIG. 12(G) (S15). The secondary payment control unit 401 notifies the user (secondary payer) of the completion of the secondary payment via the user terminal 11 (S16), and ends the process.

Note that the data structure and data contents shown in FIG. 12 are merely examples, and the present invention is not limited thereto.

(Second embodiment of the present invention)
A payment system using the payment device according to this embodiment will be explained using FIGS. 13 and 14. The payment device according to the present embodiment described below is a modified example in which the system configuration of the payment device and payment system according to the first embodiment is changed, and the restriction information set by the primary payer is transmitted on the blockchain. By managing this, it is possible to prevent falsification of the restriction information itself and realize proper payment. Note that in this embodiment, explanations that overlap with those of the first embodiment will be omitted.

FIG. 13 is a functional block diagram showing a configuration related to primary payment in the payment system according to this embodiment, and FIG. 14 is a functional block diagram showing a configuration related to secondary payment in the payment system according to this embodiment.

The functional block diagram shown in FIG. 13 implements the "primary payment" function. Although FIG. 13 only shows the processing unit related to the “primary payment” function, the payment management device 10 and blockchain 12 also include processing units for realizing other functions and information management, etc. It is. Further, since the new user registration and system login processes are the same as those in the first embodiment, their explanations will be omitted.

In FIG. 13, the configuration of the user terminal 11 is the same as that in FIG. 3 in the first embodiment. In the primary payment process, the user terminal 11 is used by the primary payer, and the information input by the primary payer to the input/output unit 111 includes the user ID of the secondary payer, the amount of the primary payment, and the secondary payment. This is the restriction information.

The configuration of the payment management device 10 is different from the case shown in FIG. The restriction information registration unit 308 broadcasts the transaction for the registration process of the license issuing user to the blockchain 12 using the information in the BC information storage unit 106, and 12 broadcast.

In addition to the usage rights registration unit 310 and the usage rights storage unit 309, the blockchain 12 executes registration processing of usage rights issuing users in response to transactions from the usage rights issuing user registration unit 306, and creates new usage rights. The usage rights issuing user registration unit (BC) 306a registers the ID in the usage rights issuing user storage unit (BC) 305a, and the restriction information storage unit (BC) 307a stores restriction information in response to transactions from the restriction information registration unit 308. and a restriction information registration unit (BC) 308a for registering.

In other words, in FIG. 7 described in the first embodiment, the restriction information storage section 307 and the usage rights issuing user storage section 305 are managed by the payment management device 10, but in this embodiment, In place of these, the restriction information storage section (BC) 307a and usage right issuing user storage section (BC) 305a are managed on the blockchain 12.

Next, in the functional block diagram shown in FIG. 14, a "secondary payment" function is realized. Although FIG. 14 only shows the processing unit related to the “secondary payment” function, the payment management device 10 and blockchain 12 also include processing units for realizing other functions and information management, etc. It is something.

In FIG. 14, the configuration of the user terminal 11 is the same as that in FIG. 3 in the first embodiment. In the secondary payment process, the user terminal 11 is used by the secondary payer, and the information input by the secondary payer to the input/output unit 111 is the usage right to be exercised at the time of secondary payment. ID, provider's user ID, and secondary payment amount.

The difference in the configuration of the payment management device 10 from the case shown in FIG. Two steps are to broadcast a transaction for confirmation processing to the blockchain 12, and for the restriction information confirmation unit 402 to broadcast a transaction for confirmation processing of restriction information to the blockchain 12 using information in the BC information storage unit 106.

The difference in the configuration of the blockchain 12 from the case shown in FIG. 9 is that, in response to a transaction from the usage rights issuing user confirmation unit 404, the usage rights issuing user confirmation process is executed and the user ID corresponding to the usage rights ID is used. The restriction information is restricted according to the transaction from the license issuing user confirmation unit (BC) 404a that is acquired from the license issuing user storage unit (BC) 305a and returned to the license issuing user confirmation unit 404, and the restriction information confirmation unit 402. A restriction information confirmation unit (BC) 402a that is acquired from an information storage unit (BC) 307a and returned to a restriction information confirmation unit 402 is provided.

In other words, the restriction information storage section (BC) 307a and the usage right issuing user storage section (BC) 305a are managed on the blockchain 12 instead of the restriction information storage section 307 and the usage right issuing user storage section 305, and the payment management device In response to transactions from 10, necessary information is extracted from the storage unit on blockchain 12 and returned to payment management device 10.

(Third embodiment of the present invention)
A payment system using the payment device according to this embodiment will be described with reference to FIGS. 15 to 18. The payment device according to the present embodiment described below is a modification of the system configuration of the payment device and payment system according to the second embodiment, and allows access to account information managed by a bank on a blockchain. This will be realized by Note that in this embodiment, explanations that overlap with those of the first and second embodiments will be omitted.

FIG. 15 is a functional block diagram showing a configuration related to new user registration in the payment system according to this embodiment, FIG. 16 is a functional block diagram showing a configuration related to primary payment in the payment system according to this embodiment, and FIG. FIG. 18, which is a diagram showing an example of an account information storage unit in the payment system according to the present embodiment, is a functional block diagram showing a configuration related to secondary payment in the payment system according to the present embodiment.

The functional block diagram shown in FIG. 15 implements a "new user registration" function. Although FIG. 15 only shows the processing unit related to the “new user registration” function, the payment management device 10 and blockchain 12 also include processing units for realizing other functions and information management, etc. It is something to be prepared for. Furthermore, since the system login process is the same as in the first embodiment, a description thereof will be omitted.

In FIG. 15, the configuration of the user terminal 11 is the same as that in FIG. 3 in the first embodiment. Furthermore, the configuration of the payment management device 10 is different from the first embodiment shown in FIG. At the same time, on the blockchain 12, the account information registration unit (BC) 107a registers the account information of the new user in the account information storage unit (BC) 108a in response to the transaction of the account information registration unit 107. That's true.

By managing account information on the blockchain 12, this account information can be viewed by an unspecified number of people, but confidentiality can be maintained by encrypting the contents or using a concealed blockchain. It may be guaranteed. Furthermore, since account information only needs to identify an account at a financial institution, it is desirable to manage only the minimum necessary information that does not identify an individual in the account information storage unit (BC) 108a on the blockchain 12.

Next, in the functional block diagram shown in FIG. 16, a "primary payment" function is realized. Although FIG. 16 only shows the processing unit related to the “primary payment” function, the payment management device 10 and blockchain 12 also include processing units for realizing other functions and information management, etc. It is.

In FIG. 16, the configuration of the user terminal 11 is the same as that in FIG. 3 in the first embodiment. In the primary payment process, the user terminal 11 is used by the primary payer, and the information input by the primary payer to the input/output unit 111 includes the user ID of the secondary payer, the amount of the primary payment, and the secondary payment. This is the restriction information.

The difference in the configuration of the payment management device 10 from the case shown in FIG. Rather than confirming the account balance, the purpose is to obtain the account balance of the financial institution via the blockchain 12.

The difference in the configuration of the blockchain 12 from that shown in FIG. 13 is that in response to a transaction from the account balance confirmation unit 303, account information is acquired from the account information storage unit (BC) 108a and accessed to the financial institution system. An account balance confirmation unit (BC) 303a that acquires the account balance of a financial institution and returns it to the account balance confirmation unit 303 is provided, and a license issue user registration unit (BC) 306a and a license issue user storage unit (BC) 305a. This is because they are not equipped with the following.

Here, regarding the account information storage unit (BC) 108a, in FIG. 12C showing an example of the account information storage unit 108, account information is stored in association with a user ID, but in this embodiment In this case, as shown in FIG. 17, account information is stored in association with BC addresses. In other words, it is necessary to obtain a user ID based on the usage right ID information using the usage right issuing user storage unit 305, as was done in the first embodiment and the second embodiment to access account information. Gender is gone. Therefore, in this embodiment, the usage rights issuing user storage unit 305, usage rights issuing user registration unit (BC) 305a, and usage rights issuing user storage unit (BC) 305a as shown in FIG. is no longer necessary. Instead, as described later in the secondary payment process, information on the transfer BC address is obtained by referring to the usage rights storage unit 309 shown in FIG. 12(G) based on the information on the usage rights ID, and Account information etc. will be accessed using the transfer BC address.

That is, in this embodiment, instead of the account information storage unit 108, the account information storage unit (BC) 108a is managed on the blockchain 12, and access to the financial institution system is not from the payment management device 10. This is performed from the blockchain 12 by the account balance confirmation unit (BC) 303a, and the acquired account balance information is returned to the payment management device 10.

Next, in the functional block diagram shown in FIG. 18, a "secondary payment" function is realized. Although FIG. 18 only shows the processing unit related to the “secondary payment” function, the payment management device 10 and blockchain 12 also include processing units for realizing other functions and information management. It is something.

In FIG. 18, the configuration of the user terminal 11 is the same as that in FIG. 3 in the first embodiment. In the secondary payment process, the user terminal 11 is used by the secondary payer, and the information input by the secondary payer to the input/output unit 111 is the usage right to be exercised at the time of secondary payment. ID, provider's user ID, and secondary payment amount.

The configuration of the payment management device 10 differs from the case shown in FIG. 14 in that it does not include the account information storage unit 108 and that the account balance confirmation unit 303 broadcasts transactions for account balance confirmation processing to the blockchain 12. Then, the account information update unit 405 broadcasts a transaction for account information update processing to the blockchain 12.

The configuration of the blockchain 12 differs from the case shown in FIG. transaction from the usage right issuing user confirmation unit (BC) 404a and the account balance confirmation unit 303, which acquires the transfer BC address corresponding to the usage right ID from the usage right storage unit 309 and returns it to the usage right issuing user confirmation unit 404. (including information on the primary payer's BC address = delivery BC address), acquires the account information corresponding to the primary payer's BC address from the account information storage unit (BC) 108a, and based on this account information. An account balance confirmation unit (BC) 303a obtains the account balance of the primary payer from a financial institution and returns it to the account balance confirmation unit 303, and a transaction from the account information update unit 405 (BC address of the primary payer, BC information storage) 106), the account information storage unit (BC) 108a stores the account information corresponding to the primary payer's BC address and the account information corresponding to the provider's BC address. and an account balance updating unit (BC) 405a that operates the financial institution's account based on this account information and moves the amount of the secondary payment from the primary payer's account to the provider's account. It is.

That is, the payment management system according to the present embodiment manages the account information storage unit (BC) 108a on the blockchain 12, and also manages the account information storage unit (BC) 108a on the blockchain 12, and also manages financial institution information using the account balance confirmation unit (BC) 303a and the account balance update unit (BC) 405a. The system is accessed from the blockchain 12 and account information is manipulated.

Note that in the payment management system according to the present embodiment, processing for approving access may be performed when accessing the financial institution's system from the blockchain 12. For example, when the account balance confirmation unit (BC) 303 or the account balance update unit (BC) 405a accesses a financial institution's system, an approval processing unit (not shown) provided in the payment management device 10 first obtains approval. It may also be possible to allow access only to users (accounts) who have been granted permission to do so.

In addition, when the secondary payer exercises the right of use and makes a payment to the provider, if the balance of the right of use is insufficient, the amount will be depleted from the balance of the secondary payer's financial institution account. It may be possible to make up for it. That is, the secondary payer may be able to make a payment by adding up the consideration paid by exercising the usage right and the balance of the secondary payer itself or its account.

Additionally, if usage rights are transferred from multiple primary payers to a common secondary payer, the secondary payer may aggregate the balance of the usage rights transferred from multiple primary payers and use them. You can also do this. For example, if multiple parents transfer usage rights to the school for school lunch expenses, the school will add up the amount of usage rights from each parent and pay for the school lunch (payment to the school lunch center, etc.). ).

Furthermore, although the above describes the relationship between the primary payer, secondary payer, and provider, for example, if the secondary payer transfers usage rights to the tertiary payer, or if the tertiary payer The device of the present invention can be applied even when the nth-tier payer exercises the usage right, such as when the usage right is transferred to the fourth-tier payer. In other words, it is transferred from a first payer to an nth payer via one or more payers, and can be exercised as payment to the provider when the nth payer purchases goods and/or receives services. a usage right issuing means for issuing a usage right; and a restriction for registering restriction information regarding usage restrictions of the usage right that the primary payer imposes on the n-th payer (or one or more payers passing through). an information registration means; a usage right exercise means for updating exercise information of the usage right when the usage right that satisfies the registered restriction information is exercised; and an account balance update means for issuing an update instruction to update the account information of the payer's financial institution and the account information of the provider's financial institution, and at least the registration of the usage right and the update of the exercise information are performed on the blockchain. It may also be a payment device managed by

1 Payment System 10 Payment Management Device 11 User Terminal 12 Blockchain 13 Financial System 101 New Registration Control Unit 102 Login Information Registration Unit 103 Login Information Storage Unit 104 BC Information Acquisition Unit 105 BC Information Registration Unit 106 BC Information Storage Unit 107 Account Information Registration Section 107a Account Information Registration Department (BC)
108 Account information storage unit 108a Account information storage unit (BC)
111 Input/output section 112 Web browser 121 BC information generation section 201 Login control section 202 Password confirmation section 204 Login session registration section 205 Session data storage section 301 Primary payment control section 302 Login session confirmation section 303 Account balance confirmation section 303a Account balance confirmation section (BC)
304 Usage rights issuing unit 305 Usage rights issuing user storage unit 305a Usage rights issuing user storage unit (BC)
306 License issuing user registration unit 306a License issuing user registration unit (BC)
307 Restriction information storage unit 307a Restriction information storage unit (BC)
308 Restriction information registration section 308a Restriction information registration section (BC)
309 Usage rights storage unit 310 Usage rights registration unit 401 Secondary payment control unit 402 Restriction information confirmation unit 402a Restriction information confirmation unit (BC)
403 License balance confirmation unit 404 License issuing user confirmation unit 404a License issuing user confirmation unit (BC)
405 Account balance update unit 405a Account balance update unit (BC)
406 Usage rights exercise section 407 Usage rights confirmation section 408 Usage rights update section 409 Usage rights deletion section

Claims (6)

Issues rights of use that are transferred from a primary payer to a secondary payer and are exercisable as a secondary payment to the provider when the secondary payer purchases goods and/or receives services. generate a usage rights issuance transaction including user information of the primary payer, user information of the secondary payer, and information on the amount available to the secondary payer, and broadcast it to a blockchain; a usage right issuing means that issues the usage right by receiving a usage right ID of the usage right registered on the blockchain;
Restriction information registration means for registering restriction information regarding usage restrictions of the usage rights imposed by the primary payer on the secondary payer, separately from information on the amount of money that the secondary payer can use;
restriction information confirmation means for checking whether the restriction information is satisfied in the secondary payment;
Usage right balance confirmation means that acquires the usable balance set in the usage right registered on the blockchain from the blockchain, and compares the usable balance with the price of the secondary payment;
Account balance confirmation means for comparing the amount of the secondary payment with the balance in the account information of the primary payer;
In the secondary payment, the restriction information is satisfied, the usable balance set in the right to use is greater than or equal to the amount of the secondary payment, and the balance in the account information of the primary payer is greater than or equal to the amount of the secondary payment. If so, update the account balance by instructing an update to move and remit the amount of the secondary payment from the account information of the financial institution of the primary payer to the account information of the financial institution of the provider. means and
In the secondary payment, the restriction information is satisfied, the usable balance set in the right to use is greater than or equal to the amount of the secondary payment, and the balance in the account information of the primary payer is greater than or equal to the amount of the secondary payment. In this case, by generating a usage right update transaction including the user information of the secondary payer, the usage right ID, and the price of the secondary payment, and broadcasting it to the blockchain, the block and a usage right exercise means for updating the available balance set in the usage right registered on the chain to an amount obtained by subtracting the price of the secondary payment from the available balance. . The payment device according to claim 1,
The account balance confirmation means compares information on the amount of money available to the secondary payer set in the usage right with the balance in the account information of the primary payer , and the usage right issuing means determines whether the balance is A payment device that broadcasts the right-to-use transaction to the blockchain when the amount is equal to or greater than the usable amount information . The payment device according to claim 1 or 2,
The restriction information registration means broadcasts and registers the transaction of the restriction information registration process on the blockchain, and the restriction information confirmation means checks whether the restriction information is satisfied in the secondary payment. A payment device characterized in that a transaction is broadcast to the blockchain, and the restriction information registration process and the restriction information confirmation process are executed on the blockchain . The payment device according to claim 1 or 2 ,
A processing means is built on the blockchain for accessing the account information of the primary payer and the account information of the provider, and performing a process of confirming or updating the account information,
A payment device characterized in that the account balance confirmation means broadcasts a confirmation processing transaction for confirming the account information or an update processing transaction for updating the account information to the blockchain so that the processing means functions. . The computer is
Issues rights of use that are transferred from a primary payer to a secondary payer and are exercisable as a secondary payment to the provider when the secondary payer purchases goods and/or receives services. generate a usage rights issuance transaction including user information of the primary payer, user information of the secondary payer, and amount information available to the secondary payer, and broadcast it to a blockchain; a usage right issuing step of issuing the usage right by receiving a usage right ID of the usage right registered on the blockchain;
a restriction information registration step of registering restriction information regarding usage restrictions of the usage rights imposed by the primary payer on the secondary payer separately from information on the amount of money that the secondary payer can use;
a restriction information checking step of checking whether the restriction information is satisfied in the secondary payment;
a usage right balance confirmation step of acquiring the usable balance set in the usage right registered on the blockchain from the blockchain and comparing the usable balance with the price of the secondary payment;
an account balance confirmation step of comparing the amount of the secondary payment with the balance in the account information of the primary payer;
In the secondary payment, the restriction information is satisfied, the usable balance set in the right to use is greater than or equal to the amount for the secondary payment, and the balance in the account information of the primary payer is greater than or equal to the amount for the secondary payment. If so, update the account balance by instructing an update to move and remit the amount of the secondary payment from the account information of the financial institution of the primary payer to the account information of the financial institution of the provider. step and
In the secondary payment, the restriction information is satisfied, the usable balance set in the right to use is greater than or equal to the amount for the secondary payment, and the balance in the account information of the primary payer is greater than or equal to the amount for the secondary payment. In this case, by generating a usage right update transaction including the secondary payer's user information, the usage right ID, and the price of the secondary payment, and broadcasting it to the blockchain, the block is updated. A payment method characterized by including a usage right exercise step of updating the available balance set for the usage right registered on the chain to an amount obtained by subtracting the price of the secondary payment from the available balance. Method. Issues rights of use that are transferred from a primary payer to a secondary payer and are exercisable as a secondary payment to the provider when the secondary payer purchases goods and/or receives services. generate a usage rights issuance transaction including user information of the primary payer, user information of the secondary payer, and amount information available to the secondary payer, and broadcast it to a blockchain; a usage right issuing means that issues the usage right by receiving a usage right ID of the usage right registered on the blockchain;
Restriction information registration means for registering restriction information regarding usage restrictions of the usage rights imposed by the primary payer on the secondary payer, separately from information on the amount of money that the secondary payer can use;
restriction information confirmation means for checking whether the restriction information is satisfied in the secondary payment;
Usage right balance confirmation means that acquires the usable balance set in the usage right registered on the blockchain from the blockchain and compares the usable balance with the price of the secondary payment;
Account balance confirmation means for comparing the amount of the secondary payment with the balance in the account information of the primary payer;
In the secondary payment, the restriction information is satisfied, the usable balance set in the right to use is greater than or equal to the amount for the secondary payment, and the balance in the account information of the primary payer is greater than or equal to the amount for the secondary payment. If so, update the account balance by instructing an update to move and remit the amount of the secondary payment from the account information of the financial institution of the primary payer to the account information of the financial institution of the provider. means,
In the secondary payment, the restriction information is satisfied, the usable balance set in the right to use is greater than or equal to the amount for the secondary payment, and the balance in the account information of the primary payer is greater than or equal to the amount for the secondary payment. In this case, by generating a usage right update transaction including the secondary payer's user information, the usage right ID, and the price of the secondary payment, and broadcasting it to the blockchain, the block is updated. The computer is characterized in that the computer functions as a usage right exercise means for updating the usable balance set in the usage right registered on the chain to an amount obtained by subtracting the price of the secondary payment from the usable balance. Payment program.

Images