Electronic contract server and electronic contract program

Abstract

To prove the authenticity of conclusion in addition to identification and non-alteration properties of an electronic contract document.SOLUTION: An electronic contract server 1 of the present embodiment performs electronic contract processing for concluding various contracts between a customer using a terminal device 3 and a bank (bank clerk) using a terminal device 4 of the bank through web screens of both devices 3 and 4. According to the electronic contract server 1, it not only causes contractors to perform electronic signature for only an electronic contract document, but also causes the electronic contract server 1 to perform electronic signature for an electronic contract document added with information (unique information) uniquely representing the details of a video conference photographed until the conclusion of the electronic contract document. This can increase the evidentiality of identification of the contractor and prove the authenticity of the conclusion in addition to proving non-alteration for the electronic contract document concluded through the electronic contract processing performed by the electronic contract server 1.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to an electronic contract server and an electronic contract program for executing so-called witness-type electronic contracts, which are electronic contracts in which parties enter into a contract electronically. [Background technology]

[0002] Electronic contracts are now being used, in which electronic signatures are made on electronic contracts that electronically state the contractual content between the parties. Depending on the content of the contract, there are two types of electronic contracts: party-type contracts and witness-type contracts. In a party-based electronic contract, a private key is issued to each party for their own exclusive use, and the electronic contract is digitally signed using the private key of each party. In contrast, in witness-type electronic contracts, the electronic contract is digitally signed using the private key of a business entity (electronic contract server) other than the parties involved. For example, the technology described in Patent Document 1 proposes a party-type electronic contract with a high level of identity authentication, in which a customer uses their personal identification number card (the so-called "My Number Card") to digitally sign a contract file and then sends it to the contract conclusion server together with the digital certificate used for the digital signature. Furthermore, the technology described in Patent Document 2 proposes an electronic contract system similar to a witness-type electronic contract, in which the electronic signature of a specified organization is attached to an electronic contract file when a contract is made between member companies of the organization.

[0003] In the case of a party-based electronic contract, when a third party verifies the electronic contract, the parties' approval can be objectively determined by their electronic signatures. Therefore, even if the contract is transferred to a third party, the contents of the contract can be objectively determined by inquiring about the identity verification status of the parties to the certification authority. However, in witness-type electronic contracts, although the business operator's confirmation of the parties is recorded in the electronic signature, the business operator only confirms the email address and device, and the parties to the contract are generally responsible for confirming the parties themselves. For this reason, if the contract is transferred to a third party, if the parties are absent, or if the memory or record of the contract status becomes unclear, doubts may arise about the contract agreement. In other words, witness-type electronic contracts are relatively easy to use because the electronic signature requires the private key of the business operator rather than the private key of the parties, but there is a problem in that the evidence of the identity of the contracting parties is less than that of party-type electronic contracts.

[0004] However, in contracts such as loan agreements made by banks and other financial institutions, and real estate purchase and sale agreements and real estate rental agreements made in real estate contracts, the parties to the contract do not simply confirm and agree to the contents of the contract before signing electronically. In other words, there are cases where it is necessary to explain various matters stipulated in the contract, and there are also cases where there is an obligation to explain important matters. In addition, there are also cases where the process leading to contract agreement, such as the person's consent to the contract, is an important factor. However, with conventional party-based electronic contracts and witness-based electronic contracts, only the parties or businesses to which the electronic contract applies have their electronic signatures entered into, and it is not possible to prove the authenticity of the electronic contract, such as whether or not an explanation was given about the contract or how the individual came to agree to the contract. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Japanese Patent Application Publication No. 2018-18536 [Patent Document 2] Japanese Patent Application Laid-Open No. 2013-114641 Summary of the Invention [Problem to be solved by the invention]

[0006] The first object of the present invention is to provide a witness-type electronic contract that provides high evidence of identity verification of the contracting parties. In addition to proving that an electronic contract has not been tampered with, a second objective is to make it possible to prove the authenticity of its creation. [Means for solving the problem]

[0007] (1) The invention described in claim 1 includes an electronic contract acquisition means for acquiring an electronic contract, a contract provision means for providing a contract content confirmation screen displaying the electronic contract to each terminal device operated by a plurality of parties making a witness-type electronic contract of the electronic contract, a video provision means for providing a video of a video conference held between the plurality of parties regarding the electronic contract on the contract content confirmation screen, a video conference data acquisition means for acquiring video conference data uniquely representing the content of the video conference, and a video data acquisition means for acquiring the video conference data uniquely representing the content of the video conference. and The video conference data include The electronic signature means is for signing an object of a signature by an electronic contract server, and a storage means is for storing the electronic contract document with the electronic signature. the video conference data acquisition means acquires the video conference data when one of the parties selects to proceed to a contract procedure during the video conference. The present invention provides an electronic contract server characterized by the above. (2) The invention described in claim 2 provides the electronic contract server described in claim 1, characterized in that the signature subject includes the account information of all the parties in a state that makes it possible to confirm the account information. (3) In the invention described in claim 3, the electronic contract server described in claim 2 is provided, characterized in that the electronic signature means, after the predetermined explanation has been given via the video conference, each time a request for an electronic signature is made by the electronic contract server, includes the account information of the requesting party in the signature subject and makes an electronic signature by the electronic contract server. (4) In the invention described in claim 4, the electronic contract server described in claim 2 is provided, characterized in that the electronic signature means performs an electronic signature by the electronic contract server, including the account information of all parties as the signature subject, after a predetermined explanation has been given via the video conference and all parties have requested electronic signatures by the electronic contract server. (5) In the invention described in claim 5, the electronic signature means assigns a timestamp to the signature subject after the electronic signature, and the storage means stores the electronic signature and the electronic contract after the timestamp, thereby providing an electronic contract server described in any one of claims 1 to 4. (6) The invention described in claim 6 provides an electronic contract server described in any one of claims 1 to 5, characterized in that the video of the video conference includes at least a video confirming the identity of the parties and explaining important points of the electronic contract. (7) The invention described in claim 7 provides an electronic contract server described in any one of claims 1 to 6, characterized in that it is equipped with a still image acquisition means for acquiring a still image of a specific state during the video conference. (8) In the invention described in claim 8, an electronic contract server described in any one of claims 1 to 7 is provided, characterized in that the video conference data that uniquely represents the content of the video conference video is any one of the following (i) to (f). (a) Video of the video conference (b) A portion of the video designated in the video conference (c) Still images of the video designated in the video conference (iv) Link information specifying the storage locations of the above (i) to (iii) (E) At least two of the above (A) to (D) (F) Hash values ​​of (A) to (E) above (9) In the invention described in claim 9, the electronic contract server described in claim 8 is provided, characterized in that the video of the video conference data is a video of the video conference provided within the contract content confirmation screen. (10) The invention described in claim 10 provides an electronic contract server described in claim 8, characterized in that the video of the video conference data is a video of the entire contract content confirmation screen, including the electronic contract and the video of the video conference. (11) In the invention described in claim 11, an electronic contract server according to claim 8, claim 9, or claim 10 is provided, characterized in that the still image of the video conference data is a still image of the video conference provided within the contract content confirmation screen. (12) In the invention described in claim 12, an electronic contract server according to claim 8, claim 9, or claim 10 is provided, characterized in that the still image of the video conference data is a still image of the entire video within the contract content confirmation screen, including the electronic contract and the video of the video conference. (13) The invention described in claim 13 includes an electronic contract acquisition function for acquiring an electronic contract, a contract provision function for providing a contract content confirmation screen displaying the electronic contract to each terminal device operated by multiple parties making a witness-type electronic contract of the electronic contract, a video provision function for providing a video of a video conference held between the multiple parties regarding the electronic contract on the contract content confirmation screen, a video conference data acquisition function for acquiring video conference data uniquely representing the content of the video conference, and a video conference data acquisition function for acquiring the video conference data uniquely representing the content of the video conference. and The video conference data include The electronic signature function stage for performing an electronic signature on the subject of the signature by the electronic contract server and the storage function for storing the electronic contract document with the electronic signature are realized on a computer. an electronic contract program, wherein the video conference data acquisition function acquires the video conference data when one of the parties during the video conference selects to proceed to a contract procedure; The present invention provides an electronic contract program characterized by: [Effects of the Invention]

[0008] In the present invention, an electronic contract to The video conference data Attached Since an electronic signature is issued by the electronic contract server to the subject of the signature, it is possible to provide a witness-type electronic contract that provides high evidence of the identity of the contracting parties, can prove non-tampering, and can also prove the authenticity of the contract. [Brief explanation of the drawings]

[0009] [Figure 1] FIG. 1 is an explanatory diagram showing the configuration of an electronic contract system including an electronic contract server. [Figure 2]FIG. 2 is a diagram illustrating the configuration of an electronic contract server. [Figure 3] 1 is a flowchart showing the flow of electronic contract processing by the electronic contract system. [Figure 4] FIG. 10 is an explanatory diagram showing a login screen in electronic contract processing. [Figure 5] FIG. 10 is an explanatory diagram of an electronic contract project list screen displayed by a bank employee. [Figure 6] FIG. 10 is an explanatory diagram of a form completion input screen operated by a bank employee. [Figure 7] FIG. 10 is an explanatory diagram of the confirmation and approval screen for an electronic contract by a bank executive. [Figure 8] 10A to 10C are explanatory diagrams of the various screens when a bank employee makes a video conference reservation. [Figure 9] FIG. 10 is an explanatory diagram of a contract viewing guide notified to a customer's terminal device. [Figure 10] FIG. 10 is an explanatory diagram of a contract procedure explanation screen for a customer. [Figure 11] FIG. 10 is an explanatory diagram of a non-face-to-face contract content confirmation screen displayed on a customer's terminal device. [Figure 12] FIG. 10 is an explanatory diagram of a non-face-to-face electronic contract using the contract content confirmation screen on the bank employee's side. [Figure 13] FIG. 10 is an explanatory diagram of a contract procedure screen displayed on a customer's terminal device. [Figure 14] This is a diagram conceptually illustrating the structure of an electronic contract with an electronic signature in a witness-type electronic contract. [Figure 15] FIG. 10 is a diagram conceptually illustrating another structure of an electronic contract with an electronic signature in a witness-type electronic contract. [Figure 16] FIG. 1 is a diagram conceptually illustrating the structure of a digitally signed electronic contract in a party-type format. [Figure 17] FIG. 10 is an explanatory diagram of a contract completion screen displayed on a customer's terminal device. [Figure 18] FIG. 10 is an explanatory diagram showing a seal approval screen provided to a terminal device of a supervisor. DETAILED DESCRIPTION OF THE INVENTION

[0010] A preferred embodiment of the electronic contract server 1 of the present invention will be described in detail below with reference to FIGS. (1) Overview of the embodiment In the electronic contract server 1 of this embodiment, the parties confirm their identities by viewing each other's images via video conference, and the electronic contract server issues an electronic signature to the signature object, which includes the electronic contract (original) and video conference data that uniquely represents the contents of the video conference.This provides high evidentiary proof of the identity of the contracting parties, and makes it possible to prove the authenticity of the contract in addition to proving non-tampering. The electronic contract server 1 is capable of conducting witness-type electronic contracts and party-type electronic contracts using similar processing, but in this embodiment, the processing for witness-type electronic contracts will be mainly explained, and party-type electronic contracts will be explained each time they differ from witness-type electronic contracts. Therefore, in the following embodiments, "witness-type electronic contract (processing)" will be abbreviated to "electronic contract (processing)."

[0011] The electronic contract server 1 of this embodiment performs electronic contract processing to conclude various contracts between a customer using a terminal device 3 and a bank (bank employee) using a terminal device 4 of the bank or the like through the web screens of both devices 3 and 4. That is, the electronic contract server 1 performs the following electronic contract processing (a) to (f) within the electronic contract system shown in FIG.

[0012] (a) The bank uses a web screen on the terminal device 4 to create an electronic contract PDF (an electronic contract saved in PDF format, hereinafter simply referred to as an electronic contract) and uploads the created electronic contract, contract type information indicating whether it is a witness-type electronic contract or a party-type electronic contract, contact information such as the customer's mobile phone number, the video conference date set in the scheduler, and login information for the electronic contract server 1 to the electronic contract server 1. (b) The electronic contract server 1 saves the uploaded contract-related information in storage and sends the customer a request to view the electronic contract via SMS (short message service) using their phone number. This request includes the URL for viewing the electronic contract, the video conference date, and login information. (c) The customer logs in to the electronic contract server 1 using the specified URL and login information, and the corresponding bank employee also logs in to the electronic contract server 1 using their own login information. As a result, the electronic contract server 1 provides the customer's terminal device 3 and the bank employee's terminal device 4 with a contract content confirmation screen (Figures 11 and 12) that is shared by both. This contract content confirmation screen displays the electronic contract that is the subject of the contract, and also displays a video of the customer side in the video conference provided by the video conference server 5 in the customer image field 106 and a video of the bank employee side in the bank employee image field 107. Then, through the video conference, the parties confirm each other's video and verify their identities by showing a screen of their driver's license or registration certificate, etc., and the bank employee explains the contents of the contract and important matters to the customer. The video of the video conference (including audio, the same applies below) and screenshots of the identity verification during the explanation and the explanation of important matters of the contract are saved as the situation related to the contract. (d) After the contract contents are confirmed and explained via video conference and the contents of the electronic contract are understood, when the customer and bank employee each request the electronic signature procedure, the electronic contract server 1 attaches the video conference data to the electronic contract and performs an electronic signature using the private key of the electronic contract server. In the case of a party-type electronic contract, after the customer has confirmed and explained the contents of the contract and understands the contents of the electronic contract, the customer carries out the contract procedure (electronic signature).The electronic contract server 1 then attaches the video conference data to the electronic contract and executes the customer's electronic signature and the bank's electronic signature. (e) The signed electronic contract is then stamped by the bank. (f) The electronic contract server 1 stamps a timestamp on the signed electronic contract and sends a URL for a copy of the electronic contract to the customer via SMS.

[0013] According to the electronic contract server 1 of this embodiment, rather than the contractor electronically signing only the electronic contract, the electronic contract server 1 electronically signs (electronic signature using the private key of the electronic contract server 1; the same applies below) the electronic contract, which includes information (unique information) that uniquely represents the content of the video conference filmed during the period leading up to the conclusion of the electronic contract, such as the parties verifying each other's identities and an explanation of the contract contents. This increases the evidentiary value of identity verification for electronic contracts concluded through electronic contract processing by the electronic contract server 1, and makes it possible to prove non-tampering and the authenticity of the electronic contract by using an electronic signature by the electronic contract server 1. In the case of a party-type electronic contract, the identity of the contracting parties can also be verified by electronically signing the contract using the parties' private keys.

[0014] In this embodiment, the video conference data (unique information) that uniquely represents the content of the video conference is a video of the video conference (including audio, hereinafter referred to as video conference video) and a screenshot image (still image) of the video specified in the video conference.

[0015] (2) Details of the embodiment FIG. 1 is a diagram showing the system configuration of an electronic contract system including an electronic contract server 1 according to this embodiment. FIG. 1 is an explanatory diagram showing the configuration of an electronic contract system including an electronic contract server 1. As shown in Figure 1, an electronic contract system is formed that includes an electronic contract server 1, a terminal device 3 of the customer who is a party to the contract, a terminal device 4 of the bank (including the bank employee in charge of the contract and the executive responsible for the contract), a video conferencing server 5, a remote signing key server 7, and a timestamp server 8. Each part of the electronic contract system is capable of communicating encrypted using SSL or TLS via a communication network such as the Internet. Although FIG. 1 shows one terminal device 3, 4, in reality, there are multiple devices corresponding to the number of contracting parties who have accounts for electronic contracts with the electronic contract server 1. In addition, in the electronic contract processing by the electronic contract server 1 of this embodiment, one of the parties to the electronic contract is a bank employee and the bank whose executive handles the procedures, and the other is a customer, and we will explain the case where a loan agreement is concluded between the two parties by electronic contract as an example.

[0016] The electronic contract server 1 includes programs such as an electronic contract program (PG) 140 and a scheduler 141, and databases (DB) such as an electronic contract DB 142 and user information 144. The electronic contract server 1 performs electronic contract processing of the electronic contract program 140 to affix an electronic signature and timestamp to the electronic contract concluded between the customer and the bank in a state that enables identity verification, non-tampering verification, existence verification, and authenticity verification of the establishment of the electronic contract. This electronic signature and / or timestamp functions as a means of authenticity verification. The electronic signature is made using the private key of the electronic contract server 1 in the case of a witness-type electronic contract, and using the private keys of the parties in the case of a party-type electronic contract.

[0017] The terminal device 3 is a terminal device used by the customer side of the contracting parties. The terminal device 3 is a computer that can be connected to a communication network wirelessly or via a wire, and is configured, for example, as a personal computer, a smartphone, a mobile phone, a game device, or the like. The terminal device 3 is equipped with a browser, a display device that displays the contract content confirmation screen provided by the electronic contract server 1, and is configured to be able to use short message service (SMS) and / or email using a telephone number. The terminal device 3 also has a camera for taking videos, a microphone, and a speaker to provide an environment for using video conferencing provided by the video conferencing server 5. It also has a touch panel and keyboard for performing various input operations on the contract content confirmation screen. In this embodiment, a smartphone is used as the terminal device 3, and the mobile phone number is "080-1122-3344".

[0018] The terminal device 4 is a terminal device owned by various businesses and individuals that use the electronic contract processing of the electronic contract server 1 of this embodiment, such as financial institutions, insurance companies, car dealerships, real estate businesses, content sales companies, accounting firms, and government and local government agencies. The terminal device 4 is a computer that can be connected to a communication network wirelessly or via a wire, and is configured, for example, by a personal computer. The terminal device 4 is equipped with a browser, a display device that displays the contract content confirmation screen provided by the electronic contract server 1, and is configured to be able to use e-mail. The terminal device 4 also has a camera for taking video, a microphone, and a speaker to provide an environment in which video conferencing provided by the video conferencing server 5 can be used. It also has a touch panel and keyboard for performing various input operations on the contract content confirmation screen.

[0019] The user of the terminal device 4 is registered in advance with the electronic contract server 1, and for example, the user information of the person in charge or approver at the business entity (corporation) that concludes the electronic contract with the customer is registered. The user information registered with the electronic contract server 1 includes account information (account and password) and company information for each user of the terminal device 4 to use the electronic contract processing of the electronic contract server 1. In the terminal device 4 of this embodiment, the pre-registered users will be described as bank employees and executives (those who have the authority to review and approve the electronic contract prepared by the bank employee) on the bank side among the contracting parties.

[0020] Although Figure 1 shows only one terminal device 4, there are multiple terminal devices 4 for each business entity, such as a financial institution or insurance company, that is registered as a user on the electronic contract server 1, and different terminal devices 4 are used by contract officers, such as bank employees, who are responsible for creating electronic contracts, and supervisors or executives, etc., who are responsible for approving and verifying electronic contracts. However, it is also possible to prepare one terminal device 4 dedicated to electronic contracts that connects to the electronic contract server 1 and that can be used in common within the business entity.

[0021] The video conference server 5 is a server configured as a computer system that provides video conferences using audio and video to the electronic contract server 1 and the terminal devices 3 and 4 via a communication network such as the Internet. The video conference server 5 is provided with a storage 6, in which video data received from each user (terminal device 3, terminal device 4, etc.) during the video conference is stored according to instructions from each terminal device. The video conference server 5 provides video of the video conference stored in the storage 6 based on a request from the electronic contract server 1.

[0022] Based on a request from the electronic contract server 1, which is the electronic contract operator, the remote signing key server 7 has already completed the following tasks: generating the public key and private key for the electronic contract server 1 to issue an electronic signature; obtaining and storing an electronic certificate from a certification authority (not shown); and sending the generated PIN code to the electronic contract server 1. When a party-type electronic contract is processed on the electronic contract server 1, the remote signature key server 7 generates public and private keys for the contracting parties, obtains and stores an electronic certificate from a certification authority (not shown), and transmits the generated PIN code to the electronic contract server 1, based on a request from the electronic contract server 1. However, for business entities that may be parties to a multiple-party electronic contract, it is possible to complete the generation of public and private keys, the acquisition and storage of an electronic certificate, and the transmission of PIN codes in advance. Based on the electronic signature request from the electronic contract server 1, the remote signing key server 7 electronically signs the electronic contract (hash value of the electronic contract and video conference data) using the private key corresponding to the PIN code, and returns the signature value to the electronic contract server 1. Here, the electronic signature performed by the remote signing key server 7 uses the private key of the electronic contract server 1 in the case of witness-type electronic contracts, and the private key of the party (or the party and the electronic contract server 1) in the case of party-type electronic contracts, depending on the PIN code received from the electronic contract server 1.

[0023] Based on a request from the electronic contract server 1, the timestamp server 8 assigns a timestamp to various data such as an electronically signed electronic contract.

[0024] FIG. 2 shows the hardware configuration of the electronic contract server 1. As shown in FIG. 2, the electronic contract server 1 includes a CPU 11, a ROM 12, a RAM 13, a storage device 14, a communication control unit 15, and other devices connected via a bus line. The CPU 11 is a central processing unit that operates in accordance with the electronic contract program 140 stored in the storage device 14, and performs communication processing between external devices such as the terminal devices 3 and 4, the video conferencing server 5, the remote signature key server 7, and the timestamp server 8, as well as internal processing related to electronic contract processing.

[0025] The ROM 12 is a read-only memory that stores basic programs and parameters for the CPU 11 to operate. The RAM 13 is a readable and writable memory, and serves as a working memory when the CPU 11 performs electronic contract processing in this embodiment. The communication control unit 15 performs communication processing with external devices such as the terminal devices 3 and 4, the video conference server 5, the remote signature key server 7, and the time stamp server 8.

[0026] The storage device 14 is configured using one or more large-capacity storage media such as a hard disk, and stores various programs such as an electronic contract program 140 and a scheduler 141 that enable the CPU 11 to perform the functions of this embodiment, an electronic contract DB 142, contract information 143, user information 144, an electronic certificate 145, an operation log 146, and other information 147.

[0027] The electronic contract program 140 is executed by the CPU 11 and is a program for performing electronic contract processing to conclude an electronic contract between the parties. In this electronic contract processing, various processes are carried out to execute witness-type electronic contracts and party-type electronic contracts between the parties (e.g., between the customer and the bank), and the following are typical processes: (a) An automatic contract creation process that provides the terminal device 4 with a completed form input screen (a screen for creating an electronic contract) that specifies input fields corresponding to various electronic contracts such as loan agreements and real estate purchase and sale agreements to be created, and automatically assists in creating an electronic contract based on the input data for the input fields from the terminal device 4. (b) The process of scheduling a video conference for the created electronic contract. (c) A process of providing a contract content confirmation screen to terminal device 3 and terminal device 4, and displaying the electronic contract together with a video of the video conference provided by the video conference server 5 based on the settings of the scheduler 141. The contract content confirmation screens provided to terminal device 3 and terminal device 4 are partially different for witness-type electronic contracts and party-type electronic contracts, but are generally the same overall. (d) Based on the selection of the terminal device 4, a process of acquiring and saving screenshots of the electronic contract and images displayed on the contract content confirmation screen at each point during the video conference, such as when the customer is verified (eKYC), when the bank employee explains the contents of the electronic contract, and when important matters are explained. (e) Identity verification process to verify the customer using the electronic contract, customer image, and customer-specific documents such as a driver's license, which are displayed on the contract content confirmation screen. This identity verification process can be more easily performed by using the screenshot image described in (d) above. (f) When the customer selects the “Contract Procedure” button on the contract content confirmation screen displayed on the terminal device 3, the video conference data (unique information) that uniquely represents the content of the video conference is added to the electronic contract, and an electronic signature is made using the private key of the electronic contract server 1 in the case of a witness-type electronic contract, or the private key of the customer in the case of a party-type electronic contract.

[0028] The scheduler 141 manages the holding of video conferences using the video conference server 5 . For example, a video conference calendar screen is displayed on the terminal devices 3 and 4 that are logged in to the electronic contract server 1, and video conferences to be held at designated dates and times are managed.

[0029] The electronic contract DB 142 manages electronic contracts created by the automatic contract creation process of the electronic contract server 1 in accordance with the content entered on the terminal device 4, original electronic contracts created by the bank on its own device and uploaded from the terminal device 4, and concluded electronic contracts that have been created by adding video conference data (unique information) to the original electronic contract and attaching an electronic signature and timestamp, all linked together by the contract number assigned to each electronic contract. This contract number functions as identification information for the electronic contract.

[0030] The electronic contract information 143 stores contract information for each electronic contract stored in the electronic contract DB 142. The contract number and the contract type (information indicating whether it is a witness-type electronic contract or a party-type electronic contract) are stored for each electronic contract in the contract information 143. In addition, in the case of this embodiment in which one of the contracting parties is a bank, the branch number, branch name, customer information file (CFI) number, handling number, customer name (kanji name), approval amount (contract amount), conditions registration date, status (waiting for creation, waiting for approval, approved, signed, stamped, etc.), contract creation (serial number), certificate issuance (issue date and time), timestamp (issue date and time), contract delivery (notification date and time), operation history, etc. are stored. In addition, input data when an electronic contract is automatically created through input from the terminal device 4 is also saved in the contract information 143.

[0031] The user information 144 stores information for identifying a customer using the terminal device 3, a bank employee using the terminal device 4, etc., for each user. For example, in the case of a bank employee, executive, or other party to an electronic contract, the account and password for logging in to the electronic contract server 1, company ID, company name, user name, email address, etc. are stored. In addition, a PIN code (corresponding to a private key) used by the bank employee (or bank) to digitally sign an electronic contract is also stored. In the case of a customer, who is another party to the electronic contract, a customer information file (CFI), an account and password for logging in to the electronic contract server 1, the customer's name, telephone number (mobile phone number) and / or email address, etc. are stored.

[0032] In addition, if the contract form is a party-type electronic contract, a PIN code (corresponding to a private key) that the customer uses to electronically sign the electronic contract, and an account and password that are created corresponding to the PIN code and notified to the customer are stored. For example, the account and password corresponding to the customer's PIN code are created by a conversion process according to a predetermined rule, or by dividing the PIN code in two and using the first half as the account and the second half as the password.

[0033] The electronic certificate 145 is issued by a certification authority (not shown) and is obtained by the electronic contract server 1 from the remote signature key server 7, and links the signature verification key (public key) to the owner of the corresponding private key (the electronic contract server 1 in the case of a witness-type electronic contract, or the user in the case of a party-type electronic contract; in this embodiment, a customer, bank employee, etc.). The digital certificate 145 includes a public key (corresponding to a private key for digitally signing an electronic contract with video conference data), the issuer (certification authority) of the private key, etc., and the digital signature of the certification authority for these.

[0034] The operation log 146 stores a log of a series of operations processed in the electronic contract processing of the electronic contract server 1. The operation log stored in the RAM 13 is added and stored in the operation log 146 at predetermined intervals. As other information 147, company information corresponding to a company ID, billing information, business partner information corresponding to a business partner ID, billing information, etc. are stored.

[0035] Next, the details of the electronic contract processing by the electronic contract server 1 will be explained. In the following electronic contract processing, an electronic contract for a witnessed electronic contract for a money loan contract will be explained as an example, in which the customer using terminal device 3 is the borrower and the bank (the bank employee in charge of the contract) using terminal device 4 is the lender. It is also assumed that user registration on the bank side using terminal device 4 has already been completed.

[0036] 3 is a flowchart showing the flow of electronic contract processing by the electronic contract system. This electronic contract processing is carried out by the CPU 11 of the electronic contract server 1 executing the electronic contract program 140. The electronic contract processing will be explained below in accordance with the flowchart of FIG. 3 and with reference to the display screens of the customer terminal device 3 or the bank terminal device 4 shown in FIG. 4 and subsequent figures.

[0037] In step 2, an electronic contract to conclude a loan agreement with the customer is created in PDF format. That is, when a bank employee first requests a login to the electronic contract server 1 from the terminal device 4, the CPU 11 of the electronic contract server 1 (hereinafter simply described as the operation of the electronic contract server 1) provides the terminal device 4 with a login screen 40. FIG. 4 is an explanatory diagram showing a login screen 40 for electronic contract processing, which is provided by the electronic contract server 1. The bank employee enters the account and password set when registering as a user into the account field 41 and password field 42 on the login screen 40 displayed on the terminal device 4, and selects the login button 43 to enter the information into the electronic contract processing of the electronic contract server 1.

[0038] When an account and password are entered on the login screen 40 of the terminal device 4, the electronic contract server 1 stores the entered account and password in RAM 13, checks the user information to confirm that the user is a registered user (bank employee), and provides the electronic contract case list screen 50 to the terminal device 4. FIG. 5 is an explanatory diagram of an electronic contract item list screen 50 provided by the electronic contract server 1 to the terminal device 4. As shown in Figure 5, the top of the electronic contract case list screen 50 has a search item field 51 for store number, CIF (customer information file) number, kanji name (customer name), status, etc., and the bottom of the screen displays a case list field 52 corresponding to the input contents of the search item field 51. Figure 5 shows the case where a bank employee selects "Waiting for contract creation" from the pull-down list of items (new creation, waiting for contract creation, waiting for approval, approved, signed, stamped, etc.) in the search item "Status" in search item field 51 and then selects the "Search" button. In addition, FIG. 5 shows a list of cases 52 displayed when a search is performed using the search item for the status "awaiting contract creation."

[0039] The electronic contract server 1 uses the selected search item "Awaiting contract creation" and the bank employee's account and password stored in RAM 13 as search keys to provide a list of electronic contracts awaiting creation corresponding to the bank employee from the electronic contract DB 142 to the case list column 52 on the electronic contract case list screen 50 on the terminal device 4. When a bank employee selects a case for which an electronic contract is to be created from the cases listed in the case list column 52 on the electronic contract case list screen 50, the electronic contract server 1 provides the terminal device 4 with a completed form input screen 60 corresponding to the selected case.

[0040] FIG. 6 is an explanatory diagram of a form completion input screen 60 provided by the electronic contract server 1 and displayed on the terminal device 4. This form completion input screen 60 has input fields predefined according to the type of electronic contract, such as a loan agreement or real estate sales contract, and bank employees can create an electronic contract by entering the necessary information into each input field. The completed form input screen 60 has a case information display field 61 at the top, a contract item input field 62 on the right, a preview display field 63 on the left, and a video conferencing check box 64, a processing button 65, and contract type selection buttons 66 and 67 at the bottom. The case information display field 61 displays case information for the case selected from the case list field 52 (Figure 5), and the contract item input field 62 displays input fields that are pre-defined depending on the type of electronic contract, such as a loan agreement or a real estate sales contract. When the "Reflect image display" button among the processing buttons 65 is selected, the preview display of the electronic contract according to the input contents in the contract item input field 62 is updated in the preview display field 63, and when the "Create contract" button is selected, the contents are confirmed and the electronic contract is created.

[0041] The video conference checkbox 64 is a checkbox for adding an option to require identity verification and explanation of the contract via video conference for the created electronic contract, and is a required check item for electronic contract processing in this embodiment. The contract type selection buttons 66, 67 are buttons for selecting the contract type for each authentication level setting case and each contract type, and one of them can be selected, with the selected side displayed as a black circle and the unselected side displayed as a white circle. The contract type selection button 66 is a button for selecting a party-type electronic contract for which electronic certificates of the parties are issued, and the contract type selection button 67 is a button for selecting a witness-type electronic contract that does not use electronic certificates of the parties. Note that when the witness-type contract type selection button 67 is selected, the electronic certificate of the electronic contract server 1 is used.

[0042] In this embodiment, an electronic contract for a loan agreement is used as an example, and therefore, in the completed form input screen 60 shown in FIG. 6, the input fields for the contract details 62 are specified, such as the debtor, loan amount, interest rate, repayment start date, repayment completion date, monthly repayment amount, and guarantor. The bank employee then enters the debtor "Ginko Taro," the loan amount "25,000,000," the interest rate "1.0," the monthly repayment amount "50,000," and the guarantor "Nakajima Katsuji," and an electronic contract corresponding to the entered information is previewed in the preview display field 63.

[0043] In Figure 6, the repayment start date and repayment completion date are not entered, but the input items in the contract item input field 62 are not required, and there may be cases where there are no input items (they are already completed). Also, it is possible to set initial values ​​for the input values, and the initial values ​​are displayed in the preview display field 63. In this case, the bank employee can also press the "Create contract" button without entering any information.

[0044] In FIG. 6, when the bank employee selects the "Create contract" button of the processing buttons 65, the content displayed in the preview display field 63 is confirmed and a corresponding electronic contract is created. The electronic contract created by the above process is stored as the original in the electronic contract DB 142 of the electronic contract server 1 (step 3). As a result, the electronic contract server 1 changes the status of the electronic contract in the contract information 143 (see FIG. 2) to waiting for approval. Although the case where an electronic contract is automatically created by the automatic contract creation process in electronic contract processing has been described, it is also possible for contracting parties such as banks and real estate companies to upload electronic contracts they have created in-house to the electronic contract server 1. In this case, the uploaded electronic contract is stored in the electronic contract DB 142 as the original.

[0045] In the next step 4 (Figure 3), approval processing is performed for the created electronic contract. That is, an executive of the bank performs approval processing for the electronic contract created by a bank employee and stored in the electronic contract server 1. A bank executive uses a terminal device 4 to log in to the login screen 40 (see Figure 4) provided by the electronic contract server 1, and performs a search for the status "waiting for approval" in the search item field 51 on the electronic contract case list screen 50 (see Figure 5), whereby electronic contracts created by the bank and awaiting approval are displayed in a list in the case list field 52. When the manager selects the relevant case from the case list field 52 on the electronic contract case list screen 50 displayed on the terminal device 4, a confirmation and approval screen provided by the electronic contract server 1 is displayed.

[0046] FIG. 7 shows a confirmation and approval screen 75 for the electronic contract, which is provided by the electronic contract server 1 and displayed on the terminal device 4 of the bank executive. As shown in Figure 7, a case information display field 76 for the confirmation and approval screen 75 is displayed at the top of the confirmation and approval screen 75, similar to the case information display field 61 described in Figure 6, and the electronic contract for the selected case is displayed in the contract confirmation field 77 below that. Although not shown in Figure 7, the case information display field 76 may be configured to display the contract type of the electronic contract, i.e., "Contract type: party-type electronic contract" or "Contract type: witness-type electronic contract" depending on which of the contract type selection buttons 67, 57 is selected on the completed form input screen 60.

[0047] The executive checks the electronic contract prepared by the bank employee in the contract confirmation field 77, and if there are no problems, selects the "Approve" button at the bottom of the screen. On the other hand, if the electronic contract needs to be amended, by selecting the "Amend" button, the electronic contract server 1 will provide the executive's completed form input screen 60 (see Figure 6), which allows the executive to make appropriate amendments.

[0048] When the manager selects the "Approve" button on the confirmation / approval screen 75, the electronic contract server 1 updates the status of the electronic contract in the contract information 143 (see FIG. 2) from "waiting for approval" to "approved."

[0049] Next, the banker prepares the non-face-to-face contract (Step 5). This non-face-to-face contract preparation involves scheduling and saving video conferences, obtaining and saving customer login accounts for electronic contracts, and sending SMS notifications. That is, the bank employee logs in to the electronic contract server 1 as described in FIGS. 4 and 5 and searches for approved electronic contracts. As a result, the electronic contract server 1 provides the bank employee's terminal device 4 with an electronic contract item list screen 80.

[0050] FIG. 8 is an explanatory diagram of each screen provided by the electronic contract server 1 when a bank employee makes a video conference reservation. FIG. 8(a) shows an electronic contract item list screen 80 provided by the electronic contract server 1. In the case list column 82 of the electronic contract case list screen 80 searched for using the search item "contract approved," a conference reservation button 83 is displayed behind each list, compared to the case list column 52 searched for using "awaiting contract creation" (see Figure 5) or the case list column searched for using "awaiting contract approval." When the desired conference reservation button 83 is selected, a video conference schedule calendar 84 is displayed in a separate frame as shown in Figure 8(b), and the bank employee inputs the date and time of the video conference with the customer. Based on the input date and time, the scheduler 141 of the electronic contract server 1 sets up a reservation for the video conference for the electronic contract.

[0051] Furthermore, the bank employee selects the relevant case from the case list field 82, and is presented with a contract notification screen 85 shown in FIG. 8(c). On this contract notification screen 85, the name of the party to the contract, "Ginko Taro," is displayed in the contract holder field 86, and input fields include a check box 87, a mobile phone number field 88, and a contract notification button 89. The bank employee confirms that the name "Ginko Taro" displayed in the contracting party field 86 is the name of the customer with whom the electronic contract is to be concluded, checks the check box 87 (by clicking with the mouse), enters the customer's mobile phone number "080 1122 3344" in the mobile phone number field 88, and then selects the contract notification button 89. After selecting the contract notification button 89, a confirmation screen will be displayed (not shown) for re-entering the mobile phone number, and if the re-entered mobile phone number matches the previous entry, it will be saved in the user information 144 of the electronic contract server 1. In addition, "Contract type: Party-type electronic contract" or "Contract type: Witness-type electronic contract" may be displayed in either or both of the case list field 82 in Figure 8(a) or the contract notification screen 85 in Figure 8(c) depending on the contract type of the electronic contract in question. The contract type of the electronic contract may also be displayed in the same way on each of the screens in Figures 9 to 13, 17, and 18 below.

[0052] The electronic contract server 1 then sends an SMS to the entered mobile phone number to guide the user to view the contract. FIG. 9 is an explanatory diagram of the contract viewing guide sent from the electronic contract server 1 to the customer's terminal device 3. As shown in Figure 9, the contract viewing guide screen 91 displays the login information (account and password) for logging in to the electronic contract server 1, the URL for viewing the electronic contract, and the date of the video conference set by the bank employee.

[0053] Next, the customer and the bank employee log in to the electronic contract server 1 (step 6). The bank employee logs in to the electronic contract server 1 from the login screen (see Figure 4) according to the scheduled video conference. Meanwhile, the customer selects the URL displayed on the contract viewing guide screen 91 on the terminal device 3, and enters login information into the login screen (see Figure 4) provided by the electronic contract server 1 to log in to the electronic contract server 1. By logging in to the electronic contract server 1, a contract procedure explanation screen 92 is displayed on the terminal device 3.

[0054] FIG. 10 shows a contract procedure explanation screen 92 provided by the electronic contract server 1 and displayed on the terminal device 3. 10, the contract procedure explanation screen 92 has a contract flow explanation 93 (issuance and notification of authentication code, explanation of contract contents, explanation of electronic signature) on the left side. Also, on the right side of the contract procedure explanation screen 92, the customer's name "Ginko Taro" is displayed in a contracting party field 95, and input fields include a check box 96, a mobile phone number field 97, an authentication code issue button 98, and a contract procedure transition button 99. The customer confirms that his / her name "Ginko Taro" is displayed in the contract holder field 95, checks the check box 96, enters the mobile phone number of the terminal device 3 "080 1122 3344" (the phone number of the SMS that received the URL from the electronic contract server 1) in the mobile phone number field 97, and then selects the authentication code issue button 98.

[0055] If the contract is a contingent electronic contract, the contract procedure explanation screen 92 displays an "account issue button" instead of the authentication code issue button 98. Additionally, the contract flow explanation 93 on the left side of the screen now says "Account issuance notification" instead of "Authentication code issuance / notification," and the explanation reads, "We will issue an account for your electronic signature. The account will be notified after identity verification is completed via video conference." The instructions for electronic signature also state, "You will need to enter your account information on your device."

[0056] The provision of the contract procedure explanation screen 92 and the procedures using the contract procedure explanation screen 92 are also provided to parties other than the customer in the same manner, and the procedures are carried out in the same manner.

[0057] Next, the electronic contract server 1 issues an authentication code for the customer's electronic signature (step 7). In other words, if the authentication code issue button 98 is selected and the entered mobile phone number matches the mobile phone number registered in the customer's user information, the electronic contract server 1 will assume that provisional identity verification has been completed and will generate an account and authentication code (one-time password) to be used (entered) when the customer requests an electronic signature from the electronic contract server 1. The created account and authentication code will be sent to the customer's terminal device 3 via SMS after official identity verification via video conference (described later) has been completed. The electronic contract server 1 also stores the created account and authentication code (one-time password) in the user information 144 for the customer.

[0058] If the contract type is a party-based electronic contract, the processing of step 7 is as follows. When the customer selects the account issue button and the customer's identity is temporarily verified, the electronic contract server 1 issues an account for the customer's electronic signature and generates a remote signature key. That is, the electronic contract server 1 requests the remote signature key server 7 to obtain an electronic certificate and PIN code for the electronic signature for the customer, and creates an account and password for the electronic signature from the obtained PIN code. The created account and password are notified to the customer's terminal device 3 by SMS after official identity verification via video conference (described later) is completed. The electronic contract server 1 also stores the acquired electronic certificate, PIN code, and the created account and password in the user information 144 for the customer. The remote signature key server 7 stores the private key corresponding to the public key included in the electronic contract as a remote signature key, linked to the PIN code.

[0059] Next, the electronic contract server 1 provides contract content confirmation screens 100a, 100b to the customer's terminal device 3 and the bank employee's terminal device 4 (step 8). That is, when the customer selects the contract procedure transition button 99 on the contract procedure explanation screen 92 of FIG. 10, the electronic contract server 1 provides the terminal device 3 with a contract content confirmation screen 100a. The electronic contract server 1 also provides the contract content confirmation screen 100b to the terminal device 4 of the bank employee who logs in to the electronic contract server 1 in accordance with the set video conference schedule.

[0060] Figure 11 shows a contract content confirmation screen 100a for electronic contracts conducted without face-to-face contact, which is provided from the electronic contract server 1 to the customer's terminal device 3, and Figure 12 shows a contract content confirmation screen 100b for electronic contracts conducted without face-to-face contact, which is provided from the electronic contract server 1 to the bank employee's terminal device 4. Both of these contract content confirmation screens 100a and 100b display an electronic contract section 101, a video conference start button 102, a video conference change button 103, a contract procedure button 105, a customer image section 106, and a bank employee image section 107. The contract details confirmation screen 100b on the bank employee's side further displays a screenshot capture button 104.

[0061] The electronic contract field 101 displays the electronic contract, such as a loan agreement, that is the subject of the electronic contract. The electronic contract displayed in the electronic contract field 101 is displayed in the same state as the contract content confirmation screen 100a on the customer side and the contract content confirmation screen 100b on the bank employee side, and for example, when the display range of the electronic contract is scrolled by operating one of the terminal devices 3 and 4, the electronic contract on the other side is also scrolled in the same way. Enlarged and reduced displays of the electronic contract are also displayed in the same way. Furthermore, when a bank employee explains a specific part of the contract contents, if the relevant part of the electronic contract is highlighted on the terminal device 4, the relevant part of the electronic contract on the customer's side will also be highlighted.

[0062] The video conference start button 102 is a button for starting a video conference between the terminal device 3 and the terminal device 4 via the video conference server 5, and the video conference change button 103 is a button for changing the schedule of the video conference. The contract procedure button 105 is a button for completing the conclusion of the contract after the explanation of the electronic contract via video conference has been completed. The customer image field 106 displays images (video) captured by the customer's terminal device 3 during the video conference. The bank employee image field 107 displays images (video) captured by the bank employee's terminal device 4 during the video conference. The display position and size of the customer image field 106 and the bank employee image field 107 can be changed independently for each terminal device 3, 4, but the default setting is such that the bank employee image field 107 is large on the customer's contract content confirmation screen 100a and the customer image field 106 is large on the bank employee's contract content confirmation screen 100b, as shown in Figures 11 and 12.

[0063] The screenshot capture button 104 is a button for capturing and saving a still image of the customer image field 106 as a screenshot image in response to identity verification based on the images displayed on both sides (customer and bank employee) in the customer image field 106, explanation of important matters regarding the electronic contract field 101, etc. In addition, the electronic contract server 1 may save a still image of the entire contract content confirmation screen 100b displayed on the bank employee's terminal device 4, rather than acquiring a still image of the customer image field 106 as a screenshot image using the screenshot acquisition button 104.

[0064] When the screenshot acquisition button 104 is selected, a pull-down screen is displayed that specifies shot item names such as license confirmation (for identity verification), disclaimer confirmation, explanation of specific clauses, contract agreement, etc. When a shot item name is selected from this pull-down screen, the electronic contract server 1 acquires a still image from the customer image field 106, and the shot item name such as license confirmation is saved as the title of the still image. If the desired shot item name is not available on the pull-down screen, the bank employee can select "Other" and input the item name from the keyboard or the like. In addition, by providing the screenshot capture button 104 not only on the bank side but also on the customer side's contract content confirmation screen 100a, that is, on the contract content confirmation screens 100a, 100b, ... of all parties, it becomes possible for the customer side to preserve evidence as well, thereby protecting the customer.

[0065] When either the customer or the bank employee selects the video conference start button 102 on the contract content confirmation screen 100a, 100b, a video conference provided by the video conference server 5 is started between the terminal device 3 and the terminal device 4, and the video images captured by the terminal devices 3, 4 are displayed in the customer image field 106 and the bank employee image field 107, and the video conference video is recorded (step 9). The videoconference video starts at the same time as the videoconference begins, and is saved in the storage 6 of the videoconference server 5. The videoconference video saves the entire contract content confirmation screen 100a displayed on the customer's terminal device 3, including the electronic contract displayed in the electronic contract field 101 and the contents displayed in the customer image field 106 and bank employee image field 107, along with audio. Therefore, when the electronic contract displayed in the electronic contract field 101 is scrolled by an operation by the customer or bank employee, the movement is also saved as part of the videoconference video. In addition, when signing electronically as described below, the electronic contract server 1 requests and obtains the stored video conference video from the video conference server 5. However, since the electronic contract server 1 provides the contract content confirmation screen 100a to the customer's terminal device 3, it is also possible to store the video conference video while the video conference is being held in the storage device of the electronic contract server 1.

[0066] When the video conference begins, the customer and the bank employee mutually explain the electronic contract and ask and answer questions (step 10). Then, while the bank employee is explaining to the customer, he or she presses the screenshot capture button 104 to capture a still image in the customer image field 106 (step 11). That is, at the beginning of the video conference, the bank employee asks the customer to hold up their identification document (driver's license, etc.) near their chest, and visually verifies that the customer's appearance displayed in the customer image field 106 and the name displayed on the electronic contract match the photo and name on the license presented, and also asks the customer to rotate the identification document to visually check its thickness. In addition, the bank employee can present personal identification documents such as his / her driver's license or bank registration on the screen, allowing the customer to visually confirm that the identity of the bank employee matches the contents of the contract, and also rotate the identification document to visually check its thickness. Then, the bank employee selects the screenshot capture button 104 to display a pull-down screen of the shot items for each of the states where the front of the customer and the driver's license are shown, the side of the driver's license is shown, and the front or side of the document that the employee has presented is shown. When "identity verification" is selected from the displayed shot items, the electronic contract server 1 saves the still image (screenshot image) in the customer image field 106 and, since proper identity verification has been completed, notifies the customer's terminal device 3 mentioned above of the account for electronic certification and the authentication code (one-time password). If the contract form is a party-based electronic contract, in step 7 the electronic contract server 1 notifies the customer's terminal device 3 of the account and password for the customer's electronic signature, which were created from the PIN code.

[0067] In this embodiment, when "identification" is selected from the shot items, the account and the like are automatically transmitted to the terminal device 3, but it is also possible to do so as follows. In other words, when the shot item "identity verification" is selected, a separate account notification confirmation screen will display an "authentication code notification" button (or, in the case of a party-type electronic contract, an "account notification" button; the same applies below), and when this button is selected by a bank employee, the electronic contract server 1 may notify the customer's terminal device 3 of the account and authentication code (one-time password) for requesting electronic certification. Furthermore, the contract content confirmation screen 100b provided to the bank employee's terminal device 4 may be configured to display an "Authentication Code Notification" button in advance. In this case, the "Authentication Code Notification" button is initially displayed in an inactive state where it cannot be selected, and is changed to an active state where it can be selected when the screenshot item "Identity Verification" is selected and the screenshot image is saved. When the bank employee selects the now-active "Authentication Code Notification" button, the electronic contract server 1 sends the account and authentication code to the terminal device 3.

[0068] Thereafter, the bank employee explains the electronic contract, and selects the screenshot capture button 104 for each explanation of disclaimers, specific clauses, contract agreement, etc. For example, after a bank employee explains the terms of the contract, he / she asks the customer for their consent by saying, "Do you agree with the explanation of Article XX?" and once the customer agrees, he / she selects the screenshot capture button 104.

[0069] After the explanation of the electronic contract is completed during the video conference, the electronic contract server 1 issues an electronic signature (step 12). That is, the bank employee explains during the video conference that they will move on to the electronic signature procedure for the electronic contract, encourages them to select the contract procedure button 105, and then selects the contract procedure button 105 from the contract content confirmation screen 100b on the terminal device 4. Each time the contract procedure button 105 is selected, the electronic contract server 1 provides the contract procedure screen 110 to the selected terminal device 3 or terminal device 4 . The electronic contract server 1 also terminates the video conference between the customer and the bank employee and its recording.

[0070] FIG. 13 shows a contract procedure screen 110 provided by the electronic contract server 1 and displayed on the customer's terminal device 3. As shown in Figure 13, the contract procedure screen 110 displays an account field 111, an authentication code field 112, a check box 113 placed before an explanation for consent that reads, "I have confirmed and understood the contract contents and will enter into the contract. Please sign electronically through the electronic contract server 1.", and a signature button 114. On this contract procedure screen 110, the customer enters the account and authentication code for requesting an electronic signature, which have been notified to them by the electronic contract server 1 after presenting a driver's license or other identification, into the account field 111 and authentication code field 112, checks the check box 113, and then selects the signature button 114. If the contract type is a party-type electronic contract, the customer inputs an account and password (created from a PIN code) to request the electronic contract server 1 to sign the contract electronically.

[0071] The electronic contract server 1 confirms that the account and authentication code for the electronic signature entered by party A (customer or bank employee) match the values ​​stored in user information 144, and then performs electronic signature processing on the electronic contract (original) by the electronic contract server 1. The digital signature process for the digital contract (original) will be described below with reference to FIG. FIG. 14 is a conceptual diagram illustrating the structure of an electronic contract with a digital signature in a witness-type electronic contract. The electronic contract server 1 takes an electronic contract document 123, which is an electronic contract (original) 120 to which video conference data 121 that uniquely represents the contents of the video conference and account information 122 for requesting an electronic signature from Party A, as the subject of signature, and calculates a hash value 124 of this subject of signature. Here, account information 122 is information for identifying party A, and one or more of party A's account, authentication code, email address, and mobile phone number are used; in this embodiment, email address and mobile phone number are used (same below).

[0072] The electronic contract server 1 sends the calculated hash value 124 and a request for an electronic signature by the electronic contract server 1 to the remote signature key server 7. The remote signature key server 7 uses the remote signature key (private key) of the electronic contract server 1 to execute an electronic signature on the hash value 124 and returns the signature value 125 to the electronic contract server 1. The electronic contract server 1 embeds the received signature value 125, as well as the electronic certificate and revocation information 126 of the electronic contract server 1 into the electronic contract document 123, thereby creating a signed electronic contract document 127 based on the request of party A.

[0073] Similarly, the electronic contract server 1 confirms that the account and authentication code match for the other party B, and then calculates a hash value 133 of the electronic contract 132 to which party B's account information 131 is attached to the signed electronic contract 127 created for party A as the signature subject. The electronic contract server 1 sends the calculated hash value 133 and a request for an electronic signature by the electronic contract server 1 to the remote signature key server 7. The remote signature key server 7 executes an electronic signature on the received hash value 133 using the remote signature key (private key) of the electronic contract server 1, and returns a signature value 134 to the electronic contract server 1.

[0074] The electronic contract server 1 embeds the received signature value 134, as well as the electronic certificate and revocation information 135 of the electronic contract server 1 into the signed electronic contract 127, thereby creating a signed electronic contract etc. 136 based on the request of party A and the request of party B. The electronic contract server 1 requests signatures when all parties select the signature button 114 (Figure 13), and after the electronic signatures based on the requests of all parties have been completed by the electronic contract server 1, the status of the signed electronic contract, etc. in the contract information 143 (see Figure 2) is changed to "contract signed." The signed electronic contract etc. 136 is accompanied by a timestamp, which will be described later, and is the final electronic contract completion document 138 that is saved.

[0075] In addition, when the electronic contract server 1 issues an electronic signature based on a request from Party B, it calculates the hash value 133 of the electronic contract 132 with Party B's account information 131 attached to the signed electronic contract 127, but it may also be done as follows. In other words, instead of hash value 133, the electronic contract server 1 may use "hash value 124 + account information 131", which is the hash value 124 of the electronic contract document 123 plus party B's account information 131, as the signature object, and calculate the hash value 133' of this signature object.

[0076] In the embodiment described above, an electronic signature is issued for each party who selects the signature button 114 (FIG. 13). Alternatively, the electronic contract server 1 may execute the electronic signature after all the parties have selected the signature button 114. FIG. 15 is a conceptual diagram illustrating another structure of an electronic contract with a digital signature in a witness-type electronic contract. As shown in Figure 15, the electronic contract server 1 waits until all parties (e.g., party A and party B) select the signature button 114, and after everyone has completed their selection, calculates a hash value 141 of an electronic contract etc. 140, which is an electronic contract (original) 120 to which video conference data 121, account information 122 for party A's electronic signature request, and account information 131 for party B are attached. The electronic contract server 1 sends the calculated hash value 141 and a request for an electronic signature to the remote signing key server 7, and the remote signing key server 7 executes an electronic signature on the hash value 141 and returns the signature value 142 to the electronic contract server 1. The electronic contract server 1 embeds the received signature value 142, as well as the electronic certificate and revocation information 143 of the electronic contract server 1 into the electronic contract document 140, thereby creating a signed electronic contract document 144 based on the request of parties A and B. The signed electronic contract etc. 144 with a timestamp (described later) affixed thereto is the finalized electronic contract 146 that is saved.

[0077] The above describes the embodiment and modifications of the electronic signature process when the contract form is a witness-type electronic contract. Next, the electronic signature process when the contract type is a party-type electronic contract will be described. In the case of a conspiracy-type electronic contract, the process after the account and password (created from the PIN code) are input from the customer's terminal device 3 in FIG. 13 is as follows. That is, the electronic contract server 1 confirms that the account and password for the electronic signature entered by the customer match the values ​​stored in the user information 144, and then calculates the hash value of the electronic contract (video conference data) with the video conference data attached to the electronic contract (original). The electronic contract server 1 sends the calculated hash value and the PIN code corresponding to the input account and password to the remote signature key server 7. The remote signature key server 7 executes a signature on the hash value using the remote signature key (private key) corresponding to the received PIN code, and returns the signature value (customer) to the electronic contract server 1. The electronic contract server 1 embeds the received signature value (customer) into the electronic contract and video conference data, and further adds the customer's electronic certificate (customer) corresponding to the PIN code used for the electronic signature and revocation information, thereby creating an electronic contract signed by the customer (customer signature).

[0078] Furthermore, the electronic contract server 1 performs the same process to affix the bank's electronic signature to this electronic contract (customer signature). That is, the electronic contract server 1 sends the hash value of the electronic contract (customer signature) and the bank's PIN code to the remote signature key server 7, and receives the signature value (bank) for the electronic contract (customer signature). By embedding this signature value (bank) in the electronic contract (customer signature) and further adding the electronic certificate (bank) corresponding to the bank's PIN code and revocation information, a completed electronic contract signed by both the customer and the bank is created and stored in the contract DB 142 (see Figure 2). As a result, the electronic contract server 1 changes the status of the electronic contract in the contract information 143 (see FIG. 2) to "contract signed."

[0079] Figure 16 conceptually explains the structure of an electronic contract with a digital signature in a party-based electronic contract. Figure 16(a) shows the structure of an electronic contract in a party-based electronic contract, where an electronic contract (original) 150 is accompanied by video conference data 151 (video conference video and screenshot images) to create an electronic contract (video conference data) 152, which has been digitally signed by the customer (customer), resulting in an electronic contract (customer signature) 153. The electronic contract (customer signature) 153 is accompanied by the bank's electronic signature (bank), resulting in an electronic contract (customer bank signature) 154 . This electronic contract (signed by the customer bank) 154 is accompanied by a timestamp, which will be described later, and is the final electronic contract completion document 155 that is saved.

[0080] The electronic contract completion document 155 of this embodiment shown in FIG. 16(a) includes the video conference data 151, and therefore the overall data size is large. Therefore, the structure of the finalized electronic contract 155 that is saved can be modified as follows. FIG. 16(b) conceptually shows another structure of the final electronic contract 155 that is ultimately saved. The electronic contract server 1 affixes the bank's electronic signature to the video conference data 151, and the electronic contract server 1 assigns a timestamp to the signed video conference data (bank signature) 160 to create video conference data (signature timestamp) 161. The electronic contract server 1 attaches the hash value (video conference hash value 156) of this video conference data (signature timestamp) 161 to the electronic contract, which becomes the electronic contract (video conference hash value) 157, and when the customer's electronic signature (customer) is added to this, it becomes the electronic contract (customer signature) 158. The electronic contract server 1 attaches a timestamp (described later) to this electronic contract (customer signature) 158 to create an electronic contract completion document 159. In this modification, unless a timestamp is added to the video conference data 151, the customer cannot digitally sign the electronic contract (original) 150 to which the video conference data 151 is attached.

[0081] In this modified example, the video conference data 151 is not included in the final saved electronic contract completion document 159, so the overall data size can be reduced. In addition, the electronic contract (customer signature) 158 is not digitally signed by the bank (bank), so the data size can be further reduced. Although the contract completion electronic contract 159 does not include the video conference data 151, this is not a problem because the video conference data (signature timestamp) 161 includes the video conference data. The electronic contract server 1 finally stores the video conference data (signature timestamp) 161 and the contract completion electronic contract 159. In this modification, the video conference data 151 is digitally signed by the bank, so that it is the signature of the party that performed the identity verification.

[0082] In the embodiment and modified example shown in FIGS. 16(a) and 16(b), the electronic contract server 1 stores video conference data with a large amount of data. In contrast to this, in the second modified example shown in FIG. 16(c), the video conference data is saved in the storage 6 on the video conference server 5 side, thereby reducing the amount of data on the electronic contract server 1. 16(c), in the second modified example, the hash value 156b of the video conference data 151 is attached to the electronic contract (original) 150 to create the electronic contract (video conference hash value) 157b. The electronic contract (video conference hash value) 157b is then digitally signed by the customer to create the electronic contract (customer signature) 158, and the electronic contract server 1 then stores the contract completion electronic contract 159 with a timestamp, which will be described later. In addition, the electronic contract server 1 adds the bank's timestamp to the electronic contract (customer signature) 162, which has been electronically signed by the bank only on the contract (original) 150, and also stores the electronic contract (customer signature) 162 with the electronic timestamp of the electronic contract server 1 added.

[0083] Now, we return to the description of this embodiment in which the contract form is a witness-type electronic contract. After creating the signed electronic contract 136 (144), the electronic contract server 1 provides a contract completion screen 149 to the customer's terminal device 3, which is displaying the contract procedure screen 110 (see Figure 13). FIG. 17 shows a contract completion screen 149 provided from the electronic contract server 1 to the customer's terminal device 3. As shown in FIG. 17, the contract completion screen 149 displays a message informing the user that the contract procedure has been completed and that a copy of the contract (contract completion electronic contract 138 (146)) will be sent at a later date. The customer can log out from the electronic contract server 1 after checking this contract completion screen 149.

[0084] Next, the electronic contract server 1 affixes a seal of approval by the manager to the signed electronic contract 136 created in the electronic signature processing in step 12, and the electronic contract server 1 also affixes a timestamp (step 13). That is, after logging in to the electronic contract server 1 from the terminal device 4, the bank executive performs a search using the status "contract signed" as the search item, and selects the desired case from the displayed list of cases to be approved and stamped. As a result, the electronic contract server 1 provides the executive's terminal device 4 with an approval screen 170 corresponding to the electronic contract (customer bank signature) 154.

[0085] FIG. 18 shows an approval seal screen 170 provided from the electronic contract server 1 to the terminal device 4 of the supervisor. An approval screen 170 shown in FIG. 18(a) displays a case display field 171, a video conference confirmation button 172, a screenshot confirmation button 173, an executive approval button 174, and the like. The case display column 171 displays the name of the contractor (borrower (A)), mobile phone number, distribution status, number of issues, send test button, store number and CIF (Customer Information File) number.

[0086] The video conference confirmation button 172 is a button for playing a video of the video conference between the customer and the bank employee regarding the electronic contract. When the video conference confirmation button 172 is selected, the video conference video is displayed in a separate frame on the terminal device 4. This video conference video is a video in which the entire contract content confirmation screen 100a (including the electronic contract field 101, the customer image field 106, the bank employee image field 107, etc.) that the bank employee was viewing on the terminal device 4 during the video conference changes. Therefore, the video conference video played by clicking the video conference confirmation button 172 includes scenes such as a bank employee verifying the customer's identity and explaining the contents of the electronic contract. However, the video conference video to be played back may not be the entire contract content confirmation screen 100a, but only the customer video captured by the customer's terminal device 3 and displayed in the customer image field 106.

[0087] The screen shot confirmation button 173 is a button for displaying a screen shot screen 180 in a separate frame from the seal approval screen 170 displayed on the terminal device 4. FIG. 18(b) shows a screenshot screen 180. As shown in FIG. 18(b), the screenshot screen 180 displays multiple screenshot images 181 and their shot item names 182 in the order they were acquired and saved when a bank employee selected the screenshot acquisition button 104 during a video conference. 18(b), the same image is displayed for convenience of display, but in reality, an image corresponding to the state at the time of acquisition is displayed. For example, in the screenshot image of shot item name 182 "Driver's License Verification," an image of the driver's license being held up in front of the chest in response to the explanation from the bank employee, or an image of the driver's license rotated to check its thickness, is displayed. In this way, the screenshot screen 180 displays multiple screenshot images 181 and shot item names 182, and since these are still images that bank employees use to verify the customer's identity or that correspond to important points in the content explanation, executives can check them more easily than with video conferencing videos.

[0088] The bank executive checks the playback of the video conference video displayed on the terminal device 4 and the screenshot images to see if the bank employee has provided the required explanation for the electronic contract and if the customer has given their consent, and if there are no problems, selects the executive approval button 174. As a result, the electronic contract server 1 changes the status of the electronic contract in the contract information 143 (see Figure 2) to approved and provides an approval confirmation screen (not shown) to the terminal device 4. This approval confirmation screen displays the comment "We will stamp the signed electronic contract, etc., which has been completed, and send it to you. Is this OK?" along with two buttons: "Yes" and "No."

[0089] When the bank executive selects "Yes" on the seal confirmation screen, the electronic contract server 1 works with the timestamp server to assign a timestamp to the signed electronic contract 136, and stores it in the contract database 142 as a completed electronic contract 138 (see Figure 14). In this embodiment, a timestamp is added to the signed electronic contract 136 when the executive approves (seals) it, but a timestamp may be added automatically when both the electronic signature based on the request of Party A (customer) and the electronic signature based on the request of Party B (bank) are completed, and a contract completion electronic contract 138 may be created and saved. Also, a timestamp may be added automatically each time the electronic signature based on the request of Party A (customer) and the electronic signature based on the request of Party B (bank) are completed, and a contract completion electronic contract 138 may be created and saved.

[0090] In addition, even when the contract type is a party-based electronic contract, as with a witness-based electronic contract, when the approval (seal) of the official is given, a timestamp is added to the electronic contract (customer / bank signature) 154, and a contract completion electronic contract 159 is created and saved; however, it is also possible to automatically add a timestamp when the customer's electronic signature and the bank's electronic signature are completed, and create and save the contract completion electronic contract 159.

[0091] Next, the electronic contract server 1 transmits a copy of the contract. That is, the electronic contract server 1 sends the completed electronic contract 155 to the customer's terminal device 3, which is the signed electronic contract etc. 144 signed by the electronic contract server 1 and time-stamped. This transmission corresponds to a message (see FIG. 17) informing the customer that a copy of the contract will be sent to them at a later date.

[0092] As described above, according to the electronic contract server 1 of this embodiment, electronic signatures are issued not only to electronic contracts concluded between the contracting parties (customer and bank), but also to electronic contracts to which video conference data is attached. This video conference data includes video conference footage that uniquely represents the contracting process, such as identity verification and explanation of important matters, which are conducted between the contracting parties without meeting face-to-face via video conference. This provides a witness-type electronic contract that provides high evidentiary proof of identity verification of the contracting parties to the electronic contract, and can prove the authenticity of the contract in addition to proving that it has not been tampered with. In addition, since the subject of the customer's electronic signature is an electronic contract to which the video conference data is attached, and the video conference data contains a copy of the electronic contract, it is possible to confirm and prove that the video conference data corresponds to the electronic contract. On the other hand, if the contract type is a party-based electronic contract, the customer's electronic signature is also obtained on the electronic contract to which the video conference data is attached, making it possible to provide more reliable certification by the court.

[0093] Furthermore, the video conference data of this embodiment includes not only the video conference video between the customer and the bank employee, but also still images (screenshot images) of scenes during the video conference where the authenticity of the contract is confirmed (such as identity verification and explanation of important matters), making it possible to efficiently confirm authenticity.

[0094] Although the embodiment of the electronic contract server 1 has been described, the following modifications are also possible. For example, in the embodiment described above, a video conference video and screenshot images are used as the video conference data to be attached to the electronic contract, but any of the following (A) to (F) can be used as the video conference data (unique information) that uniquely represents the content of the video conference. Note that the set of (A) and (F) is the case in this embodiment. (a) Video of the video conference (b) A portion of the video designated for the video conference (c) Still images of videos designated in video conferences (iv) Link information specifying the storage locations of the above (i) to (iii) (E) At least two of the above (A) to (D) (F) Hash values ​​of (A) to (E) above

[0095] For the portion of the video specified in the video conference (b) above, the video will be saved for N minutes (e.g., 1 minute, 2 minutes, etc.) going back from the time when the screenshot capture button 104 (see Figure 12) was selected, or for N minutes before and after. It is also possible to create a chapter or insert a delimiter mark in the video conference video at the position at which the screenshot capture button 104 is selected or at a position N minutes before the position, which allows the video to be played back from that position.

[0096] The above video conference data (i) to (e) are stored in the storage 6 of the video conference server 5 hosting the video conference, and in addition to the electronic contract server 1 retrieving them from the video conference server 5 after the video conference has ended, the electronic contract server 1 may also store video and still images (or screenshot images) of the entire contract content confirmation screen 100a that it provides to the terminal device 3 during the video conference.

[0097] In addition, in the embodiment described, the procedure for concluding an electronic contract between a customer and the bank (bank employees, executives) was explained using a loan agreement in banking as an example, but it can also be applied to the conclusion of electronic contracts in financial institutions other than banks, various companies such as insurance companies, car dealerships, real estate businesses, content sales companies, accounting firms, government and local government agencies, etc. Furthermore, the subject of electronic contracts for which electronic contracts are created is not limited to loan agreements, but can also be sales contracts, non-disclosure agreements, employment contracts, and other various contracts.

[0098] In this case, the form completion input screen corresponding to the various electronic contracts provided by the electronic contract server 1 in the automatic contract creation process described in the embodiment is created in advance based on the contract type, the business type of the operator, etc., and is stored in the electronic contract server 1. For the completed form input screen, it is possible to have business entities that are users of the electronic contract server 1 upload PDF data that serves as a contract template, and then analyze the PDF to create input fields. In addition, the program for automatically creating contracts and the form completion input screen (see Figure 6) can be created by the user business entity and uploaded to the electronic contract server 1, and then saved and used.

[0099] In the embodiment described above, a case where a smartphone is used as the customer's terminal device 3 has been taken as an example, and various notifications are sent by SMS using a mobile phone number. On the other hand, the terminal device 3 can be any of various electronic devices equipped with a communication function and a display screen, such as a tablet device or a personal computer. However, if the terminal device 3 does not have a mobile phone function, it is possible to respond by email instead of SMS. In this case, in the described embodiment, in the places where a mobile phone number is to be input and displayed (for example, Figure 8(c), Figure 10, etc.), an email address is to be input and displayed. For devices that can use both a mobile phone and email, it is also possible to input and display both.

[0100] In addition, in the embodiment described above, the electronic contract server 1 is described as processing electronic contract documents for one terminal device 3 (smartphone), but it is also possible to use multiple terminal devices 3 (for example, a smartphone and a personal computer). In this case, it is possible to receive a notification from the electronic contract server 1 on a smartphone and log in to the electronic contract server 1 on a personal computer. Video recording for video conferencing can be done on either a smartphone or a personal computer.

[0101] In the case of a contract form involving two parties, the case has been explained in which the customer signs the electronic contract (electronic contract (video conference data) 152) to which the video conference data is attached, and then the bank signs the electronic contract, but the order of the electronic signatures may be reversed. In this case, the customer selects the signature button 114 (Fig. 13), and then the bank signs, followed by the customer's signature, and the official's seal of approval is entered after both electronic signatures. Furthermore, although the case where both the customer's electronic signature and the bank's electronic signature are used has been described, it is also possible to use only the customer's electronic signature.

[0102] Furthermore, we have explained that in the case of witness-type electronic contracts, the electronic contract server 1 stamps a timestamp after the electronic signature is issued by the electronic contract server 1 at the request of all parties (customer, bank), and in the case of party-type electronic contracts, the electronic signature is issued by the customer and the bank. However, if there is little need to prove that the corresponding electronic contract exists at the relevant time, it is also possible to omit the timestamp. On the other hand, if proof of existence is important, it is possible to stamp the video conference data at the end of the video conference. In this case, the timestamp after the official's seal of approval can be omitted, and it can be added as a second timestamp.

[0103] In the embodiment, the case where the image of the customer image field 106 (see Figures 11 and 12) is saved as a screenshot image that functions as video conference data is described, but the image of the entire contract content confirmation screen 100b on the bank side may also be saved as a screenshot image. In this case, not only the image of the customer but also the electronic contract field 101 is displayed, so that when checking a screenshot image for confirming a disclaimer, for example, the part of the electronic contract that describes the disclaimer is included in the image, allowing for a more accurate understanding of the situation at the time of the screenshot.

[0104] In the case of witness-type electronic contracts, the case where the bank's electronic signature is used has been described, but the electronic signature of a bank employee may also be used.

[0105] In the embodiment described above, an electronic signature by the electronic contract server 1 (an electronic signature of the customer and an electronic signature of the bank (bank employee or bank) in the case of a party-type electronic contract) and a timestamp are added to the electronic contract to which the video conference data has been added as proof of non-tampering, in the case of a witness-type electronic contract, but it is also possible to add only an electronic signature or only a timestamp. When only electronic signatures are used in a party-type electronic contract, the customer's electronic signature and / or the bank's (banker's or / and bank's) electronic signature are used.

[0106] In the embodiment and modified examples described above, an electronic contract server or the like when the contract form is a party-based electronic contract can be configured as follows. (Configuration 1) an electronic contract acquisition means for acquiring an electronic contract; a contract providing means for providing a contract content confirmation screen displaying the electronic contract to each terminal device operated by the parties making the electronic contract; a video providing means for providing a video of a video conference held among the parties regarding the electronic contract on the contract content confirmation screen; a video conference data acquisition means for acquiring video conference data that uniquely represents the content of the video conference; an authenticity verification means for verifying at least that the electronic contract to which the acquired video conference data is attached has not been tampered with; a storage means for storing the electronic contract that has been certified as non-tampered with; An electronic contract server comprising: (Configuration 2) The authenticity certification means performs at least one of a digital signature and a time stamp as the non-tampering certification. 2. The electronic contract server according to configuration 1, (Configuration 3) The authenticity certification means performs an electronic signature by at least one party as the non-tampering certification. 2. The electronic contract server according to configuration 1, (Configuration 4) The video of the video conference includes at least a video of the parties verifying their identities and explaining the important parts of the electronic contract; 4. The electronic contract server according to configuration 1, 2, or 3, (Configuration 5) a still image acquisition means for acquiring a still image of a specific state in the video conference; 5. The electronic contract server according to any one of configurations 1 to 4, comprising: (Configuration 6) An electronic contract server according to any one of configurations 1 to 5, characterized in that the video conference data that uniquely represents the content of the video conference video is any one of the following (i) to (f). (a) Video of the video conference (b) A portion of the video designated in the video conference (c) Still images of the video designated in the video conference (iv) Link information specifying the storage locations of the above (i) to (iii) (E) At least two of the above (A) to (D) (F) Hash values ​​of (A) to (E) above (Configuration 7) The video of the video conference data is a video of the video conference provided on the contract content confirmation screen. 7. The electronic contract server according to configuration 6. (Configuration 8) The video of the video conference data is a video of the entire contract content confirmation screen including the electronic contract and the video of the video conference. 7. The electronic contract server according to configuration 6. (Configuration 9) the still image of the video conference data is a still image of the video conference data provided on the contract content confirmation screen; 9. The electronic contract server according to configuration 6, 7, or 8, (Configuration 10) The still image of the video conference data is a still image of the entire video within the contract content confirmation screen including the electronic contract and the video of the video conference. 9. The electronic contract server according to configuration 6, 7, or 8, (Configuration 11) An electronic contract acquisition function to acquire electronic contracts, a contract provision function that provides a contract content confirmation screen displaying the electronic contract to each terminal device operated by the multiple parties entering into the electronic contract; a video provision function that provides a video of a video conference held between the multiple parties regarding the electronic contract within the contract content confirmation screen; a video conference data acquisition function for acquiring video conference data uniquely representing the content of the video conference; a certification function for certifying that the electronic contract to which the acquired video conference data is attached has not been tampered with; a storage function for storing the electronic contract that has been certified as non-tampered; An electronic contract program characterized by causing a computer to implement the above. [Explanation of symbols]

[0107] 1. Electronic contract server 3. Terminal device 4. 5 Video conferencing server 6 Storage 7 Remote Signing Key Server 8 Timestamp Server 11 CPU 12 ROM 13 RAM 14 Storage device 140 Electronic Contract Program 141 Scheduler 142 Electronic Contract DB 143 Contract Information 144 User Information 145 Digital Certificate 146 Operation Log 147 Other Information 15 Communication control unit 40 Login screen 41 Account field 42 Password field 43 Login button 50 Electronic contract project list screen 51 Search item field 52 Project list field 60 Completed form input screen 61 Case information display field 62 Contract details input field 63 Preview display field 64 Videoconferencing checkbox 65 Action buttons 66, 67 Contract type selection button 75 Confirmation / approval screen 76 Project information display field 77 Contract confirmation field 80 Electronic contract project list screen 82 Project list field 83 Meeting reservation button 84 Schedule calendar 85 Contract notification screen 86 Contractor column 87 Check box 88 Mobile phone number field 89 Contract notification button 91 Contract viewing guide screen 92 Contract procedure explanation screen 93 Contract flow explanation 95 Contractor column 96 Checkbox 97 Mobile phone number field 98 Authentication code issue button 99 Contract procedure transition button 100a, 100b Contract details confirmation screen 101 Electronic contract section 102 Start video conference button 103 Change video conference button 104 Screenshot capture button 105 Contract procedure button 106 Customer image column 107 Bank employee image column 110 Contract procedure screen 111 Account field 112 Password field 113 Check box 114 Signature button 149 Contract completion screen 150 Electronic contract (original) 151 Video conference data 152 Electronic Contracts (Videoconferencing Data) 153 Electronic contract (customer signature) 154 Electronic contract (customer bank signature) 155 Contract completion electronic contract 156 Video conference hash value 157 Electronic Contract (Video Conference Hash Value) 158 Electronic contract (customer signature) 159 Completed contract electronic contract 160 Video conference data (bank signature) 161 Signed video conference data 170 Inspection stamp screen 171 Item display field 172 Video conference confirmation button 173 Screenshot confirmation button 174 Official Seal Button 180 Screenshot Screen 181 Screenshot image 182 Shot item name

Claims

1. an electronic contract acquisition means for acquiring an electronic contract; a contract provision means for providing a contract content confirmation screen on which the electronic contract is displayed to each terminal device operated by a plurality of parties making a witness-type electronic contract of the electronic contract; a video providing means for providing a video of a video conference held among the parties regarding the electronic contract on the contract content confirmation screen; a video conference data acquisition means for acquiring video conference data that uniquely represents the content of the video conference; an electronic signature means for performing an electronic signature on a signature subject including the electronic contract and the video conference data by an electronic contract server; a storage means for storing the electronic contract with the electronic signature; the video conference data acquisition means acquires the video conference data when one of the parties selects to proceed to a contract procedure during the video conference. An electronic contract server characterized by:

2. The signature subject includes verifiable account information of all the parties involved. The electronic contract server according to claim 1 .

3. the electronic signature means, after the predetermined explanation has been given via the video conference, each time a request for an electronic signature is made by the electronic contract server, issues an electronic signature by the electronic contract server, including the account information of the requesting party as the subject of the signature; 3. The electronic contract server according to claim 2.

4. the electronic signature means, after a predetermined explanation has been given via the video conference and all parties have requested electronic signatures via the electronic contract server, issues electronic signatures via the electronic contract server, including the account information of all parties as the signature subject; 3. The electronic contract server according to claim 2.

5. The electronic signature means assigns a timestamp to the signature subject after the electronic signature is signed, The storage means stores the electronic contract after the electronic signature and the time stamp.

5. The electronic contract server according to claim 1, wherein the electronic contract server is a server that performs the electronic contract.

6. The video of the video conference includes at least a video of the parties verifying their identities and explaining the important parts of the electronic contract; 6. The electronic contract server according to claim 1, wherein the electronic contract server is a server that performs the electronic contract.

7. a still image acquisition means for acquiring a still image of a specific state in the video conference; 7. The electronic contract server according to claim 1, further comprising:

8. An electronic contract server according to any one of claims 1 to 7, characterized in that the video conference data that uniquely represents the content of the video conference video is any one of the following (i) to (f). (a) Video of the video conference (b) A portion of the video designated in the video conference (c) Still images of the video designated in the video conference (iv) Link information specifying the storage locations of the above (i) to (iii) (E) At least two of the above (A) to (D) (F) Hash values ​​of (A) to (E) above

9. The video of the video conference data is a video of the video conference provided on the contract content confirmation screen.

9. The electronic contract server according to claim 8.

10. The video of the video conference data is a video of the entire contract content confirmation screen including the electronic contract and the video of the video conference.

9. The electronic contract server according to claim 8.

11. the still image of the video conference data is a still image of the video conference data provided on the contract content confirmation screen; 11. The electronic contract server according to claim 8, claim 9, or claim 10.

12. The still image of the video conference data is a still image of the entire video within the contract content confirmation screen including the electronic contract and the video of the video conference.

11. The electronic contract server according to claim 8, claim 9, or claim 10.

13. An electronic contract acquisition function to acquire electronic contracts, a contract provision function that provides a contract content confirmation screen displaying the electronic contract to each terminal device operated by the multiple parties entering into a witness-type electronic contract of the electronic contract; a video provision function that provides a video of a video conference held between the multiple parties regarding the electronic contract within the contract content confirmation screen; a video conference data acquisition function for acquiring video conference data uniquely representing the content of the video conference; an electronic signature function for performing an electronic signature on a signature object including the electronic contract and the video conference data by an electronic contract server; a storage function for storing the electronic contract with the electronic signature; An electronic contract program that causes a computer to realize the following: the video conference data acquisition function acquires the video conference data when one of the parties during the video conference selects to proceed to a contract procedure; An electronic contract program characterized by:

Images