KR20220048880A - The safe and convenient method to transfer trade account receivable - Google Patents

Abstract

The present invention relates to a technique for efficiently matching an accounts receivables transfer intention and an accounts receivables takeover intention and a technique for preventing the risk of later denying an intention expressed by each party non-face-to-face in a process in which a seller expresses an intention to transfer accounts receivables non-face-to-face and a person holding temporary funds expresses an intention to take over accounts receivables non-face-to-face, in order to conduct a non-face-to-face transfer of accounts receivables. A method for safely and conveniently transferring accounts receivables by using a blockchain comprises the steps in which: a buyer registers accounts receivables for products purchased by the buyer in an accounts receivables relay server in a non-repudiation manner; a seller registers at least one of the registered accounts receivables as a transfer target in the accounts receivables relay server in a non-repudiation manner; a person holding temporary funds registers an intention to take over one of the registered accounts receivables to be transferred in the accounts receivables relay server in a non-repudiation manner; the seller notifies the buyer of an intention to transfer accounts receivables, for which an intention to take over the same is registered, of the seller to a person who indicated the intention to take over the same in a non-repudiation manner; and in each of the above steps, each subject distributes and stores the record of the non-face-to-face expression of an intention by the other party, received by the subject in a manner that the record cannot be tampered with later. Therefore, the method can reduce "uneconomic inconvenience that the seller directly searches for the person holding temporary funds" and "uneconomic inconvenience that the person holding temporary funds directly searches for the seller".

Description

{The safe and convenient method to transfer trade account receivable}

In the present invention, in the process of non-face-to-face transfer of trade receivables, the seller expresses his intention to transfer trade receivables non-face-to-face, and the person holding temporary funds expresses his/her intention to acquire trade receivables non-face-to-face, the intention to transfer trade receivables It relates to a technology for efficiently matching the intention to take over trade receivables and a technology to prevent the risk of later denying the intention expressed by each party non-face-to-face in the above process.

Currently, as one of the methods of cashing out the price delivered by the seller to the buyer, a method of obtaining a loan from a bank, etc. using trade receivables as collateral (hereinafter referred to as the "trade receivable loan method") and receiving the trade receivables as bills A method of transferring at a discount to cash, etc. (hereinafter referred to as "trade receivables factoring method") is widely used.

In addition, these trade receivable-backed loan methods and trade receivable factoring methods have recently been made online, and the convenience has been improved so that there is no need to visit the handling financial company in person.

However, in order to convert trade receivables into cash in this way, it is necessary to obtain a loan from a financial institution or transfer the trade receivables to a financial institution. Since only conservative-oriented financial institutions need to be converted into cash, only trade receivables that conform to the conservative counterparty policy can be converted into cash (hereinafter referred to as “conservative constraint inconvenience”).

In addition, since the subjects that can be converted into cash are limited to financial institutions, the seller who wants to cash out trade receivables suffers from the inconvenience of limited bargaining power (hereinafter referred to as "constraints in the bargaining power of the transferor").

On the other hand, in order to solve the above-mentioned inconvenience of the conservative tendency and the transferor's negotiating power constraint, it is possible to think of a method in which the seller directly searches for temporary fund holders. Excessive inconvenience (hereinafter referred to as "inconvenience of non-economic direct search for temporary fund holders") follows.

On the other hand, in order to solve the above inconvenience of quantitative bargaining power, it is possible to think of a method in which temporary fund holders directly search for sellers who hold trade receivables. Inconvenience (hereinafter referred to as "seller direct shopping non-economic inconvenience") follows.

The object of the present invention is to solve the "conservative-oriented constraint" and "transferor's negotiating power constraint discomfort" accompanying the conventional trade receivable factoring method, and "temporary fund holder direct search non-economic inconvenience" and "seller direct search non-economic inconvenience" "is to reduce

One embodiment of the method according to the features of the present invention for solving this technical problem, the step of a buyer registering the trade receivable for the purchased product in a non-repudiation method in the trade receivable relay server; registering at least one of the seller's trade receivables registered as described above with the trade receivable relay server in a non-repudiation method; registering, in a non-repudiation method, the intention of the person holding temporary funds to acquire one of the registered transfer receivables in a trade receivable relay server; Notifying the buyer of the seller's intention to transfer the trade receivable to the person who has indicated the intention to acquire the trade receivable in a non-repudiation manner as described above; and distributing and storing the records of 'non-face-to-face intentions of the other party received by each subject in each step in a way that cannot be tampered with afterwards; includes

The step of registering the trade receivable for the product purchased by the buyer in a non-repudiation method to the trade receivable relay server includes 'buyer identification information and seller identification information, the date of occurrence of trade receivables, the amount of trade receivables and delivery creating a trade receivable list including at least one 'individual trade receivable information including product identification information and trade receivable settlement date; creating trade receivable registration transaction data including creator identification information and the list of trade receivables; A step in which the person in charge of trade receivable registration business inputs his/her ID and password into the purchaser device; calculating a root hash value of the ID and password as an encryption/decryption key of the person in charge; decrypting the 'encrypted secret key' matched with the ID in the secret key DB with the encryption/decryption key; creating an electronic signature for the trade receivable registration transaction data using the decrypted secret key; transmitting the trade receivable registration transaction data and electronic signature from the purchaser device to a trade receivable relay server; and the trade receivable relay server matches the transaction data serial number in the transaction data DB to store a timestamp, the trade receivable registration transaction data, and an electronic signature, and store the transaction data serial number and timestamp and 'the transaction data serial number' in the hash DB and storing the root hash value of the timestamp and trade receivable registration transaction data and digital signature; includes

The step of the seller registering one or more of his or her registered trade receivables as a transfer object in a non-repudiation manner to the trade receivable relay server comprises: the trade receivables registration transaction data and the electronic transmitting the signature to the corresponding seller device; A step in which the person in charge of the trade receivable transfer business inputs his/her ID and password into the seller device; calculating a root hash value of the ID and password as an encryption/decryption key of the person in charge; decrypting the 'encrypted secret key' matched with the ID in the secret key DB with the encryption/decryption key; inputting a discount rate by the person in charge selecting and matching one or more of the individual accounts receivable information extracted from the trade receivable registration transaction data; creating a list of receivables subject to transfer including at least one 'individual transfer receivable information including the selected individual receivables information and the discount rate' in the seller device; creating transfer object bond registration transaction data including creator identification information and the transfer object bond list; creating an electronic signature for the transfer target bond registration transaction data using the decrypted secret key; transmitting the transfer target receivable registration transaction data and electronic signature from the seller device to a trade receivable relay server; and the trade receivable relay server matches the transaction data serial number in the transaction data DB to store a timestamp, the transfer target receivable registration transaction data, and an electronic signature, and store the transaction data serial number and timestamp and 'the transaction data serial number in the hash DB storing the number, timestamp, trade receivable registration transaction data, and root hash value of the digital signature; includes

The step of registering the person holding the temporary funds in the trade receivable relay server in a non-repudiation way of the intention to acquire one of the registered transfer receivables includes: inputting a comparative value into the 'comparative value input field matched with the account receivable DB field identification information' output to the transferee device; transmitting the input information from the transferee device to a trade receivable relay server; extracting field values of records that satisfy all of the 'transferable trade receivable search conditions implied by the transmitted information' in the trade receivable relay server, preparing transferable trade receivable identification information, and transmitting it to the transferee device; selecting one of the transferable trade receivable identification information by the transferee; The transferee inputs the master password into the transferee device; retrieving the accounts receivable relay agency identification information in the secret information DB and calculating 'the root hash value of the accounts receivable relay agency identification information and the master password' as an encryption/decryption key for the accounts receivable relay agency; retrieving 'encrypted secret key for accounts receivable relay agency' in the secret information DB and decrypting using the encryption decryption key for accounts receivable relay agency; creating trade receivables application transaction data including a public key for trade receivables relay agency as author identification information and the transferable trade receivable identification information; creating an electronic signature for the trade receivable transfer application transaction data using the secret key for the trade receivable relay agency; transmitting the trade receivable application transaction data and electronic signature from the transferee device to the trade receivable relay server; and the trade receivable relay server matches the transaction data serial number in the transaction data DB to store a timestamp, the transaction data for the takeover of accounts receivable, and an electronic signature, and store the transaction data serial number and timestamp and 'the transaction data series in a hash DB storing the number and timestamp, the transaction data for the transfer of accounts receivable and the root hash value of the digital signature; includes

As described above, the step of notifying the buyer of the seller's intention to transfer the trade receivable to the person who has indicated the intention to acquire the trade receivable in a non-repudiation way for the trade receivables registered as a transferee as described above is, in the trade receivable relay server, creating transfer notification transaction data including seller identification information as author identification information, buyer identification information as recipient identification information, and transfer receivable identification information, transferee's real name, and transfer amount; Transfer notification request transaction data including 'the public key of the trade receivable relay institution as author identification information, the seller identification information as recipient identification information, the transfer notification transaction data, the transfer target trade receivable identification information, the transfer amount and discount rate' writing; transmitting the transfer notification request transaction data and electronic signatures for the transfer notification request transaction data to the seller device in the trade receivable relay server; extracting transfer notification transaction data from transfer notification request transaction data in the seller device; A step in which the person in charge of the trade receivable transfer business inputs his/her ID and password into the seller device; calculating a root hash value of the ID and password as an encryption/decryption key of the person in charge; decrypting the 'encrypted secret key' matched with the ID in the secret key DB with the encryption/decryption key; creating an electronic signature for the transfer notification transaction data using the secret key; transmitting the transfer notification transaction data and the electronic signature from the seller device to the accounts receivable relay server and the purchaser device; The trade receivable relay server matches the transaction data serial number in the transaction data DB, stores the timestamp, the transfer notification transaction data, and the electronic signature, and stores the transaction data serial number and timestamp in the hash DB and 'the transaction data serial number and time' Storing the 'root hash value of the stamp and transfer notification transaction data and digital signature'; includes

In each of the above steps, the step of distributing and storing the records of 'the other party's non-face-to-face intention' received by each subject in a way that cannot be tampered with afterwards is performed in each subject's device in their own hash DB for each block generation cycle. extracting 'matched timestamps, transaction data serial numbers, and root hash values' corresponding to the block generation period and calculating their root hash values as integrity proofs corresponding to the block generation period; creating each period proof transaction data including 'own public key as author identification information', corresponding block generation period identification information, and the integrity proof in the device of each subject; and creating, in the device of each subject, an electronic signature for the proof transaction data for each period by using the secret key of the subject. Broadcasting the 'verified transaction data and digital signature for each period' written by the device in the block chain network; includes

According to the embodiment of the present specification, since trade receivables can be transferred to various temporary fund holders, including individuals, "conservative tendency constraint" and "transferor's negotiating power constraint inconvenience" that must be converted into cash only for conservative financial institutions this is resolved

On the other hand, if the seller registers the trade receivables subject to transfer in the trade receivable relay server, temporary fund holders can search for the trade receivables subject to transfer on their own, thereby avoiding the "inconvenience of inefficiency in searching for temporary fund holders directly" from the seller's point of view.

In addition, the transferee can search for trade receivables that satisfy the above conditions by simply presenting his/her conditions to the trade receivable relay server, thereby avoiding the "inconvenience of inefficiency in finding direct sellers".

In addition, when the 'trade receivables registration transaction data and electronic signature' transmitted to the trade receivable relay server to register the trade receivables for the products purchased by the buyer to the trade receivable relay server is received from the trade receivable relay server, the 'sales The root hash value of information including 'bond registration transaction data and digital signature' is stored in the hash DB, and the root hash value of the root hash values stored in the hash DB in the corresponding cycle for each block generation cycle is stored in the block chain network. After broadcasting, the trade receivable registration transaction data includes 'buyer identification information as author identification information' and 'trade receivable relay agency identification information as recipient identification information', so the buyer sells the trade receivable registration transaction data afterwards It becomes impossible to deny the fact that it was transmitted to the bond relay server.

In addition, when the 'transfer target receivables registration transaction data and electronic signature' sent by the seller to the trade receivable relay server to register one or more of his or her trade receivables as a transfer target is received from the trade receivable relay server, Storing the root hash value of information including the 'transfer target bond registration transaction data and digital signature' in a hash DB, and root hash values of the root hash values stored in the hash DB in the corresponding cycle for each block generation cycle is broadcast to the blockchain network, and the transfer target receivable registration transaction data includes 'seller identification information as author identification information' and 'trade receivable relay agency identification information as recipient identification information' The fact that the target receivable registration transaction data is transmitted to the trade receivable relay server cannot be denied.

In addition, the 'trade receivable transfer application transaction data and electronic signature' transmitted to the trade receivable relay server by the person holding the temporary funds to register their intention to acquire one of the registered transfer receivables in the trade receivables relay server When the relay server receives it, the root hash value of the information including the 'in the transaction data for the application for acquisition of accounts receivable and the digital signature' is stored in the hash DB, and the root hash stored in the hash DB at the corresponding cycle for each block generation cycle Broadcast the root hash value of the values to the blockchain network, and in the trade receivable transfer application transaction data, 'identification information of the temporary fund holder as author identification information' and 'trade receivable relay agency identification information as recipient identification information' Because it is included, it is impossible to deny the fact that the temporary fund holder transmits the trade receivable application transaction data to the trade receivable relay server afterwards.

In addition, the 'transfer notification transaction data and electronic signature' sent by the seller to the buyer and the trade receivable relay server to notify the buyer of 'the seller's intention to transfer the trade receivable to the person who has indicated the intention to acquire the above trade receivable' When the relay server receives it, it stores the root hash value of information including the 'in the transfer notification transaction data and the digital signature' in the hash DB, and stores the root hash values stored in the hash DB in the corresponding cycle for each block generation cycle. The root hash value is broadcast to the block chain network, and the transaction data for the transfer of accounts receivable includes 'seller identification information as author identification information' and 'buyer identification information as recipient identification information'. The fact that the transfer notification transaction data is transmitted to the purchaser device and the account receivable relay server cannot be denied.

1 is a block diagram of a device for implementing a method of transferring trade receivables safely and conveniently using a block chain according to the present invention.
2 is a method of safely and conveniently transferring trade receivables using a block chain according to the present invention. In one embodiment, the purchaser registers the trade receivable for the product he/she purchased in a non-repudiation method in the trade receivable relay server A flowchart illustrating an embodiment.
3 is a method for safely and conveniently transferring trade receivables using a block chain according to the present invention. In one embodiment, a trade receivable relay server is a method in which the seller is prevented from denying one or more of his registered trade receivables as transfer targets. It is a flowchart showing an embodiment of the operation of registering to .
4 is a method for safely and conveniently transferring trade receivables using a block chain according to the present invention in an embodiment in which the transferee does not deny his/her intention to transfer one of the registered transfer receivables. Trade receivable relay server It is a flowchart showing an embodiment of the operation of registering to .
5 is a method for safely and conveniently transferring trade receivables using a block chain according to the present invention in one embodiment is a flowchart showing
6 is a method for safely and conveniently transferring trade receivables using a block chain according to the present invention. It is a flowchart showing an embodiment of the operation of notifying the purchaser of the fact in a non-repudiation manner.
7 is a flowchart illustrating an operation of settling the transfer price of trade receivables notified of transfer in an embodiment of a method for safely and conveniently transferring trade receivables using a block chain according to the present invention.
8 is a flowchart illustrating an operation of settling trade receivables on the settlement date of trade receivables transferred at a discount in an embodiment of a method for safely and conveniently transferring trade receivables using a block chain according to the present invention.
9 is a method for safely and conveniently transferring trade receivables using a block chain according to the present invention in one embodiment It is a flow chart showing an embodiment of the operation of distributed storage in a method.

Hereinafter, the present invention will be described in detail through preferred embodiments described with reference to the accompanying drawings so that those skilled in the art can easily understand and reproduce. In describing the present invention, if it is determined that a detailed description of a related well-known function or configuration may unnecessarily obscure the gist of the embodiments of the present invention, the detailed description thereof will be omitted. Various embodiments of the present invention are different, but need not be mutually exclusive. For example, specific shapes, structures, and characteristics described in connection with a specific embodiment of the present invention may be implemented in other embodiments without departing from the spirit and scope of the present invention.

In addition, the position or arrangement of individual components in each embodiment may be variously changed without departing from the spirit and scope of the present invention. The following detailed description is not intended to limit the present invention, and terms used in the detailed description are selected for readability or convenience of description.

Terms used throughout the present specification are terms defined in consideration of the functions in the embodiment of the present invention, and can be sufficiently modified according to the intention of the trade receivable relay server operator or the notary server operator, industry practices, etc. Therefore, definitions of these terms should be made based on the content throughout this specification. Meanwhile, when the same reference numerals are used in a plurality of drawings, the same reference numerals refer to the same or similar functions for various embodiments.

In addition, the "root hash value" referred to in this specification means a hash value in which hash values of each transaction data included in a predetermined block are compressed into a Merkle tree structure or other predetermined structure using a predetermined hash function.

In addition, the "master password" referred to in this specification is a password selected and memorized by a user, and means a password that does not need to be exposed or stored in external devices such as a bank server or remittance server, as well as to a customer terminal or to anyone in the world.

In addition, the "real-name linked public key" referred to in this specification refers to the real-name verification financial company registered by matching the confirmed real name with the real-name financial company according to the real-name financial system for one or more of the buyer, seller, trade receivables relay agency, and transferee. It means the public key of the subject.

In addition, the "real-name-linked secret key" referred to in this specification means a secret key that matches the real-name-linked public key according to a public key algorithm.

In addition, "real-name verification financial company" referred to in this specification means a subject in charge of real-name verification under the real-name financial system.

Also, "input" referred to in this specification refers to an operation in which predetermined information is input into a predetermined system. Accordingly, an operation of inputting predetermined information using an input unit of the system and an operation of receiving predetermined transmission information using a transmission/reception unit of the system may be examples of the "input".

In addition, the term "timestamp" referred to in this specification refers to information in which the date and time of the occurrence of a predetermined operation are displayed in a predetermined format in order to identify the time when the predetermined operation occurs. Accordingly, identification information of the date and hour, minute, and second output by a timer configured in a predetermined user terminal or a predetermined server at the time a specific step is operated may be an embodiment of the timestamp.

Also, in the present specification, "information matching OO" means information that enables extraction of "OO". Therefore, “OO” itself may be an embodiment of “information matching OO”.

Also, in this specification, "select OO" means that the user inputs information for selecting "OO" by touching or clicking the area where "OO" is output among the areas output to the output unit of the trader's terminal. means to do

Hereinafter, the configuration and operation of the present invention will be described in more detail based on the accompanying drawings.

1 is a block diagram of a device for implementing a method of transferring trade receivables safely and conveniently using a block chain according to the present invention.

The accounts receivable relay server 100 communicates with one or more seller apparatuses 200, one or more purchaser apparatuses 300, one or more transferee apparatuses 400 and an escrow server 500 through a predetermined network, and a customer DB 110 ) and transaction data DB 120 , hash DB 130 , accounts receivable DB 140 , financial relay DB 150 , account DB 160 , and escrow DB 170 as components.

The customer DB 110 constitutes an ID field, a password field, a terminal verification code field, a public key field, a real name field, a real name number field, a real name account field, an address field, an e-mail address field, and a phone number field. According to an additional aspect of the present invention, each of the fields includes 'settlement account ID given to each customer by the accounts receivable relay agency', 'a hash value of the password registered by the customer with the accounts receivable relay agency', and 'trade receivable relay agency', respectively. This single-use terminal verification code shared with the customer's device', 'public key registered by the customer with the trade receivables relay agency', 'the customer's real name', 'the customer's real name number' and 'the customer's purpose for receiving payment' 'Your real name account number registered with the trade receivable relay agency' as 'the customer's address registered with the trade receivable relay agency' Your phone number registered with the relay agency is stored.

According to the first additional aspect of the public key field, the public key stored in the public key field is a 'public key registered by the customer with the accounts receivable relay agency' (hereinafter referred to as "the public key for the accounts receivable relay agency").

According to the second additional aspect of the public key field, the public key stored in the public key field is 'a real name linked public key registered by the customer after verifying his or her real name with a real name verification financial company where his or her real name account is opened' (hereinafter "" Real-name linked public key").

The transaction data DB 120 stores a timestamp, transaction data, and an electronic signature by matching the transaction data serial number. According to an additional aspect of the present invention, the transaction data is at least one of trade receivable registration transaction data, transfer target receivable registration transaction data, trade receivable takeover application transaction data, and transfer notification transaction data.

The hash DB 130 stores a timestamp and a root hash value by matching the transaction data serial number.

The trade receivable DB 140 constitutes a seller field, a purchaser field, an occurrence date field, an amount field, a delivery product field, a payment date field, a transfer object registration date field, and a transferable amount field. According to an additional aspect of the present invention, the accounts receivable DB 140 further configures 'at least one of a discount rate field and a subscription closing date field'.

According to the first embodiment of the seller field, 'settlement account ID given to the seller by the trade receivable relay agency' is stored in the seller field as seller identification information.

According to the second embodiment of the seller field, 'public key for trade receivables relay agency registered by the seller to the trade receivable relay agency' is stored in the seller field as seller identification information.

According to the third embodiment of the seller field, the seller field stores the 'real-name linked public key registered by the seller with the trade receivable relay agency' as seller identification information.

The financial relay DB 150 includes a trade receivable field, a seller field, a settlement date field, a transfer application date field, a transfer applicant field, an acquisition request trade receivable amount field, an escrow account field, a transfer notice date field, a transfer payment settlement date field, a transfer amount field, Discount rate field, buyer real name field, buyer real name number field, buyer address field, buyer email address field, buyer phone number field, seller real name field, seller real name number field, seller address field, seller email address field, seller phone number field and the seller account field, the transferee real name field, the transferee real name number field, and the transferee account field, and in each of the fields, trade receivable identification information, seller identification information, payment date and 'matched trade receivable transfer application transaction data and electronic signature, respectively Timestamp (or date) at the time of receipt of ', identification information of the applicant for trade receivables, identification information of the applicant for takeover, the amount of trade receivables applied for takeover, and 'Yes scroo included in the escrow confirmation transaction data for the amount of trade receivables received from the escrow institution 'Account ID' and 'Time stamp (or date) when the matching transfer notification transaction data and electronic signature are received' and 'Time stamp (or date) when the matching escrow transfer notification transaction data and electronic signature are received )' and 'Amount of trade receivable transferred' and 'Trade receivable discount rate applied at the time of transfer' and 'Real name and real name number and address and e-mail address and phone number of trade receivable buyer' and 'Real name and real name of transferor of trade receivables' Stores the number, address, e-mail address, phone number, account receivable transfer payment account ID' and 'trade receivable transferee's real name and real name number and account receivable payment receipt account ID'.

An embodiment of the trade receivable transfer applicant identification information is a public key for trade receivables relay agency of the trade receivable transfer applicant.

According to an additional aspect of the present invention, the financial relay DB 150 further includes a transferee proposal discount rate field and a transfer receivable amount field.

The account DB 160 constitutes an account ID field and a balance field. According to an additional aspect of the present invention, the account ID field stores the account ID of the transferee's trade receivable payment receipt and the seller's trade receivable transfer payment account ID.

The escrow DB 170 constitutes an account field, a trade receivable field, a transfer application receivable amount field, a discount transfer amount field, a timestamp field, an inscription field, and a fulfillment date field. In the account field, the YesCrow account ID is stored, in the trade receivable field, transferable trade receivable identification information is stored, in the timestamp field, 'time stamp for the first mapping key received from the escrow institution' is stored, and the inscription field 'Inscription for escrow matching for the use of the second mapping key received from the escrow institution' is stored, and the date (or timestamp) when the transfer notice is received is stored in the implementation date field.

The seller device 200 communicates with the accounts receivable relay server 100 and one or more purchaser devices 300 and the escrow server 500 through a predetermined network, and the secret information DB 210 and the transaction data DB 220 and It includes a hash DB 230, trade receivable DB 240, and transfer receivable DB 250 as components.

In the secret information DB 210, an 'encrypted secret key' is stored by matching one or more IDs.

The transaction data DB 220 stores a timestamp, transaction data, and an electronic signature by matching the transaction data serial number. Trade receivable registration transaction data and transfer notification request transaction data are examples of the transaction data.

The hash DB 230 stores a timestamp and a root hash value by matching the transaction data serial number.

The trade receivable DB 240 comprises a seller field, a purchaser field, a date of occurrence field, an amount field, a holding amount field, a delivery product field, a payment date field, a transfer subject registration date field, and a discount rate field, and each field includes seller identification information and Purchaser identification information, the date of occurrence of trade receivables, the amount of trade receivables, 'the amount deducted from the amount of trade receivables', product identification information, the date of settlement of trade receivables, and 'the time when the seller notifies the transfer of trade receivables to the transferee of 'time stamp (or date)' and 'trade receivable discount rate applied at the time of the transfer' are stored.

According to an additional aspect of the present invention, the trade receivable DB 240 further comprises a subscription deadline field, and the 'deadline date at which the seller receives an application for takeover of the trade receivables of the record' is stored in the subscription deadline field. .

The transfer receivable DB 250 constitutes a trade receivable field, a transfer amount field, a discount rate field, a discount amount field, and a transfer amount after discount field, and each of the fields includes 'transfer target trade receivable identification information, transfer amount, transfer discount rate and Save the discount amount and transfer amount after discount.

The purchaser device 300 communicates with the trade receivable relay server 100 and one or more seller devices 200 and through a predetermined network, and the secret information DB 310, the transaction data DB 320, and the hash DB 330. and a trade receivable DB 340 and a transfer receivable DB 350 as components.

In the secret information DB 310, an 'encrypted secret key' is stored by matching one or more IDs.

The transaction data DB 320 stores a timestamp, transaction data, and an electronic signature by matching the transaction data serial number. Transfer notification transaction data is an embodiment of the transaction data.

The hash DB 330 stores a timestamp and a root hash value by matching the transaction data serial number.

The accounts receivable DB 340 constitutes a seller field, a delivery date field, a trade receivable amount field, an untransferred amount field, a delivery product field, a settlement date field, a trade receivable registration date field, and a settlement execution date field.

The transfer receivable DB 350 includes a trade receivable identification information field, a purchaser identification information field, a trade receivable occurrence date field, a trade receivable amount field, a delivery product identification information field, a settlement date field, a settlement execution date field, and a transfer receivable amount field and The seller identification information field, the seller real name field, the seller real name number field, the seller address field, the seller e-mail address, the seller phone number field, the transferee real name field, the transferee real name number field, and the transferee account field are configured.

The transferee device 400 communicates with the accounts receivable relay server 100 and one or more seller devices 200 and the escrow server 500 through a predetermined network, and includes a secret information DB 411 as a component.

The secret information DB 411 comprises a site field, an ID field, a password field, a terminal verification code field, a public key field, and a secret key field, and each field contains site identification information, 'ID registered in the site' and encrypted 'corresponding The 'password of the transferee registered in the site' and the encrypted 'one-time terminal verification code shared by the transferee device 400 with the site', the public key and the 'encrypted secret key' are stored. An example of the 'ID registered on the site' is 'a real name account ID allocated by the transferee from the escrow institution'.

According to an additional aspect of the present invention, in one record of the secret information DB 411, the 'site field, the ID field, the password field, the terminal verification code field, the public key field and the private key field' are respectively the accounts receivable relay agency. trade name, 'settlement account ID given to the transferee by the trade receivable relay agency' (hereinafter referred to as "trade receivable relay agency ID") and the encrypted 'password registered by the transferee with the trade receivable relay agency' (hereinafter referred to as "trade receivables") “Password for relay agency”) and encrypted 'terminal verification code shared by the accounts receivable relay agency with the transferee's terminal' (hereinafter referred to as "terminal verification code for accounts receivable relay agency") and 'for accounts receivable relay agency of the transferee' The 'public key' and the encrypted 'secret key matching the public key' (hereinafter referred to as the "secret key for trade receivables relay agency") are stored respectively, and the 'site field, ID field, and password field of the other record are In the terminal verification code field, public key field, and secret key field, 'the name of the real name verification financial company that opened the real name account to receive the trade receivable payment transferred by the transferee' and 'identification information of the real name account', respectively The encrypted 'password registered by the transferee with the real-name confirmation financial company' (hereinafter referred to as "password for real-name confirmation financial company") and the encrypted 'terminal verification code shared by the transferee device 400 by the real-name confirmation financial company '(hereinafter referred to as "Terminal Verification Code for Real-Name Confirmation Financial Company") and 'Real-Name Linked Public Key of the Assignee' and encrypted 'Real-Name Linked Secret Key Matching the Real Name Linked Public Key' (hereinafter "Real Name Linked Secret Key") ") are stored respectively.

The escrow server 500 communicates with the trade receivable relay server 100, the seller device 200, and one or more transferee devices 400 through a predetermined network, and the escrow account DB 510 and the transaction data DB 520 and It includes a hash DB 530 and a real name account DB 540 as components.

The escrow account DB 510 constitutes an escrow account field, a real name account field, a trade receivable field, a transfer receivable amount field, an escrow amount field, a timestamp field, an inscription field, and an application transaction field. According to an additional aspect of the present invention, the escrow account field is pre-stored with a yes-crow account ID, transferable trade receivable identification information is stored in the trade receivable field, and a transaction data serial number is stored in the application transaction field.

The transaction data DB 520 stores a timestamp, transaction data, and an electronic signature by matching the transaction data serial number. The escrow confirmation application transaction data and the escrow account update transaction data are examples of the transaction data.

The hash DB 530 stores a timestamp and a root hash value by matching the transaction data serial number.

The real name account DB 540 comprises a real name account field, a public key field, a password field, a terminal verification code field, and a balance field. The real name account ID is stored in the real name account field, the real name linked public key registered by the account holder through real name verification is stored in the public key field, the 'hashed account owner's password' is stored in the password field, and the account holder's password is stored in the terminal verification code field The terminal verification code shared with the device is stored, and the balance of the 'real name account corresponding to the matched real name account ID' is updated in the balance field.

According to an additional aspect of the present invention, the real name account DB 540 may further configure a 'real name field in which the real name of the account holder is stored' and a 'real name number field in which the real name number of the account holder is stored'.

2 is a method of safely and conveniently transferring trade receivables using a block chain according to the present invention. In one embodiment, the purchaser registers the trade receivable for the product he/she purchased in a non-repudiation method in the trade receivable relay server. A flowchart illustrating an embodiment.

In step 101, the record in which the default value is stored in the trade receivable registration date field is extracted from the trade receivable DB 340 in the purchaser device 300, and the 'seller field value, the delivery date field value, the trade receivable amount field value and the delivered product The field value and the date of payment field value are extracted as 'seller identification information, the date of occurrence of trade receivables, the amount of accounts receivable, and the identification information of the delivered products and the date of settlement of the accounts receivable', respectively, and the entity operating the purchaser device 300 (hereinafter referred to as the "buyer") (hereinafter referred to as "purchase identification information") and individual accounts receivable information including the above 'seller identification information, the date of occurrence of trade receivables, the amount of trade receivables, identification information of delivered products and the date of settlement of trade receivables' Prepare a list of trade receivables including the above.

In the first embodiment of the purchaser identification information, the entity (hereinafter referred to as "trade receivable relay agency") that operates the trade receivable relay server 100 is the entity that operates the purchaser device 300 (hereinafter referred to as "buyer") ) is the settlement account ID given to

The second embodiment of the purchaser identification information is a public key (hereinafter referred to as a "real name-linked public key") registered by the purchaser after real-name verification with his/her real-name verification agency.

The third implementation of the purchaser identification information is a public key registered by the purchaser with the trade receivable relay agency (hereinafter referred to as "the public key for the purchaser's trade receivable relay agency").

Hereinafter, the third embodiment of the purchaser identification information will be mainly described.

The first embodiment of the seller identification information is a settlement account ID given to the seller by the subject (hereinafter referred to as "trade receivable relay agency") operating the accounts receivable relay server 100 .

The 'second embodiment and the third embodiment' of the seller identification information are 'the seller's real-name linked public key and the seller's public key for accounts receivable relay agency', respectively.

The fourth embodiment of the seller identification information is pseudonym information given by the buyer to identify the 'subject who delivered the product subject to the trade receivable' (hereinafter referred to as the "seller") from other sellers, and the purchaser device It is pseudonymous information independent of pseudonym information given to identify the seller in devices other than (300).

Hereinafter, the third embodiment of the seller identification information will be mainly described.

Meanwhile, according to another additional aspect of the present invention, the delivery product identification information is a value obtained by encrypting the delivery product name with 'the seller's own public key registered with the purchaser'.

In step 102, the purchaser device 300 creates trade receivable registration transaction data including the creator identification information and 'the list of trade receivables created in step 101'.

According to the first additional aspect of step 102, the author identification information is a public key linked to the real name of the purchaser.

According to the second additional aspect of step 102, the author identification information is a public key for a buyer's accounts receivable relay agency.

Hereinafter, an embodiment to which the second additional aspect of step 102 is applied will be mainly described.

In step 103, the ID and password of the person in charge of trade receivable registration are input using an input unit (not shown) in the purchaser device 300 .

In step 104, the purchaser device 300 calculates each hash value of the 'ID and password input in step 103', and calculates the root hash value of the calculated hash values as the encryption/decryption key of the person in charge.

In step 105, the 'encrypted secret key' matching the 'ID input in step 103' is searched for in the secret information DB 310, and the searched 'encrypted secret key' is converted into the 'encryption/decryption key calculated in step 104' decrypt it with

The first embodiment of the 'encrypted secret key' is a value obtained by encrypting the purchaser's real name-linked secret key with the same encryption/decryption key as the 'encryption/decryption key calculated in step 104'.

The second embodiment of the 'encrypted secret key' is a value obtained by encrypting the purchaser's secret key for the receivables relay agency with the same encryption/decryption key as the 'encryption/decryption key calculated in step 104'.

Hereinafter, the second embodiment of the 'encrypted secret key' will be mainly described.

In step 106, the purchaser device 300 creates an electronic signature for the 'trade receivable registration transaction data created in step 102' using the 'secret key decrypted in step 105'.

In step 107, the purchaser device 300 transmits the 'trade receivable registration transaction data created in step 102' and the 'electronic signature created in step 106' to the trade receivable relay server 100, and the accounts receivable DB 340 transmits the 'step' 'Trade receivable amount constituting individual accounts receivable information in step 101' and 'time stamp of when step 107 is operated' are stored in the 'untransferred amount field and trade receivable registration date field' of the 'record extracted in step 101', respectively. .

In step 108, when the trade receivable relay server 100 receives 'the trade receivable registration transaction data and the electronic signature transmitted in step 107', the electronic signature is generated using the creator identification information included in the trade receivable registration transaction data. verify

If the verification is successful, steps 109 and below are operated.

In step 109, by matching the transaction data serial number in the transaction data DB 120 of the trade receivable relay server 100, the 'time stamp when step 108 is operated' and the 'trade receivable registration transaction data and electronic signature' are stored and calculate the root hash value of the 'transaction data serial number and timestamp, trade receivable registration transaction data and electronic signature', and match the 'transaction data serial number and timestamp' in the hash DB 130 to the Stores the root hash value.

In step 110, in the trade receivable relay server 100, in each individual trade receivable information of the trade receivable list included in the 'trade receivable registration transaction data received in step 108', 'buyer identification information, seller identification information, trade receivable The trade receivable amount, delivery product identification information, and trade receivable settlement date are extracted, respectively, to constitute one record in the trade receivable DB 140, and the 'buyer field, seller field, accrual date field, amount field, amount field and delivery product' of the records, respectively. field and payment date field'.

According to an additional aspect of the present invention, the trade receivable relay server 100 is seller identification information included in each individual receivable information included in the trade receivable list included in the 'trade receivable registration transaction data received in step 108'. are the same, and following step 110, transmitting the 'trade receivable registration transaction data and electronic signature received in step 108' from the trade receivable relay server 100 to the node corresponding to the seller identification information; is composed

On the other hand, according to another additional aspect of the present invention, users who have authenticated themselves to the accounts receivable relay server 100 and connected to the records stored in the accounts receivable DB 140 ' among the seller identification information and the purchaser identification information One or more' can search or download records corresponding to 'identification information registered with the trade receivable relay agency'.

3 is a method of safely and conveniently transferring trade receivables using a block chain according to the present invention. In an embodiment, a trade receivable relay server in a method in which a seller is able to transfer one or more of his or her registered trade receivables as a non-repudiation method. It is a flowchart showing an embodiment of the operation of registering to .

In step 201, when the seller device 200 receives the 'trade receivable registration transaction data and electronic signature' transmitted from the 'at least one of the buyer device 300 and the trade receivable relay server 100', the transaction data DB 220 stores the 'time stamp at the time step 201 is operated' and the 'trade receivable registration transaction data and electronic signature' by matching the transaction data serial number in the 'transaction data serial number and timestamp and trade receivable registration transaction data and 'digital signature' is calculated, and the root hash value is stored by matching the 'transaction data serial number and timestamp' in the hash DB 230 .

According to an additional aspect of the present invention, prior to step 201, verifying the electronic signature using the creator identification information included in the trade receivable registration transaction data; is operated, and if the verification is successful, step 201 is operated.

In the seller device 200 in step 202, in the list of trade receivables included in the 'trade receivable registration transaction data received in step 201', 'buyer identification information and seller identification information, the date of occurrence of trade receivables, trade receivable amount, and delivery product identification information' and 'individual trade receivable information including the date of settlement of trade receivables' are extracted, respectively, to form one record for each individual trade receivable information in the trade receivable DB 240, and the 'buyer field and 'Buyer identification information, seller identification information, trade receivable accrual date, trade receivable amount, delivery product identification information and sales' Receivable settlement date' is stored respectively.

In step 203, the ID and password of the person in charge of the trade receivable transfer business are input using an input unit (not shown) in the seller device 200 .

In step 204, the seller device 200 calculates each hash value of the 'ID and password input in step 203', and calculates the root hash value of the calculated hash values as the encryption/decryption key of the person in charge.

In step 205, the 'encrypted secret key' matching the 'ID input in step 203' is searched for in the secret information DB 210, and the retrieved 'encrypted secret key' is used as the 'encryption/decryption key calculated in step 204' decrypt it with

The first embodiment of the 'encrypted secret key' is a value obtained by encrypting the seller's real name-linked secret key with the same encryption/decryption key as the 'encryption/decryption key calculated in step 104'.

The second embodiment of the 'encrypted secret key' is a value obtained by encrypting the seller's secret key for the receivables relay agency with the same encryption/decryption key as the 'encryption/decryption key calculated in step 104'.

Hereinafter, the second embodiment of the 'encrypted secret key' will be mainly described.

In step 206, 'records in which the settlement date field value is later than the current date and the transfer target registration date field value is the default value' from each record of the trade receivable DB 240 is extracted and output, and a discount rate input field is output for each record.

According to an additional aspect of the present invention, in step 207, 'at least one of the discount amount input field, the transfer amount after discount input field, and the transfer subscription deadline input field' is further output for each record.

In step 207, the person in charge of the trade receivable transfer service selects 'at least one of the records output in step 206' using the input unit (not shown) of the seller device 200, and inputs a discount rate in the discount rate input field matching the selected record do.

According to the first additional aspect of step 207, when a discount rate is input in the 'discount rate input field output in step 206', the seller apparatus 200 determines that the record matching the input field is selected by the person in charge of the trade receivable transfer service do.

According to the second additional aspect of step 207, in step 207, the person in charge of the transfer of accounts receivable uses the input unit (not shown) of the seller device 200 to enter the 'delivery subscription deadline input field output in step 206'. to enter; includes

According to another aspect of step 207, in step 207, the person in charge of transfer of accounts receivable uses an input unit (not shown) of the seller device 200 to 'one of the 'discount amount input field outputted in step 206 and the transfer amount after discount input field' inputting 'one of the discount amount and the transfer amount after discount' into '; and calculating 'remaining uninputted values of the discount rate, the discount amount, and the post-discount transfer amount' using the 'corresponding one of the discount rate, the discount amount, and the post-discount transfer amount input in step 207 '; includes

In one embodiment, if a discount rate is entered in step 207, 'the amount of trade receivables of the record selected in step 207 x the discount rate x the number of days remaining until the date of settlement of the trade receivables of the record ÷ 365' is calculated as the discount amount, and 'the trade receivable amount - 'The discount amount' is calculated as the transfer amount after discount.

In another embodiment, if a discount amount is entered in step 207, 'the discount amount ÷ the trade receivable amount of the record selected in step 207 ÷ 365 x the number of days remaining until the trade receivable settlement date of the record' is calculated as the discount rate, and 'the trade receivable amount - Calculate the above discount amount as the transfer amount after discount.

In another embodiment, if the transfer amount after discount is entered in step 207, 'trade receivable amount of the record selected in step 207 - the transfer amount after discount' is calculated as the discount amount, and 'the discount amount ÷ sales of the record selected in step 207' The amount of receivables x 365 ÷ the number of days remaining until the date of settlement of trade receivables of the record' is calculated as the discount rate.

In step 209, 'time stamp at the time when step 207 is operated' and 'step 207' in the 'transfer target registration date field and discount rate field' of the 'record selected in step 207' in the trade receivable DB 240 in the seller device 200 in step 209, respectively store the 'discount rate input in step 207, 'each buyer field value, seller field value, occurrence date field value, amount field value, delivery product field value, and settlement date field value' of the records selected in step 207 and the 'of the record Prepare a list of receivables subject to transfer including one or more individual receivables subject to transfer information consisting of 'discount rate stored in the discount rate field'.

In step 207, the step of inputting the application deadline for transfer; When an additional aspect including 240) in the subscription deadline field, the transfer subscription deadline is further stored.

Hereinafter, an embodiment of composing the individual transfer target bond information with the discount rate and each buyer field value, seller field value, occurrence date field value, amount field value, delivery product field value, and settlement date field of the records selected in step 207 will be explained based on

In step 210, the seller device 200 creates transfer object bond registration transaction data including 'seller identification information as author identification information' and 'transfer object bond list created in step 209'.

The first embodiment of the seller identification information is a real-name linked public key registered by the 'seller operating the seller device 200' after real-name verification with his/her real-name verification agency.

The second embodiment of the author identification information is a public key for a trade receivable relay agency registered by the seller with the trade receivable relay agency.

Hereinafter, the second embodiment will be mainly described.

In step 211, the seller device 200 creates an electronic signature for the 'transfer target bond registration transaction data created in step 210' using the 'secret key decrypted in step 205'.

In step 212 , the seller device 200 transmits the 'transfer target receivable registration transaction data created in step 210 ' and the 'electronic signature created in step 211' to the trade receivable relay server 100 .

In step 213, when the trade receivable relay server 100 receives the 'transfer target receivables registration transaction data and electronic signature transmitted in step 212', using the 'writer identification information included in the transfer target receivables registration transaction data' The electronic signature is verified.

If the verification is successful, step 214 is operated.

In step 214, by matching the transaction data serial number in the transaction data DB 120 of the trade receivable relay server 100, the 'time stamp at the time step 213 is operated' and the 'transfer target receivable registration transaction data and electronic signature' Store, calculate the root hash value of the 'transaction data serial number and timestamp, transfer target bond registration transaction data and electronic signature', and match the 'transaction data serial number and timestamp' in the hash DB 130 to store the root hash value.

In step 215, in the trade receivable relay server 100, in the list of receivables to be transferred included in the 'transfer target receivable registration transaction data received in step 213', the 'Individual trade receivable information including delivery product identification information, trade receivable settlement date and discount rate' is extracted, respectively, and 'buyer field, seller field, occurrence date field, amount field, delivery product field and settlement date field' are extracted from the trade receivable DB 140 extracts the record storing the extracted information in the 'transfer target registration date field and discount rate field' of the record, 'time stamp at the time step 213 is operated' and 'discount rate included in the individual accounts receivable information' save the

When one or more of the individual transfer subject receivable information included in the transfer subject receivables list prepared in step 209 applies an additional aspect including 'the closing date of the acquisition subscription input in step 207' is applied, step 215 is a trade receivable relay server In (100), the operation of extracting the closing date for the acquisition of receivables matching the extracted individual receivable information from the list of receivables subject to transfer included in the 'transfer target receivables registration transaction data received in step 213', and in the trade receivables DB (140) and storing the 'extracted transfer subscription deadline' in the subscription deadline field of the extracted record.

According to an additional aspect of the present invention, users who have authenticated themselves to the accounts receivable relay server 100 and accessed the records stored in the accounts receivable DB 140 have a transfer target registration date field value other than the default value. You can search or download them. According to an additional aspect of the present invention, at this time, one or more field values of the records to be searched or downloaded may be masked or excluded from the search or download target.

Figure 4 is a method of safely and conveniently transferring trade receivables using a block chain according to the present invention in a way that the transferee does not deny the intention of the transferee to take over one of the registered transfer receivables trade receivables relay server It is a flowchart showing an embodiment of the operation of registering to .

In step 301, the transferee device 400 matches with one or more field identification information constituting the 'trade receivable DB 140' provided by the trade receivable relay server 100 and includes one or more input fields for inputting comparative values. The transferable receivables search page is accessed, and a screen relating to the transferable receivables search page is output to the transferee device 400 .

In one embodiment of the screen related to the transferable trade receivable search page, "buyer", "transferable amount", "remaining date" and "discount rate" are output as trade receivable DB field identification information, and matching with the "buyer" The mutual purchaser input field is outputted, and "≥" and the amount input field are output in order by matching the "transferable amount", "≥" and the number of days input field are outputted sequentially by matching the "remaining due date", and the "discount rate" Matching with ", "≥" and the % input field are sequentially output.

According to an additional aspect of the present invention, step 301 is a step in which the transferee device 400 accesses the login page of the account receivable relay server 100 and the master password input field is output to the transferee device 400; inputting a master password in the master password input field by the transferee; Retrieving the password field value, the terminal verification code field value, the public key field value, and the private key field value of the record in which the account receivable relay agency identification information is stored in the site field in the secret information DB 411 configured in the transferee device 400 ; calculating each hash value of the 'receivables relay agency identification information and master password'; calculating a root hash value of the hash values as an encryption/decryption key for accounts receivable relay agency; decrypting the 'encrypted password that is the searched password field value' and the 'encrypted secret key that is the searched secret key field value' with the encryption/decryption key for the account receivable relay agency; decrypting the 'encrypted terminal verification code that is the retrieved terminal verification code field value' with the decrypted secret key; calculating an OTP by encrypting the decrypted password with the decrypted terminal verification code; transmitting 'the searched public key field value as a public key registered with the accounts receivable relay agency' and the 'the calculated OTP' from the transferee device 400 to the accounts receivable relay server 100; Receiving the transmitted 'public key and OTP' from the accounts receivable relay server 100, searching the customer DB 110 for a 'hashed password' and a terminal verification code matching the public key; Decrypting the received OTP with the searched terminal verification code in the accounts receivable relay server 100 to calculate a password; Compiling the hash value of the calculated password in the accounts receivable relay server 100 and comparing it with the searched 'hashed password'; allowing the accession of the transferee device 400 when the matching result matches; Calculating a terminal verification code randomly in the accounts receivable relay server 100 and updating the 'terminal verification code field value retrieved from the customer DB 110' with the calculated terminal verification code; encrypting the 'updated terminal verification code' with the 'searched public key field value' and sending a reply to the transferee device 400; And by receiving the 'encrypted terminal verification code' from the transferee device 400, the terminal verification code field value of the 'record in which the account receivable relay agency identification information is stored in the site field' is received in the secret information DB 411 updating to 'encrypted terminal verification code'; includes

In step 302, the transferee uses the input unit (not shown) of the transferee device 400 to match the 'one or more accounts receivable DB field identification information' configured in the 'screen related to the transferable receivables search page output in step 301' When a comparison value is entered in the comparison value input field, the transferee device 400 transmits 'the input comparison value' and field identification information matched to the comparison value to the trade receivable relay server 100 .

In one embodiment, "100,000,000", "30" and "4.00%" in the 'amount input field, number of days input field, and % input field' configured on the screen related to the transferable receivables search page illustrated as an embodiment in step 301, respectively Upon input, the transferee device 400 transmits 'transferable amount ≥ 100,000,000 & remaining due date ≥ 30 days & discount rate ≥ 4.00%' to the accounts receivable relay server 100 .

In step 303, when the 'field identification information transmitted in step 302 matched with the comparative value' is received from the trade receivable relay server 100, records that satisfy all of the 'received comparative value' in the trade receivable DB 140 The transferee device 400 that extracts the 'transferable accounts receivable identification information including 'field values constituting the record' for each extracted record and connects the transferable receivable identification information in 'step 301' )' is sent.

In one embodiment, the 'buyer field value, seller field value, occurrence date field value, amount field value, delivery product field value, payment date field value, and discount rate field value' constituting the record are respectively 'buyer identification information and seller identification information'. and trade receivable occurrence date, trade receivable amount, delivery product identification information, trade receivable settlement date, and discount rate' Write identification information.

According to an additional aspect of the present invention, when the transferable amount field is configured separately from the amount field in the trade receivable DB 140, the transferable amount field value is replaced with the transferable amount field value and the transferable trade receivable including the transferable amount field value Write identification information.

In step 304, when the transferee device 400 receives the 'transferable trade receivable identification information transmitted in step 303', it outputs the received transferable trade receivable identification information.

In step 305, by using the input unit (not shown) of the transferee device 400, the 'person using the transferee device 400' (hereinafter referred to as the "transferee") 'transferable trade receivable identification information output in step 304' If you enter information to select one of ', the input box for the amount of sales receivables applied for acquisition and the input box for the master password are output.

According to an additional aspect of the present invention, in step 305, the purchaser's proposed discount rate input field is further outputted by matching the purchase receivable amount input field.

In step 306, when the transferee enters the amount of sales receivable applied for acquisition in the transfer receivable amount input field and inputs the master password in the master password input field, the secret information DB 411 of the transferee device 400 stores the account receivable relay agency identification information Search, calculate each hash value of 'the account receivable relay agency identification information and the master password', and calculate a root hash value of the calculated hash values as an encryption/decryption key for accounts receivable relay agency.

According to an additional aspect of the present invention, the accounts receivable relay agency identification information is the trade name of the accounts receivable relay agency.

On the other hand, according to another aspect of step 306, in step 306, in the secret information DB 411 of the transferee device 400, the identification information of the transferee's escrow institution (hereinafter referred to as "escrow institution identification information") and the real name confirmation finance match Search for company identification information (hereinafter referred to as "real name verification financial company identification information"), calculate a hash value of the real name verification financial company identification information, The root hash value of 'hash value' is calculated as an encryption/decryption key for real-name verification financial companies.

According to an additional aspect of the present invention, in step 306, the transferee inputs the transferee's proposed discount rate into the transferee's proposed discount rate input field; includes

In step 307, the 'encrypted secret key for accounts receivable relay agency' is retrieved from the secret information DB 411, and the 'encrypted secret for accounts receivable relay agency' is used using the 'encrypted decryption key for accounts receivable relay agency calculated in step 306' Decrypt the 'key'.

On the other hand, when another aspect of step 306 is applied, in step 307, 'encrypted transferee's real name link secret key' is searched for in the secret information DB 411, and 'real name verification financial company lava calculated in another aspect of step 306' The 'encrypted transferee's real name link secret key' is decrypted using the 'decryption key'.

In step 308, the public key for the accounts receivable relay agency matched with the accounts receivable relay agency identification information is searched for in the secret information DB 411, the 'encrypted password for the accounts receivable relay agency', and the 'encrypted terminal verification code for the accounts receivable relay agency' , decrypts the 'encrypted password for accounts receivable relay agency' using the 'encryption decryption key for accounts receivable relay agency calculated in step 306', and uses the 'secret key for accounts receivable relay agency decrypted in step 307' Decrypts the 'encrypted terminal verification code for accounts receivable relay agency', and uses the decrypted terminal verification code for accounts receivable relay agency to encrypt the decrypted password for accounts receivable relay agency to calculate OTP.

In step 309, in the transferee device 400, the 'public key for trade receivables relay agency retrieved in step 308 as author identification information' and 'transferable trade receivable identification information selected in step 305' and 'transferable trade receivable identification information selected in step 306 as trade receivable identification information' The trade receivable application transaction data including 'the amount of trade receivable applied for acquisition' and 'OTP calculated in step 308' is created.

According to an additional aspect of step 309, the transaction data for the application for transfer of accounts receivable further includes 'the discount rate proposed by the transferee inputted in the additional aspect of step 306'.

Meanwhile, according to another aspect of step 309, the public key for the accounts receivable relay agency is replaced or added to the trade receivables transfer application transaction data, and the 'real name linkage public key and ID for the accounts receivable relay agency searched in the 'secret information DB 411' It may include one or more of '.

In step 310, an electronic signature is created for the 'trade receivable transfer application transaction data created in step 309' using the 'secret key for trade receivable relay agency decrypted in step 307'.

Meanwhile, according to another aspect of the present invention, in step 310, by using the 'real name linkage secret key decrypted in step 307' by replacing the 'secret key for trade receivables relay agency decrypted in step 307' in step 310, 'acquisition of trade receivables created in step 309' You can also create an electronic signature for 'application transaction data'.

In step 311, the transferee device 400 transmits the 'transaction data for the application for transfer of accounts receivable created in step 309' and the 'electronic signature created in step 310' to the trade receivable relay server 100 in step 311.

In step 324, when the trade receivable relay server 100 receives 'transaction data and electronic signature transmitted in step 311', the electronic Verify the signature.

If the verification is successful, steps 325 and below are operated.

In step 325, the trade receivable relay server 100 matches the transaction data serial number in the transaction data DB 120 to obtain the 'time stamp when step 324 is operated' and the 'trade receivable transfer application transaction data and electronic signature' Store, calculate the root hash value of the 'transaction data serial number and timestamp, trade receivable transfer application transaction data and electronic signature', and match the 'transaction data serial number and timestamp' in the hash DB 130 to store the root hash value.

On the other hand, according to another aspect of the present invention in which an organization separate from the trade receivable relay agency provides an escrow service for the trade receivable transfer price, the steps 306-2 to 325-2 below are it works

In step 306-2, when the transferee inputs the amount of the sales receivable applied for acquisition in the transfer application receivable amount input field and enters the master password in the master password input field, the trade receivable relay agency is identified in the secret information DB 411 of the transferee device 400 Search information and escrow agency identification information, calculate hash values of 'the account receivable relay agency identification information, the escrow agency identification information, and the master password', and the calculated hash value of the 'trade receivable relay agency identification information' Calculate the root hash value of 'and the hash value of master password' as an encryption/decryption key for accounts receivable relay agency, and calculate the root hash value of 'Hash value of escrow institution identification information and hash value of master password' as encryption/decryption key for escrow agency do.

Another aspect in step 306 and an additional aspect are also applicable in step 306-2.

In step 307-2, 'encrypted secret key for accounts receivable relay agency' and 'encrypted secret key for escrow agency' are searched for in the secret information DB 411, and 'encryption decryption key for accounts receivable relay agency calculated in step 306-2 ' to decrypt the 'encrypted secret key for accounts receivable relay agency', and 'encryption decryption key for escrow agency calculated in step 306-2' to decrypt the 'encrypted secret key for escrow agency'.

Another aspect in step 307 is also applicable to step 307-2.

In step 308-2, in the confidential information DB 411, the public key for the accounts receivable relay agency matching the identification information of the accounts receivable relay agency, the 'encrypted password for the accounts receivable relay agency', and the 'encrypted terminal verification code for the accounts receivable relay agency' Search, search for the real name account ID and real name linked public key matching the escrow institution identification information, 'encrypted escrow institution password' and 'encrypted escrow institution terminal verification code', and 'trade receivable calculated in step 306-2 Decrypt the 'encrypted password for the account receivable relay agency' using the 'relay decryption key', and decrypt the 'encrypted escrow institution password' using the 'encryption decryption key for the escrow institution calculated in step 306-2' and decrypts the 'encrypted terminal verification code for accounts receivable relay agency' using the 'secret key for accounts receivable relay agency decrypted in step 307-2', and 'secret key for escrow agency decrypted in step 307-2' Decrypting the 'encrypted terminal verification code for escrow agencies' using the decrypted terminal verification code for accounts receivable relay agency by encrypting the decrypted password for the accounts receivable relay agency OTP for the accounts receivable relay agency, and the The decrypted escrow institution password is encrypted using the decrypted escrow institution terminal verification code to calculate the escrow institution OTP.

In step 309-2, in the transferee device 400, 'public key for trade receivable relay agency retrieved in step 308-2 as author identification information' and 'transferable trade receivable identification information selected in step 305 as trade receivable identification information' and 'steps In step 308-2, the trade receivables takeover application transaction data including the ‘acquisition application trade receivable amount input in step 306-2’ and ‘OTP for trade receivable relay agency calculated in step 308-2’ is prepared, and in step 308-2 The searched real-name linked public key', 'real name account ID retrieved in step 308-2', 'transferable trade receivable identification information selected in step 305 as trade receivable identification information', and 'transferred trade receivable amount input in step 306-2 ' and 'OTP for escrow institutions calculated in step 308-2' is created.

An aspect different from the additional aspect in step 309 is also applicable in step 309-2.

On the other hand, when an additional aspect of step 306-2 including 'the transferee inputs the transferee's proposed discount rate in the transferee's proposed discount rate input field' is applied, the trade receivables transfer price escrow confirmation application transaction data created in step 309-2 includes The discount rate offered by the adoptee is also included.

Meanwhile, according to another aspect of step 309-2, the real-name account ID is included in the real-name linked public key by replacing the real-name linked public key in the transaction data for the escrow confirmation of the trade receivables acquisition price.

In step 310-2, an electronic signature is created for the 'trade receivable transfer application transaction data created in step 309-2' using the 'secret key for trade receivable relay agency decrypted in step 307-2', and 'step 307-2 Using the 'secret key for escrow institution decrypted in ', create an electronic signature for 'transaction data for escrow confirmation application created in step 309-2'.

Another aspect in step 310 is also applicable to step 310-2.

In step 311-2, in the transferee device 400, 'transaction data for escrow confirmation application created in step 309-2' and 'digital signature for the transaction data for escrow confirmation application created in step 310-2 ' to the escrow server 500 .

In step 312-2, when the escrow server 500 receives 'transaction data and electronic signature for escrow confirmation of trade receivables transfer payment sent in step 311-2', The digital signature is verified using the author identification information.

If the verification is successful, steps 313-2 and below are operated.

In step 313-2, by matching the transaction data serial number in the transaction data DB 520 in the escrow server 500 in step 313-2, the 'time stamp at the time when step 312-2 is operated' and the 'trade receivables transfer payment escrow confirmation application transaction data' and 'electronic signature', calculates the root hash value of the 'transaction data serial number and timestamp, escrow confirmation application transaction data and electronic signature', and in the hash DB 530, the 'transaction data The root hash value is stored by matching the 'serial number and timestamp'.

In step 314-2, the escrow server 500 extracts 'writer identification information and OTP for the escrow institution' from the 'transaction data for escrow confirmation of the trade receivables transfer payment received in step 312-2' in the escrow server 500, and in the real name account DB 540 The password field value and terminal verification code field value of the record in which 'the extracted author identification information' is stored in the public key field is searched as 'hashed password and terminal verification code', respectively, and the escrow value is used as the terminal verification code field value. Decrypts the OTP for banking, calculates a hash value of the decrypted value, and compares the hash value with the 'searched hashed password'.

On the other hand, according to another aspect of step 309-2, when the real name account ID is included in the escrow confirmation application transaction data by replacing the real name link public key, step 314-2 is 'received in step 312-2 The real name account ID is extracted from the transaction data for escrow confirmation of the transfer of trade receivables, and the password field value and the terminal verification code field value of the record in which the 'extracted real name account ID' is stored in the account field in the real name account DB 540 and retrieving the public key field values as 'hashed password, terminal verification code, and real-name linked public key', respectively.

If the matching results in step 314-2 match, steps 315-2 and below are operated.

In step 315-2, the escrow server 500 randomly calculates a terminal verification code, and updates the terminal verification code field value retrieved from the real name account DB 540 in step 314-2 with the calculated terminal verification code, and Encrypt the updated terminal verification code with 'the author identification information extracted in step 314-2' (or the real name linked public key retrieved from the real name account DB 540 in step 314-2) to 'receive in step 312-2' As a reply, it is transmitted to the adoptee device 400 .

When the transferee device 400 receives the 'encrypted terminal verification code transmitted in step 315-2' in step 316-2, terminal verification of the record in which the escrow agency identification information is stored in the site field in the secret information DB 411 The code field value is updated with the received 'encrypted terminal verification code'.

In step 317-2, in the escrow server 500 in the 'transaction data for escrow confirmation of the trade receivable acquisition payment received in step 312-2' and 'Amount of sales receivable applied for transfer', and the balance field value of 'Record stored in the real name account ID in the real name account field' is retrieved from the real name account DB 540, Compare.

On the other hand, when an additional aspect of step 309-2 including the transferee proposal discount rate is applied to the trade receivables transfer price escrow confirmation application transaction data, the transferee proposal in the trade receivable transfer price escrow confirmation application transaction data in step 317-2 More discount rate is extracted.

When the amount of the sales receivable applied for transfer is within the value of the balance field, steps 318-2 and lower are operated.

In step 318-2, the escrow server 500 extracts the discount rate and the settlement date from the 'transferable trade receivable identification information extracted in step 317-2', and calculates the 'remaining days until the settlement date' using the settlement date, A discount amount is calculated by applying the discount rate and the number of remaining days to the amount of sales receivables extracted in step 317-2, and the discount amount is deducted from the amount of sales receivables applied for acquisition to calculate the amount of purchase price after discount.

On the other hand, if the transferee's proposed discount rate is further extracted from the transaction data for the escrow confirmation request in step 317-2, the 'discount rate extracted from the transferable trade receivable identification information' is replaced in step 318-2 and the proposed discount rate is applied to calculate the discount amount.

In step 319-2, the escrow server 500 generates a timestamp, randomly generates an inscription for escrow matching, and sets the 'balance field value retrieved in step 317-2' in the real name account DB 540 to 'step 318 -2 is reduced and updated by the 'acquisition amount after discount' calculated in step -2, and the 'real name account field, trade receivable field, transfer receivable amount field, escrow amount field, timestamp field and inscription field in the escrow account DB (510) In each of the fields of 'one of the records in which the 'and application transaction field' are both default values, 'Real name account ID, transferable trade receivable identification information, and transfer receivable amount extracted in step 317-2' and 'in step 318-2 Transaction data serial number matched to the transaction data for escrow confirmation stored in the transaction data DB 520 in step 313-2 and the 'time stamp and escrow matching inscription' ' to save

In step 320-2, in the escrow server 500, 'public key of the escrow institution as author identification information' and 'transferable trade receivable identification information and transfer receivables amount stored in the escrow account DB 510 in step 319-2' Trade receivables including 'yescrow account field value of the escrow account field value of the escrow account DB 510 record in which the transferable trade receivable identification information is stored' and 'the inscription for the transferable trade receivable identification information, etc.' Create escrow confirmation transaction data for positive payment.

According to an additional aspect of the present invention, the public key of the escrow institution is one of the public key associated with the real name of the escrow institution and the public key for the escrow business.

In step 321-2, the escrow server 500 uses the 'secret key of the escrow institution matched with the creator identification information included in the escrow confirmation transaction data of the trade receivable acquisition price created in step 320-2' in the 'step 320-2' Create an electronic signature for the created trade receivable acquisition price escrow confirmation transaction data.

In step 322-2, in the escrow server 500, 'receipt of the trade receivable acquisition price escrow confirmation transaction data created in step 320-2' and the 'electronic signature created in step 321-2' in the 'reception in step 312-2' It is transmitted to the adoptee device 400 as a reply.

In step 323-2, when the transferee device 400 receives 'transaction data and electronic signature for escrow confirmation of trade receivables transfer price transmitted in step 322-2' and 'Electronic signature for the trade receivable acquisition payment escrow confirmation transaction data and the trade receivable acquisition price escrow confirmation transaction data' by matching with the 'electronic signature for the trade receivable transfer application transaction data prepared in step 310-2' It is transmitted to the bond relay server (100).

In step 324-2, the trade receivable relay server 100 receives the 'transaction data for trade receivable takeover application transaction data and the matched electronic signature and the escrow confirmation transaction data and the matched electronic signature sent in step 323-2' Then, each transferable trade receivable identification information is extracted from the trade receivable transfer application transaction data and the trade receivable takeover payment escrow confirmation transaction data and compared with each other, and the matching using the creator identification information included in the trade receivable transfer application transaction data The electronic signature is verified, and the matched electronic signature is verified using the author identification information included in the escrow confirmation transaction data of the trade receivables acquisition price.

If the extracted trade receivable identification information matches each other and both digital signature verifications are successful, steps 325-2 and below are operated.

In step 325-2, by matching the transaction data serial number in the transaction data DB 120 in the trade receivable relay server 100, the 'time stamp of when step 324-2 is operated' and the 'trade receivable transfer application transaction data and Storing the matched electronic signature', calculating the root hash value of the 'transaction data serial number and timestamp, transaction data and electronic signature for acquisition of accounts receivable', and in the hash DB 130, the 'transaction data serial number' and 'time stamp' to match the root hash value, while matching the next transaction data serial number to store the timestamp and the 'trade receivables acquisition price escrow confirmation transaction data and matched electronic signature', and the Calculate the root hash value of 'transaction data serial number and timestamp, escrow confirmation transaction data and matched electronic signature' of trade receivables acquisition price, and match the 'transaction data serial number and timestamp' in the hash DB 130 to store the root hash value.

In step 326, the accounts receivable relay server 100 extracts 'author identification information and OTP' from the 'trade receivable transfer application transaction data received in step 324 (or step 324-2)', and discloses it in the customer DB 110 Search the password field value, terminal verification code field value, and public key field value of the record in which 'the extracted author identification information' is stored in the key field as 'hashed password, terminal verification code, and public key for trade receivables relay agency', respectively and decrypts the OTP with the terminal verification code field value, calculates a hash value of the decrypted value, and compares the hash value with the 'searched hashed password'.

On the other hand, according to another aspect of step 309, when the trade receivable transfer application transaction data includes an ID for the trade receivable intermediary by replacing the public key for the trade receivable intermediary, step 326 is 'acquisition of trade receivable received in step 324' The ID for the accounts receivable relay agency is extracted from the 'application transaction data', and the password field value, the terminal verification code field value and the public key field of the record in which the 'the extracted ID for the accounts receivable relay agency' is stored in the ID field in the customer DB 110 It includes an operation of retrieving the values as 'hashed password, terminal verification code, and public key for accounts receivable relay agency', respectively.

If the matching results in step 326 match, steps 327 and below are operated.

In step 327, the account receivable relay server 100 randomly calculates a terminal verification code, and updates the 'terminal verification code field value retrieved from the customer DB 110 in step 326' with the calculated terminal verification code, and the updated The terminal verification code is encrypted with the 'public key for accounts receivable relay agency retrieved from the customer DB 110 in step 326' and transmitted to the transferee device 400 as a reply to the 'receipt in step 324 (or step 324-2)' do.

In step 328, when the transferee device 400 receives 'the encrypted terminal verification code transmitted in step 327', the terminal verification code field of the record in which the account receivable relay agency identification information is stored in the site field in the secret information DB 411 The value is updated with the received 'encrypted terminal verification code'.

In step 329, the trade receivable relay server 100 extracts transferable trade receivable identification information and the transfer receivable amount from the 'trade receivable transfer application transaction data received in step 324', and extracts the transferable trade receivable amount from the transferable trade receivable identification information. Identification information and trade receivable settlement date are extracted, and in the financial relay DB 150, 'the extracted, transfer Possible trade receivable identification information, seller identification information, trade receivable settlement date', 'time stamp when step 324 is operated' and 'public key for trade receivable relay agency extracted in step 326' and the amount of trade receivable applied for acquisition are stored and new compose a record

On the other hand, in the embodiment to which another aspect of the present invention is applied in which the 'steps 306-2 to 325-2' are operated by replacing the 'steps 306 to 325', the following step 329-2 is operated to replace the step 329 .

In step 329-2, the trade receivable relay server 100 extracts the transferable trade receivable identification information and the transfer receivable amount from the 'transaction receivable transfer application transaction data received in step 324-2', and the transferable trade receivable Seller identification information and trade receivable settlement date are extracted from the identification information, and in 'escrow confirmation transaction data for transfer receivables received in step 324-2', 'Public key of escrow institution, identification information of transferable trade receivables, and trade receivables applied for acquisition Extract the amount, the amount to be acquired after discount, the timestamp, the inscription for escrow matching, and the yes-crow account ID', and the 'trade receivable field, the seller field, the settlement date field, the takeover application date field and the takeover applicant field' from the financial relay DB 150 In the 'transferable trade receivable identification information, seller identification information, and trade receivable settlement date' and 'time stamp when step 324 is operated' and 'in step 326, 'Extracted public key for trade receivable relay agency', the amount of trade receivable applied for acquisition, and the yes-crow account ID are stored to form a new record, and the 'account field, trade receivable field, and transfer receivable amount field' in the escrow DB 170 and the 'Yes-Crow account ID, transferable trade receivable identification information, transfer application receivable amount, after-discount transfer amount, timestamp and escrow matching Save the inscription.

According to an additional aspect of the present invention, step 329 or step 329-2 comprises the steps of: extracting the discount rate proposed by the transferee from the 'transaction data for the transfer of accounts receivable received in step 324 (or step 324-2)'; and storing the 'extracted transferee's proposed discount rate' in a field of the proposed new record in the financial relay DB 150; includes

According to an additional aspect of the present invention, users who have authenticated themselves to the accounts receivable relay server 100 and have accessed, among the records stored in the financial relay DB 150, the value of the transfer applicant field is 'Customer DB (110) You can search for or download records matching the stored public key matching the ID for the accounts receivable relay agency presented by the user for access.

5 is a method for safely and conveniently transferring trade receivables using a block chain according to the present invention in one embodiment is a flowchart showing

In step 405, the record corresponding to 'transferable trade receivable identification information extracted in step 329 of FIG. 4' is extracted from the trade receivable DB 140 in the trade receivable relay server 100, and the discount rate field value of the record is extracted .

In step 406, in the financial relay DB 150 in the trade receivable relay server 100, the 'transfer amount field and the discount rate field' of the 'record configured in step 329 of FIG. and 'discount rate field value extracted in step 405' is stored, and the 'transferable amount field value of the record extracted in step 405 is updated in the trade receivable DB 140 by deducting the amount of the trade receivable applied for acquisition.

Meanwhile, according to another embodiment of the present invention in which the discount rate suggested by the transferee is applied within the discount rate range suggested by the seller, the following steps 401-1 to 407-1 are operated in place of steps 405 to 406.

In step 401-1, the accounts receivable relay server 100 extracts the records in which the settlement target date is stored in the subscription deadline field from the trade receivable DB 140, and calculates the discount rate field value and the transferable amount field value for each extracted record. Search and calculate trade receivable identification information.

In one embodiment, the 'buyer field value, seller field value, occurrence date field value, amount field value, delivery product field value, payment date field value, and discount rate field value' constituting the record are respectively 'buyer identification information and seller identification information'. and trade receivable occurrence date, trade receivable amount, delivery product identification information, trade receivable settlement date and discount rate', and connect the extracted information in order, but place "/" between each information to identify trade receivables of the record write

The first embodiment of the settlement target date is 'the previous business day of the date on which step 401-1 is operated'.

The second and third embodiments of the settlement target date are 'the date on which step 401-1 is operated' and 'the date n business days before the date on which step 401-1 is operated', respectively.

Hereinafter, the first embodiment will be mainly described.

In step 402-1, the financial relay DB 150 extracts records in which 'trade receivable identification information calculated in step 401-1' is stored in the trade receivable field.

In step 403-1, for each 'record extracted in step 402-1', the 'property proposal discount rate field value, the takeover application sales receivable amount field value, and the takeover applicant field value' are extracted, and the ' The transferee proposal discount rate field value, the transfer receivable amount field value, and the transfer applicant field value' are combined into one transfer application detail.

In step 404-1, the transferee proposed discount rate field value is extracted from the 'each transfer application details combined in step 403-1', and the extracted transferee proposed discount rate field value is less than or equal to the 'discount rate field value retrieved in step 401-1' decide whether

In step 404-1, steps 405-1 or less are operated for the details of the transfer application in which the value of the discount rate field proposed by the transferee is equal to or less than the value of the discount rate field.

In step 405-1, 'each transfer application details for which the judgment in step 404-1 is positive' are listed in the order of the lowest 'transferee proposal discount rate field value included in each transfer application details', and the first order of transfer application Accumulate the value of the sales receivable amount field included in the transfer application details from the details, and accumulate until the accumulated value is greater than or equal to the 'transferable amount field value retrieved in step 401-1'.

In step 406-1, 'details of acquisition applications in which the amount of sales receivables applied for acquisition in step 405-1 were used for accumulation in step 405-1' are extracted from among the 'details of acquisition applications combined in step 403-1', and the financial relay DB 150 ) extracts the records corresponding to each of the extracted transfer application details, and stores 'the amount of trade receivables used for the accumulation in step 405-1' in the transfer amount field of the extracted record, but 'step 405 If the final accumulated transfer receivable amount in -1 exceeds the 'transferable amount field value retrieved in step 401-1', in the transferable amount field value, 'from the final accumulated transfer receivable amount The amount of sales receivables was calculated by deducting the amount of sales receivables applied for acquisition last added,' In the transfer amount field of the record, the amount of leftover sales receivables is stored.

For example, the 'transferable amount field value retrieved in step 401-1' is 500 million won, and the 'acquisition transaction receivable amount used for accumulation in step 405-1' is '200 million won, 100 million won, 150 million won, In the case of '120 million won', if all the amounts of the sales receivables applied for takeover are accumulated, the transferable amount field value (ie, 500 million won) exceeds the value of the transferable amount field by 570 million won. Therefore, from the value of the transferable amount field (that is, 500 million won), '50 million won after deducting '570 million won, which is the last accumulated amount of takeover application sales receivable - 120 million won, which is the amount of the last added takeover application sales receivable = 450 million won' Calculated as the amount of leftover sales receivables, and in the transfer amount field of the record corresponding to the takeover application details including 'the amount of sales receivables last added in step 405-1 of 120 million won' Save billions of dollars

In step 407-1, in the financial relay DB 150, in the 'Acquisition discount rate field of each record extracted in step 406-1', the details of each transfer application in which the amount of trade receivable applied for acquisition in step 405-1 is used Stores the best transferee-suggested discount rate field value among adoptee-suggested discount rate field values included in

In the case exemplified in step 406-1, the value of the proposed discount rate field matching the 'accumulation in step 405-1 of 200 million won, 100 million won, 150 million won, and 120 million won' is '3.98%, 3.80%, 3.50%, 3.75%, the highest value of 3.98% among the values of the proposed discount rate fields is stored in the 'positive discount rate field of each record extracted in step 406-1'.

Meanwhile, according to another aspect of the present invention, in step 407-1, in the financial relay DB 150, the 'acquisition discount rate field of each record extracted in step 406-1' is entered in the 'acquisition application sales in step 405-1'. It is also possible to store the 'value of the transferee suggested discount rate field included in each record' by replacing the best transferee proposed discount rate field value among the transferee proposal discount rate field values included in each transfer application details in which the bond amount is used.

If the above case occurs in the embodiment to which the other aspect is applied, each record matching the 'Accumulation in step 405-1, the amounts of sales receivables applied for acquisition of 200 million won, 100 million won, 150 million won, and 120 million won' '3.98%, 3.80%, 3.50%, and 3.75%' are stored in the positive discount rate fields, respectively.

6 is a method for safely and conveniently transferring trade receivables using a block chain according to the present invention. It is a flowchart showing an embodiment of the operation of notifying the purchaser of the fact in a non-repudiation manner.

In step 501, the account receivable relay server 100 extracts the 'record for which the transfer amount field is updated in step 406 (or step 406-1) of FIG. 5' from the financial relay DB 150, and the 'trade receivable Extract the field value (that is, transferable trade receivable identification information), transfer applicant field value, and transfer amount field value, and extract 'buyer identification information and seller identification information' from the extracted trade receivable field value, and trade receivables The DB 140 extracts the discount rate field value of the record corresponding to the trade receivable field value.

According to the first additional aspect of step 501, step 501 includes 'buyer identification information, seller identification information, trade receivable occurrence date, trade receivable amount, delivery product identification information, and trade receivable settlement date' in each of the extracted trade receivable field values. extracting; and calculating transfer target trade receivable identification information using at least two of the extracted 'buyer identification information, seller identification information, trade receivable generation date, trade receivable amount, delivery product identification information, and trade receivable settlement date'; includes

According to the second additional aspect of step 501, step 501 calculates each of the extracted trade receivable field values as transfer target trade receivable identification information.

Hereinafter, an embodiment to which the second additional aspect of step 501 is applied will be mainly described.

According to an additional aspect of the present invention, step 501 is operated after step 407-1 (or step 406) of FIG. 5 .

Meanwhile, according to another aspect of the present invention in which the discount rate suggested by the transferee is applied within the discount rate range suggested by the seller, in step 501, 'Discount rate field value of the record corresponding to the trade receivable field value in the accounts receivable DB 140 In the financial relay DB 150, the operation of extracting the proposed discount rate field value from the record in which the transfer amount field is updated in step 406 (or step 406-1) of FIG. .

In step 502, the 'real name field value, real name number field value, and real name account field value' matched to the 'takeover applicant field value extracted in step 501' in the customer DB 110 in the trade receivable relay server 100 are respectively 'acquired real name' and the transferee's real name number and the transferee's account receivable payment receipt account ID', and the 'real name field value and real name number field value and address field value matched with the 'buyer identification information extracted in step 501' in the customer DB 110 and e-mail address field value and phone number field value' are extracted as 'buyer name, buyer real name number, buyer address, buyer e-mail address, and buyer phone number', respectively, and the seller extracted in step 501 in the customer DB 110 'Real name field value, real name number field value, address field value, e-mail address field value, phone number field value, and real name account field value' matched to 'identification information' are set to 'seller name, seller real name number, seller address, and seller, respectively. E-mail address, seller phone number, and account ID for the transfer of trade receivables are extracted as 'the seller identification information as author identification information (ie, the seller's public key)' and 'the seller name as the author's real name' and 'writer' The seller's real name number as the real name number, the seller's address as the author's address, the seller's e-mail address as the author's e-mail address, the seller's phone number as the author's phone number, and the trade receivable transfer payment account ID and 'the buyer identification information as recipient identification information (ie, the public key of the purchaser)', 'the buyer name as the recipient's real name', 'the buyer real name number as the recipient's real name number', and 'the buyer address as the recipient address' and ' The buyer's e-mail address as the recipient's e-mail address', 'the buyer's phone number as the recipient's phone number', 'the trade receivable field value extracted in step 501 as transfer receivable identification information' and the extracted 'transferee real name and transferee real name number' and the transfer notice transaction data including the transferee's account receivable payment receipt account ID' and 'transfer amount field value extracted in step 501 as transfer receivable amount', and the trade receivable field value in the financial relay DB 150 (i.e., extract the record containing the transfer receivable identification information), 'Acquired real name field, transferee real name number field, transferee account field, buyer real name field, buyer real name number field, buyer address field, buyer e-mail address field, buyer phone number field, seller real name field, seller real name number field, 'Corresponding information included in the transfer notification transaction data' is stored in the seller address field, the seller e-mail address field, the seller phone number field, and the seller account field, respectively.

In step 503, the sales receivable relay server 100 calculates the discount amount and the transfer amount after discount using the 'transfer amount field value extracted in step 501' and the 'discount rate field value extracted in step 501', and 'sales as author identification information' 'Public key of receivable brokerage', 'seller identification information extracted in step 501 as recipient identification information', 'transfer notification transaction data prepared in step 502', and 'trade receivable field value extracted in step 501 as transfer receivable identification information' and 'transfer amount field value extracted in step 501 as the transfer amount', 'discount rate field value extracted in step 501 as transfer discount rate' and 'the calculated discount amount and transfer amount after discount'. .

On the other hand, if another aspect in step 501 of applying the discount rate suggested by the transferee within the discount rate range suggested by the seller is applied, in step 503, the discount amount and the discount rate using the 'discount rate field value extracted in step 501' is used. and calculating a transfer amount, and the transfer notification request transaction data includes the transferee-suggested discount rate field value by replacing the discount rate field value.

In step 504, the trade receivable relay server 100 creates an electronic signature for the 'transfer notification request transaction data created in step 502' using the secret key of the trade receivable relay agency.

In step 505, the trade receivable relay server 100 converts the 'transfer notification request transaction data created in step 503' and the 'electronic signature created in step 504' to the seller device 200 corresponding to the 'seller identification information extracted in step 501' send.

In step 506, when the seller device 200 receives 'transfer notification request transaction data and transfer signature transmitted in step 505', the electronic signature is verified using the author identification information included in the transfer notification request transaction data. .

If the verification is successful, steps 507 and below are operated.

In step 507, by matching the transaction data serial number in the transaction data DB 220 of the seller device 200, the 'time stamp of when step 506 is operated' and the 'transfer notification request transaction data and electronic signature' are stored, Calculate the root hash value of the 'transaction data serial number and timestamp, transfer notification request transaction data and electronic signature', and match the 'transaction data serial number and timestamp' in the hash DB 230 to solve the root solution save the time value

In step 508, the seller device 200 extracts 'transfer target trade receivable identification information, transfer amount, transfer discount rate, discount amount, and transfer amount after discount' from 'transfer notification request transaction data received in step 506', respectively (250), each stored in the 'trade receivable field, transfer amount field, discount rate field, discount amount field, and after-discount transfer amount field', constitute a new record, and in the trade receivable DB 240, The corresponding record is searched and the value of the holding amount field of the record is decreased by the transfer amount and updated.

In step 509, the seller device 200 extracts the transfer notification transaction data from the 'transfer notification request transaction data received in step 506'.

Steps 203 to 205 of FIG. 3 are operated.

In step 513, the seller device 200 creates an electronic signature for the 'transfer notification transaction data extracted in step 509' using the 'secret key decrypted in step 205'.

In step 514, the seller device 200 transmits the 'transfer notification transaction data extracted in step 509' and the 'electronic signature created in step 513' to the trade receivable relay server 100 and the purchaser device 300.

When the 'transfer notification transaction data and electronic signature transmitted in step 514' is received from the trade receivable relay server 100 in step 515, the electronic signature is verified using the author identification information included in the transfer notification transaction data. .

If the verification is successful, step 516 is operated.

In step 516, by matching the transaction data serial number in the transaction data DB 120 of the trade receivable relay server 100, the 'time stamp at the time step 515 is operated' and the 'transfer notification transaction data and electronic signature' are stored, , calculates the root hash value of the 'transaction data serial number and timestamp, transfer notification transaction data and electronic signature', and matches the 'transaction data serial number and timestamp' in the hash DB 130 to solve the root solution save the time value

In step 517, in the 'transfer notification transaction data received in step 515' in the trade receivable relay server 100 Extract the real name, real name number and address, e-mail address and phone number, identification information of trade receivables subject to transfer, 'real name and real name number of the transferee, account ID for payment of trade receivables,' and the amount of transfer receivables, and a financial relay DB In step 150, a record including the transfer target sales receivable identification information is extracted, and 'each information extracted from the transfer notification transaction data' is compared with corresponding field values of the extracted record.

If all of the matching results of step 517 match, step 518 is operated.

In step 518, the account receivable relay server 100 stores the 'time stamp when step 515 is operated' in the transfer notice date field of the 'record extracted in step 517' in the financial relay DB 150.

When the purchaser device 300 receives 'transfer notification transaction data and electronic signature transmitted in step 514' in step 521, the electronic signature is verified using the author identification information included in the transfer notification transaction data.

If the verification is successful, step 522 is operated.

In step 522, by matching the transaction data serial number in the transaction data DB 320 of the purchaser device 300, the 'time stamp when step 521 is operated' and the 'transfer notification transaction data and electronic signature' are stored, and the Calculate the root hash value of 'transaction data serial number and timestamp, transfer notification transaction data and electronic signature', and match the 'transaction data serial number and timestamp' in the hash DB 330 to the root hash value save the

In step 523, in the 'transfer notification transaction data received in step 521' in the purchaser device 300 in step 523, 'identification information, real name, real name number, address, and e-mail address and phone number of the creator (ie, seller)' and sales subject to transfer Extract the receivable identification information, 'Acquirer's real name and real name number, trade receivable payment receipt account ID' and transfer receivable amount, and delivery product identification information and trade receivable settlement date' are extracted, the extracted information is stored in the relevant field in the transfer and purchase receivable DB 350, and a new record is constructed, and the transfer target trade receivable is extracted from the trade receivable DB 340 A record matching the identification information is extracted, and the value of the untransferred amount field of the record is updated with the amount reduced by the amount of the transferred receivables.

7 is a flowchart illustrating an operation of settling the transfer price of trade receivables notified of transfer in an embodiment of a method for safely and conveniently transferring trade receivables using a block chain according to the present invention.

After step 518 of FIG. 6 is operated, step 601 is operated.

In step 601, in the financial relay DB 150 in the trade receivable relay server 100, the 'acquisition applicant field value, the seller field value, the discount rate field value and the The transfer amount field value and the payment date field value' are extracted.

On the other hand, according to another aspect of step 601, 'records in which the settlement target date is stored in the transfer notice date field' are extracted from the financial relay DB 150, and the 'acquisition applicant field value and seller field value and The discount rate field value, transfer amount field value, and settlement date field value' are extracted.

In step 602, the 'remaining days until the settlement date' is calculated using the 'settlement date field value extracted in step 601 (or step 601-2)', and the transfer amount field extracted in step 601 (or step 601-2) The discount amount is calculated by applying the 'discount rate field value extracted in step 601 (or step 601-2)' and the 'remaining days until payment date' to the Calculate the transfer amount.

According to an additional aspect of the present invention, in step 602, 'the transfer amount field value x the discount rate field value x the number of days remaining until the settlement date ÷ 365' is calculated as a discount amount.

In step 603, the value of the real name account field of the record storing the 'value of the transfer applicant field extracted in step 601' in 'one of the ID field and the public key field' of the customer DB 110 is set to the transferee's trade receivable payment receipt account. Search as ID, and retrieve the real name account field value of the record storing the 'seller field value extracted in step 601' in 'one of the ID field and the public key field' as the seller's account receivable transfer payment account ID, In the account DB 160, the balance matching the 'account ID of the retrieved transferee's trade receivable payment receipt account ID' is updated to a value obtained by deducting the 'transfer amount after discount calculated in step 602', and the seller's trade receivable transfer price The necessary operation is performed to deposit the amount (hereinafter referred to as "transfer fee and transfer amount after discount") to the account corresponding to the receiving account ID by deducting the predetermined transfer fee from the 'transfer amount after discount calculated in step 602'.

According to the first additional aspect of step 603 in which the seller's trade receivable transfer payment receipt account ID is identification information of an account opened at a trade receivable relay agency, step 603 is the seller's trade receivable transfer searched in the account DB 160 and updating the balance matched with the payment receiving account ID to the amount added by the transfer amount after the fee and discount.

According to the additional second aspect of step 603, where the account ID of the seller's accounts receivable transfer payment receipt is identification information of an account opened at a financial institution other than a trade receivable relay institution, step 603 is a settling account of the trade receivable relay institution is opened ‘Withdraw the transfer amount after the commission and discount from the settlement account of the trade receivable relay institution and transfer it to the account corresponding to the account ID of the seller’s trade receivable transfer payment receiving account found in step 603’ It includes the operation of composing and transmitting the full text of the application.

On the other hand, according to another aspect of the present invention in which an organization separate from the trade receivable relay agency provides an escrow service for the trade receivable transfer price, steps 601-2 to 621-2 below are operated in place of steps 601 to 603 do.

In step 601-2, in the financial relay DB 150, in 'each record for which the transfer notice date field is updated in step 518 of FIG. 6' Field value, escrow account field value, seller account field value, and buyer account field value' are extracted.

Step 602 is operated.

In step 603-2, in the trade receivable relay server 100, the 'public key of the trade receivable relay agency as author identification information', 'transfer notification transaction data and electronic signature received in step 515', and 'trade receivable transferor identification information as steps The seller field value extracted in 601-2, the seller account field value extracted in step 601-2 as the account ID for the transfer of trade receivables, and the value of the transfer applicant field extracted in step 601-2 as the identification information of the transferee of the trade receivable Create escrow condition fulfillment notification transaction data including 'the escrow account field value extracted in step 601-2 as the escrow account ID of the trade receivables transfer price' and the 'transfer amount after discount calculated in step 602 as the trade receivable transfer amount' .

In step 604-2, the account receivable relay server 100 creates an electronic signature for 'the escrow condition fulfillment notification transaction data created in step 603-2' using the secret key of the sales relay agency.

In step 605-2, the trade receivable relay server 100 transmits 'the escrow condition fulfillment notification transaction data created in step 603-2' and the 'electronic signature created in step 604-2' to the escrow server 500.

When the 'escrow condition fulfillment notification transaction data and electronic signature sent in step 605-2,' is received from the escrow server 500 in step 606-2, using the author identification information included in the escrow condition fulfillment notification transaction data The electronic signature is verified.

If the verification in step 606-2 is successful, steps 607-2 and below are operated.

In step 607-2, the escrow server 500 extracts 'transfer notification transaction data and electronic signature' from the 'escrow condition fulfillment notification transaction data received in step 606-2', and 'creator included in the transfer notification transaction data' Identification information' is used to verify the digital signature.

If the verification in step 607-2 is successful, steps 608-2 and below are operated.

In step 608-2, by matching the transaction data serial number in the transaction data DB 520 of the escrow server 500, the 'time stamp at the time step 606-2 is operated' and the 'escrow condition fulfillment notification transaction data and electronic signature' ', calculates the root hash value of the 'transaction data serial number and timestamp and escrow condition fulfillment notification transaction data and digital signature', and in the hash DB 330, the 'transaction data serial number and timestamp' to match and store the root hash value.

In step 609-2, in the escrow server 500 in the 'escrow condition fulfillment notification transaction data received in step 606-2', 'creator identification information, identification information of the transferor of accounts receivable, identification of the account receivable transfer payment account ID and identification of the transferee of trade receivables' information, escrow account ID and transfer amount after discount are extracted, and the escrow amount field value and the extracted Compare the transfer amount after discount.

If the matching results in step 609-2 match, steps 610-2 and below are operated.

In step 610-2, in the escrow account DB 510 in the escrow server 500, 'step 606-2' in the fulfillment date field of the record in which 'the escrow account ID extracted in step 609-2' is stored in the account field It is necessary to store the 'time stamp at the time when do the action.

According to an additional aspect of step 610-2 corresponding to the case that the account corresponding to the account ID of the trade receivable transfer payment receipt account is an account opened by an escrow institution, the operation required to deposit the trade receivable transfer amount to the account In the real-name account DB 540, the balance field value of the record stored in the real-name account field 'Account ID for transfer of trade receivables extracted in step 609-2' is equal to the 'transfer amount after discount extracted in step 609-2'. adding and updating; includes

In step 611-2, in the escrow server 500, the hash value of the 'public key of the escrow institution as author identification information' and the 'escrow condition fulfillment notification transaction data received in step 606-2' and the 'extracted in step 609-2 Escrow transfer notification transaction data including 'trade receivable transfer payment escrow account ID' and 'as escrow transfer amount, the amount deposited in the account corresponding to the trade receivable transfer payment receiving account ID in step 610-2' is created.

In step 612-2, the escrow server 500 creates an electronic signature for the 'escrow transfer notification transaction data created in step 611-2' using the secret key of the escrow institution.

In step 613-2, the 'escrow transfer notification transaction data created in step 611-2' and 'electronic signature created in step 612-2' in the escrow server 500 correspond to 'creator identification information extracted in step 609-2' It is transmitted to the accounts receivable relay server (100).

In step 614-2, upon receiving the 'transaction data and electronic signature of the escrow notice transaction sent in step 613-2' from the trade receivable relay server 100, the 'creator identification information included in the escrow notice transaction data' to verify the electronic signature.

If the verification in step 614-2 is successful, steps 615-2 and below are operated.

In step 615-2, by matching the transaction data serial number in the transaction data DB 120 of the accounts receivable relay server 100, the 'time stamp at the time step 614-2 is operated' and the 'escrow transfer notification transaction data and electronic 'Signature' is stored, the root hash value of the 'transaction data serial number and timestamp, escrow transfer notification transaction data and electronic signature' is calculated, and the 'transaction data serial number and timestamp' in the hash DB 130 to match and store the root hash value.

In step 616-2, in the trade receivable relay server 100, in the 'escrow transfer notification transaction data received in step 614-2', the hash value of the 'escrow condition fulfillment notification transaction data and the trade receivable acquisition price escrow account ID and escrow transfer amount ', and the 'time stamp at the time step 614-2 is operated' is stored in the fulfillment date field of the 'record in which the trade receivable acquisition price escrow account ID is stored in the account field' in the escrow DB 170, and the The value of the trade receivable field of the record is retrieved, and the timestamp is stored in the transfer payment date feed of the record stored in the trade receivable field in the financial relay DB 150 .

8 is a flowchart illustrating an operation of settling trade receivables on the settlement date of trade receivables transferred at a discount in an embodiment of a method for safely and conveniently transferring trade receivables using a block chain according to the present invention.

In step 701, the purchaser device 300 extracts records whose settlement date field value corresponds to the 'business day on which step 701 is operated' from the transfer receivable DB 350.

In step 702, the 'trade receivable identification information field value, the transferee account field value and the transfer receivable amount field value' are extracted from the 'each records extracted in step 701', and the 'transfer receivable amount field value is set to the transferee account The remittance is made to the account corresponding to the field value, and the 'time stamp of when step 702 is operated' is stored in the payment execution date field of the record.

In step 703 , records corresponding to the 'business day on which step 701 is operated' are extracted from the account payable DB 340 in the purchaser device 300 in step 703 .

In step 704, the 'seller field value and the untransferred amount field value' are extracted from the 'each records extracted in step 703', and the untransferred amount field value is transferred to the 'account matching the seller field value', The 'time stamp of when step 704 is operated' is stored in the payment execution date field of the record.

9 is a method for safely and conveniently transferring trade receivables using a block chain according to the present invention in one embodiment It is a flow chart showing an embodiment of the operation of distributed storage in a method.

In step 801, in the 'sales receivable relay server 100, the seller device 200, the purchaser device 300, and the escrow server 500' for each predetermined block generation period in step 801, the hash DB 130, 230, 330 configured in the device , 530) extracting timestamps corresponding to the block generation period, extracting transaction data serial numbers and root hash values matched to each timestamp, and extracting the extracted timestamps and transaction data serial A root hash value of 'numbers and root hash values' is calculated as integrity proof corresponding to the block generation period.

In step 802, in the 'devices 100, 200, 300, 500 that operated step 801', respectively, 'as author identification information, the public key of the subject operating the device' and the corresponding block generation period identification information and 'in step 801 Create your own proof transaction data for each cycle including 'the proof of integrity calculated by yourself'.

A first embodiment of the public key is the real-name linked public key of the subject.

A second embodiment of the public key is a public key for a trade receivable relay agency of the subject.

In step 803, in the 'devices 100, 200, 300, 500 that operated step 802', using the 'secret key of the subject who operates itself' respectively Write your own e-signature.

A first embodiment of the secret key is the real name-linked secret key of the subject.

A second embodiment of the secret key is a secret key for the account receivable relay agency of the subject.

In step 804, in the 'devices (100, 200, 300, 500) that operated step 803', 'one's own proof transaction data for each period written in step 802' and 'one's own digital signature written in step 803' are recorded in the block chain network, respectively. broadcast to

100: Trade receivable relay server
110: customer DB
120: transaction data DB
130: hash DB
140: Trade receivable DB
150: financial relay DB
160: Account DB
170: Escrow DB
200: seller device
210: secret information DB
220: transaction data DB
230: hash DB
240: Trade receivable DB
250: Transfer receivable DB
300: buyer device
310: secret information DB
320: transaction data DB
330: hash DB
340: Trade payable DB
350: Transfer receivable DB
400: positive quantum device
411: secret information DB
500: Escrow server
510: Escrow account DB
520: transaction data DB
530: hash DB
540: Real name account DB

Claims (6)

In the purchaser device to implement a method of transferring trade receivables safely and conveniently using blockchain,
creating a trade receivable list including at least one 'individual trade receivable information including buyer identification information, seller identification information, trade receivable amount and trade receivable settlement date';
creating trade receivable registration transaction data including 'buyer identification information as author identification information' and the list of accounts receivable;
creating an electronic signature for the trade receivable registration transaction data using the buyer's private key; and
transmitting the trade receivable registration transaction data and electronic signature to a trade receivable relay server; A method comprising
In a device for implementing a method of transferring trade receivables safely and conveniently using blockchain,
receiving transaction data and digital signatures from one or more other devices;
calculating a root hash value of 'information including the transaction data and digital signature';
calculating an integrity proof corresponding to a block generation period using one or more root hash values calculated as described above; and
broadcasting information including the integrity proof to a block chain network; A method comprising
In a device for implementing a method of transferring trade receivables safely and conveniently using blockchain,
Step of inputting the ID and password of the person in charge;
calculating the encryption/decryption key of the person in charge by using the hash value of the ID and the hash value of the password;
searching for an 'encrypted secret key' matching the ID;
decrypting the searched 'encrypted secret key' with the calculated encryption/decryption key; and
creating a digital signature of the device operator using the decrypted secret key; A method comprising
In the seller device for implementing a method of transferring trade receivables safely and conveniently using blockchain,
Receiving the trade receivable registration transaction data and electronic signature including at least one creator identification information and 'individual trade receivable information including buyer identification information, seller identification information, trade receivable amount and trade receivable settlement date';
outputting the individual accounts receivable information;
inputting 'information for selecting one or more of the individual accounts receivable information' and 'a discount rate matched to one or more of the selected individual accounts receivable information';
creating transfer object bond registration transaction data including at least one 'seller identification information as author identification information' and 'individual transfer object bond information including the selected individual receivable information and the discount rate';
creating an electronic signature for the transfer target bond registration transaction data using the seller's private key; and
transmitting the transfer target receivable registration transaction data and electronic signature to a trade receivable relay server; A method comprising
In the transferee device to implement a method of transferring trade receivables safely and conveniently using block chain,
outputting one or more 'comparative numerical input fields matched to the accounts receivable DB field identification information';
inputting a numerical value into the comparative numerical input field;
transmitting the input information to a trade receivable relay server;
receiving one or more transferable trade receivable identification information from a trade receivable relay server in response to the transmission;
outputting the received transferable receivables identification information;
inputting 'information for selecting one or more of the output transferable receivables identification information';
creating trade receivables application transaction data including 'acquirer identification information as author identification information' and 'the selected transferable trade receivable identification information';
creating an electronic signature for the trade receivable transfer application transaction data using the transferee's secret key; and
transmitting the 'trade receivable application transaction data and electronic signature' to a trade receivable relay server; A method comprising
In a trade receivable relay server to implement a method of transferring trade receivables safely and conveniently using block chain,
creating transfer notification transaction data including 'seller identification information as author identification information', 'buyer identification information as recipient identification information' and transfer receivable identification information;
creating transfer notice request transaction data including 'receivables relay agency identification information as author identification information' and 'information identifying the seller as recipient identification information' and the transfer notice transaction data;
transmitting the transfer notification request transaction data to a seller device;
receiving the transfer notification transaction data and 'an electronic signature prepared using a seller's private key for the transfer notification transaction data'; and
verifying the digital signature using the public key of the seller; A method comprising

Images