Program, method, information processing device and manufacturing method of system

Abstract

To provide a program for improving a user's operation experience regarding an electronic contract.SOLUTION: A program comprises: in response to a call from an external service, issuing browsing information for users to browse contract data and presenting the browsing information to an end user of the external service; receiving input of communication information issued after identity verification; in response to the end user referring to the browsing information, presenting a screen for requesting communication information; in response to receiving of the input of the communication information from the end user in the screen for requesting the communication information, generating authentication information and transmitting the generated authentication information; upon receiving input of the authentication information from the end user, presenting to the end user, a screen for causing the end user to browse the contract data and receiving consent thereto; and in response to operation for receiving the consent to the contract data from the end user, managing the contract data on the assumption that the end user has consented to the contract data.SELECTED DRAWING: Figure 8

Description

[Technical field]

[0001] The present disclosure relates to a program, a method, an information processing device, and a method for manufacturing a system. [Background technology]

[0002] In business activities, various agreements and applications are approved both inside and outside the company to advance the business. For example, within a business, an approver makes decisions on the contents that need to be approved. In addition, with regard to contracts both inside and outside a business, in recent years, advances in IT technology have meant that contracts that were previously concluded on paper are gradually being converted to electronic contracts.

[0003] In electronic contracts, users of electronic contract services electronically sign the contract documents to be signed. Electronic contract services are provided by businesses in various formats, including the so-called party signature type and the so-called business signature type (witness type). When a contract is concluded using an electronic contract service, the parties may be able to view the contract document between themselves using information that identifies the parties. For example, when an email address is used to identify the parties, one of the parties who wants to enter into a contract sends the contract to the electronic contract service with the email address of the other party specified. The person who receives the contract then uses the electronic contract service to approve the contract, and so on, thereby proceeding with the conclusion of the electronic contract.

[0004] The following Patent Publication No. 2019-144749 (Patent Document 1) describes support for electronic contractual handling of multiple contracts concluded with borrowers. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] JP 2019-144749 A Summary of the Invention [Problem to be solved by the invention]

[0006] Although the information processing device of the above Patent Document 1 is capable of supporting the electronic handling of multiple contracts concluded with borrowers, there is ample room for improvement in the user's operational experience regarding the contracts. The objective of the present invention is to improve the user's operational experience regarding electronic contracts. [Means for solving the problem]

[0007] One embodiment of the present disclosure is a program for operating a computer, the computer being for providing an electronic contract service to a user, the program causing a processor of the computer to execute the following steps: issuing viewing information for viewing contract data in response to a call from an external service, and presenting the issued viewing information to an end user of the external service; accepting, from the external service, input of communication information issued after identity verification as information required for identity verification of the end user; presenting a screen for requesting communication information to the end user in response to the end user referring to the viewing information; generating authentication information in response to accepting input of communication information from the end user on the screen for requesting communication information, and transmitting the generated authentication information to the end user based on the communication information; accepting input of authentication information from the end user, and presenting a screen for viewing and accepting consent to the contract data to the end user; and managing the contract data as if the end user had consented to the contract data in response to an operation of accepting consent to the contract data from the end user. Effect of the Invention

[0008] According to the present disclosure, it is possible to improve the user's operating experience regarding electronic contracts. [Brief description of the drawings]

[0009] [Figure 1] FIG. 1 is a block diagram showing the overall configuration of an electronic contract system 1 according to an embodiment. [Diagram 2] FIG. 2 is a block diagram showing the functional configuration of a terminal device 10 of an end user of an external service. [Diagram 3] FIG. 3 is a block diagram showing the functional configuration of the server 20 for the electronic contract service. [Figure 4] FIG. 4 is a block diagram showing the functional configuration of the external service server 30. As shown in FIG. [Diagram 5] FIG. 5 is a conceptual diagram for explaining an electronic contract. [Figure 6] FIG. 6 is a diagram showing the data structure of the contract management database 2021. [Figure 7] FIG. 7 is a diagram showing the data structure of the contract database 2022. [Figure 8] FIG. 8 is a diagram showing the flow of contract processing among the server 30 of the external service, the server 20 of the electronic contract service, and the terminal device 10 of the end user of the external service. [Figure 9] FIG. 9 is a diagram showing the flow of contract processing among the server 30 of the external service, the server 20 of the electronic contract service, and the terminal device 10 of the end user of the external service. [Figure 10] FIG. 10 is a diagram showing a login screen for an external service. [Figure 11] FIG. 11 shows a screen presenting contract information for end users of an external service on the My Page of the external service. [Figure 12] FIG. 12 is a diagram showing a screen for performing SMS authentication by an end user of an external service. [Figure 13] FIG. 13 is a diagram showing a screen presenting the contract contents of the contract. [Figure 14]FIG. 14 shows a screen on an external service's My Page that presents information on a contract relating to an end user of the external service, as well as information on an authentication method for the end user of the external service in the contract. [Figure 15] FIG. 15 is a diagram showing how information on the authentication method of the parties to a contract is presented in a document that objectively certifies the fact that an electronic contract has been exchanged. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] The following describes an embodiment of the present disclosure. The embodiment of the present disclosure will be described with reference to the drawings. In addition, in the description of the embodiment of the present disclosure, the same parts are denoted by the same reference numerals. Their names and functions are also the same. Therefore, detailed descriptions thereof will not be repeated.

[0011] <Outline of the first embodiment> In the following embodiment, an example will be described in which an external service screen is presented to the end user to have them confirm the contract details, an authentication code is sent to the end user's communication information such as a telephone number, and the authentication code is received from the end user in the external service, thereby advancing the conclusion of a contract between the end user and the external service provider. This allows the end user to maintain the experience of using an external service, while an electronic contract system can be used to affix an electronic signature to the contract data upon contract conclusion and store it, further improving the convenience of each party and further encouraging the use of electronic contracts. Here, the external services include, for example, the following: Real estate rental services: We act as an intermediary between property owners and end users who wish to rent properties, and assist them in concluding rental contracts to use the properties. Insurance services provided by insurance companies, etc. Insurance services are provided when end users agree to predetermined coverage and payment of insurance premiums. Vehicle sales services: For example, a business operator accepts purchase offers from end users for new and used cars managed by the business operator and concludes sales contracts that stipulate the payment method. In addition, matters that are subject to approval by the end user include contracts concluded between the parties and terms of use for using the service (including licenses for using software, etc.). In this embodiment, a user operates a PC (Personal Computer) to conclude a contract using an electronic contract service. An electronic contract has one or more approvers who approve the contract. The approvers determine whether or not a contract can be concluded under the conditions set out in the contract, based on the contract.

[0012] <1.1 Overall system configuration> Fig. 1 is a block diagram showing an example of the overall configuration of an electronic contract system 1 according to an embodiment. As shown in Fig. 1, the electronic contract system 1 includes a terminal device 10 of an end user of an external service, a server 20 of an electronic contract service, and a server 30 of the external service. In the electronic contract system 1, the terminal device 10 of the end user of the external service and the server 30 of the external service are connected to each other via a network 80 so as to be able to communicate with each other. In addition, in the electronic contract system 1, the server 20 of the electronic contract service and the server 30 of the external service are connected to each other via the network 80 so as to be able to communicate with each other.

[0013] 1 shows a terminal device 10 of an end user of an external service. The terminal device 10 of the end user of the external service is, for example, a PC, a smartphone, or the like.

[0014] The terminal device 10 of the end user of the external service executes a program to provide the user with an environment for operating a system corresponding to the program. The terminal device 10 of the end user of the external service reads and executes the program to communicatively connect the terminal device 10 of the end user of the external service with the server 30 of the external service. The terminal device 10 of the end user of the external service transmits and receives data related to the electronic contract between the terminal device 10 of the end user of the external service and the server 30 of the external service.

[0015] The example in Fig. 1 shows a server 20 of an electronic contract service that manages various data related to the electronic contract system 1. The server 20 of the electronic contract service transmits data necessary for an electronic contract to a server 30 of an external service as appropriate, thereby visualizing the status of an electronic contract on a terminal device 10 of an end user of the external service. In addition, the server 20 of the electronic contract service communicates with the server 30 of the external service, and transmits images, files, text data, and the like to the server 30 of the external service according to the progress of the electronic contract of each user.

[0016] For example, the server 20 of the electronic contract service manages various data such as user information related to electronic contracts, information on contract documents used in electronic contracts, and the like.

[0017] The terminal device 10 of an end user of an external service includes a communication IF (Interface) 12 , an input device 13 , an output device 14 , a memory 15 , a storage unit 16 , and a processor 19 .

[0018] The communication IF 12 is an interface for inputting and outputting signals so that the terminal device 10 of the end user of the external service can communicate with an external device.

[0019] The input device 13 is a device for accepting input operations from an end user of an external service (hereinafter, referred to as an “end user”). The device for accepting input operations is, for example, a touch panel, a touch pad, a pointing device such as a mouse, or a keyboard.

[0020] The output device 14 is a device (such as a display or a speaker) for presenting information to an end user.

[0021] The memory 15 is for temporarily storing programs, data to be processed by the programs, etc. The memory 15 is, for example, a volatile memory such as a DRAM (Dynamic Random Access Memory).

[0022] The storage unit 16 is for storing data and is, for example, a flash memory or a hard disk drive (HDD).

[0023] The processor 19 is hardware for executing an instruction set written in a program, and is composed of an arithmetic unit, a register, peripheral circuits, and the like.

[0024] The server 20 for the electronic contract service is a device that manages information on users who enter into contracts through electronic contracts, and information such as contract documents used when making electronic contracts.

[0025] The server 20 for the electronic contract service includes a communication IF 22 , an input / output IF 23 , a memory 25 , a storage 26 , and a processor 29 .

[0026] The communication IF 22 is an interface for inputting and outputting signals so that the electronic contract service server 20 can communicate with external devices.

[0027] The input / output IF 23 functions as an interface with an input device for receiving an input operation from a user and an output device for presenting information to the user.

[0028] The memory 25 is for temporarily storing programs, data to be processed by the programs, etc. The memory 25 is, for example, a volatile memory such as a DRAM (Dynamic Random Access Memory).

[0029] The storage 26 is for storing data and is, for example, a flash memory or a hard disk drive (HDD).

[0030] The processor 29 is hardware for executing an instruction set written in a program, and is composed of an arithmetic unit, a register, peripheral circuits, and the like.

[0031] The external service server 30 is a device that manages information on end users in the external service, information on electronic contracts linked to the end users, and the like.

[0032] The server 30 for the electronic contract service includes a communication IF 32 , an input / output IF 33 , a memory 35 , a storage 36 , and a processor 39 .

[0033] The communication IF 32 is an interface for inputting and outputting signals so that the server 30 of the external service can communicate with an external device.

[0034] The input / output IF 33 functions as an interface with an input device for receiving an input operation from a user and an output device for presenting information to the user.

[0035] The memory 35 is for temporarily storing programs, data to be processed by the programs, etc. The memory 35 is, for example, a volatile memory such as a DRAM (Dynamic Random Access Memory).

[0036] The storage 36 is for storing data and is, for example, a flash memory or a hard disk drive (HDD).

[0037] The processor 39 is hardware for executing an instruction set written in a program, and is composed of an arithmetic unit, a register, peripheral circuits, and the like.

[0038] <1.2 Functional configuration of the terminal device 10 of the end user of the external service> 2 is a diagram showing a functional configuration of a terminal device 10 of an end user of an external service. The terminal device 10 of the end user of the external service includes an antenna 111, a first wireless communication unit 121, a processor 19, an operation reception unit 130, a storage unit 16, a memory 15, a display 132, a voice processing unit 140, a microphone 141, and a speaker 142.

[0039] The antenna 111 radiates a signal emitted by the terminal device 10 of an end user of an external service as a radio wave into space. The antenna 111 also receives the radio wave from space and provides the received signal to the first wireless communication unit 121.

[0040] The first wireless communication unit 121 performs modulation / demodulation processing and the like for transmitting and receiving signals via the antenna 111 and the like so that the terminal device 10 of the end user of the external service can communicate with other communication devices. The first wireless communication unit 121 is a communication module for wireless communication including a tuner, a high-frequency circuit, and the like, and performs modulation / demodulation and frequency conversion of wireless signals transmitted and received by the terminal device 10 of the end user of the external service, and provides the received signals to the processor 19.

[0041] The processor 19 controls the operation of the terminal device 10 of the end user of the external service by reading and executing the programs stored in the storage unit 16. The processor 19 is realized by, for example, an application processor.

[0042] The operation reception unit 130 has a mechanism for receiving an input operation by a user. For example, the operation reception unit 130 is realized as a pointing device such as a mouse, a touch pad, or a touch panel, a keyboard, a controller, a photographing means for sensing the end user's body movement as an input operation, or the like. For example, the operation reception unit 130 senses the movement of a body part such as a hand, the end user's facial expression, or the like as the end user's body movement, and receives the movement of these body parts, or the like, as an input operation. The operation reception unit 130 determines the type of operation, such as whether the end user's operation is a flick operation or a tap operation, based on the coordinates at which the end user touches a finger on a touch panel or the like to receive the input operation.

[0043] The storage unit 16 is composed of a flash memory, a RAM (Random Access Memory), etc. The storage unit 16 also stores programs used by the terminal device 10 of the end user of the external service, and various data received by the terminal device 10 of the end user of the external service from the server 20 of the electronic contract service, etc.

[0044] The display 132 displays data such as images, videos, and text under the control of the processor 19. The display 132 is realized by a display device such as an LCD (Liquid Crystal Display) or an organic EL (Electro Luminescence) display.

[0045] The audio processing unit 140 modulates and demodulates an audio signal. The audio processing unit 140 modulates a signal provided from a microphone 141, and provides the modulated signal to the processor 19. The audio processing unit 140 also provides the audio signal to a speaker 142.

[0046] The microphone 141 receives a voice input and provides the voice processor 140 with a voice signal corresponding to the voice input.

[0047] The speaker 142 converts the audio signal provided from the audio processor 140 into audio and outputs the audio to the outside of the terminal device 10 of the end user of the external service.

[0048] The storage unit 16 stores contract management information 161 and contract information 162 . The contract management information 161 is information for managing information on the contract status of an electronic contract in the electronic contract system 1. The contract information 162 is information for managing contracts in the electronic contract system 1.

[0049] The processor 19 operates according to a program to thereby fulfill the functions of an input operation reception unit 191, a transmission / reception unit 192, a data processing unit 193, and a notification control unit 194. The input operation reception unit 191 performs processing to receive an input operation by an end user to an input device such as the operation reception unit 130. When the operation reception unit 130 is, for example, a touch device, the input operation reception unit 191 determines the type of operation, such as whether the end user's operation is a flick operation or a tap operation, based on information on the coordinates where the end user touches the touch device with a finger or the like. The transmission / reception unit 192 performs processing for the terminal device 10 of the end user of the external service to transmit and receive data to and from an external device such as the server 30 of the external service in accordance with a communication protocol. The data processing unit 193 performs calculations according to a program on data that is received by the terminal device 10 of the end user of the external service, and outputs the calculation results to a memory or the like. The notification control unit 194 performs processing for presenting information to an end user, such as processing for displaying a display image on the display 132, processing for outputting sound to the speaker 142, and processing for generating vibrations from a vibrator or the like.

[0050] <1.3 Functional configuration of the server 20 for electronic contract service> 3 is a diagram showing the functional configuration of the server 20 for the electronic contract service. As shown in FIG. 3, the server 20 for the electronic contract service fulfills the functions of a communication unit 201, a storage unit 202, and a control unit 203.

[0051] The communication unit 201 performs processing for the server 20 of the electronic contract service to communicate with external devices.

[0052] The storage unit 202 stores various databases such as a contract management database 2021 and a contract database 2022.

[0053] The contract management database 2021 is a database that contains information for managing the contract status in the electronic contract system 1. Details will be described later.

[0054] The contract database 2022 is a database for managing information on contracts in the electronic contract system 1. Details will be described later.

[0055] The control unit 203 is realized by the processor 29 reading a program stored in the storage unit 202 and executing instructions included in the program. The control unit 203 performs functions indicated as a reception control module 2031, a transmission control module 2032, a contract management information acquisition module 2033, and a contract information acquisition module 2034 by operating in accordance with the program.

[0056] The reception control module 2031 controls the process in which the electronic contract service server 20 receives signals from external devices in accordance with a communication protocol.

[0057] The transmission control module 2032 controls the process in which the electronic contract service server 20 transmits signals to external devices in accordance with a communication protocol.

[0058] The contract management information acquisition module 2033 performs a series of processes for managing the contract status in the electronic contract system 1.

[0059] The contract information acquisition module 2034 performs a series of processes for managing contract information in the electronic contract system 1.

[0060] <1.4 Functional configuration of the external service server 30> 4 is a diagram showing the functional configuration of the external service server 30. As shown in FIG. 4, the external service server 30 exerts the functions of a communication unit 301, a storage unit 302, and a control unit 303.

[0061] The communication unit 301 performs processing for the server 30 of the external service to communicate with an external device.

[0062] The storage unit 302 stores various databases such as a contract management database 3021, a contract database 3022, and an end user database 3023.

[0063] The contract management database 3021 is a database that contains information for managing the contract status in the electronic contract system 1.

[0064] The contract database 3022 is a database for managing contract information in the electronic contract system 1.

[0065] The end user database 3023 is a database for managing information on end users in external services.

[0066] The control unit 303 is realized by the processor 39 reading a program stored in the storage unit 302 and executing instructions included in the program. The control unit 303 operates in accordance with the program to perform functions shown as a reception control module 3031, a transmission control module 3032, a contract management information acquisition module 3033, a contract information acquisition module 3034, and an end user information acquisition module 3035.

[0067] The reception control module 3031 controls the process in which the server 30 of the external service receives a signal from an external device in accordance with a communication protocol.

[0068] The transmission control module 3032 controls the process in which the server 30 of the external service transmits a signal to an external device in accordance with a communication protocol.

[0069] The contract management information acquisition module 3033 performs a series of processes for managing the contract status in the electronic contract system 1.

[0070] The contract information acquisition module 3034 performs a series of processes for managing contract information in the electronic contract system 1.

[0071] The end user information acquisition module 3035 performs a series of processes for managing end user information in the external service.

[0072] <1.5 Conceptual diagram to explain electronic contracts> 5 is a conceptual diagram for explaining an electronic contract. In this embodiment, an "electronic contract" refers to exchanging a contract document on the Internet, the contracting parties expressing their intention to agree, and attaching a digital signature to the contract document.

[0073] First, the contract sender uploads the contract to the server 20 of the electronic contract service on the cloud by operating the sender terminal device 50. The server 20 of the electronic contract service affixes the contract sender's digital signature to the contract that the contract sender has agreed to send.

[0074] The contract sender performs an operation to request the contract receiver to conclude an agreement. Specifically, the sender terminal device 50 accepts an operation to designate a contract receiver from the contract sender, and transmits it to the server 20 of the electronic contract service. In this embodiment, the sender terminal device 50 accepts an operation to designate an email address or telephone number of each of one or more contract receivers from the contract sender as information identifying the contract receiver. The server 20 of the electronic contract service of the electronic contract system 1 sends information for accessing the contract to the contract recipient, addressed to the email address or telephone number of the recipient specified by the user of the contract sender. In this embodiment, the server 20 of the electronic contract service of the electronic contract system 1 sends information for accessing the contract to the server 30 of the external service, addressed to the email address or telephone number of the recipient specified by the user of the contract sender. The information for accessing the contract is, for example, a link described as a URL (Uniform Resource Locator). Note that this embodiment uses SMS for user authentication of the contract recipient in the external service.

[0075] The contract recipient performs an operation (click, tap, etc.) to specify information for accessing the contract received on the external service server 30, and can confirm the contents of the contract on the electronic contract service server 20 online and enter into an agreement. The recipient terminal device 40 presents a screen for accepting an operation indicating agreement to the contract to the user of the recipient terminal device 40, and accepts an operation for agreement from the contract recipient. If there are any defects in the contract contents at this stage, the server 20 of the electronic contract service may accept an operation from the contract recipient indicating that the contract is not agreed to.

[0076] The electronic contract service server 20, upon receiving an operation from the contract recipient to agree to the contract, affixes the contract recipient's electronic signature to the contract. The contract is stored in the electronic contract service server 20. With electronic signatures from both contracting parties affixed, the contract is prevented from being tampered with.

[0077] This embodiment realizes such a cloud-based electronic contract service.

[0078] <2 Data Structure> 6 and 7 are diagrams showing the data structure of the database stored in the server 20 of the electronic contract service. Note that Figs. 6 and 7 are merely examples and do not exclude data that is not shown.

[0079] Fig. 6 is a diagram showing the data structure of the contract management database 2021. The contract management database 2021 is a database including information for managing the contract status in the electronic contract system 1. Each record of the contract management database 2021 in Fig. 6 includes an item "contract ID", an item "contract ID", an item "sender email address", an item "recipient email address", an item "recipient phone number", an item "contract status", and an item "contract completion date and time".

[0080] The item "contract ID" indicates identification information issued, for example, by the server 20 of the electronic contract service, for each contract concluded by electronic contract.

[0081] Specifically, the item "contract ID" is a unique ID for an electronic contract that is required when managing each contract concluded between users by electronic contract.

[0082] The item "contract ID" indicates a unique ID for each contract concluded by electronic contract, specified by the sender of the contract when the contract that is the subject of the electronic contract is made. For example, the contract identification information includes unique information that is associated with the contract and issued by the server 20 of the electronic contract service when the server 20 accepts an upload of the contract as the subject of the electronic contract. The unique information that is associated with the contract and issued includes, for example, identification information issued for the contract, link information for each terminal device to access the contract, etc. A contract is typically created using document creation software and is a file whose contents cannot be modified, such as a PDF file.

[0083] The item "sender email address" indicates the email address of the user who will be the contract sender for each contract concluded by electronic contract.

[0084] The item "recipient email address" indicates the email address of the user who will be the recipient of the contract for each contract concluded by electronic contract.

[0085] The item "recipient telephone number" indicates the telephone number of the user who will be the recipient of the contract for each contract concluded by electronic contract.

[0086] The item "contract status" indicates the status of the electronic contract being concluded between the contract sender and the contract receiver. Specifically, the item "contract status" may include the following as the status of the electronic contract between the parties. "Not yet contracted" means that the recipient of the contract has not been designated and the conclusion of the contract via electronic contract has not yet begun. "Contract completed" is the state in which the parties to the contract have approved the contract at the server 20 of the electronic contract service, and the conclusion of the contract by electronic contract has been completed.

[0087] The item "contract completion date and time" indicates the date and time when the conclusion of each contract concluded by electronic contract was completed.

[0088] Fig. 7 is a diagram showing the data structure of the contract database 2022. The contract database 2022 is a database for managing contract information in the electronic contract system 1. Each record in the contract database 2022 in Fig. 7 includes an item "contract ID", an item "document title", an item "contract conclusion date", an item "contract start date", and an item "contract end date".

[0089] The item "contract ID" indicates a unique ID for each contract concluded by electronic contract, specified by the sender of the contract when the contract that is the subject of the electronic contract is made. For example, the contract identification information includes unique information that is associated with the contract and issued by the server 20 of the electronic contract service when the server 20 accepts an upload of the contract as the subject of the electronic contract. The unique information that is associated with the contract and issued includes, for example, identification information issued for the contract, link information for each terminal device to access the contract, etc. A contract is typically created using document creation software and is a file whose contents cannot be modified, such as a PDF file.

[0090] The item "Document Title" indicates the title of the contract used for each contract, such as a lease agreement, a non-disclosure agreement, etc.

[0091] The item "contract conclusion date" indicates the date on which the contract was concluded.

[0092] The item "contract start date" indicates the date on which the contract of the contract started.

[0093] The item "contract termination date" indicates the date on which the contract expires.

[0094] <Operation of the First Embodiment> Next, the operation of each device that constitutes the electronic contract system 1 will be explained.

[0095] FIG. 8 is a diagram showing the flow of contract processing among the server 30 of the external service, the server 20 of the electronic contract service, and the terminal device 10 of the end user of the external service.

[0096] In step S8031, the server 30 of the external service accepts an input operation for creating a contract and requesting the conclusion of the contract from a user of the external service. In this embodiment, the recipient of the contract created and requested to be concluded in step S8031 is assumed to be an end user of the external service.

[0097] In step S8021, the electronic contract service server 20 accepts the end user's telephone number information from the external service server 30. In this embodiment, it is assumed that the external service server 30 stores the end user's telephone number information in the storage unit 302.

[0098] In step S8022, the server 20 of the electronic contract service affixes the signature of the sender to the contract. The server 20 of the electronic contract service affixes the signature of the sender of the contract to a document that objectively certifies that the electronic contract of the contract has been exchanged. The document that objectively certifies that the electronic contract of the contract has been exchanged is, for example, a signature panel, an agreement conclusion certificate, etc. The parties to the contract can view the signature panel, agreement conclusion certificate, etc. to confirm the signature of the sender of the contract.

[0099] In step S8023, the server 20 of the electronic contract service generates a consent URL. The consent URL is a URL that allows the recipient of the contract to confirm the contractual contents of the contract and transition to a page where the recipient can consent to the contract. After generating the consent URL, the server 20 of the electronic contract service transmits information about the consent URL to the server 30 of the external service.

[0100] In step S8032, the server 30 of the external service presents a consent URL on a web page (hereinafter referred to as "my page") that displays information related to the end user of the external service. It is assumed that the external service provides a My Page within the external service. The My Page of the external service is presented on the terminal device 10 of the end user of the external service. The My Page of the external service presents, for example, information on the end user's account and information on the end user's personal information. The My Page may also present information on a contract for the end user used in the external service.

[0101] In step S8011, the terminal device 10 of the end user of the external service presents a login screen for the external service. When using the external service, the external service accepts a login operation from the end user on a login screen of the external service. The login screen of the external service is presented on the terminal device 10 of the end user of the external service. The login screen accepts information such as an ID and a password. The external service server 30 accepts an operation of inputting an ID and a password from the end user on a login screen of the external service, and authenticates the end user. Next, the terminal device 10 of the end user of the external service presents My Page. My Page presents contract information related to the end user used in the external service. The screen presented on My Page is, for example, a screen as shown in FIG. Then, the terminal device 10 of the end user of the external service accepts an operation to select a contract from the end user. When the terminal device 10 of the end user of the external service accepts an operation to select a contract from the end user, the terminal device 10 of the end user of the external service performs a page transition from My Page to an SMS authentication screen.

[0102] In step S8024, the server 20 of the electronic contract service presents an SMS authentication screen. The SMS authentication screen is, for example, a screen as shown in FIG.

[0103] In step S8012, the terminal device 10 of the end user of the external service presents an SMS authentication screen. The terminal device 10 of the end user of the external service first accepts an operation from the end user to input the end user's phone number on the SMS authentication screen. The terminal device 10 of the end user of the external service then transmits the phone number information input by the end user to the server 20 of the electronic contract service.

[0104] In step S8025, the electronic contract service server 20 determines whether the telephone number received from the external service server 30 matches the telephone number input from the end user's terminal device 10. If the telephone numbers match, the electronic contract service server 20 generates an authentication code. The authentication code is like a temporarily issued password. If the telephone numbers do not match, the electronic contract service server 20 ends the process.

[0105] In step S8026, the server 20 of the electronic contract service transmits an authentication code to the terminal device 10 of the end user of the external service by SMS based on the information of the end user's telephone number. After transmission, the terminal device 10 of the end user of the external service receives the information of the authentication code.

[0106] In step S8013, the terminal device 10 of the end user of the external service accepts input of an authentication code from the end user on the SMS authentication screen. Then, the terminal device 10 of the end user of the external service transmits information on the authentication code accepted from the end user to the server 20 of the electronic contract service.

[0107] In step S8027, the server 20 of the electronic contract service determines whether the authentication code generated by the server 20 of the electronic contract service matches the authentication code input from the terminal device 10 of the end user of the external service. If the authentication codes match, the server 20 of the electronic contract service authenticates the end user. If the authentication codes do not match, the server 20 of the electronic contract service does not authenticate the end user.

[0108] FIG. 9 is a diagram showing the flow of contract processing among the server 30 of the external service, the server 20 of the electronic contract service, and the terminal device 10 of the end user of the external service.

[0109] Step S8027 is as described in FIG.

[0110] In step S9021, the server 20 of the electronic contract service presents the contract contents of the contract to the terminal device 10 of the end user of the external service.

[0111] In step S9011, the terminal device 10 of the end user of the external service presents the contract contents of the contract. The end user checks the contract contents of the contract and determines whether or not to agree to the contract. If it is determined that the end user agrees to the contract, the end user performs an input operation indicating that the end user agrees to the contract. The terminal device 10 of the end user of the external service accepts the input operation indicating that the end user agrees to the contract from the end user.

[0112] In step S9022, the server 20 of the electronic contract service performs processing related to the completion of the agreement to the contract. Specifically, the server 20 of the electronic contract service updates the item "contract status" of the contract management database 2021 to "contract completed." In addition, in response to receiving an input operation indicating agreement to the contract, the server 20 of the electronic contract service updates the value of the item "contract completion date and time" of the contract management database 2021.

[0113] In step S9023, the electronic contract service server 20 affixes the recipient's signature to the contract. The electronic contract service server 20 affixes the recipient's signature to a document that objectively certifies that the electronic contract of the contract has been exchanged. The document that objectively certifies that the electronic contract of the contract has been exchanged is, for example, a signature panel, an agreement conclusion certificate, etc. The parties to the contract can view the signature panel, agreement conclusion certificate, etc. to confirm the signature of the recipient of the contract.

[0114] In step S9031, the external service server 30 is a diagram showing a screen on the external service's My Page that presents information on the end user's authentication method in the contract along with information on the contract related to the end user. The information on the end user's authentication method in the contract is, for example, information on SMS authentication. The information on SMS authentication is information on the date and time when SMS authentication was performed, the phone number used when SMS authentication was performed, etc. The screen presented on My Page is, for example, as shown in FIG.

[0115] <Screen example> FIG. 10 is a diagram showing a login screen for an external service.

[0116] When using the external service, the external service accepts a login operation from an end user on a login screen of the external service. The login screen of the external service is presented on the terminal device 10 of the end user of the external service. The login screen accepts information such as an ID and a password. The external service server 30 accepts an operation of inputting an ID and a password from an end user on a login screen of the external service, and authenticates the end user.

[0117] Specifically, the terminal device 10 of the end user of the external service presents the following information on a dialog screen 1000: Area 1001 is an area where ID and password information is input by the end user. A button 1002 is a button for accepting a login operation from an end user.

[0118] FIG. 11 shows a screen presenting contract information relating to an end user on the My Page of an external service.

[0119] It is assumed that the external service provides a My Page within the external service. The My Page of the external service is presented on the terminal device 10 of the end user of the external service. The My Page of the external service may present, for example, information related to the end user's account and information related to the end user's personal information. The My Page of the external service may also present information about contracts related to the end user used in the external service. For example, information about contracts related to the end user used in the external service may be displayed so that the user can easily view it, depending on the contract status of the contract. For example, the My Page of the external service may separately display contracts that have been requested to be concluded and contracts that have already been concluded.

[0120] Specifically, the terminal device 10 of the end user of the external service presents the following information on a dialogue screen 1100. Note that the dialogue screen 1100 represents a part of My Page. Area 1101 is an area for displaying information about the contract requested to be concluded. Area 1102 is an area for displaying information about a concluded contract.

[0121] FIG. 12 is a diagram showing a screen for an end user to perform SMS authentication.

[0122] As explained in Fig. 8, the terminal device 10 of the end user of the external service presents an SMS authentication screen. The terminal device 10 of the end user of the external service accepts input of a phone number from the end user on the SMS authentication screen. The server 20 of the electronic contract service determines whether the phone number accepted from the server 30 of the external service matches the phone number accepted from the terminal device 10 of the end user of the external service. Then, if the phone numbers match, the server 20 of the electronic contract service generates an authentication code. After the authentication code is generated, the terminal device 10 of the end user of the external service accepts input of the authentication code from the end user on the SMS authentication screen. The server 20 of the electronic contract service determines whether the authentication code generated by the server 20 of the electronic contract service matches the authentication code accepted from the terminal device 10 of the end user of the external service. If the authentication codes match, the server 20 of the electronic contract service performs authentication. After authentication, the SMS authentication screen may display a message requesting confirmation of the terms of use, a button to transition to a page where the contents of the contract can be confirmed, etc.

[0123] Specifically, the terminal device 10 of the end user of the external service presents the following information on a dialog screen 1200: Area 1201 is an area where a telephone number is input by an end user. A button 1202 is a button for accepting an operation to transmit an authentication code from the end user. Area 1203 is an area where an authentication code is input by the end user. A button 1204 is a button that receives an operation from the end user to press a button for transitioning to a page where the contents of the contract can be confirmed.

[0124] FIG. 13 is a diagram showing a screen presenting the contract contents of the contract.

[0125] As described in FIG. 8, after SMS authentication, the terminal device 10 of the end user of the external service presents the contract contents of the contract. The end user checks the contract contents of the contract and determines whether or not to agree to the contract. If it is determined that the end user agrees to the contract, the end user performs an input operation indicating that the end user agrees to the contract. Then, the terminal device 10 of the end user of the external service accepts the input operation indicating that the end user agrees to the contract from the end user.

[0126] Specifically, the terminal device 10 of the end user of the external service presents the following information on a dialog screen 1300: Area 1301 is an area where the contract contents of the contract are presented. A button 1302 is a button for accepting an input operation from the end user indicating that the end user agrees to the contract.

[0127] FIG. 14 shows a screen on the My Page of an external service that presents information on the contract regarding the end user as well as information on the authentication method for the end user in the contract.

[0128] As explained in Fig. 11, the My Page of the external service may display contracts that have been requested to be concluded and already concluded contracts separately. Fig. 14 shows that the My Page of the external service may present information on the authentication method of the end user in the contract along with contract information related to the end user. The information on the authentication method of the end user in the contract is, for example, information on SMS authentication. The information on SMS authentication is information on the date and time when SMS authentication was performed, the phone number used when SMS authentication was performed, etc.

[0129] Specifically, the terminal device 10 of the end user of the external service presents the following information on a dialogue screen 1400. Note that the dialogue screen 1400 represents a part of My Page. Area 1101 is an area for displaying information about the contract requested to be concluded. Area 1102 is an area for displaying information about a concluded contract. Area 1401 is an area for displaying information on the authentication method of the end user in the contract.

[0130] FIG. 15 is a diagram showing how information on the authentication method of the parties to a contract is presented in a document that objectively certifies the fact that an electronic contract has been exchanged.

[0131] Documents that objectively certify that an electronic contract has been exchanged include, for example, an agreement conclusion certificate, an electronic contract conclusion certificate, etc. Documents that objectively certify that an electronic contract has been exchanged contain information about who agreed to which contract, when, and on which document. Figure 15 shows information on the authentication method of the end user in the contract in a document that objectively certifies the fact that an electronic contract has been exchanged. The information on the authentication method of the end user in the contract is, for example, information on SMS authentication. The information on SMS authentication is information on the date and time when SMS authentication was performed, the phone number used when SMS authentication was performed, etc.

[0132] Specifically, the terminal device 10 of the end user of the external service presents the following information on a dialog screen 1500: An area 1501 is an area for displaying bibliographic information of the contract. The bibliographic information of the contract is, for example, the title of the contract, the contract ID of the contract, and the like. Area 1502 is an area for displaying information about the parties to the contract. An area 1503 displays information on the authentication method of the parties in the contract. <Modification> (1) A method to allow users to view the contract on a page other than the My Page provided by an external service In addition to the above embodiments, for example, the server 20 of the electronic contract service may send a URL for viewing the contract contents of the contract via SMS or the like so that the end user of the external service can agree to the contract contents, thereby allowing the end user to view the contract contents via a browser or the like running on the terminal device 10 of the end user of the external service. For example, suppose that a business operator (e.g., a real estate business operator, a communications business operator, an insurance business operator, etc.) that operates an external service prepares a terminal (tablet, PC, etc.) at a storefront or the like for an end user to input information such as a telephone number and the end user's name. The end user receives a URL for viewing the contents of the contract from the server 20 via SMS on the terminal device 10, checks the contract contents on a browser or the like, and performs an operation to agree to the contract. The end user may be able to check the contents of the contract on the terminal device 10 without performing an operation to log in to a personal page provided by the server 30 of the external service. (2) If the device used to view the contract and the device used to receive the authentication code are not the same In the above embodiment, an example has been described in which the terminal device 10 allows the end user to view the details of the subscription on a personal page provided by an external service, and receives a verification code via a telephone number. In addition, the terminal for allowing the end user to view the contract details may be separate from the terminal for receiving the authentication code via a telephone number. For example, a real estate rental business, an insurance business, etc. may install a terminal (such as a tablet) in a store and accept input of information required for a contract (such as a personal name and phone number) from an end user at the store's terminal. The store's terminal may allow the end user to use an external service while transmitting an authentication code to the end user's terminal via the phone number.

[0133] Although several embodiments of the present disclosure have been described above, these embodiments can be implemented in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and modifications are within the scope of the invention and its equivalents as described in the claims, as well as the scope and spirit of the invention.

[0134] <Additional Notes> The following description adds to the matters described in the above embodiments. (Appendix 1) A program for operating a computer, the computer for providing an electronic contract service to a user, the program including a step of causing a processor of the computer to issue viewing information for viewing contract data in response to a call from an external service and present the issued viewing information to an end user of the external service (S8032); a step of accepting input of communication information issued after identity verification from the external service as information required for identity verification of the end user (S8021); and a step of presenting a screen for requesting communication information to the end user in response to the end user referring to the viewing information (S8024). A program which executes the steps of: generating authentication information (S8025) in response to receiving input of communication information from an end user on a screen for requesting communication information (S8012), and transmitting the generated authentication information to the end user based on the communication information; receiving input of authentication information from the end user (S8013), and presenting a screen for viewing and accepting consent to contract data to the end user (S9021); and managing the contract data as if the end user had consented to the contract data in response to an operation (S9011) for accepting consent to the contract data from the end user (S9023).

[0135] (Appendix 2) The program according to claim 1, wherein in the managing step, at least the end user is presented with information (1500) proving that the end user has agreed to the contract data to which the end user has agreed, the information including communication information entered by the end user.

[0136] (Appendix 3) The program according to claim 1, wherein in the step of presenting the browsing information to the end user, the browsing information is presented to the end user via the external service by responding with the browsing information to the external service in response to a call of the external service (1100).

[0137] (Appendix 4) 4. The program according to claim 3, wherein in the managing step, information indicating consent is sent to an external service for the contract data to which the end user has given consent, thereby presenting the information indicating consent to the end user via the external service (1401).

[0138] (Appendix 5) A method for operating a computer, the computer being for providing an electronic contract service to a user, the method includes a step of having a processor of the computer issue viewing information for viewing contract data in response to a call from an external service, and present the issued viewing information to an end user of the external service (S8032); a step of accepting input of communication information issued after identity verification from the external service as information required for identity verification of the end user; a step of presenting a screen for requesting communication information to the end user in response to the end user referring to the viewing information (S8024); a step of generating authentication information (S8025) in response to receiving input of communication information from the end user on a screen for requesting communication information from the end user (S8012), and transmitting the generated authentication information to the end user based on the communication information; a step of presenting a screen for viewing and accepting consent to contract data to the end user (S9021) by receiving input of authentication information from the end user (S8013); and a step of managing the contract data by assuming that the end user has consented to the contract data in response to an operation (S9011) for accepting consent to the contract data from the end user (S9023).

[0139] (Appendix 6) An information processing device having a control unit, the information processing device for providing an electronic contract service to a user, the control unit issuing viewing information for viewing contract data in response to a call from an external service and having the issued viewing information presented to an end user of the external service (S8032), accepting input of communication information issued after identity verification from the external service as information required for identity verification of the end user (S8021), presenting a screen for requesting communication information to the end user in response to the end user referring to the viewing information (S8024), and an information processing device which executes the steps of: generating authentication information (S8025) in response to receiving input of communication information from an end user on the screen (S8012), and transmitting the generated authentication information to the end user based on the communication information; receiving input of authentication information from the end user (S8013), and presenting a screen for viewing and accepting consent to contract data to the end user (S9021); and managing the contract data as if the end user had consented to the contract data in response to an operation (S9011) of receiving consent to the contract data from the end user (S9023). (Appendix 7) A manufacturing method for a system for providing an electronic contract service to a user, the manufacturing method including providing a program that causes an information processing device having a control unit to execute the following steps: issue viewing information for viewing contract data in response to a call from an external service, and present the issued viewing information to an end user of the external service; accept input of communication information issued after identity verification from the external service as information required for identity verification of the end user; present a screen for requesting communication information to the end user in response to the end user referring to the viewing information; generate authentication information in response to accepting input of communication information from the end user on the screen for requesting communication information, and transmit the generated authentication information to the end user based on the communication information; accept input of authentication information from the end user, and present a screen for viewing and accepting consent to the contract data to the end user; and manage the contract data as if the end user has consented to the contract data in response to an operation of accepting consent to the contract data from the end user. [Explanation of symbols]

[0140] 1: Electronic contract system, 10: Terminal device of end user of external service, 12: Communication IF, 13: Input device, 14: Output device, 15: Memory, 16: Storage unit, 19: Processor, 20: Server of electronic contract service, 22: Communication IF, 23: Input / output IF, 25: Memory, 26: Storage, 29: Processor, 30: Server of external service, 32: Communication IF, 33: Input / output IF, 35: Memory, 36: Storage, 39: Processor, 80: Network, 111: Antenna, 121: First wireless communication unit, 130: Operation reception unit, 132: Display, 140: Audio processing unit, 141: Microphone, 142: Speaker, 161: Contract management information, 162: Contract information, 191: Input operation reception unit, 192: Transmitting / receiving unit, 193: Data processing unit, 194: notification control unit, 201: communication unit, 202: storage unit, 203: control unit, 2021: contract management database, 2022: contract database, 2031: reception control module, 2032: transmission control module, 2033: contract management information acquisition module, 2034: contract information acquisition module, 301: communication unit, 302: storage unit, 303: control unit, 3021: contract management database, 3022: contract database, 3023: end user database, 3031: reception control module, 3032: transmission control module, 3033: contract management information acquisition module, 3034: contract information acquisition module, 3035: end user information acquisition module, 40: receiver terminal device, 50: sender terminal device

Claims

1. A program for operating a computer, the computer is for providing an electronic contract service to a user; The program causes the processor of the computer to: receiving a request for contract conclusion regarding the authenticated end user of the external service from a server of the external service; receiving, from the external service, input of communication information issued after identity verification as information required for identity verification of the end user; issuing viewing information for allowing the contract data to be viewed in response to the request for the conclusion of the contract; presenting a screen to the end user requesting information for the communication in response to the end user referring to the browsing information; generating authentication information in response to receiving input of the communication information from the end user on the screen for requesting the communication information, and transmitting the generated authentication information to the end user based on the communication information; a step of accepting input of the authentication information from the end user and presenting a screen for the end user to view the contract data and accept consent; In response to an operation to accept consent to the contract data from the end user, the program executes a step of managing the contract data as if the end user had consented to the contract data.

2. In the managing step, The program according to claim 1, wherein the program presents to at least the end user information that proves that the end user has agreed to the contract data to which the end user has agreed, the proof information including the communication information entered by the end user.

3. In the step of presenting the browsing information to the end user, The program according to claim 1 , wherein the program responds with the browsing information to the external service in response to the call of the external service, thereby presenting the browsing information to the end user via the external service.

4. In the managing step, by transmitting information indicating that the end user has consented to the contract data to the external service, 4. The program according to claim 3, wherein information indicating that the consent has been given is presented to the end user via the external service.

5. 1. A method for operating a computer, comprising: the computer is for providing an electronic contract service to a user; The method includes causing a processor of the computer to: receiving a request for contract conclusion regarding the authenticated end user of the external service from a server of the external service; receiving, from the external service, input of communication information issued after identity verification as information required for identity verification of the end user; issuing viewing information for allowing the contract data to be viewed in response to the request for the conclusion of the contract; presenting a screen to the end user requesting information for the communication in response to the end user referring to the browsing information; generating authentication information in response to receiving input of the communication information from the end user on the screen for requesting the communication information, and transmitting the generated authentication information to the end user based on the communication information; a step of accepting input of the authentication information from the end user and presenting a screen for the end user to view the contract data and accept consent; In response to an operation from the end user to accept consent to the contract data, managing the contract data as if the end user had consented to the contract data.

6. An information processing device including a control unit, the information processing device is for providing an electronic contract service to a user, The control unit receiving a request for contract conclusion regarding the authenticated end user of the external service from a server of the external service; receiving, from the external service, input of communication information issued after identity verification as information required for identity verification of the end user; issuing viewing information for allowing the contract data to be viewed in response to the request for the conclusion of the contract; presenting a screen to the end user requesting information for the communication in response to the end user referring to the browsing information; generating authentication information in response to receiving input of the communication information from the end user on the screen for requesting the communication information, and transmitting the generated authentication information to the end user based on the communication information; a step of accepting input of the authentication information from the end user and presenting a screen for viewing the contract data and accepting consent to the end user; In response to an operation of accepting consent to the contract data from the end user, managing the contract data as if the end user had consented to the contract data.

7. 1. A method for manufacturing a system for providing electronic contract services to a user, comprising: An information processing device including a control unit, receiving a request for contract conclusion regarding the authenticated end user of the external service from a server of the external service; receiving, from the external service, input of communication information issued after identity verification as information required for identity verification of the end user; issuing viewing information for allowing the contract data to be viewed in response to the request for the conclusion of the contract; presenting a screen to the end user requesting information for the communication in response to the end user referring to the browsing information; generating authentication information in response to receiving input of the communication information from the end user on the screen for requesting the communication information, and transmitting the generated authentication information to the end user based on the communication information; a step of accepting input of the authentication information from the end user and presenting a screen for viewing the contract data and accepting consent to the end user; A method for manufacturing a system, including providing a program that executes a step of managing the contract data as if the end user had agreed to the contract data in response to an operation from the end user accepting consent to the contract data.

Images