WO2022101980A1 - Système d'aide au paiement et procédé d'aide au paiement - Google Patents

Système d'aide au paiement et procédé d'aide au paiement Download PDF

Info

Publication number
WO2022101980A1
WO2022101980A1 PCT/JP2020/041921 JP2020041921W WO2022101980A1 WO 2022101980 A1 WO2022101980 A1 WO 2022101980A1 JP 2020041921 W JP2020041921 W JP 2020041921W WO 2022101980 A1 WO2022101980 A1 WO 2022101980A1
Authority
WO
WIPO (PCT)
Prior art keywords
payment
request information
information
user
user terminal
Prior art date
Application number
PCT/JP2020/041921
Other languages
English (en)
Japanese (ja)
Inventor
広伸 上野
亮 満足
Original Assignee
ｄｏｕｂｌｅ ｊｕｍｐ．ｔｏｋｙｏ株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by ｄｏｕｂｌｅ ｊｕｍｐ．ｔｏｋｙｏ株式会社 filed Critical ｄｏｕｂｌｅ ｊｕｍｐ．ｔｏｋｙｏ株式会社
Priority to PCT/JP2020/041921 priority Critical patent/WO2022101980A1/fr
Priority to JP2021553129A priority patent/JPWO2022101980A1/ja
Publication of WO2022101980A1 publication Critical patent/WO2022101980A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/04—Payment circuits
    • G06Q20/06—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/22—Payment schemes or models

Definitions

  • the present invention relates to a payment support system and a payment support method.
  • Non-Patent Document 1 Transactions and settlements of crypto assets (assets, virtual currencies, etc.) using smart contracts in blockchain are widely performed.
  • Ethereum executes an arbitrary transaction by a smart contract, and the transaction history is shared by each node (Non-Patent Document 1).
  • an execution fee (GAS fee, etc.) is required to execute a transaction (transaction and settlement) in such a blockchain system.
  • GAS fee an execution fee
  • a transaction transaction and settlement
  • a consensus building process must be performed to ensure data consistency in the blockchain system, but this consensus building process requires a certain amount of time.
  • the present invention has been made in view of such a background, and an object of the present invention is to provide a payment support system capable of reducing the burden of payment processing by a user and smoothly performing transaction processing, and a payment support method. There is something in it.
  • One of the present inventions for solving the above problems is configured to include a plurality of user terminals and server devices that are communicably connected to each other, and each of the plurality of user terminals and the server device has a smart contract.
  • a memorized payment support system wherein the smart contract includes a deposit processing unit that accepts and stores a deposit input of a specified amount of a value exchange medium to which a signature information related to the user terminal is attached, and stores the server.
  • the device comprises one or a plurality of payment request information which is information requesting payment using the deposited value exchange medium based on a predetermined transaction, and includes a payment request information receiving processing unit for receiving payment request information from the user terminal.
  • a payment support system including a payment processing unit on the management side that transfers from the smart contract to the account related to the server device.
  • another one of the present invention is configured to include a plurality of user terminals and server devices that are communicably connected to each other, and each of the plurality of user terminals and the server device stores a smart contract.
  • a payment support method in a payment support system the smart contract executes a deposit process of receiving and storing a deposit of a specified amount of a value exchange medium with signature information related to the user terminal, and the server.
  • the device executes payment request information reception processing for receiving one or more payment request information, which is information requesting payment using the deposited value exchange medium, from the user terminal based on a predetermined transaction, and the smart.
  • FIG. 1 is a diagram showing an example of a configuration of a payment support system according to the present embodiment.
  • FIG. 2 is a diagram showing an example of the function of a smart contract in a blockchain system.
  • FIG. 3 is a diagram showing an example of a data structure of deposit information.
  • FIG. 4 is a diagram showing an example of a function provided in a user terminal.
  • FIG. 5 is a diagram showing an example of a function provided in the server device.
  • FIG. 6 is a diagram showing an example of hardware included in a server device and a user terminal.
  • FIG. 7 is a diagram illustrating an outline of processing performed in the payment support system.
  • FIG. 8 is a flow chart illustrating an example of the deposit process.
  • FIG. 9 is a diagram showing an example of the data structure of the deposit request.
  • FIG. 1 is a diagram showing an example of a configuration of a payment support system according to the present embodiment.
  • FIG. 2 is a diagram showing an example of the function of a smart contract
  • FIG. 10 is a flow chart illustrating an example of payment request information transmission processing.
  • FIG. 11 is a diagram showing an example of payment request information 0.
  • FIG. 12 is a flow chart illustrating an example of payment processing on the management side.
  • FIG. 13 is a flow chart illustrating an example of user-side payment processing.
  • FIG. 14 is a diagram showing an example of user payment information.
  • FIG. 15 is a flow chart illustrating an example of the forced withdrawal process.
  • FIG. 16 is a diagram showing an example of forced withdrawal request information.
  • FIG. 1 is a diagram showing an example of the configuration of the payment support system 1 according to the present embodiment.
  • the payment support system 1 includes a server device 3 and a plurality of user terminals 5 used by each user.
  • the server device 3 is an information processing device used by a predetermined operator.
  • the user terminal 5 is an information processing device used by a user who uses various services provided by the operator, and is, for example, a personal computer, a smartphone, or the like.
  • Each user terminal 5 and the server device 3 are connected by, for example, a wired or wireless communication network 2 such as a LAN (Local Area Network), a WAN (Wide Area Network), the Internet, or a dedicated line.
  • a wired or wireless communication network 2 such as a LAN (Local Area Network), a WAN (Wide Area Network), the Internet, or a dedicated line.
  • individual communication that does not depend on the blockchain system 10 can also be performed between the server device 3 and each user terminal 5.
  • the payment support system 1 constitutes the blockchain system 10.
  • the blockchain system 10 manages accounts associated with the server device 3 and each user terminal 5 (hereinafter, referred to as an operating account and a user account, respectively).
  • the blockchain system 10 stores a smart contract (Smart contract) that executes various transaction processes between accounts, which will be described later, using transaction data. By accepting the input of transaction data, the smart contract executes transactions and settlements between accounts of the blockchain system 10 using a value exchange medium (cryptocurrency or the like) implemented in the blockchain system 10.
  • Smart contract Smart contract
  • a value exchange medium cryptocurrency or the like
  • the smart contract verifies the signature data included in the input transaction data and determines that the signature data is valid (specifically, the signature data is registered in the smart contract in advance. If it is determined that the signature is the user's signature), the transaction processing is executed.
  • the above-mentioned value exchange medium is required to execute this transaction processing. Further, it takes a predetermined time to execute the transaction processing due to the consensus building process for ensuring the consistency of the blockchain data in the blockchain system 10.
  • the blockchain system 10 of the present embodiment is Ethereum, and the value exchange medium thereof is Ether (ETH).
  • FIG. 2 is a diagram showing an example of the function of the smart contract in the blockchain system 10.
  • the blockchain system 10 includes a deposit contract 100 as a smart contract.
  • the deposit contract 100 includes a deposit processing unit 101, an operation side payment processing unit 102, a user side payment processing unit 103, and a forced withdrawal processing unit 104. Further, the deposit contract 100 stores the deposit information 120.
  • the deposit contract 100 is deployed in the blockchain system 10 by, for example, the administrator of the server device 3.
  • the deposit processing unit 101 accepts the input of the deposit of the value exchange medium of the specified amount to which the signature information (user signature) related to the user terminal 5 is attached, and stores it in the deposit information 120.
  • the operation side payment processing unit 102 accepts input of payment request information described later from an account (operation account) managed by the administrator of the server device 3, and uses the signature information attached to the payment request information and the deposit processing unit 101.
  • the input signature information (user signature) related to the user terminal 5 matches, the amount indicated by the payment request information is transferred from the deposit contract 100 to the account (operating account) related to the server device 3.
  • the user-side payment processing unit 103 accepts input of user payment information to be described later, including payment request information, from an account (user account) managed by the user related to the user terminal 5, and the signature information attached to the user payment information and the user.
  • the signature information (user signature) related to the terminal 5 matches, the amount of the value exchange medium indicated by the user payment information is transferred from the deposit contract 100 to the account (operating account) of the server device 3 and the deposit contract 100.
  • the amount obtained by subtracting the amount of the value exchange medium indicated by the user payment information from the amount of the value exchange medium deposited in the deposit contract 100 is transferred from the deposit contract 100 to the account (user account) of the user terminal 5.
  • the forced withdrawal processing unit 104 is information for requesting withdrawal of a value exchange medium from the account (user account) of the user terminal 5 at least exceeding the amount indicated by the payment request information input to the operation side payment processing unit 102.
  • the amount of the exchange medium is transferred from the deposit contract 100 to the account (user account) related to the user terminal 5.
  • the forced withdrawal processing unit 104 receives the payment request information from the account (operating account) related to the server device 3 for a predetermined time.
  • the amount of the value exchange medium indicated by the forced withdrawal request information is set in the account (user account) related to the user terminal 5.
  • FIG. 3 is a diagram showing an example of the data structure of the deposit information 120.
  • the deposit information 120 is information on the deposit amount (value exchange medium) of each account deposited in the deposit contract 100, and is deposited by the user's account 121 (user account) related to each user terminal 5 and the account 121. It has each information of the deposit amount 122 which is the amount of ETH.
  • FIG. 4 is a diagram showing an example of a function provided in the user terminal 5. As shown in the figure, the user terminal 5 includes a payment request information transmission processing unit 51 and a payment request information reception processing unit 52.
  • the settlement request information transmission processing unit 51 transmits one or a plurality of settlement request information, which is information requesting settlement using the value exchange medium deposited in the deposit contract 100, to the server device 3 based on a predetermined transaction.
  • the payment request information is accompanied by the signature information of the account related to the user terminal 5.
  • the payment request information reception processing unit 52 receives all or part of the payment request information previously transmitted by the payment request information transmission processing unit 51 to the server device 3 from the server device 3.
  • FIG. 5 is a diagram showing an example of the functions included in the server device 3.
  • the server device 3 includes a payment request information reception processing unit 31 and a payment request information transmission processing unit 32.
  • the payment request information reception processing unit 31 receives one or more payment request information from the user terminal 5, and stores and stores the received payment request information.
  • the payment request information transmission processing unit 32 transmits (replies) all or part of the payment request information received by the payment request information reception processing unit 31 to the user terminal 5.
  • FIG. 6 is a diagram showing an example of hardware included in the server device 3 and the user terminal 5.
  • the server device 3 and the user terminal 5 include a processing device 11 such as a CPU (Central Processing Unit), a main storage device 12 such as a RAM (Random Access Memory) and a ROM (Read Only Memory), and an HDD (Hard Disk Drive).
  • An auxiliary storage device 13 such as an SSD (Solid State Drive), an input device 14 consisting of a keyboard, mouse, touch panel, etc., an output device 15 consisting of a monitor (display), etc., and a communication device that communicates with other information processing devices. It is an information processing device provided with 16.
  • a processing device 11 such as a CPU (Central Processing Unit)
  • main storage device 12 such as a RAM (Random Access Memory) and a ROM (Read Only Memory)
  • HDD Hard Disk Drive
  • An auxiliary storage device 13 such as an SSD (Solid State Drive)
  • an input device 14 consisting of a keyboard, mouse, touch panel
  • each smart contract or program stored in the main storage device 12 or the auxiliary storage device 13
  • the processing content of each smart contract or program is realized.
  • These smart contracts or programs are non-temporary readable by each node, for example, secondary storage devices, non-volatile semiconductor memories, hard disk drives, storage devices such as SSDs, or IC cards, SD cards, DVDs, etc. It may be stored in a data storage medium.
  • FIG. 7 is a diagram illustrating an outline of processing performed in the payment support system 1.
  • the deposit contract 100 executes deposit of a specified amount of ETH from the user account 50 of a certain user terminal 5 to the deposit contract 100 (deposit process s1).
  • the user related to the user terminal 5 acquires (purchases) assets (property information such as NFT (NonFungibleToken)) on the blockchain system 10 from the operator account or other accounts using the user account. do. Then, since payment (settlement) of ETH is required as consideration for the acquisition or purchase of this asset, the user uses ETH of the deposit contract 100.
  • assets property information such as NFT (NonFungibleToken)
  • NFT NonFungibleToken
  • the user terminal 5 transmits the payment request information accompanied by the user's signature data to the server device 3 so that the purchased portion of the ETH deposited in the deposit contract 100 by the deposit process s1 can be used for the payment.
  • Settlement request information transmission process s2) When the user acquires the asset a plurality of times, the settlement request information transmission process s2 is also executed a plurality of times accordingly.
  • the deposit contract 100 accepts the input of payment request information (with a user signature) from the operating account 30, and when this payment request information is input, the user attached to the payment request information. After verifying the signature data of, the ETH of the purchase of the asset among the ETH of the user deposited in the deposit contract 100 is transferred to the operation account 30 (operation side settlement process s3).
  • the user terminal 5 receives all or part of the payment request information that has been transmitted to the server device 3 and is stored in the server device 3 from the server device 3 (payment request information reception process s4).
  • the deposit contract 100 accepts input of user payment information from the user account 50, which is information associated with the payment request information received by the user terminal 5 in the payment request information receiving process s4, and the user request information is received.
  • user payment information is information associated with the payment request information received by the user terminal 5 in the payment request information receiving process s4, and the user request information is received.
  • the ETH of the user's ETH deposited in the deposit contract 100 for the asset purchase is transferred to the operating account 30 and at the same time.
  • the balance of ETH of the deposit contract 100 is refunded to the user account 50 (user side payment process s5).
  • the user can forcibly withdraw the ETH deposited in the deposit contract 100 without considering the payment amount related to the purchase of the asset.
  • the deposit contract 100 accepts the input of the forced withdrawal request information from the user account 50, and when the forced withdrawal request information is input, the deposit contract 100 verifies the user's signature data accompanying the forced withdrawal request information. , Withdraw the entire amount of ETH deposited in the deposit contract 100 from the deposit contract 100 to the user account 50.
  • the deposit contract 100 waits for a predetermined time from the input of the forced withdrawal request information to the withdrawal, and also accepts the input of the payment request information from the operating account 50 (user-side forced withdrawal process s6). .. If the payment request information is not input for this predetermined time, only the above-mentioned withdrawal to the user account 50 is performed.
  • these processes will be specifically described.
  • FIG. 8 is a flow chart illustrating an example of the deposit process s1.
  • the deposit processing unit 101 of the deposit contract 100 is waiting for input of a deposit request from the user account (s11).
  • FIG. 9 is a diagram showing an example of the data structure of the deposit request 300.
  • the deposit request 300 includes the account 301 of the depositing user, the deposit amount 302 which is the deposit request amount, and the user signature information 303 of the depositing user (for example, information generated from the user's encryption key). Have information.
  • the deposit processing unit 101 verifies the signature when the deposit request 300 is input (s11: input) (s12). Specifically, the deposit processing unit 101 verifies whether or not the user signature information 303 of the deposit request 300 is the signature of the registered user of the deposit contract 100.
  • the deposit processing unit 101 deposits the contents of the deposit request 300. It is registered in the information 120 (s13), and the deposit process s1 is completed.
  • the deposit processing unit 101 sets the account 301 of the deposit request 300 as the account 121 of the deposit information 120, and sets the deposit amount 302 (for example, "100 ETH") of the deposit request 300 to the deposit amount 122 of the deposit information 120. Set to.
  • FIG. 10 is a flow chart illustrating an example of the settlement request information transmission process s2.
  • the settlement request information transmission process s2 is executed after the execution of the deposit process s1 is completed.
  • the payment request information transmission processing unit 51 of the user terminal 5 accepts the input of a part or all of the ETH deposited by the deposit processing s1 (hereinafter referred to as the payment amount) (s21).
  • the user terminal 5 may display a predetermined screen and accept input of a payment amount (for example, 10 ETH out of 100 ETH) from the user, or receive information on the payment amount from another information processing device. May be good.
  • a payment amount for example, 10 ETH out of 100 ETH
  • the payment request information transmission processing unit 51 transmits the payment request information related to the input payment amount to the server device 3 (s22).
  • FIG. 11 is a diagram showing an example of payment request information 320.
  • the payment request information 320 includes the user's account 321 and the payment amount 322, and the user signature information 323.
  • the payment request information reception processing unit 31 of the server device 3 receives the payment request information 320, stores the received payment request information 320 (s23), and the payment request information transmission processing s2 finish.
  • the server device 3 receives the payment request information 320 three times, and stores a total payment amount of 30 ETH with a user signature.
  • FIG. 12 is a flow chart illustrating an example of the operation side settlement process s3.
  • the management-side settlement process s3 is started, for example, after the server device 3 stores the settlement request information 320 by the settlement request information transmission process s2.
  • the management side payment processing unit 102 of the deposit contract 100 accepts the input of the payment request information 320 from the management account (s31).
  • the server device 3 displays a list of the payment request information 320 currently stored, and accepts the selection of one or a plurality of payment request information 320 to be settled this time from the operator.
  • the operation side payment processing unit 102 of the deposit contract 100 accepts the input of the above-selected payment request information 320 from the operation account managed by the server device 3.
  • the server device 3 when the server device 3 receives the payment request information 320 from the user terminal 5 by the payment request information transmission process s2, the payment request information 320 is automatically input to the deposit contract 100 or after a predetermined time after receiving the payment request information 320. You may do so.
  • the management side payment processing unit 102 verifies the signature of the payment request information 320 (s32). Specifically, the operation side payment processing unit 102 verifies whether or not all the user signature information 323 of each payment request information 320 is a registered signature of the user.
  • the side payment processing unit 102 transfers the payment amount 322 of each payment request information 320 from the deposit contract 100 to the account (operating account) of the server device 3 (s33).
  • the management-side payment processing unit 102 subtracts the payment amount 322 of the payment request information 320 from the deposit amount 122 of the account 121 corresponding to the account 321 of the payment request information 320 in the deposit information 120, and reduces the deposit amount 122. Set the payment amount 322 in the operating account. This completes the payment to the management side.
  • FIG. 13 is a flow chart illustrating an example of the user-side payment process s4. This process is executed, for example, after the settlement request information transmission process s2 is executed.
  • the payment request information reception processing unit 52 of the user terminal 5 accepts an input to settle the amount indicated by the payment request information 320 transmitted to the server device 3 in the payment request information transmission processing s2 on behalf of the operator ( s41).
  • the payment request information receiving processing unit 52 displays a predetermined screen and accepts input from the user of information specifying the payment request information 320 previously transmitted to the server device 3 in the payment request information transmission processing s2.
  • the payment request information reception processing unit 52 When the payment request information reception processing unit 52 receives the input of information from the user (s41: input), the payment request information reception processing unit 52 transmits a request for acquisition of the payment request information 320 related to the settlement to the server device 3 (s42).
  • the user payment information acquisition request is accompanied by information specifying the payment request information 320 input in s41.
  • the payment request information receiving processing unit 52 may automatically transmit the acquisition request of the payment request information 320 to the server device 3 after a predetermined time has passed since the payment request information 320 was transmitted to the server device 3. ..
  • the server device 3 When the server device 3 receives the acquisition request from the user terminal 5, the server device 3 transmits the payment request information 320 indicated by the acquisition request to the user terminal 5 among the payment request information 320 stored in the server device 3 (s43).
  • the user-side payment processing unit 103 of the deposit contract 100 accepts the input of the user payment information 360 regarding the payment request information 320 received by the user terminal 5 in s43 from the user account (s44: reception).
  • FIG. 14 is a diagram showing an example of user payment information.
  • the user payment information 360 is information obtained by collecting one or more payment request information 320 received in s43, and includes each information of the user account 361, the payment amount 362, and the user signature information 363.
  • the user-side payment processing unit 103 verifies the signature of the user payment information 360 (s45). For example, the user-side payment processing unit 103 verifies whether or not the user signature information 363 of the user payment information 360 is a registered signature of the user. At this time, the user-side payment processing unit 103 refers to the predetermined information incidental to the user payment information 360 or the predetermined information stored in the deposit contract 100, so that each payment request information in the user payment information 360 can be obtained. It may be confirmed whether the 320 is transmitted to the server device 3 (whether the operation account has been requested to settle).
  • the user-side payment process s4 ends, and if the verification of the signature of the user payment information 360 succeeds (s45: OK), the user The side payment processing unit 103 performs the payment indicated by the user payment information 360 to the operating account, and withdraws ETH from the deposit contract 100 to the user account.
  • FIG. 15 is a flow chart illustrating an example of the forced withdrawal process s5. This process is executed, for example, after the execution of the settlement request information transmission process s2 is completed and when the management side settlement process s3 is not executed.
  • the forced withdrawal processing unit 104 of the deposit contract 100 accepts the input of the forced withdrawal request information from the user account (s52).
  • the user terminal 5 displays a screen showing the ETH deposited in the deposit process s1 (for example, the deposit amount 122 of the deposit information 120), and is related to the payment amount transmitted to the server device 3 in the payment request information transmission process s2. It accepts the input of confirmation as to whether or not to withdraw the full amount (for example, 100 ETH) (s51). Then, when the confirmation is input, the user terminal 5 generates the forced withdrawal request information and inputs it to the deposit contract 100.
  • the ETH deposited in the deposit process s1 for example, the deposit amount 122 of the deposit information 120
  • the user terminal 5 receives the input of confirmation as to whether or not to withdraw the full amount (for example, 100 ETH) (s51). Then, when the confirmation is input, the user terminal 5 generates the forced withdrawal request information and inputs it to the deposit contract 100.
  • the user terminal 5 may generate the forced withdrawal request information after a predetermined time after transmitting the payment request information 320 to the server device 3, and input the payment request information into the deposit contract 100.
  • FIG. 16 is a diagram showing an example of forced withdrawal request information 380.
  • the forced withdrawal request information 380 has each information of the user account 381 and the user signature information 382.
  • the forced withdrawal processing unit 104 verifies the signature of the forced withdrawal request information 380 (s53). For example, the forced withdrawal processing unit 104 verifies whether or not the user signature information 382 of the forced withdrawal request information 380 is a registered signature of the user.
  • the forced withdrawal processing unit 104 refers to the predetermined information incidental to the forced withdrawal request information 380 or the predetermined information stored in the deposit contract 100, so that the user terminal 5 can advance the server device 3 to the server device 3. It may be confirmed whether the payment request information 320 has been sent to (whether the operation account has been requested to settle).
  • the forced withdrawal processing unit 104 accepts input of a payment request from the operating account for a predetermined time (for example, 24 hours) before actually executing the forced withdrawal (s54, s55: NO). Specifically, the forced withdrawal processing unit 104 accepts the input of the settlement request information 320 from the management account by the management side settlement processing s3 described above for a predetermined time.
  • the forced withdrawal processing unit 104 executes the process of s58 described later.
  • the forced withdrawal processing unit 104 verifies the signature of the forced withdrawal request information 380 (s56). For example, the forced withdrawal processing unit 104 determines whether or not the user signature information 382 of the forced withdrawal request information 380 is a registered signature of the user.
  • the forced withdrawal processing unit 104 transfers the amount indicated by the settlement request information 320 from the deposit contract 100 to the operating account (s57).
  • the forced withdrawal processing unit 104 subtracts the settlement amount 322 of the settlement request information 320 from the deposit amount 122 of the account 121 corresponding to the account 381 of the forced withdrawal request information 380 in the deposit information 120, and reduces the deposit amount 122. Set the settlement amount 322 for the minute in the operating account. After that, the processing of s58 is performed.
  • the forced withdrawal processing unit 104 withdraws (refunds) the entire balance of the deposit contract 100 to the user account.
  • the forced withdrawal processing unit 104 sets the deposit amount 122 of the account 121 corresponding to the account 381 of the forced withdrawal request information 380 in the deposit information 120 to the account 381 (user account) of the forced withdrawal request information 380.
  • the deposit amount 122 is set to zero. As a result, the deposit amount of the user in the deposit contract 100 becomes zero, and the full withdrawal to the user is realized.
  • the smart contract (deposit contract 100) accepts the deposit request 300 with the user signature, and the server device 3 receives the payment request information with the signature information.
  • the smart contract sets the amount indicated by the payment request information 320 in the operating account.
  • the payment support system 1 of the present embodiment only allows the user to send his / her signature to the server device 3, and makes payment using the value exchange medium (ETH) that he / she has deposited in the deposit contract 100. You can request it from the server device side (operation side).
  • ETH value exchange medium
  • the user since the user does not have to execute the deposit contract 100 by himself / herself, he / she bears the burden necessary for executing the deposit contract 100 (for example, payment of gas fee, waiting until the transaction processing of the deposit contract 100 is completed). It is possible to make a payment using the deposit contract 100.
  • the burden of payment processing on the user can be reduced and transaction processing can be smoothly performed.
  • the operating account or the server device 3 side makes payments related to the deposit contract 100 based on the user's signature attached by the user's intention, and the operating side does not independently manage the operation of the transaction. Payment support using such a deposit contract 100 does not fall under the custody business.
  • the blockchain system 10 is not limited to Ethereum, and may be any blockchain system that implements smart contracts.
  • the value exchange medium is not limited to ETH, and may be any other type of value exchange medium.
  • each program and smart contract described in this embodiment may be divided into a plurality of parts, or a plurality of programs or smart contracts may be integrated into one program or smart contract, respectively.
  • the user of the user terminal 5 and the executor of the transaction do not have to be the same as long as the user signature can be shared.
  • the compulsory withdrawal request information 380 may include the amount of the compulsory withdrawal. As a result, only a part of the deposit amount of the deposit contract 100 can be forcibly withdrawn.
  • the user terminal includes a settlement information reception processing unit that receives user payment information, which is information including the payment request information, from the server device, and the smart contract is a smart contract.
  • user payment information which is information including the payment request information
  • the smart contract is a smart contract.
  • the amount of the value exchange medium indicated by the user payment information is calculated by the server.
  • the user-side payment processing unit that transfers to the account related to the device and transfers the amount obtained by subtracting the amount of the value exchange medium indicated by the user payment information from the amount of the deposited value exchange medium to the account related to the user terminal. May be provided.
  • the user terminal 5 receives the payment request information 320 once transmitted to the server device 3 in return, and the deposit contract 100 corresponds to the user signature in the signature attached to the input payment request information 320.
  • the user side can proactively perform the payment processing on behalf of the operating side when the operating side does not make the payment. .. As a result, the payment can be completed quickly at the timing desired by the user.
  • the smart contract when the smart contract is attached with signature information and accepts input of forced withdrawal request information requesting withdrawal of a value exchange medium equal to or more than the amount indicated by the payment request information.
  • the signature information attached to the input forced withdrawal request information corresponds to the signature information related to the user terminal
  • the amount of the value exchange medium indicated by the forced withdrawal request information is related to the user terminal. It may be provided with a forced withdrawal processing unit set in the account.
  • the deposit contract 100 uses the requested amount when the forced withdrawal request information 380 requesting the withdrawal of the value exchange medium (for example, the entire deposit amount) exceeding the settlement amount is input and the user signature is correct. Set in your account. As a result, even if the management side becomes inoperable due to bankruptcy, bankruptcy, unknown location, etc., the user side can surely refund the ETH deposited in the deposit contract 100.
  • the forced withdrawal processing unit performs the forced withdrawal processing unit for a predetermined time when the signature information attached to the input forced withdrawal request information corresponds to the signature information related to the user terminal. Only when the input of the usage request information is accepted from the account related to the server device and the usage request information is not input for the predetermined time, the amount of the value exchange medium indicated by the forced withdrawal request information is set by the user. It may be set to the account related to the terminal.
  • the user side is fraudulent by accepting the payment request from the management side for a predetermined time. It is possible to prevent the withdrawal from the deposit contract 100.
  • a payment support system is configured to include a plurality of user terminals and server devices that are communicably connected to each other, and each of the plurality of user terminals and the server device stores a smart contract.
  • the smart contract executes a deposit process of accepting and storing a deposit input of a specified amount of a value exchange medium to which a signature information related to the user terminal is attached, and the server device performs a deposit process.
  • One or more payment request information which is information requesting payment using the deposited value exchange medium based on a predetermined transaction, is executed, and the payment request information reception process for receiving the payment request information from the user terminal is executed, and the smart contract
  • the amount indicated by the payment request information is set to the smart. It may be a payment support method that executes the management side payment process to transfer from the contract to the account related to the server device.
  • the user terminal executes a settlement information reception process for receiving the payment request information transmitted to the server device from the server device, and the smart contract is the user.
  • the input of the user payment information which is the information for requesting the payment indicated by the payment request information received by the terminal is accepted and the signature information attached to the input user payment information corresponds to the signature information related to the user terminal, the above
  • the amount of the value exchange medium indicated by the user payment information is transferred from the smart contract to the account related to the server device, and the amount of the value exchange medium indicated by the user payment information is deducted from the amount of the deposited value exchange medium.
  • the user-side payment process for transferring the amount of money from the smart contract to the account related to the user terminal may be executed.
  • the user terminal includes a payment request information receiving processing unit that receives the payment request information transmitted to the server device from the server device, and the smart contract is described by the smart contract.
  • the compulsory withdrawal request information which is the information requesting the withdrawal of the value exchange medium in the amount exceeding the amount indicated by the payment request information received by the user terminal
  • the signature information to be used corresponds to the signature information related to the user terminal
  • the forced withdrawal process for transferring the value exchange medium indicated by the forced withdrawal request information from the smart contract to the account related to the user terminal is executed. May be good.
  • the signature information attached to the input forced withdrawal request information corresponds to the signature information related to the user terminal.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

L'invention concerne un système d'aide au paiement 1 dans lequel une pluralité de terminaux utilisateur 5 et de dispositifs serveurs 3 stockent chacun un contrat intelligent, le système d'aide au paiement 1 comprenant : une unité de traitement de dépôt dans laquelle le contrat intelligent accepte l'entrée du montant désigné de dépôt d'un moyen d'échange de valeur accompagné d'informations de signature appartenant à un terminal utilisateur 5 ; une unité de traitement de réception d'informations de demande de paiement dans laquelle un dispositif serveur 3 reçoit, d'un terminal utilisateur 5, un ou plusieurs éléments d'informations de demande de paiement, qui sont des informations basées sur une transaction prescrite et demandant un paiement à l'aide du moyen d'échange de valeur déposé ; et une unité de traitement de paiement côté opération dans laquelle le contrat intelligent accepte l'entrée des informations de demande de paiement ayant été reçues par le dispositif serveur 3, et le montant indiqué par les informations de demande de paiement est transféré du contrat intelligent au compte qui appartient au dispositif serveur 3 quand les informations de signature accompagnant les informations de demande de paiement introduites correspondent aux informations de signature appartenant au terminal utilisateur 5.
PCT/JP2020/041921 2020-11-10 2020-11-10 Système d'aide au paiement et procédé d'aide au paiement WO2022101980A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/JP2020/041921 WO2022101980A1 (fr) 2020-11-10 2020-11-10 Système d'aide au paiement et procédé d'aide au paiement
JP2021553129A JPWO2022101980A1 (fr) 2020-11-10 2020-11-10

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2020/041921 WO2022101980A1 (fr) 2020-11-10 2020-11-10 Système d'aide au paiement et procédé d'aide au paiement

Publications (1)

Publication Number Publication Date
WO2022101980A1 true WO2022101980A1 (fr) 2022-05-19

Family

ID=81600857

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2020/041921 WO2022101980A1 (fr) 2020-11-10 2020-11-10 Système d'aide au paiement et procédé d'aide au paiement

Country Status (2)

Country Link
JP (1) JPWO2022101980A1 (fr)
WO (1) WO2022101980A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2020047104A (ja) * 2018-09-20 2020-03-26 日本電信電話株式会社 決済システム、決済方法、利用者装置、決済プログラム
JP6710401B1 (ja) * 2019-12-05 2020-06-17 ｂａｃｏｏｒ ｄＡｐｐｓ株式会社 対象物を管理する方法及び管理サーバ

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2020047104A (ja) * 2018-09-20 2020-03-26 日本電信電話株式会社 決済システム、決済方法、利用者装置、決済プログラム
JP6710401B1 (ja) * 2019-12-05 2020-06-17 ｂａｃｏｏｒ ｄＡｐｐｓ株式会社 対象物を管理する方法及び管理サーバ

Also Published As

Publication number Publication date
JPWO2022101980A1 (fr) 2022-05-19

Similar Documents

Publication Publication Date Title
JP6145188B1 (ja) 情報処理システム、サーバ装置、情報処理方法、及び情報処理プログラム
JP5882122B2 (ja) カード支払情報通知システム、カード支払情報通知方法及びカード支払情報通知プログラム
US10535055B2 (en) Collaborative betting platform
JP7276495B2 (ja) 制御方法、制御プログラム、情報処理装置および制御システム
JP5836162B2 (ja) クレジットカードシステム
WO2022020609A1 (fr) Procédé et système de définition, de création, de gestion et de transaction de classes multiples d'objets numériques
WO2014155664A1 (fr) Dispositif, procédé et programme de gestion d'identifiants
JP6583999B2 (ja) 決済処理装置、決済システム、決済処理方法、及びプログラム
WO2022101980A1 (fr) Système d'aide au paiement et procédé d'aide au paiement
JP6338564B2 (ja) Ａｔｍ予約システムおよび方法
JP7161347B2 (ja) 支払代行装置、決済システム、決済方法、及びプログラム
JP6356326B1 (ja) ポイント変換システム
JP7111560B2 (ja) 支払代行装置、決済システム、決済方法、及びプログラム
JP4838288B2 (ja) 信託型電子決済支援システム、方法、及びプログラム
JP2012203874A (ja) 電子商取引システム
JP2017037593A (ja) 決済処理装置、決済システム、決済処理方法、及びプログラム
JP6844905B2 (ja) 積立購入システム、積立購入方法、積立購入装置、及びコンピュータプログラム
JP2020095711A (ja) 情報処理装置、情報処理方法および情報処理プログラム
JP2020173734A (ja) 商品の運用方法
TW201443797A (zh) 資訊處理系統、資訊處理系統之控制方法、及資訊處理程式
JP7268233B1 (ja) 情報処理装置、情報処理方法及びプログラム
JP7280060B2 (ja) 決済一括管理サーバ、決済情報生成方法及びプログラム
TWI772710B (zh) 提供應用主機介接以進行電子支付之系統及方法
KR101138965B1 (ko) 수수료 쿠폰을 이용한 금융 거래 시스템 및 그 동작방법
JP6827133B1 (ja) 予約システム用エスクロー決済システム及び予約システム用エスクロー決済方法

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 2021553129

Country of ref document: JP

Kind code of ref document: A

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20961508

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20961508

Country of ref document: EP

Kind code of ref document: A1