Insurance claims system, insurance claims method, and insurance claims program

Abstract

To appraise an insurance claim for a cyber insurance for digital currency, while securing validity for an evidence of insurance appraisal, in the case where an insured person delegates account management of the digital currency to a custody agent.SOLUTION: When a terminal device submits an insurance claim, an insurance claim appraisal device requests submission of proof of account ownership after receiving the insurance claim. The terminal device issues a proof of account ownership token via an account management device. The token is transferred from an account of an insured individual to an account of an insurance company. The insurance claim appraisal device verifies the proof of account ownership of the account that is an object of insurance of the insured person, determines whether insurance money can be paid or not on the basis of a transaction history of a settlement device, and calculates a loss and the amount of insurance.SELECTED DRAWING: Figure 13

Description

[Technical Field]

[0001] The present invention relates to an insurance claim system, an insurance claim method, and an insurance claim program for electronic settlement. [Background technology]

[0002] Due to technological innovation in the financial sector and the advancement of cashless transactions, central banks and financial institutions around the world are engaged in research and development of digital currencies.

[0003] Digital currency is a currency that has been digitized on a computer system and is managed, stored, and exchanged over the internet. Digital currency includes central bank digital currency, which is legal tender issued as a liability of a central bank, electronic money issued by private companies, and crypto assets that utilize blockchain algorithms.

[0004] Digital currency is expected to serve as a new payment infrastructure that supports the digitalization of economic activity. The spread of mobile devices and cloud computing has created new connections and combinations between various economic entities, goods, and services. Economic activities in the virtual space, such as e-commerce and the sharing economy, are expanding. Furthermore, connections with economic activities in the real space, such as carbon footprints, are also emerging. Digital currency is responsible for the flow of money in these economic spheres.

[0005] Various models have been proposed for the operation of digital currency systems, including a model in which the issuer of the digital currency manages the system centrally, a model in which a consortium of multiple companies that issue and distribute digital currency manages the system in a decentralized manner, and a model in which an unspecified number of companies or individuals manage the system decentralized.

[0006] Digital currency users, such as consumers and businesses, access the system through applications on their computers or mobile devices. Because digital currency utilizes blockchain technology, transactions are digitally signed with the user's private key when making payments.

[0007] For digital currency to be accepted by society as a new means of payment, it is necessary to ensure not only convenience but also safety. First, it is necessary to prevent cyber incidents and fraudulent transactions by improving the quality of the system and taking security measures. However, as it is a system, it is impossible to predict and deal with all problems in advance. Therefore, as a post-event measure, cyber insurance is also necessary to compensate for damages caused by cyber incidents and fraudulent transactions in the digital currency system.

[0008] For example, Patent Document 1 is known as a technology for calculating insurance product rates for cyber insurance for digital currencies. In this system, the relationship between digital currencies and users is expressed in a tree structure, and if the digital currency is subjected to a cyber attack, multiple scenarios are simulated to see how the damage will spread, and the risk is assessed by the total of the damage, and the insurance premium rate is calculated. [Prior art documents] [Patent documents]

[0009] [Patent Document 1] US20210256623 Summary of the Invention [Problem to be solved by the invention]

[0010] The above-mentioned Patent Document 1 calculates the premium rate for the insurance product, but does not mention how insurance claims are assessed and insurance payments are made. The insured person enters into an insurance contract, setting the coverage period and coverage amount for various types of digital currencies that they own. Coverage often covers vulnerability attacks and hacking of the digital currency system's programs, but if the insured person loses the private key for the digital currency, the insurance will not be paid.

[0011] In the event of a loss due to a digital currency cyber incident, the insured submits an insurance claim and evidence. The evidence is proof that the digital currency private key is still safely managed, i.e., proof of account ownership. The insurance company analyzes the insured's claim information and transaction history collected from the digital currency system, and if it can verify that the cyber incident occurred during the insurance contract period and that the insured still possesses the digital currency private key, it will determine that the event is grounds for payment and will pay the insurance claim.

[0012] When building a system for assessing insurance claims and paying insurance benefits, it is possible to run it on a public blockchain with the participation of an unspecified number of companies and individuals. Because the insured person manages the private key of the digital currency, they can submit proof of account ownership themselves. In addition, because the insured person can also refer to the transaction history of the digital currency system, they can directly refer to the evidence used by the insurance company in the assessment and confirm the validity of the assessment results.

[0013] However, because it is intended for a system in which an unspecified number of companies and individuals operate a digital currency system in a decentralized manner on a public blockchain, there was a problem in that it could not accommodate a system in which a specific approved organizational group manages a digital currency system in a decentralized manner on a private blockchain.

[0014] When operating a digital currency system on a private blockchain, there is an information asymmetry between the insured and the insurance company using cyber insurance.

[0015] In this type of operation, users access the digital currency system via custody, meaning they cannot directly access evidence such as proof of digital currency account ownership or transaction history. Safely managing digital currency private keys requires advanced expertise. To reduce this burden, the insured entrusts the management of private keys and accounts to a custodian such as a bank. Because the insured does not have direct access to the digital currency system, they cannot submit proof of account ownership to the insurance company themselves. Furthermore, because they cannot check the transaction history used by the insurance company in their assessment, they cannot determine the validity of the assessment results.

[0016] Custody has the business function of settling digital currencies, but does not have the business function of handling insurance claims for digital currencies.

[0017] On the other hand, while insurance companies can collect transaction history as participants in the digital currency system, they do not have access to the custody system, and therefore cannot verify whether the insured’s private keys are being managed securely, i.e., proof of account ownership.

[0018] In other words, the insurance claim process for cyber insurance for digital currencies faces the issue of a lack of mutual trust between the insured and the insurance company in the process of collecting and verifying evidence, which makes it impossible to guarantee the legitimacy of the evidence used in insurance assessments.

[0019] The present invention has been made in consideration of the above-mentioned problems, and aims to provide technology that makes it possible to assess insurance claims for digital currency cyber insurance while ensuring the legitimacy of the evidence for insurance assessment when the insured entrusts the management of digital currency account to a custody company. [Means for solving the problem]

[0020] The insurance claim system according to the present invention comprises a terminal device, an account management device, a settlement device, and an insurance claim assessment device, each of which has a processor and a memory, and the processor of the terminal device executes a first program to output insurance claim information relating to a digital currency insurance claim procedure input by a user to the insurance claim assessment device, and the processor of the insurance claim assessment device executes a second program to request the terminal device to submit an account ownership certificate to prove that a user identified by account identification information for identifying the user's account, which is included in the insurance claim information, owns an account as an insured person, and the processor of the terminal device executes the first program to output a request to issue the account ownership certificate to the account management device, and the processor of the account management device executes a third program to generate an account ownership certificate using insurance contract identification information for identifying the digital currency insurance contract, the account identification information, and digital currency identification information for identifying the digital currency, which are included in the insurance claim information. and outputs to the payment device a request for issuance of the account possession proof token whose owner is the insured person, and the processor of the payment device executes a fourth program to add the token for which the issuance request has been received to a first table that associates token identification information for identifying the token, the value of the token, and the owner of the token, and outputs the result of the addition to the account management device as a token issuance transaction result, and the processor of the account management device executes the third program to output to the payment device a transfer request in response to the token issuance transaction result, with the owner of the added token being the insurance company, and the processor of the payment device executes the fourth program to update the owner of the token added to the first table to the insurance company and output the result of the update to the account management device as a token transfer transaction result, and the processor of the account management device executes the third program to receive the token transfer transaction result from the payment device, and outputs a completion of issuance of the account possession proof to the terminal device, and the processor of the terminal deviceThe insurance claim system is configured to execute the first program, and output completion of submission of the account ownership proof to the insurance claim assessment device based on completion of issuance of the account ownership proof, and the processor of the insurance claim assessment device executes a fifth program, and assesses the insurance claim based on the insurance claim information using a second table that manages insurance contract information identified by the insurance contract identification information and a third table that manages accident information for digital currency identified by the currency identification information. [Effects of the Invention]

[0021] According to the present invention, when an insured person entrusts digital currency account management operations to a custody company, it is possible to assess insurance claims for digital currency cyber insurance while ensuring the legitimacy of the evidence for insurance assessment.

[0022] The details of at least one implementation of the subject matter disclosed herein are set forth in the accompanying drawings and the description below. Other features, aspects, and advantages of the disclosed subject matter will become apparent from the following disclosure, drawings, and claims. [Brief explanation of the drawings]

[0023] [Figure 1] 1 is a block diagram illustrating an example of a device configuration of an insurance claim system according to an embodiment of the present invention. [Figure 2] FIG. 2 is a block diagram illustrating an example of a terminal device according to the present embodiment. [Figure 3] FIG. 2 is a block diagram illustrating an example of an account management device according to the present embodiment. [Figure 4] FIG. 2 is a block diagram illustrating an example of a payment device according to the present embodiment. [Figure 5] FIG. 2 is a block diagram illustrating an example of an insurance claim assessment device according to the present embodiment. [Figure 6] FIG. 10 is a diagram illustrating an example of a wallet table according to the present embodiment. [Figure 7]FIG. 10 is a diagram illustrating an example of a digital currency transaction history table according to the present embodiment. [Figure 8] FIG. 10 illustrates an example of an account possession proof token management table according to the present embodiment. [Figure 9] FIG. 10 is a diagram illustrating an example of an account possession proof token transaction history table according to the present embodiment. [Figure 10] FIG. 10 is a diagram showing an example of an insurance contract table according to the present embodiment. [Figure 11] FIG. 10 is a diagram illustrating an example of a billing table according to the present embodiment. [Figure 12] FIG. 10 is a diagram illustrating an example of an accident information table according to the present embodiment. [Figure 13] FIG. 2 is a sequence diagram illustrating an example of a processing flow between devices in the insurance claim system according to the embodiment. [Figure 14] 10 is a flowchart illustrating an example of an insurance claim program executed by the terminal device according to the present embodiment. [Figure 15] 10 is a flowchart illustrating an example of a certificate issuing program executed by the account management device according to the present embodiment. [Figure 16] 10 is a flowchart illustrating an example of an account possession proof token program executed by the payment device according to the present embodiment. [Figure 17] 4 is a flowchart illustrating an example of a claim management program executed by the insurance claim assessment device according to the present embodiment. [Figure 18] 10 is a flowchart illustrating an example of an evidence collection program executed by the insurance claim assessment device according to the present embodiment. [Figure 19] 4 is a flowchart illustrating an example of a damage assessment program executed by the insurance claim assessment device according to the present embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0024] Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings. Note that the embodiments described below do not limit the scope of the invention as claimed, and not all of the elements and combinations thereof described in the embodiments are necessarily essential to the solution of the invention.

[0025] In other words, the following description and drawings are examples for explaining the present invention, and have been omitted or simplified as appropriate for clarity of explanation. The present invention can be implemented in various other forms. Unless otherwise specified, each component may be singular or plural.

[0026] In order to facilitate understanding of the invention, the position, size, shape, range, etc. of each component shown in the drawings may not represent the actual position, size, shape, range, etc. Therefore, the present invention is not necessarily limited to the position, size, shape, range, etc. disclosed in the drawings.

[0027] In the following explanation, various types of information may be described using expressions such as "database," "table," and "list," but the various types of information may also be expressed in data structures other than these. To indicate that the information is not dependent on the data structure, "XX table," "XX list," etc. may be referred to as "XX information." When describing identification information, expressions such as "identification information," "identifier," "name," "ID," and "number" are used, and these are interchangeable.

[0028] When there are multiple components with the same or similar functions, they may be described using the same reference numeral with different subscripts. However, when there is no need to distinguish between these multiple components, the subscripts may be omitted.

[0029] Furthermore, in the following description, processing performed by executing a program may be described, but the program is executed by a processor (e.g., a CPU (Central Processing Unit) or a GPU (Graphics Processing Unit)) to perform the specified processing while appropriately using storage resources (e.g., memory) and / or interface devices (e.g., communication ports), and therefore the processor may be the subject of the processing. Similarly, the subject of the processing performed by executing a program may be a controller, device, system, computer, or node having a processor. The subject of the processing performed by executing a program may be any computing unit, and may include a dedicated circuit (e.g., an FPGA (Field-Programmable Gate Array) or an ASIC (Application Specific Integrated Circuit)) that performs specific processing.

[0030] A program may be installed on a device such as a computer from a program source. The program source may be, for example, a program distribution server or a computer-readable storage medium. If the program source is a program distribution server, the program distribution server may include a processor and storage resources for storing the program to be distributed, and the processor of the program distribution server may distribute the program to be distributed to other computers. Also, in the following description, two or more programs may be realized as one program, and one program may be realized as two or more programs.

[0031] FIG. 1 is a block diagram illustrating an example of the device configuration of an insurance claim system, which is an assessment system that accepts insurance claims and performs assessments, according to an embodiment of the present invention. In this embodiment, the insurance claim system handles insurance claims for cyber insurance for digital currency. When a terminal device submits an insurance claim, the insurance claim assessment device accepts the insurance claim and then requests the submission of an account ownership certificate, which is proof of account ownership for the insured person who is the insured. The terminal device issues an account ownership certificate token via the account management device and transfers the token from the insured person's account to the insurance company's account. The insurance claim assessment device verifies the account ownership certificate, determines whether to pay insurance claims based on the transaction history of the settlement device, and calculates the damage and insurance amount.

[0032] The insurance claim system 100 includes a terminal device 200 used by a user who makes an insurance claim, an account management device 300 owned by the custody, a settlement system 4000 that can be accessed by companies and organizations that have been approved after a predetermined screening process, such as financial institutions such as banks and insurance companies, and an insurance claim assessment device 500. The settlement system 4000 includes one or more settlement devices 400 owned by companies and organizations that are members of the settlement system.

[0033] <Terminal Device> 2 is a block diagram showing an example of a terminal device 200. The terminal device 200 is a computer including a memory 201, an arithmetic unit 202, an input unit 203, an output unit 204, a communication unit 205, and a storage unit 206. The storage device 206 stores an insurance claim program 1400 for processing insurance claims.

[0034] The input device 203 is configured, for example, by a keyboard, a mouse, or a touch panel. The output device 204 is configured, for example, by a display. The communication device 205 is connected to a network and communicates with other computers.

[0035] The insurance claim program 1400 is loaded into the memory 201 and executed by the processing device 202 . The arithmetic device 202 is, for example, a processor, and operates as a functional unit that provides a predetermined function by executing processing according to the program of each functional unit. For example, the arithmetic device 202 functions as an insurance claim unit by executing processing according to the insurance claim program 1400. Furthermore, the arithmetic device 202 also operates as a functional unit that provides each function of multiple processes executed by each program. A computer and a computer system are devices and systems that include these functional units.

[0036] <Account Management Device> 3 is a block diagram showing an example of an account management device 300. The account management device 300 is a computer including a memory 301, a calculation device 302, an input device 303, an output device 304, a communication device 305, and a storage device 306.

[0037] The storage device 306 stores a wallet table 600 that manages the private keys of the insured person, and a certificate issuing program 1500 that issues and transfers account possession proof tokens.

[0038] The input device 303 is configured, for example, by a keyboard, a mouse, or a touch panel. The output device 304 is configured, for example, by a display. The communication device 305 is connected to a network and communicates with other computers.

[0039] The certificate issuing program 1500 is loaded into the memory 301 and executed by the processing unit 302 . The arithmetic device 302 is, for example, a processor, and operates as a functional unit that provides a predetermined function by executing processing in accordance with the program of each functional unit. For example, the arithmetic device 302 functions as a certificate issuing unit by executing processing in accordance with the certificate issuance program 1500. Furthermore, the arithmetic device 302 also operates as a functional unit that provides each function of multiple processes executed by each program. A computer and a computer system are devices and systems that include these functional units.

[0040] <Payment device> 4 is a block diagram showing an example of a payment device 400. The payment device 400 is a computer including a memory 401, a calculation device 402, an input device 403, an output device 404, a communication device 405, and a storage device 406.

[0041] The storage device 406 stores a digital currency transaction history table 700 that records the transaction history of digital currency, an account possession proof token management table 800 that manages the status of account possession proof tokens, an account possession proof token transaction history table 900 that records the transaction history of account possession proof tokens, a digital currency program 407 that handles digital currency transactions, and an account possession proof token program 1600 that handles account possession proof token transactions. There are many types of digital currency program 407, and each is stored as a single program.

[0042] The input device 403 is configured, for example, by a keyboard, a mouse, or a touch panel. The output device 404 is configured, for example, by a display. The communication device 405 is connected to a network and communicates with other computers.

[0043] The digital currency program 407 and the proof-of-account token program 1600 are loaded into the memory 401 and executed by the processing device 402 . The arithmetic device 402 is, for example, a processor, and operates as a functional unit that provides a predetermined function by executing processing according to the program of each functional unit. For example, the arithmetic device 402 functions as a digital currency unit by executing processing according to the digital currency program 407. The same applies to other programs. Furthermore, the arithmetic device 402 also operates as a functional unit that provides each function of multiple processes executed by each program. A computer and a computer system are devices and systems that include these functional units.

[0044] <Insurance claim assessment device> 5 is a block diagram showing an example of an insurance claim adjustment device 500. The insurance claim adjustment device 500 is a computer including a memory 501, an arithmetic unit 502, an input unit 503, an output unit 504, a communication unit 505, and a storage unit 506.

[0045] The storage device 506 stores an insurance contract table 1000 that manages insurance contract information, a claim table 1100 that manages the status of insurance claims, an accident information table 1200 that records information on cyber accidents, a claim management program 1700 that controls the insurance claim assessment process, an evidence collection program 1800 that collects evidence for claim assessment, and a damage assessment program 1900 that determines whether the reason for insurance payment is appropriate and calculates the insurance payment.

[0046] The input device 503 is configured, for example, by a keyboard, a mouse, or a touch panel. The output device 504 is configured, for example, by a display. The communication device 505 is connected to a network and communicates with other computers.

[0047] The claims management program 1700 , the evidence collection program 1800 , and the loss assessment program 1900 are loaded into memory 501 and executed by the computing device 502 . The arithmetic device 502 is, for example, a processor, and operates as a functional unit that provides a predetermined function by executing processing in accordance with the program of each functional unit. For example, the arithmetic device 502 functions as a billing management unit by executing processing in accordance with the billing management program 1700. The same applies to other programs. Furthermore, the arithmetic device 502 also operates as a functional unit that provides each function of multiple processes executed by each program. A computer and a computer system are devices and systems that include these functional units.

[0048] <Data> 6 is a diagram showing an example of the wallet table 600. The wallet table 600 is managed by the account management device 300. The wallet table 600 includes an account ID 601, a private key 602, a validity state 603, and a timestamp 604 in one entry.

[0049] The account ID 601 stores a unique identifier that indicates the insured's digital currency account. The private key 602 stores a private key for digitally signing transactions made by the settlement device 400. The validity status 603 stores a flag that indicates whether the account ID 601 is valid or invalid. The timestamp 604 stores the time the wallet record was updated.

[0050] 7 is a diagram showing an example of a digital currency transaction history table 700. The digital currency transaction history table 700 is managed by the settlement device 400. The digital currency transaction history table 700 includes a transaction ID 701, a currency ID 702, a sender 703, a recipient 704, a transaction amount 705, and a timestamp 706 in one entry.

[0051] Transaction ID 701 stores a unique identifier for each digital currency transaction result. Currency ID 702 stores an identifier indicating the type of digital currency. Sender 703 stores the ID of the account that sent the digital currency. Destination 704 stores the ID of the account that received the digital currency. Transaction amount 705 stores the amount of digital currency transferred in this transaction. Timestamp 706 stores the time the transaction was executed.

[0052] 8 is a diagram showing an example of the account possession proof token management table 800. The account possession proof token management table 800 is managed by the payment device 400. The account possession proof token management table 800 includes a token ID 801, a token value 802, and an owner 803 in one entry. A unique identifier of the token is stored in the token ID 801. The value of the token is stored in the token value 802. The account ID of the token owner is stored in the owner 803.

[0053] 9 is a diagram showing an example of the account possession proof token transaction history table 900. The account possession proof token transaction history table 900 is managed by the settlement device 400. The account possession proof token transaction history table 900 includes a transaction ID 901, a token ID 902, a token value 903, a sender 904, a destination 905, a signature 906, and a timestamp 907 in one entry.

[0054] Transaction ID 901 stores a unique identifier for each transaction result of an account possession proof token. Token ID 902 stores the ID of the traded token. Token Value 903 stores the value of the traded token. Sender 904 stores the ID of the account that sent the token. Destination 905 stores the ID of the account that received the token. Signature 906 stores the digital signature of the account that executed this transaction. Timestamp 907 stores the time the transaction was executed.

[0055] 10 is a diagram showing an example of the insurance contract table 1000. The insurance contract table 1000 is managed by the insurance claim adjustment device 500. The insurance contract table 1000 includes an insurance contract ID 1001, an account ID 1002, a currency ID 1003, an insurance start date 1004, an insurance end date 1005, a coverage rate 1006, and a maximum amount 1007 in one entry.

[0056] The insurance contract ID 1001 stores a unique identifier for the insurance contract. The account ID 1002 stores the account ID of the insured who has concluded this insurance contract. The currency ID 1003 stores the currency ID of the digital currency that is the subject of the insurance. The insurance start date 1004 stores the start date of application of this insurance contract. The insurance end date 1005 stores the end date of application of this insurance contract. The coverage rate 1006 stores the percentage of damages that will be compensated under this insurance contract. The limit amount 1007 stores the maximum amount of damages that will be compensated under this insurance contract.

[0057] 11 is a diagram showing an example of the billing table 1100. The billing table 1100 is managed by the insurance claim adjustment device 500.

[0058] The billing table 1100 includes a billing ID 1101, an insurance contract ID 1102, an account ID 1103, a currency ID 1104, a verification code 1105, a verification code timestamp 1106, proof of account ownership 1107, payment availability 1108, insurance payment 1109, and a status 1110 in one entry.

[0059] Claim ID 1101 stores a unique identifier for the insurance claim. Insurance contract ID 1102 stores the ID of the insurance contract that is the subject of the insurance claim. Account ID 1103 stores the account ID that is the subject of the insurance claim. Currency ID 1104 stores the ID of the currency that is the subject of the insurance claim. Verification code 1105 stores a random number used to verify the insurance adjustment. Verification code timestamp 1106 stores the time the verification code was issued. Account ownership proof 1107 stores the result of the determination of account ownership proof. Payment possibility 1108 stores the result of the adjustment on whether the insurance claim can be paid. Insurance claim 1109 stores the amount of the insurance claim to be paid. Status 1110 stores the progress of the insurance adjustment.

[0060] 12 is a diagram showing an example of the accident information table 1200. The accident information table 1200 is managed by the insurance claim assessment device 500. The accident information table 1200 includes an incident ID 1201, a currency ID 1202, an accident content 1203, a cause 1204, a countermeasure 1205, an accident occurrence date 1206, and a countermeasure completion date 1207 in one entry.

[0061] The incident ID 1201 stores a unique identifier for a cyber incident related to digital currency. The currency ID 1202 stores the currency ID of the digital currency in which the cyber incident occurred. The accident details 1203 stores summary information about the incident. The cause 1204 stores the cause of the incident. The countermeasures 1205 store the details of the countermeasures taken against the incident. The accident occurrence date 1206 stores the date and time when the incident occurred. The countermeasure completion date 1207 stores the date and time when the countermeasures for the incident were completed.

[0062] <Processing> In the following explanation, an example of insurance claim assessment for insurance contract ID "P01" will be explained, but the present invention is not limited to this.

[0063] FIG. 13 is a sequence diagram showing an example of processing performed by the insurance claim system 100.

[0064] The terminal device 200 transmits an insurance claim to the insurance claim adjustment device 500 (S1301). The insurance claim adjustment device 500 accepts the insurance claim and transmits a request for submission of account ownership proof to the terminal device 200 (S1302). The terminal device 200 transmits a request for issuing an account possession certificate to the account management device 300 (S1303).

[0065] The account management device 300 transmits a request for issuing a token for proof of account possession to the payment device 400 (S1304).

[0066] The settlement device 400 executes the token issuing process (S1305) and transmits the token transaction result to the account management device 300 (S1306).

[0067] The account management device 300 transmits a token transfer request for the account possession proof to the payment device 400 (S1307).

[0068] The settlement device 400 executes the token transfer process (S1308) and transmits the token transaction result to the account management device 300 (S1309).

[0069] The account management device 300 transmits a notification that the account possession certificate has been issued to the terminal device 200 (S1310).

[0070] The terminal device 200 transmits a notification that the account ownership proof has been submitted to the insurance claim adjustment device 500 (S1311).

[0071] The insurance claim adjustment device 500 determines whether or not the insurance payment is possible, calculates the damage and the insurance payment (S1312), and transmits the assessment result to the terminal device 200 (S1313).

[0072] FIG. 14 is a flow chart illustrating an example of an insurance claim program 1400 . In the following description, the insurance claim program 1400 will be described as the subject of processing, but the arithmetic device 202 may also be the subject of processing.

[0073] The insurance claim program 1400 displays an insurance claim form on the output device (S1401). Next, the insurance claim program 1400 receives user input via the input device and generates insurance claim information (S1402). The insurance claim information includes an insurance contract ID, an account ID, and a currency ID as information related to the insurance claim procedure. For example, the insurance claim information is a message such as {insurance contract ID: P01, account ID: user01, currency ID: PU085}. Next, the insurance claim program 1400 transmits the insurance claim to the insurance claim adjustment device 500 (S1403). Next, the insurance claim program 1400 receives a request to submit proof of account ownership from the insurance claim adjustment device 500 (S1404). Next, the insurance claim program 1400 transmits a request for issuing an account ownership certificate to the account management device 300 (S1405). Next, the insurance claim program 1400 receives a notification that the issuance of the account ownership certificate has been completed from the account management device 300 (S1406). Next, the insurance claim program 1400 transmits a notification that the account ownership proof has been submitted to the insurance claim adjustment device 500 (S1407). Next, the insurance claim program 1400 receives the assessment result from the insurance claim adjustment device (S1408).

[0074] FIG. 15 is a flowchart showing an example of the certificate issuing program 1500. In the following description, the certificate issuing program 1500 will be described as the subject of processing, but the processing device 302 may also be the subject of processing.

[0075] The certificate issuance program 1500 receives a request for issuing an account possession certificate from the terminal device 200 (S1501). For example, the issuance request is a message such as {insurance contract ID: P01, currency ID: PU085, insured person account ID: user01, insurance company account ID: insurance01, verification code: h8ex3h}.

[0076] The certificate issuance program 1500 extracts the insurance contract ID, currency ID, insured person account ID, insurance company account ID, and verification code from the issuance request message (S1502).

[0077] The certificate issuing program 1500 inputs the insurance contract ID, the insured person's account ID, the currency ID, and the verification code into a hash function to generate a hash value (S1503).

[0078] The certificate issuance program 1500 transmits a token transaction request to the settlement device 400 to perform a token issuance transaction (S1504). The token transaction request has the following information: request category: issuance, token ID: insurance contract ID, token value: hash value generated in the previous step, sender: custody account ID, destination: insured account ID, and signature: digital signature using the custody's private key. For example, the token transaction request is a message of {request category: issuance, token ID: P01, token value: xjfi9j3424la890d, sender: Bank02, destination: user01, signature: sig-bank02}.

[0079] The certificate issuing program 1500 receives the token transaction result from the settlement device 400 (S1505).

[0080] The certificate issuance program 1500 transmits a token transaction request to the settlement device 400 to perform a token transfer transaction (S1506). The token transaction request has the following information: request category: transfer, token ID: insurance contract ID, sender: insured person account ID, destination: insurance company account ID, and signature: digital signature using the insured person's private key. For example, the token transaction request is a message of {request category: transfer, token ID: P01, sender: user01, destination: insurance01, signature: sig-user01}. The certificate issuing program 1500 receives the token transaction result from the settlement device 400 (S1507). The certificate issuance program 1500 transmits a notification of completion of issuance of the account possession certificate to the terminal device 200 (S1508).

[0081] FIG. 16 is a flow chart illustrating an example of an account ownership token program 1600 . In the following description, the account possession proof token program 1600 will be described as the subject of processing, but the computing device 402 may also be the subject of processing.

[0082] The account possession proof token program 1600 receives a token transaction request from the account management device 300 (S1601).

[0083] The account possession proof token program 1600 references the request category of the token transaction request message and determines the requested transaction content (S1602). If it is an issuance, proceed to S1603. If it is a transfer, proceed to S1610.

[0084] The account possession proof token program 1600 extracts the token ID, token value, sender, destination, and signature from the token transaction request (S1603). For example, the following values are extracted from the token transaction request: token ID: P01, token value: xjfi9j3424la890d, sender: bank02, destination: user01, and signature: sig-bank02.

[0085] The account possession proof token program 1600 searches the account possession proof token management table 800 using the token ID as a key (S1604).

[0086] The account ownership proof token program 1600 determines whether a record with the same token ID exists to prevent duplicate claims for account ownership proof (S1605). If yes, the issuance transaction is interrupted due to duplicate claims, and the program proceeds to S1614. If no, the program proceeds to S1606 due to a new claim.

[0087] The account possession proof token program 1600 adds a record to the account possession proof token management table 800 (S1606). The data items of the record are the token ID, token value, and owner. The token ID and token value are set to values extracted from the token transaction request. The owner is set to the value of the destination of the token transaction request. For example, the account possession proof token management record has the information: token ID: P01, token value: xjfi9j3424la890d, owner: user01.

[0088] The account ownership proof token program 1600 adds a record to the account ownership proof token transaction history table 900 (S1607). The data items of the record are transaction ID, token ID, token value, sender, destination, signature, and timestamp. A value that uniquely identifies the transaction is set in the transaction ID. Values extracted from the token transaction request are set in the token ID, token value, sender, destination, and signature. The timestamp is set to the time the transaction was executed. For example, an account ownership proof token transaction history record has the following information: transaction ID: x2nd8hapo, token ID: P01, token value: xjfi9j3424la890d, sender: Bank02, destination: user01, signature: sig-bank02, and timestamp: 2022 / 02 / 11 14:23:01.

[0089] The account ownership proof token program 1600 sets the status of the token transaction result to success (S1608).

[0090] The account possession proof token program 1600 transmits the token transaction result to the account management device 300 (S1609).

[0091] The account possession proof token program 1600 extracts the token ID, sender, destination, and signature from the token transaction request (S1610). For example, the following values are extracted from the token transaction request: token ID: P01, sender: user01, destination: insurance01, and signature: sig-user01.

[0092] The account possession proof token program 1600 searches the account possession proof token management table 800 using the token ID as a key (S1611).

[0093] The account ownership proof token program 1600 determines whether a record with the same token ID exists (S1612) to prevent a non-existent account ownership proof from being submitted to the insurance company. If Yes, the account ownership proof exists, so proceed to S1613. If No, the account ownership signature does not exist, so the transfer transaction is aborted and proceed to S1614.

[0094] The account possession proof token program 1600 updates the owner in the account possession proof token management table 800 (S1613). The owner is set to the value of the destination of the token transaction request. For example, the account possession proof token management record has the following information: token ID: P01, token value: xjfi9j3424la890d, owner: insurance01.

[0095] If the issuance transaction or transfer transaction is interrupted, the account ownership proof token program 1600 sets the status of the token transaction result to failure (S1614).

[0096] FIG. 17 is a flow chart illustrating an example of a billing management program 1700. In the following description, the billing management program 1700 will be described as the subject of processing, but the arithmetic device 502 may also be the subject of processing.

[0097] The claim management program 1700 receives an insurance claim from the terminal device 200 (S1701). The insurance claim information includes an insurance contract ID, an account ID, and a currency ID as information related to the insurance claim procedure. For example, the insurance claim information is a message such as {insurance contract ID: P01, account ID: user01, currency ID: PU085}.

[0098] The claim management program 1700 adds the insurance claim information to the claim table 1100 (S1702). The claim ID is set to a value that uniquely identifies the claim. The insurance contract ID, account ID, and currency ID are set to values extracted from the insurance claim. The status is set to the value "claim accepted." Other data items are left blank at this point. For example, a claim record has the following information: claim ID: C101, insurance contract ID: P01, account ID: user01, currency ID: PU085, status: claim accepted.

[0099] The billing management program 1700 executes the evidence collection program 1800 (S1703). The claims management program 1700 executes the damage assessment program 1900 (S1704). The billing management program 1700 acquires the post-assessment record from the billing table 1100 (S1705). The billing management program 1700 notifies the terminal device 200 of the assessment result (S1706).

[0100] FIG. 18 is a flowchart showing an example of the evidence collection program 1800. In the following description, the evidence collection program 1800 will be described as the subject of processing, but the arithmetic device 502 may also be the subject of processing.

[0101] The evidence collection program 1800 receives an evidence collection request from the billing management program 1700 (S1801). The evidence collection request includes a billing ID. For example, the evidence collection request is a message such as {Billing ID: C101}.

[0102] The evidence collection program 1800 extracts the request ID from the evidence collection request message (S1802). For example, the request ID is C101.

[0103] The evidence collection program 1800 searches the billing table using the billing ID and acquires the billing record (S1803).

[0104] The evidence collection program 1800 generates a random number for a verification code for the claim (S1804). The verification code is used to verify that the account ownership proof is issued for the insured digital currency. Because there are various types of digital currencies, which digital currency is affected by a cyber incident depends on the situation. Also, a single cyber incident may affect multiple digital currencies. Therefore, the insured selects the digital currency that suffered damage when filing an insurance claim. If the account ownership proof is submitted for a digital currency that is not covered by the insurance, the claim adjustment device must refuse to pay the insurance money. For these reasons, a verification code is issued. The assessment method using the verification code will be described in the flowchart of the damage assessment program 1900.

[0105] The evidence collection program 1800 adds the verification code and verification code timestamp to the claim table 1100 (S1805). The random number generated in the previous step is set as the verification code. The time when the verification code was generated is set as the verification code timestamp. For example, the claim record has the following information: Claim ID: C101, Insurance Contract ID: P01, Account ID: user01, Currency ID: PU085, Verification Code: h8ex3h, Verification Code Timestamp: 2022 / 02 / 11 14:21:50, Status: Claim Accepted.

[0106] The evidence collection program 1800 transmits a request for submitting proof of account ownership to the terminal device 200 (S1806). The request for submitting proof of account ownership includes an insurance contract ID, a currency ID, an insured person account ID, an insurance company account ID, and a verification code. For example, the request for submitting proof of account ownership is a message that reads {insurance contract ID: P01, currency ID: PU085, insured person account ID: user01, insurance company account ID: insurance01, verification code: h8ex3h}.

[0107] The evidence collection program 1800 receives a notification of completion of submission of the account possession certificate from the terminal device 200 (S1807).

[0108] The evidence collection program 1800 updates the status of the claim table to waiting for assessment (S1808).

[0109] FIG. 19 is a flow chart illustrating an example of a loss assessment program 1900 . In the following description, the damage assessment program 1900 will be described as the subject of processing, but the arithmetic device 502 may also be the subject of processing.

[0110] The damage assessment program 1900 receives a damage assessment request from the claim management program 1700 (S1901). The damage assessment request includes a claim ID. For example, the damage assessment request is a message such as {Claim ID: C101}.

[0111] The damage assessment program 1900 extracts the claim ID from the damage assessment request message (S1902). For example, the claim ID is C101.

[0112] The damage assessment program 1900 searches the claim table 1100 using the claim ID and obtains the claim record (S1903).

[0113] The loss adjustment program 1900 extracts the insurance contract ID, account ID, currency ID, verification code, and verification code timestamp from the claim record (S1904). For example, the following information is extracted: claim ID: C101, insurance contract ID: P01, account ID: user01, currency ID: PU085, verification code: h8ex3h, and verification code timestamp: 2022 / 02 / 11 14:21:50.

[0114] The loss adjustment program 1900 searches the insurance contract table 1000 using the insurance contract ID to obtain the insurance contract record (S1905).

[0115] The loss adjustment program 1900 extracts the account ID, currency ID, insurance start date, and insurance end date from the insurance contract record (S1906). For example, the following information is extracted: insurance contract ID: P01, account ID: user01, currency ID: PU085, insurance start date: 2022 / 01 / 01, insurance end date: 2022 / 03 / 31. The loss adjustment program 1900 compares the account ID in the claim record with the account ID in the contract record to verify whether the account ID for which the insurance claim was made is the insured account ID (S1907).

[0116] The loss adjustment program 1900 determines whether the account IDs match (S1908). If yes, proceed to S1909. If no, the claim details do not match the insurance contract, so the adjustment process is interrupted and proceed to S1937.

[0117] The loss adjustment program 1900 compares the currency ID of the claim record with the currency ID of the contract record to verify whether the currency ID of the insurance claim is the currency ID of the insured item (S1909).

[0118] The loss assessment program 1900 determines whether the currency IDs match (S1910). If yes, proceed to S1911. If no, the claim details do not match the insurance contract, so the assessment process is interrupted and proceed to S1937.

[0119] The loss assessment program 1900 extracts records that meet the condition "currency ID = currency ID AND accident occurrence date >= insurance start date AND accident occurrence date <= insurance end date" from the accident information table 1200 (S1911). For example, a search is performed using the condition "currency ID = PU085 AND accident occurrence date >= 2022 / 01 / 01 AND accident occurrence date <= 2022 / 03 / 31."

[0120] The damage assessment program 1900 determines whether an accident information record that meets the conditions of the previous step exists (S1912) to verify whether a cyber-accident has been reported for the insured digital currency during the insurance period. If the answer is Yes, a cyber-accident has occurred, so the program proceeds to S1913 to continue the assessment process. If the answer is No, a cyber-accident has not occurred, so the program interrupts the assessment process and proceeds to S1937.

[0121] To check the issuance history of account possession signature tokens, the loss assessment program 1900 extracts records that match the condition "token ID = insurance contract ID AND sender = custody account ID AND destination = insured account ID" from the account possession proof token transaction history table 900 of the settlement device 400 (S1913). For example, a search is performed using the condition "token ID = P01 AND sender = Bank02 AND destination = user01."

[0122] The damage assessment program 1900 determines whether an account possession proof token transaction history record exists (S1914). If Yes, the process proceeds to S1915 to continue the assessment process. If No, the process interrupts the assessment process and proceeds to S1926.

[0123] The damage assessment program 1900 extracts the signature and timestamp from the account proof-of-possession token transaction history record (S1915). For example, signature: sig-bank02, timestamp: 2022 / 02 / 11 14:23:01.

[0124] The damage assessment program 1900 determines whether the signature extracted in the previous step is the signature of the custodian (S1916) to verify that the account ownership proof token was issued to the custodian. If yes, proceed to S1917 to continue the assessment process. If no, interrupt the assessment process and proceed to S1926.

[0125] The loss assessment program 1900 compares the verification code timestamp of the claim record with the timestamp of the account ownership proof token transaction record to prevent the reuse of previously issued account ownership proof (S1917). One of the conditions for insurance payment is that the insured is the account owner of the insured digital currency at the time of the insurance claim, and the private key is securely stored. If a previously issued account ownership proof is resubmitted, the current account management status cannot be confirmed. Therefore, it is necessary to verify that the account ownership proof token was issued after the insurance claim was filed.

[0126] The loss assessment program 1900 determines whether the verification code timestamp of the claim record is earlier than the timestamp of the account proof-of-possession token transaction record (S1918). If yes, proceed to S1919 to continue the assessment process. If no, proceed to S1926 to abort the assessment process.

[0127] To check the transfer history of the account possession signature token, the loss assessment program 1900 extracts records that match the condition "token ID = insurance contract ID AND sender = insured person account ID AND destination = insurance company account ID" from the account possession proof token transaction history table 900 of the settlement device 400 (S1919). For example, a search is performed using the condition token ID = P01 AND sender = user01 AND destination = insurance01.

[0128] The damage assessment program 1900 determines whether an account possession proof token transaction history record exists (S1920). If Yes, proceed to S1915 to continue the assessment process. If No, interrupt the assessment process and proceed to S1926.

[0129] The damage assessment program 1900 extracts the token value and signature from the account proof-of-possession token transaction history record (S1921). For example, the token value is xjfi9j3424la890d, and the signature is sig-user01.

[0130] The loss assessment program 1900 determines whether the signature extracted in the previous step is the signature of the insured to verify that the insured's key is securely managed and that digital currency transactions are possible (S1922). If the answer is Yes, proceed to S1923 to continue the assessment process. If the answer is No, proceed to S1926 to interrupt the assessment process.

[0131] The loss adjustment program 1900 inputs the insurance contract ID, the insured account ID, the currency ID, and the verification code obtained from the claim record into a hash function to generate a hash value (S1923).

[0132] To verify that the account ownership proof has been issued for the insured digital currency, the loss assessment program 1900 determines whether the hash value generated in the previous step matches the token value obtained from the account ownership proof token transaction history record (S1924). If Yes, proceed to S1925 to continue the assessment process. If No, interrupt the assessment process and proceed to S1926. The hash value compared in this step is a value unique to the combination of account ID and digital currency ID. If the account ownership proof is for an account ID or digital currency that is not covered by insurance, the token value will be different and will therefore not match the hash value. This verifies that the account ownership proof has been issued for the insured digital currency.

[0133] The loss adjuster program 1900 updates the account ownership proof in the claims table to OK (S1925). The loss adjustment program 1900 updates the account ownership proof in the claims table to NG (S1926). The damage assessment program 1900 extracts the accident occurrence date and the countermeasure completion date from the accident information record (S1927). For example, the program extracts information such as accident occurrence date: 2022 / 02 / 07, countermeasure completion date: 2022 / 02 / 09.

[0134] To collect information on digital currency transactions made to the insured's account between the occurrence of a cyber-accident and the completion of countermeasures, the loss assessment program 1900 extracts records that meet the condition "currency ID = currency ID AND (sender = account ID OR destination = account ID) AND timestamp >= date of accident timestamp <= date of countermeasures completion" from the digital currency transaction history table 700 of the settlement device 400 (S1928). For example, a search is performed using the condition "currency ID = PU085 AND (sender = user01 OR destination = user01) AND timestamp >= 2022 / 02 / 07 timestamp <= 2022 / 02 / 09."

[0135] The damage assessment program 1900 extracts transaction amounts from the group of transaction history records acquired in the previous step and totals the fluctuation amount (S1929). The fluctuation amount is the amount of digital currency that fluctuates between the occurrence of a cyber incident and the completion of countermeasures for digital currency in the insured person's account. If this total value is negative, that amount is considered to be the amount of damage, and the amount of damage is considered to be the loss caused by the cyber incident. If the total value is positive or zero, it is determined that there was no damage caused by the cyber incident.

[0136] The damage assessment program 1900 determines whether the change amount tallied in the previous step is positive or negative (S1930). If it is negative, the program proceeds to S1931. If it is positive or zero, the program interrupts the assessment process and proceeds to S1937.

[0137] The loss assessment program 1900 extracts the coverage rate and the upper limit from the insurance contract record (S1931). For example, the coverage rate is 80, and the upper limit is 1000.

[0138] The damage assessment program 1900 calculates the insurance amount by multiplying the fluctuation amount calculated from the digital currency transaction history by the coverage rate (S1933). For example, if the fluctuation amount is 1,000, it is multiplied by 80% of the coverage rate, and the insurance amount becomes 800.

[0139] The damage assessment program 1900 determines whether the insurance amount calculated in the previous step exceeds the upper limit (S1934). If the answer is Yes, the program proceeds to S1935 to adjust the insurance amount. If the answer is No, the insurance amount is fixed, so the program proceeds to S1936.

[0140] The damage assessment program 1900 changes the insurance amount to the upper limit (S1935). For example, if the calculated insurance amount is 1500 and the upper limit is 1000, the insurance amount is changed to 1000, which is the upper limit.

[0141] The damage assessment program 1900 records the calculated insurance amount in the insurance amount field of the claim table 1100, and updates the payment possibility field to yes (S1936).

[0142] The damage assessment program 1900 updates the payment availability in the claim table 1100 to "no" (S1937).

[0143] The loss adjustment program 1900 updates the status in the claims table to complete (S1938).

[0144] As described above, in this embodiment, as described using FIG. 13 etc., in the insurance claim system 100 having the terminal device 200, the account management device 300, the settlement device 400, and the insurance claim assessment device 500, each device has a processor and a memory, and the processor of the terminal device 200 executes a first program (insurance claim program 1400) to output insurance claim information related to the insurance claim procedure for digital currency input by the user to the insurance claim assessment device 500, and the processor of the insurance claim assessment device 500 executes a second program (insurance claim program 1400). The processor of the terminal device 200 executes the first program (certificate issuance program 1500) to request the terminal device 200 to submit an account ownership certificate to prove that the user identified by the account ID for identifying the user's account, which is included in the insurance claim information, owns an account as an insured person, and the processor of the terminal device 200 executes the first program to output an issuance request for the account ownership certificate to the account management device 300, and the processor of the account management device 300 executes the third program (certificate issuance program 1500) to , an issuance request for the account possession proof token, whose owner is the insured, is generated using an insurance contract ID for identifying the insurance contract of the digital currency, the account ID, and a currency ID for identifying the digital currency, which are included in the insurance claim information, and is output to the settlement device 400; the processor 400 of the settlement device executes a fourth program (account possession proof token program 1600) to add the token for which the issuance request was received to a first table (account possession proof token management table 900) that associates a token ID for identifying the token, the value of the token, and the owner of the token, and outputs the result of the addition to the account management device 300 as a token issuance transaction result; the processor of the account management device 300 executes the third program to output a transfer request to the settlement device 400, with the owner of the added token being the insurance company, in response to the token issuance transaction result; and the processor of the settlement device 400 executes the fourth program to update the owner of the token added to the first table to the insurance company;The updated result is output to the account management device 300 as the token transfer transaction result, and the processor of the account management device 300 executes the third program, and upon receiving the token transfer transaction result from the payment device 400, outputs a completion of issuance of the account ownership proof to the terminal device 200, and the processor of the terminal device 200 executes the first program, and based on the completion of issuance of the account ownership proof, outputs a completion of submission of the account ownership proof to the insurance claim assessment device 500, and the processor of the insurance claim assessment device 500 executes a fifth program (damage assessment program 1900) and assesses the insurance claim based on the insurance claim information using a second table (insurance contract table 1000) that manages insurance contract information identified by the insurance contract ID and a third table (accident information table 1200) that manages accident information for the digital currency identified by the currency ID.

[0145] That is, in this embodiment, in the insurance claim system 100 having a terminal device 200 having a processor and a memory, an account management device 300 having a processor and a memory, a settlement device 400 having a processor and a memory, and an insurance claim assessment device 500 having a processor and a memory, when the terminal device 200 submits an insurance claim, the insurance claim assessment device 500 accepts the insurance claim and then requests the submission of proof of account ownership, the terminal device 200 issues an account ownership proof token via the account management device 300 and transfers the token from the insured person's account to the insurance company's account, the insurance claim assessment device 500 verifies the insured person's proof of insured account ownership, determines whether or not to pay the insurance claim based on the transaction history of the settlement device 400, and calculates the damage and the insurance claim.

[0146] As a result, when an insured person entrusts digital currency account management operations to a custody company, and the insured person and insurance company do not trust each other, that is, in a situation where there is information asymmetry between the insured person using cyber insurance and the insurance company, the custody account management device will complement the mutual trust by mediating evidence collection, making it possible to assess insurance claims for digital currency cyber insurance. Furthermore, the scope of applicability of digital currency cyber insurance will be expanded, contributing to the protection of consumers who use digital currencies.

[0147] 16, the processor of the settlement device 400 executes the fourth program to perform the association using a token ID for identifying the token having the same ID as the insurance contract ID, and adds the token to the first table. As a result, the token ID of the account possession proof token becomes the same as the insurance contract ID, and if the token ID and the insurance contract ID overlap when a token issuance request is made, the issuance request can be rejected to eliminate the duplication of the token ID, thereby preventing duplicate claims for account possession proof for one insurance contract.

[0148] 15S1503, S1504, FIG. 16S1607, etc., the processor of the account management device 300 executes the third program to input, into a hash function, the insurance contract ID, the account ID, the currency ID, and also a verification code for verifying the assessment of the insurance claim generated by the insurance claim assessment device 500, to generate a hash value, and outputs the account possession proof token with the generated hash value as the token value to the settlement device 400, and the processor of the settlement device 400 executes the fourth program to associate the token with each of the issued transactions and record it in a fourth table (account possession proof token transaction history table 900). This allows the transaction history of account possession proof tokens with hash values as token values to be centrally managed throughout the system.

[0149] As explained using S1923 in FIG. 19 , the processor of the insurance claim assessment device 500 executes the fifth program, inputs the insurance contract ID, account ID, currency ID, and verification code received when the insurance claim information is received from the terminal device 200 into a hash function to generate a hash value, and determines whether the generated hash value matches the token value recorded in the fourth table. This makes it possible to verify that the account possession proof token has been issued for the insured digital currency. That is, the custodian embeds a hash value unique to each insured item, generated from the insurance contract information and the verification code (random number), into the account possession proof token, and the insurance company compares the hash value it generated with the hash value extracted from the token. By verifying that the hash values do not match when the account ID or currency ID is different, it is possible to reject account possession proof for digital currencies not covered by insurance.

[0150] 19, the processor of the account management device 300 executes the third program to output the timestamp of the verification code generated by the insurance claim assessment device 500 at the time of the insurance claim, the processor of the account management device 300 executes the third program to associate a token ID for identifying the token, the value of the token, and the timestamp of the time when the issuance transaction was executed with each transaction of the token, and records these in a fifth table (account possession proof token transaction history table 900) similar to the fourth table, and the processor of the settlement device 400 executes the fifth program to assess the insurance claim based on the insurance claim information if the timestamp of the verification code is earlier than the timestamp of the time when the issuance transaction was executed. This verifies that the timestamp of the verification code issued at the time of insurance claim acceptance is earlier than the timestamp of the account possession proof token, thereby preventing the reuse of previously issued account possession proof tokens.

[0151] Conventionally, two-tier digital currency systems have adopted private blockchains, and users entrust the private key that manages their digital currency account to a custodian such as a bank, which poses a problem in that the user (i.e., the insured) cannot submit proof of account ownership to the insurance company. As described above, this embodiment solves this problem by having the custodian issue an account ownership proof token upon receiving an insurance claim from the insured. The custodian then transfers the token from the insured's account to the insurance company, verifying the insured's ownership of the insured account, determining whether to pay insurance claims based on the transaction history of the digital currency system, and calculating the damages and insurance amount. This ensures the authenticity of the account ownership proof submitted by the insured via the custodian. Furthermore, various types of digital tokens can be issued, and the transaction history of these tokens is recorded in a ledger and shared among stakeholders. This makes it possible to track changes in token ownership.

[0152] As described above, the digital currency insurance claim system of this embodiment can perform insurance assessment based on valid evidence even when there is information asymmetry between the insured and the insurance company. Note that in the above embodiment, an example of a claim assessment was given in which the contract ID is P101, the account ID is 101, and the currency ID is PU085, but this is not limited to this. There are various types of claim assessments, such as when the contract ID, account ID, and currency ID are different.

[0153] Furthermore, although the present embodiment has exemplified information storage in a table, the information is not limited to a table and may be stored as schema-less data.

[0154] The present invention is not limited to the above-described embodiments as they are, and in the implementation stage, the components can be modified and embodied within the scope of the gist of the present invention, or multiple components disclosed in the above-described embodiments can be appropriately combined. [Explanation of symbols]

[0155] 200 Terminal Device 300 Account Management Device 400 Payment Device 500 Insurance Claim Adjustment Device 600 Wallet Table 700 Digital Currency Transaction History Table 800 Proof-of-Possession Token Management Table 900 Proof-of-Ownership Token Transaction History Table 1000 Insurance Policy Table 1100 Billing Table 1200 Accident Information Table 1400 Insurance Claims Program 1500 Certificate Issuance Program 1600 Proof-of-Ownership Token Program 1700 Claims Management Program 1800 Evidence Collection Program 1900 Loss Assessment Program

Claims

1. An insurance claim system having a terminal device, an account management device, a settlement device, and an insurance claim assessment device, Each device has a processor and a memory; The processor of the terminal device executes a first program to output insurance claim information related to the insurance claim procedure for the digital currency input by the user to the insurance claim assessment device; a processor of the insurance claim adjustment device executes a second program to request the terminal device to submit proof of account ownership to prove that a user identified by account identification information for identifying the user's account, which is included in the insurance claim information, owns an account as an insured person; the processor of the terminal device executes the first program to output a request for issuing the account ownership certificate to the account management device; The processor of the account management device executes a third program to output to the payment device a request for issuance of a token of proof of account ownership, the token being generated using insurance contract identification information for identifying the insurance contract for the digital currency, the account identification information, and digital currency identification information for identifying the digital currency, which are included in the insurance claim information; and the processor of the payment device executes a fourth program to add the token for which the issuance request has been received to a first table that associates token identification information for identifying the token, the value of the token, and the owner of the token, and outputs the result of the addition to the account management device as a token issuance transaction result; The processor of the account management device executes the third program, and outputs a transfer request to the settlement device in response to the token issuance transaction result, with the insurance company as the owner of the added token; the processor of the settlement device executes the fourth program to update the owner of the token added to the first table to the insurance company, and outputs the updated result to the account management device as a token transfer transaction result; the processor of the account management device executes the third program, and upon receiving the token transfer transaction result from the payment device, outputs a notification of completion of issuance of the account ownership proof to the terminal device; the processor of the terminal device executes the first program, and based on the completion of issuance of the account ownership proof, outputs a notification of completion of submission of the account ownership proof to the insurance claim adjustment device; a processor of the insurance claim assessment device executes a fifth program, and assesses the insurance claim based on the insurance claim information by using a second table that manages insurance contract information identified by the insurance contract identification information and a third table that manages accident information regarding the digital currency identified by the currency identification information; An insurance claim system characterized by:

2. 10. The insurance claim system of claim 1, the processor of the settlement device executes the fourth program, performs the association using account possession proof token identification information for identifying the token having the same identification information as the insurance contract identification information, and adds the token to the first table; An insurance claim system characterized by:

3. 10. The insurance claim system of claim 1, the processor of the account management device executes the third program to input the insurance contract identification information, the account identification information, the digital currency identification information, and also a verification code for verifying the assessment of the insurance claim generated by the insurance claim assessment device into a hash function to generate a hash value, and outputs the account ownership proof token, with the generated hash value as the token value, to the payment device; The processor of the payment device executes the fourth program to associate the token with each issuance transaction and record it in a fourth table. An insurance claim system characterized by:

4. 4. The insurance claim system of claim 3, The processor of the insurance claim assessment device executes the fifth program, inputs the insurance contract identification information, the account identification information, the digital currency identification information, and the verification code into a hash function when the insurance claim information is received from the terminal device, to generate a hash value, and determines whether the generated hash value matches the value of the token recorded in the fourth table. An insurance claim system characterized by:

5. 4. The insurance claim system of claim 3, a processor of the account management device executes the third program to output a timestamp of the verification code generated in the insurance claim adjustment device at the time of the insurance claim; the processor of the account management device executes the third program to associate token identification information for identifying the token, the value of the token, and a timestamp of the time when the issuance transaction was executed with each of the issuance transactions of the token, and record them in a fifth table; the processor of the payment device executes the fifth program to assess the insurance claim based on the insurance claim information if the timestamp of the verification code is earlier than the timestamp of the time when the issuance transaction was executed; An insurance claim system characterized by:

6. 1. An insurance claim method performed in an insurance claim system having a terminal device, each having a processor and a memory, an account management device, a settlement device, and an insurance claim assessment device, the method comprising: The terminal device outputs insurance claim information regarding the insurance claim procedure for the digital currency input by the user to the insurance claim assessment device; the insurance claim assessment device requests the terminal device to submit proof of account ownership to prove that the user identified by account identification information for identifying the user's account, which is included in the insurance claim information, owns the account as an insured person; the terminal device outputs a request for issuing the account ownership certificate to the account management device; the account management device outputs to the payment device a request for issuing a token of proof of account ownership, the token being generated using insurance contract identification information for identifying the insurance contract for the digital currency, the account identification information, and digital currency identification information for identifying the digital currency, all of which are included in the insurance claim information; and the payment device adds the token for which the issuance request has been received to a first table that associates token identification information for identifying the token, the value of the token, and the owner of the token, and outputs the result of the addition to the account management device as a token issuance transaction result; the account management device outputs a transfer request to the settlement device in response to the token issuance transaction result, the transfer request specifying the insurance company as the owner of the added token; the settlement device updates the owner of the token added to the first table to the insurance company, and outputs the updated result to the account management device as a token transfer transaction result; When the account management device receives the token transfer transaction result from the payment device, it outputs a notification that the issuance of the account ownership proof has been completed to the terminal device; the terminal device outputs a notification of completion of submission of the account ownership proof to the insurance claim assessment device based on completion of issuance of the account ownership proof; the insurance claim assessment device assesses the insurance claim based on the insurance claim information by using a second table that manages insurance contract information identified by the insurance contract identification information and a third table that manages accident information regarding the digital currency identified by the currency identification information; An insurance claim method characterized by:

7. 7. The insurance claim method according to claim 6, the settlement device performs the association using account possession proof token identification information for identifying the token having the same identification information as the insurance contract identification information, and adds the token to the first table; An insurance claim method characterized by:

8. 7. The insurance claim method according to claim 6, the account management device inputs the insurance contract identification information, the account identification information, the digital currency identification information, and also a verification code for verifying the assessment of the insurance claim generated by the insurance claim assessment device into a hash function to generate a hash value, and outputs the account ownership proof token, with the generated hash value as the token value, to the payment device; The settlement device associates the token with each issuance transaction and records it in a fourth table. An insurance claim method characterized by:

9. 9. The insurance claim method according to claim 8, the insurance claim assessment device inputs the insurance contract identification information, the account identification information, the digital currency identification information, and the verification code into a hash function when receiving the insurance claim information from the terminal device to generate a hash value, and determines whether the generated hash value matches the value of the token recorded in the fourth table; An insurance claim method characterized by:

10. 9. The insurance claim method according to claim 8, the account management device outputs a timestamp of the verification code generated by the insurance claim adjustment device when the insurance claim is filed; the account management device associates token identification information for identifying the token, the value of the token, and a timestamp of the time when the issuance transaction was executed for each of the token issuance transactions, and records the information in a fifth table; the settlement device assesses the insurance claim based on the insurance claim information if the timestamp of the verification code is earlier than the timestamp of the time when the issuance transaction was executed; An insurance claim method characterized by:

11. A computer having a processor and a memory, A process of outputting insurance claim information regarding the digital currency insurance claim procedure input by the user; a process of requesting submission of proof of account ownership to prove that a user identified by account identification information for identifying the user's account, which is included in the insurance claim information, owns an account as an insured person; a process of outputting a request for issuing the account ownership certificate; a process of outputting a request for issuing a token of proof of account ownership, the token being generated using insurance contract identification information for identifying the insurance contract for the digital currency, the account identification information, and digital currency identification information for identifying the digital currency, which are included in the insurance claim information; and a process of adding the token for which the issuance request has been received to a first table that associates token identification information for identifying the token, the value of the token, and the owner of the token, and outputting the result of the addition as a token issuance transaction result; a process of outputting a transfer request for the token issuance transaction result, with the added token being owned by an insurance company; updating the owner of the token added to the first table to the insurance company and outputting the updated result as a token transfer transaction result; Upon receiving the token transfer transaction result, outputting a completion of issuance of the account ownership proof; a process of outputting a notification indicating completion of submission of the proof of account ownership based on completion of issuance of the proof of account ownership; a process of assessing an insurance claim based on the insurance claim information using a second table that manages insurance contract information identified by the insurance contract identification information and a third table that manages accident information regarding the digital currency identified by the currency identification information; An insurance claim program characterized by executing the above.

Images