Trade certification system, trade certification device, and trade certification method

Abstract

To make it possible to issue a receipt certifying contents of a transaction as electronic data and manage whether the receipt is issued as electronic data.SOLUTION: A transaction proof system 1 has a configuration in which a transaction data management unit 2 that generates and manages transaction data indicating transaction contents, a user terminal 3 used by a user of the transaction proof system 1, a transaction proof unit 4 that issues a receipt certifying the transaction contents as electronic data, and an advertisement server 5 that generates advertisement data indicating an advertisement are connected to each other via a communication network 100 that transmits data by wired and wireless communication lines. A transaction management server 24 and a transaction proof server 44 may be directly connected to each other without going through the communication network 100.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a transaction certification system, a transaction certification device, and a transaction certification method. [Background technology]

[0002] For example, Patent Document 1 discloses a device that processes data that certifies the contents of a transaction, issues a receipt, and manages the receipt in association with a status indicating whether the receipt has been issued. However, while the device disclosed in Patent Document 1 is suitable for printing and issuing data that certifies the contents of a transaction as a receipt, it is not suitable for issuing a receipt as electronic data and further managing whether the receipt has been issued as electronic data. In addition, it may be necessary to affix a revenue stamp to the printed receipt. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2017-139022 A Summary of the Invention [Problem to be solved by the invention]

[0004] The present invention has been made to solve the above-mentioned problems, and aims to issue proof of transaction contents as electronic data and to make it possible to manage whether or not it has been issued as electronic data. [Means for solving the problem]

[0005] In order to achieve the above object, the proof-of-transaction system of the present invention comprises: A transaction certification system comprising: a registration device that registers transaction details; a transaction management device; a transaction certification device; a first terminal device that specifies a transaction and requests the transaction certification device to certify the transaction details; and a second terminal device that receives and displays certification data transmitted by the transaction certification device in response to the certification request from the first terminal device, The transaction management device receives transaction details from the registration device, and stores transaction data including the received transaction details and a transaction identifier in a transaction database; the first terminal device transmits a transmission request to the transaction management device, the transmission request including designation data that designates the transaction data, and requests transmission of the transaction data; the transaction management device receives a transmission request sent from the first terminal device, retrieves from the transaction database the transaction data designated by the designation data included in the received transmission request, and transmits the retrieved transaction data to the first terminal device that originated the request; The first terminal device management device receives the transaction data transmitted in response to the transmission request, and displays it as an electronic receipt, the first terminal device designates a transaction and requests the transaction certification device to certify the contents of the designated transaction; The transaction certification device A transaction management device is provided separately from the transaction management device, in response to a request for certification from the first terminal device, reads out transaction data of a specified transaction from the transaction database, generates certification data for certifying the content of the transaction included in the read transaction data, and transmits the certification data to the second terminal device; A transaction identifier and a proof of transaction data are sent to the second terminal device. issue storing management data including information indicating whether the authentication was successful or not in a certification database; The transaction certification device generates the certification data when a certification request is received from the first terminal device, on condition that the management data for a specified transaction indicates that the certification data has not been issued. when transmitting the certification data to the second terminal device, changing information in the management data indicating whether the certification data has been issued to the second terminal device to "issued"; The certification data is data different from the electronic receipt and is certification data in the form of a receipt. . Effect of the Invention

[0006] In the transaction certification system configured as above, the transaction data that certifies the contents of the transaction corresponds to a certificate or receipt. This is issued as electronic data, and it is possible to manage whether or not a receipt has been issued. [Brief description of the drawings]

[0007] [Figure 1] 1 is a diagram showing a configuration of a transaction proof system according to the present invention. [Diagram 2] A diagram showing a summary data request sent by a user terminal to a transaction management server. [Diagram 3] 3 is a diagram illustrating an example of a display screen of summary data transmitted by the transaction management server in response to the summary data request shown in FIG. 2. [Figure 4] 2 is a diagram showing a proof data issuance request sent by the user terminal shown in FIG. 1 to a transaction proof server of the transaction proof unit. [Diagram 5] 2 is a diagram illustrating a display screen of proof data generated by the user terminal shown in FIG. 1; [Figure 6] 2 is a diagram illustrating an example of the contents of transaction data transmitted from the registration device shown in FIG. 1 to the transaction management server. [Figure 7] 2 is a diagram illustrating an example of a display screen of transaction data transmitted from the registration device shown in FIG. 1 to the transaction management server. [Figure 8] 2 is a diagram showing a configuration of a transaction management server shown in FIG. 1. [Figure 9] 9 is a diagram showing storage data generated by the transaction data processing device shown in FIG. 8 and stored in a transaction DB. [Figure 10] 2 is a diagram illustrating a configuration of a transaction proof server illustrated in FIG. 1. [Figure 11] 11 is a diagram showing management data generated by the management data generating device shown in FIG. 10. [Figure 12] FIG. 1 is a first sequence diagram showing the operation of the proof-of-transaction system. [Figure 13] FIG. 2 is a second sequence diagram showing the operation of the proof-of-transaction system. [Figure 14] FIG. 11 is a third sequence diagram showing the operation of the proof-of-transaction system. [Figure 15] FIG. 4 is a fourth sequence diagram showing the operation of the proof-of-transaction system. [Figure 16]2 is a diagram showing the configuration of a first registration system used in place of a registration device in the proof-of-transaction system shown in FIG. 1. [Figure 17] 2 is a diagram showing the configuration of a second registration system used in place of the registration device in the proof-of-transaction system shown in FIG. 1. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] [Transaction Proof of Origin System 1] A transaction proof system 1 according to an embodiment of the present invention will now be described with reference to the drawings. In the following embodiments, the same components are given the same reference numerals.

[0009] First, the overall configuration of the transaction certification system 1 will be described. Fig. 1 is a diagram showing the configuration of the transaction certification system 1 according to this embodiment. As shown in Fig. 1, the transaction certification system 1 is configured such that a transaction data management unit 2 that generates and manages transaction data indicating the contents of a transaction, a user terminal 3 used by a user of the transaction certification system 1, a transaction certification unit 4 that issues receipts as electronic data verifying the contents of a transaction, and an advertising server 5 that generates advertising data indicating advertisements are all connected via a communications network 100 that transmits data via wired communications lines and wireless communications lines. The transaction management server 24 and the transaction certification server 44 may be connected directly without going through the communications network 100.

[0010] Using these components, the transaction certification system 1 generates transaction data for each transaction indicating the subject of the transaction and its value, includes advertisements in the transaction data, processes the transaction data, and issues certification data in the form of a receipt.

[0011] The transaction proof system 1 may include two or more user terminals 3 and two or more viewer terminals 40. Two or more of the transaction management server 24, the transaction proof server 44 and the advertising server 5 may be integrated.

[0012] The transaction data management unit 2 includes registration devices 20-1 to 20-m provided for transactors #1 to #m, respectively, who transfer money to and from one another, such as selling goods and providing services, and a transaction management server 24 that manages transaction data indicating the contents of transactions. Note that m is an integer of 2 or more, and when referring to any of the registration devices 20-1 to 20-m without specifying it, the subscripts are omitted and the device is simply referred to as "registration device 20." Similarly, the subscripts of the symbols attached to other components may be omitted as appropriate.

[0013] The transaction certification unit 4 includes a viewer terminal 40 used by a viewer who views the certification data, and a transaction certification server 44 that issues the certification data.

[0014] Next, we will explain each of the components of the transaction proof system 1. The user terminal 3 is realized as a dedicated information processing device, or as a combination of a general-purpose information processing device such as a personal computer or a smartphone and an application program.

[0015] Fig. 2 is a diagram showing a summary data request sent by the user terminal 3 to the transaction management server 24. Fig. 3 is a diagram showing an example of a display screen of summary data sent by the transaction management server 24 in response to the summary data request shown in Fig. 2.

[0016] The user terminal 3 transmits authentication data used to authenticate the user terminal 3 to the transaction management server 24, performs authentication processing with the transaction management server 24, and accesses the transaction management server 24. The user terminal 3 also transmits a summary data request requesting the transmission of summary data shown in Fig. 2, receives the summary data transmitted by the transaction management server 24 in response to this request, and displays it to the user as shown in Fig. 3.

[0017] Furthermore, in response to a user's operation on the displayed summary data, the user terminal 3 generates a proof data issuance request for requesting the issuance of proof data in the form of a receipt, and transmits the request to the transaction proof server 44 of the transaction proof unit 4.

[0018] 2, the summary data request includes a destination address, a source address, a summary request, and specified data. In the summary data request, the destination address indicates the address of the transaction management server 24 to which the data is to be sent.

[0019] The sender address indicates the address of the user terminal 3. The summary request requests the transaction management server 24 to send summary data. The specified data specifies which transaction summary data is requested. The specified data may be, for example, a hash value obtained by converting part or all of the transaction data, or part or all of the summary data input from the transaction management server 24, using a hash function. The hash function used to generate the specified data is, for example, SHA-2 (Secure Hash Algorithm-2), more specifically, SHA-255.

[0020] As shown in parentheses in Figure 2, the summary data request can be used as a transaction data request or a confirmation data request by replacing it with a transaction data request requesting transaction data, or a confirmation data request requesting confirmation of the proof data.

[0021] As shown in Fig. 3, the summary data summarizes part of the contents of the transaction specified by the specified data. In Fig. 3, the consumption tax rate is 10%, and each of the multiple entries contained in the summary data includes the date of the transaction, the transactor (X department store), the location of the transaction (Tokyo store, Osaka store, Kyoto store), the total amount paid by the transactor's trading partner ((M+Q) x 1.1, V x 1.1, W x 1.1), and the trading partner ID (customer number), all of which are associated with each other. The summary data may also be a list of the contents of the transaction.

[0022] Each of the multiple entries on the summary data display screen is used as a GUI (Graphical User Interface) button that requests the transaction proof server 44 to issue a receipt corresponding to that entry, and when proof data in the form of a receipt corresponding to that entry has already been issued, an input section indicating this (receipt not yet issued / receipt issued) is provided. Additionally, the summary data display screen has an input section (viewer designated) that indicates the address of the destination of the proof data issued by the transaction proof server 44.

[0023] Fig. 4 is a diagram showing a proof data issuance request sent by the user terminal 3 shown in Fig. 1 to the transaction proof server 44 of the transaction proof unit 4. The proof data issuance request is sent from the user terminal 3 to the transaction management server 24 in response to an operation on the input section "receipt not issued" shown in Fig. 3. As shown in Fig. 4, the proof data issuance request includes a destination address, a sender address, issuance request data, user data, a display destination address, access restriction data, and designated data.

[0024] In the proof data issuance request, the destination address indicates the address of the destination transaction proof server 44. The source address indicates the address of the user terminal 3. The issuance request data requests the transaction proof server 44 to issue proof data in the form of a receipt.

[0025] Note that after an operation is performed on the input section "receipt not issued" of any of the multiple entries shown in Figure 3, a proof data issuance request is sent to the transaction proof server 44, and proof data in the form of a receipt corresponding to this entry is issued, the message "receipt issued" is displayed in this input section. Note that the display contents in the input sections of "receipt not issued" and "receipt issued" are merely examples, and other character strings or symbols may be used as appropriate.

[0026] The user data uniquely indicates the user terminal identifier attached to the trading partner of traders #1-#m using the user terminal 3 or to the user terminal 3. The display destination address is specified by the input section "viewer specification" of the summary data shown in Fig. 3, and indicates the address of the display destination user terminal 3 or transaction certification unit 4 that displays the certification data in the form of a receipt.

[0027] The access restriction data indicates one or more restrictions on access to the proof data, such as whether the display destination user terminal 3 or transaction certification unit 4 can access the proof data, the number of times the proof data is permitted to be displayed, the period for which it is displayed, and whether printing is permitted. The designation data specifies which transaction content is to be certified.

[0028] Fig. 5 is a diagram showing an example of a display screen of proof data generated by the user terminal 3 shown in Fig. 1. The user terminal 3 transmits the proof data issuance request shown in Fig. 4 to the transaction proof server 44, which generates proof data and transmits it to the user terminal 3 or the viewer terminal 40. When the transaction proof system 1 includes multiple user terminals 3, the user terminal 3 may transmit the proof data to the user terminal 3 that transmitted the proof data issuance request itself, or to another user terminal 3.

[0029] If the display destination address indicates the address of the user terminal 3 itself, the proof data is transmitted from the transaction proof server 44 to the user terminal 3. The user terminal 3 receives the proof data transmitted by the transaction proof server 44, and displays it to the user in the form of a receipt as shown in Fig. 5, within the range of access restrictions indicated by the access restriction data shown in Fig. 4.

[0030] As shown in Fig. 5, the display screen of the proof data includes data indicating a link indicating a verification address in a format such as a Uniform Resource Locator (URL) and a QR code (registered trademark) that is used by the user of the user terminal 3 or the viewer using the viewer terminal 40 to verify the contents of the proof data. This verification address is associated with the same hash value as the specified data included in the summary data request shown in Fig. 2.

[0031] The viewer terminal 40 shown in Fig. 1 is realized as a dedicated information processing device or as a combination of a general-purpose information processing device such as a personal computer or a smartphone and an application program, similar to the user terminal 3. The viewer terminal 40 displays to the user, as shown in Fig. 5, the proof data that is generated by the transaction proof server 44 in response to the proof data issuance request from the user terminal 3 shown in Fig. 4 and transmitted to the transaction proof server 44.

[0032] The registration device 20 of the transaction data management unit 2 is a cash register device, a POS (Point Of Sale) terminal device, or the like, capable of data communication with the transaction management server 24 via the communication network 100. Every time a transactor #1-#m carries out a transaction with a trading partner, the registration device 20 generates transaction data in response to the transactor's operation of the registration device 20, and transmits the transaction data to the transaction management server 24.

[0033] For the sake of concreteness and clarity of explanation, the drawings illustrate an example in which transactors #1 to #m are retailers such as department stores, and their trading partners are individuals. Fig. 6 is a diagram illustrating the contents of transaction data transmitted from registration device 20 shown in Fig. 1 to transaction management server 24. Fig. 7 is a diagram illustrating a display screen of transaction data transmitted from registration device 20 shown in Fig. 1 to transaction management server 24.

[0034] The structure of the transaction data transmitted from the registration device 20 to the transaction management server 24 may be determined arbitrarily by each of the traders #1 to #m, and does not have to be standardized for all of the traders #1 to #m. However, the structure of the transaction data is standardized at the stage of being stored in the transaction management server 24.

[0035] 7 is also called an electronic receipt. An electronic certificate such as an electronic watermark may be inserted into one or more of the summary data and transaction data sent to the user terminal 3 and the certification data sent to the user terminal 3 or the viewer terminal 40, as appropriate.

[0036] As shown in Figures 6 and 7, the transaction data includes a transaction identifier (transaction ID), transaction partner data, transactor data, location data, date and time data, total amount excluding tax data, total payment data and form data, as well as product data #1-#n, name data #1-#n, quantity data #1-#n, unit price data #1-#n, tax amount data #1-#n and total amount data #1-#n, which are associated with number data #1-#n, respectively.

[0037] Here, n is an integer equal to or greater than 1. In addition, the part of the transaction data other than the transaction partner data is also referred to as content data.

[0038] In the transaction data, the transaction ID uniquely identifies each transaction carried out by a transactor #1 to #m. The transaction partner data is obtained, for example, when an individual transactor's transacting partner purchases an item using a point card. The transaction partner data indicates attributes of the transacting partner, such as the transaction partner ID that uniquely identifies the transacting partner in each transaction, the name (appellation) of the transacting partner, the name (appellation), date of birth, and gender, and the user terminal ID that uniquely indicates the user terminal 3 used by the transacting partner.

[0039] The transaction ID uniquely identifies each transaction performed by a trader #1 to #m. The trader data indicates the name of one of the traders #1 to #m who performed the transaction. To give specific examples, the trader data is names such as "Supermarket A," "Drugstore B," "Department Store C," "Discount Store D," "Convenience Store E," and "Holding Company F." Note that it does not have to be a name, and any information that can identify the trader may be used, such as code information. The contents of the trader data can be set arbitrarily depending on the specifications of the transaction certification system 1, and in addition to the name of the trader, it may further include brand names when the trader has multiple brands.

[0040] The location data indicates the location where the transaction was conducted when any of the transactors #1 to #m who conducted the transaction can conduct the transaction at multiple locations. As a specific example, the location data indicates the names and locations of stores such as "Supermarket A," "Drug Store B," "Department Store C," "Discount Store D," and "Convenience Store E," or indicates the names and locations of companies under "Holding Company F."

[0041] The date and time data indicates the date and time when the transaction was made. The total amount excluding tax data indicates the total amount of money excluding tax that any of transactors #1 to #m received from the counterparty in the transaction. The total tax data indicates the total amount of tax that any of transactors #1 to #m received from the counterparty in the transaction.

[0042] The total payment data indicates the total amount, including tax, received by any of transactors #1 to #m from the counterparty in the transaction. The form data indicates the format (form) in which the transaction data shown in FIG. 6 is displayed as shown in FIG. 7.

[0043] Number data #1 to #n indicate serial numbers assigned to the n types of goods and services that were the subject of a transaction. Product data #1 to #n indicate the names of the n types of goods and services that were the subject of a transaction. Quantity data #1 to #n indicate the quantities (number of pieces) of the n types of goods and services that were the subject of a transaction.

[0044] Unit price data #1 to #n indicate the unit price of each of the n types of goods and services involved in the transaction. Tax amount data #1 to #n indicate the tax amount paid by the trading partner for each of the n types of goods and services involved in the transaction. Total amount data #1 to #n indicate the total amount paid by the trading partner for each of the n types of goods and services involved in the transaction.

[0045] The advertisement data is generated by the advertisement server 5 shown in Fig. 1 according to the attributes of the trading partner indicated by the trading partner data. The advertisement data indicates, for example, the content of the advertisement to be displayed at the position specified by the form data on the receipt when the transaction data is displayed in the form of a so-called receipt as shown in Fig. 7.

[0046] Fig. 8 is a diagram showing the configuration of the transaction management server 24 shown in Fig. 1. As shown in Fig. 8, the transaction management server 24 includes a communication device 240 that performs data communication with other components via the communication network 100, a transaction data processing device 242, a transaction database (transaction DB) 244, an authentication device 246, a data generation device 248, and a trader data processing device 250.

[0047] The transaction management server 24 provides a web server function for the registration device 20. Using these components, the transaction management server 24 manages and stores the transaction data input from the registration device 20, as shown in Figures 1 and 6. The transaction data stored and managed by the transaction management server 24 is used for processing by the transaction proof server 44.

[0048] The transaction management server 24 also receives a summary data request from the user terminal 3 shown in Fig. 2, generates summary data showing the contents of the summary data display screen shown in Fig. 3 in accordance with the contents of the received summary data request, and transmits it to the user terminal 3 that issued the summary data request. The transaction management server 24 also receives a transaction data request from the user terminal 3 shown in Fig. 3, and transmits the transaction data specified by the transaction request to the user terminal 3.

[0049] In the transaction management server 24, the communication device 240 performs data communication with the registration device 20 and the user terminal 3 shown in FIG. 1 via the communication network 100. The communication device 240 receives the transaction data shown in FIG. 6 from the registration device 20 and outputs it to the transaction data processing device 242.

[0050] 2 from the user terminal 3, and outputs them to the data generating device 248. The communication device 240 also receives authentication data from the user terminal 3, and outputs them to the authentication device 246.

[0051] The communications device 240 also receives from the transaction data processing device 242 transaction data generated in response to the receipt of a transaction data request, and transmits the transaction data to the user terminal 3. The communications device 240 also receives from the transaction data processing device 242 summary data generated in response to the receipt of a summary data request shown in FIG. 2 and displayed as shown in FIG. 3, and transmits the summary data to the user terminal 3.

[0052] Fig. 9 is a diagram showing storage data generated by the transaction data processing device 242 shown in Fig. 8 and stored in the transaction DB 244. The trader data and content data shown in Fig. 9 are the same as the transaction data shown in Fig. 6.

[0053] 9, the transaction data processing device 242 generates p entries by associating the transaction data ID and the advertisement data input from the advertisement server 5 with each of the p transaction data input from the communication device 240, and stores the entries in the transaction DB 244 together with the storage data. Note that p is an integer of 2 or more.

[0054] The authentication device 246 uses the authentication data input from the communication device 240 to authenticate the user terminal 3 that transmitted the authentication data and its user, and notifies other components of the authentication result. Note that the authentication by the authentication device 246 may be performed by a method using a user ID and a password, or may be performed by a method that performs two-stage authentication.

[0055] The data generating device 248 reads out one or more entries of the stored data specified by the designation data of the summary data request shown in Fig. 2 in response to a summary data request input from a user terminal 3 authenticated by the authentication device 246. The data generating device 248 generates summary data using part of the transaction data included in the one or more read entries, and transmits the summary data via the communication device 240 and the communication network 100 to the user terminal 3 and transaction proof unit 4 that sent the summary data request.

[0056] Furthermore, in response to a transaction data request input from a user terminal 3 authenticated by the authentication device 246, the data generating device 248 reads out an entry of the stored data designated by the designation data included in the transaction data. The data generating device 248 uses the transaction data and advertisement data included in the read entry to generate transaction data displayed as shown in Fig. 7, and transmits the generated transaction data via the communication device 240 and the communication network 100 to the user terminal 3 that sent the transaction data request.

[0057] The trader data processing device 250 processes the trader data included in the transaction data input from the registration device 20 via the communication network 100 and the communication device 240, generates attribute data indicating attributes of the trading partner, and transmits it to the advertisement server 5. Note that the trader data processing device 250 may transmit the attribute data to the advertisement server 5 only when, for example, it receives designation of attribute data from the advertisement server 5 and generates the designated attribute data.

[0058] Fig. 10 is a diagram showing the configuration of the transaction proof server 44 shown in Fig. 1. As shown in Fig. 10, the transaction proof server 44 includes a communication device 240, an authentication device 246, a management data generation device 440, a proof data generation device 442, a proof DB 444, and a verification device 446.

[0059] The transaction proof server 44 provides a function as a web server for the user terminal 3 and the viewer terminal 40. Using these components, the transaction proof server 44 performs authentication processing between the user terminal 3 or the viewer terminal 40.

[0060] In response to receiving the proof data issuance request shown in Fig. 4 from the user terminal 3, the transaction proof server 44 reads the transaction data shown in Fig. 6 from the transaction management server 24, attaches access restriction data, and generates proof data that proves the contents of each transaction shown in Fig. 5. The transaction proof server 44 also generates and stores management data indicating whether or not the proof data for each transaction has been issued to the user terminal 3 or the viewer terminal 40. The issuance of proof data more specifically means that the proof data has been sent to the user terminal 3 or the viewer terminal 40.

[0061] Furthermore, the transaction certification server 44 issues and manages certification data based on the stored management data. Note that the transaction certification server 44 does not need to store the transaction data shown in FIG.

[0062] In the transaction proof server 44, the communication device 240 receives the proof data issuance request shown in Fig. 4 from the user terminal 3 and outputs it to the management data generation device 440 and the proof data generation device 442. The communication device 240 also receives the confirmation data request described with reference to Fig. 2 from the user terminal 3 and outputs it to the confirmation device 446. The communication device 240 also receives the transaction data shown in Fig. 6 from the confirmation device 446 and transmits it as summary data to the user terminal 3 via the communications network 100.

[0063] The communication device 240 also receives proof data generated by the proof data generating device 442 and transmits it to the user terminal 3 via the communication network 100. Similarly to the transaction management server 24, the communication device 240 also receives authentication data from the user terminal 3 and outputs it to the authentication device 246.

[0064] Fig. 11 is a diagram showing management data generated by the management data generating device 440 shown in Fig. 10. The management data generating device 440 processes an authentication data issuance request from the user terminal 3 authenticated by the authentication device 246, generates the management data shown in Fig. 11, and stores it in the certification DB 444.

[0065] As shown in Figure 11, each entry of p included in the management data includes the transaction data ID shown in Figure 9, a hash value corresponding to the specified data included in the proof data issuance request shown in Figure 4, unissued / issued data, confirmation data, access restriction data, viewer / count data, and issue time data.

[0066] As described with reference to Fig. 5, a hash value may be used as the verification address. In this case, the verification data may be omitted by setting the value of the verification address to be the same as the hash value.

[0067] In the management data, the unissued / issued data indicates whether or not proof data has been issued in response to a request from the user terminal 3. The confirmation data is an address in a format such as a URL used to refer to transaction data used by the user of the user terminal 3 or the viewer terminal 40 to confirm the contents of the proof data. The access restriction data is the same as the access restriction data included in the proof data issuance request shown in FIG. 4.

[0068] The viewer / count data indicates the user terminal 3 or viewer terminal 40 that received and displayed the proof data, its user (viewer), and the number of times the proof data was issued. The issue count data indicates the number of times the transaction proof unit 4 has issued proof data.

[0069] When the proof data generation device 442 receives a proof data issuance request from a user terminal 3 authenticated by the authentication device 246, it reads out from the proof DB 444 an entry of management data including a hash value corresponding to the specified data shown in Fig. 4. The proof data generation device 442 judges whether the access restriction data in the read management data entry permits the user terminal 3 or viewer terminal 40 to which the proof data is to be sent to access the proof data.

[0070] When the user terminal 3 or the viewer terminal 40 is permitted to access the proof data and the unissued / issued data is a value indicating unissued, the proof data generation device 442 reads the transaction data, including the transaction data ID contained in the read entry, from the management data generation device 440 of the transaction proof server 44 shown in Figure 8.

[0071] Furthermore, the proof data generating device 442 generates proof data to which the access restriction data is added and which is displayed as shown in Fig. 5. The proof data generating device 442 transmits the proof data issuance request to the user terminal 3 or the viewer terminal 40 indicated by the display destination address shown in Fig. 4 via the communication device 240 and the communication network 100, and issues the request.

[0072] In addition, the proof data generating device 442 generates proof data that proves the transaction data of each entry included in the storage data shown in Figure 9 only once when the unissued / issued data has a value indicating unissued, and only for the user terminal 3 or viewer terminal 40 indicated by the display destination address of the proof data issuance request.

[0073] However, the proof data may be transmitted to the user terminal 3 or the viewer terminal 40 indicated by the display destination address of the proof data issuance request multiple times within the range permitted by the access restriction data. At this time, the proof data generating device 442 notifies the management data generating device 440 of the transmission of the proof data each time.

[0074] When the management data generating device 440 receives this notification for the first time, it changes the unissued / issued data shown in Fig. 11 from a value indicating unissued to a value indicating issued, and writes the date and time when the proof data was issued in the issue time data. In addition, the management data generating device 440 writes an address indicating the user terminal 3 or viewer terminal 40 to which the proof data is to be sent, and the number of times the proof data has been sent, in the viewer / count data.

[0075] When the confirmation device 446 receives a confirmation data request including a confirmation address from the user terminal 3 authenticated by the authentication device 246, it reads from the certification DB 444 an entry including the hash value used as this confirmation address.

[0076] The confirmation device 446 reads out the transaction data corresponding to the transaction data ID included in the read entry from the transaction DB 244 of the transaction management server 24. It causes the user terminal 3 that issued the confirmation data request to transmit the transaction data as summary data via the communication device 240 and the communication network 100. The user terminal 3 that receives this transaction data displays the received transaction data to show it to the user.

[0077] The operation of the transaction proof system 1 will now be described. Fig. 12 is a first sequence diagram showing the operation of the transaction proof system 1. As shown in Figs. 1 and 12, in steps S100-1 to S100-p, the registration devices 20-1 to 20-m transmit transaction data #1 to #p for each of p transactions carried out between transactors #1 to #m and their trading counterparties to the transaction management server 24. The data contained in each of the transaction data #1 to #p is as described with reference to Fig. 6.

[0078] In steps S102-1 to S102-p, the transaction management server 24 processes the transaction data #1 to #p received from the registration device 20. The transaction management server 24 outputs part of the management data obtained as a result of this processing, namely, the transaction data IDs #1 to #p, the hash values ​​#1 to #p, and the verification addresses #1 to #p, to the transaction certification server 44. Note that the management data is as described with reference to Fig. 11, and data other than this included in the management data can be set separately for the transaction certification server 44 as appropriate by the user, etc.

[0079] Fig. 13 is a second sequence diagram showing the operation of the transaction proof system 1. As shown in Fig. 1 and Fig. 13, in step S200, the user terminal 3 transmits authentication data to the transaction management server 24 in response to an operation by the user. In step S202, when the transaction management server 24 authenticates the user terminal 3 or its user, it transmits data to that effect to the user terminal 3.

[0080] In step S204, the authenticated user terminal 3 transmits a summary data request as shown in Fig. 2 to the transaction management server 24. In step S206, the transaction management server 24 transmits to the user terminal 3 the summary data to be displayed as described with reference to Fig. 3.

[0081] In step S206, the user terminal 3 selects one of the transaction data included in the summary data in response to a selection operation performed by the user on the display screen of the summary data. The user terminal 3 transmits the transaction data request described with reference to FIG. 2 to the transaction management server 24, with the designated data being a value indicating the selected transaction data.

[0082] In step S208, the transaction management server 24 receives a transaction data request from the user terminal 3. In step S210, the transaction management server 24 transmits the transaction data indicated by the designation data included in the received transaction data request to the user terminal 3. The user terminal 3 displays the transaction data from the transaction management server 24 and shows it to the user, as described with reference to FIG.

[0083] Fig. 14 is a third sequence diagram showing the operation of the transaction proof system 1. As shown in Figs. 1 and 14, in step S400, the advertisement server 5 sets conditions for generating attribute data in the transaction management server 24. In step S402, the transaction management server 24 generates attribute data that meets the set conditions, and then transmits the generated attribute data to the advertisement server 5.

[0084] In step S404, the advertisement server 5 generates advertisement data based on the attribute data indicating the attributes of the transaction partner, and transmits the advertisement data to the advertisement server 5. The transaction management server 24 generates and stores the storage data described with reference to Fig. 9 by associating the transaction data ID, the transaction data, and the advertisement data. When the processes of S400 to S404 are not performed, the advertisement data of the stored data is set to a value indicating that no advertisement exists.

[0085] Fig. 15 is a fourth sequence diagram showing the operation of the transaction certification system 1. As shown in Fig. 1 and Fig. 15, authentication processing is performed between the user terminal 3 and the transaction certification server 44 in steps S200 and S202.

[0086] In step S500, in response to the user's operation on the summary data display screen described with reference to FIG. 3, the authenticated user terminal 3 sets the specified data of the proof data issuance request described with reference to FIG. 4 as a value indicating the viewer terminal 40 and transmits it to the transaction proof server 44.

[0087] In steps S200 and S202, the viewer terminal 40 and the transaction proof server 44 perform authentication processing in response to the viewer's operation.

[0088] In step S502, the authenticated transaction proof server 44 transmits proof data having the contents described with reference to Fig. 5 to the viewer terminal 40. The viewer terminal 40 displays the proof data to show it to the viewer. Note that the viewer can also operate the viewer terminal 40 to print the received proof data if the access restriction data attached to the proof data allows it.

[0089] In step S504, viewer terminal 40 transmits to transaction proof server 44 a request for confirmation data as described with reference to FIG.

[0090] In step S506, the transaction certification server 44 reads from the transaction management server 24 the transaction data indicated by the designation data included in the confirmation data request.

[0091] In step S508, the transaction certification server 44 transmits the transaction data read from the transaction management server 24 to the viewer terminal 40. The viewer terminal 40 displays the transaction data from the transaction certification server 44 to the viewer for confirmation.

[0092] In addition, in the fourth sequence diagram shown in Figure 15, it will be easy for a person skilled in the art to understand the process of sending certification data from the transaction certification server 44 to the user terminal 3 by changing the information transmitted and received between the viewer terminal 40 and the transaction certification server 44 to information transmitted and received between the user terminal 3 and the transaction certification server 44.

[0093] In the above embodiment, the transaction certification system 1 is an example of a transaction certification system as claimed, the registration device 20 is an example of a registration device as claimed, the transaction DB 244 is an example of a transaction database as claimed, the transaction certification server 44 is an example of a transaction certification device as claimed, the certification DB 444 is an example of a certification database as claimed, the user terminal 3 is an example of a first terminal device as claimed, the viewer terminal 40 is an example of a second terminal device as claimed, and the data generation device 248 is an example of a summary data generation device as claimed.

[0094] [Variations] Below, a description will be given of a modified example of the registration device 20 shown in Fig. 1. Fig. 16 is a diagram showing the configuration of a registration system 6 used in place of the registration device 20 in the transaction proof system 1 shown in Fig. 1. As shown in Fig. 16, the registration system 6 includes trader systems 50-1 to 50-m provided for traders #1 to #m, respectively, and a transaction management server 24.

[0095] The trader systems 50-1 to 50-m include brand systems 52-1-1 to 52-1-r, . . . , 52-m-1 to 52-mr that are provided corresponding to the brands #1 to #r owned by the traders #1 to #m, respectively. The brand systems 52-1-1 to 52-1-r, . . . , 52-m-1 to 52-mr include registration devices 20-1-1-1 to 20-1-1-q, . . . , 20-mr-1 to 20-mrq, and registration servers 56-1-1 to 56-1-q, . . . , 56-m-1 to 56-mq.

[0096] Here, q and r are integers of 1 or more that may differ for each trader system 50 and brand system 52. For convenience of illustration, FIG. 16 omits all components other than the registration devices 20-1-1-1 to 20-1-1-q, the brand systems 52-1-1 to 52-1-r, and the registration servers 56-1-1 to 56-1-r.

[0097] In the registration system 6, the registration device 20 is a cash register device, a POS terminal device, or the like, similar to the registration device 20 in the transaction proof system 1. For each transaction, the registration device 20 generates transaction data in response to the transactor's operation on the registration device 20, and transmits the transaction data to the registration server 56. The registration server 56 receives and stores the transaction data from the registration device 20, and transmits the stored transaction data to the transaction management server 24 by file linkage at predetermined time intervals or in response to a request from the transaction management server 24.

[0098] Fig. 17 is a diagram showing the configuration of a registration system 7 used in place of the registration device 20 in the transaction proof system 1 shown in Fig. 1. As shown in Fig. 17, the registration system 7 includes trader systems 60-1 to 60-m provided for traders #1 to #m, respectively, and a transaction management server 24.

[0099] The trader systems 60-1 to 60-m include registration devices 20-1-1 to 20-1-q, . . . , 20-m-1 to 20-mq and registration servers 62-1 to 62-m. For convenience of illustration, some of the components of the registration system 7 are omitted in FIG. 17 as in FIG. 16.

[0100] In the registration system 7, the registration device 20 generates transaction data for each transaction in response to the trader's operation on the registration device 20, and transmits the transaction data to the registration server 62. The registration server 62 receives and stores the transaction data from the registration device 20, and transmits the stored transaction data to the transaction management server 24 via API linkage at predetermined time intervals or in response to a request from the transaction management server 24. Note that a combination of parts of the components of the registration systems 6 and 7 can also be used in the transaction proof system 1 instead of the registration system 6.

[0101] Although the embodiment of the present invention has been described, this embodiment is presented as an example and is not intended to limit the scope of the invention. This novel embodiment can be embodied in various other forms, and various omissions, substitutions, and modifications can be made without departing from the gist of the invention. This embodiment and its modifications are included in the scope and gist of the invention, and are included in the scope of the invention and its equivalents described in the claims. [Explanation of symbols]

[0102] 1 transaction proof system, 2 transaction data management unit, 20 registration device, 24 transaction management server, 5 advertising server, 240 communication device, 242 transaction data processing device, 244 transaction DB, 246 authentication device, 248 data generation device, 3 user terminal, 4 transaction proof unit, 40 viewer terminal, 44 transaction proof server, 440 management data generation device, 442 proof data generation device, 444 proof DB, 446 confirmation device, 6, 7 registration system, 50, 60 trader system, 52 brand system, 56, 62 registration server, 100 communication network.

Claims

1. A transaction certification system comprising: a registration device that registers transaction details; a transaction management device; a transaction certification device; a first terminal device that specifies a transaction and requests the transaction certification device to certify the details of the transaction; and a second terminal device that receives and displays certification data transmitted by the transaction certification device in response to the certification request from the first terminal device, The transaction management device receives transaction details from the registration device, and stores transaction data including the received transaction details and a transaction identifier in a transaction database; the first terminal device transmits a transmission request to the transaction management device, the transmission request including designation data for designating the transaction data, and requests transmission of the transaction data; the transaction management device receives a transmission request sent from the first terminal device, retrieves from the transaction database transaction data designated by designation data included in the received transmission request, and transmits the transaction data to the first terminal device that originated the request; the first terminal device receives the transaction data transmitted by the transaction management device in response to the transmission request, and displays the data as an electronic receipt; the first terminal device designates a transaction and requests the transaction certification device to certify the contents of the designated transaction; The transaction certification device A transaction management device is provided separately from the transaction management device, in response to a request for certification from the first terminal device, reads out transaction data of a specified transaction from the transaction database, generates certification data for certifying the content of the transaction included in the read transaction data, and transmits the certification data to the second terminal device; storing management data in a certification database, the management data including a transaction identifier and information indicating whether certification data for the transaction has been issued to the second terminal device; the transaction certification device, upon receipt of a certification request from the first terminal device, generates the certification data on condition that the management data of the specified transaction indicates that the certification data has not been issued, and, upon transmitting the certification data to the second terminal device, changes information in the management data indicating whether the certification data has been issued to the second terminal device to "issued," The certification data is data different from the electronic receipt and is certification data in the form of a receipt. Proof-of-Trade system.

2. the first terminal device displays information indicating whether the proof data has been issued for the transaction data stored in the transaction database; 2. The transaction proof system of claim 1.

3. each of the first terminal devices transmits attribute data indicating attributes of the user to the transaction management device; The transaction management device includes: storing the attribute data received from the first terminal device and the advertisement data corresponding to the attribute data in the transaction database in association with the transaction data; In response to the received transmission request, transmit to the first terminal device the transaction data of the transaction related to the first terminal device and the advertising data associated with the transaction data in association with each other; the first terminal device, in response to a request for displaying the transaction data including the identifier of the first terminal device, receives from the transaction database advertisement data indicating an advertisement transmitted in association with the transaction data, and further displays the advertisement data.

3. The proof-of-transaction system of claim 2.

4. A summary data generating device is further provided, A unique identifier is assigned to each of the first terminal devices; the transaction database further stores an identifier of the first terminal device related to each of the transactions in association with the transaction data; The first terminal device is sending a request to the summary data generator for displaying the transaction data, the request including an identifier of the first terminal device; receiving and displaying summary data indicating a summary of the transaction data of the transaction related to the first terminal device, the summary data being transmitted from the summary data generating device in response to the transmitted display request; the summary data generating device generates the summary data relating to the first terminal device in response to a request for display of the transaction data including an identifier of the first terminal device, and transmits the summary data to the first terminal device; 4. A transaction proof-of-transaction system according to claim 1, 2 or 3.

5. The first terminal device is Accepting an operation of selecting the transaction for the displayed summary data; sending a request for certification of the contents of the transaction to the transaction certification device, specifying the transaction selected by the accepted selection operation; 5. The transaction proof system of claim 4.

6. Each of the summary data is assigned a unique identifier; The identifier included in the management data is an identifier of the summary data, the first terminal device transmits a request for certification of contents including an identifier of the selected summary data to the transaction certification device to designate the transaction as a subject of certification of contents; 6. The transaction proof system of claim 5.

7. The unique identifier assigned to each of the summary data is a hash value of at least a portion of the transaction data or each of the summary data.

7. The transaction proof system of claim 6.

8. The first terminal device is further accepting input of an address of the second terminal device; requesting from the transaction certification device a certification of the contents of the transaction, further including the address of the second terminal device that accepted the transaction; the transaction certification device transmits certification data for certifying the specified content of the transaction to the second terminal device indicated by the address included in the certification of the content of the transaction; A transaction proof system according to any one of claims 1 to 7.

9. The authentication database further stores an address of the transaction data corresponding to each of the transaction data; the second terminal device transmits a request for verification of the transaction data, including the address of the transaction data, to the transaction certification device; the transaction certification device transmits to the second terminal device the transaction data corresponding to an address of the transaction data included in a request for confirmation of the transaction data from the second terminal device; A transaction proof system according to any one of claims 1 to 8.

10. the first terminal device receives and displays, on behalf of the second terminal device, the certification data transmitted by the transaction certification device in response to a certification request; A transaction proof system according to any one of claims 1 to 9.

11. the request for certification of the transaction content includes access restriction data indicating a restriction of access to the certification data; the transaction certification device permits the second terminal device to access the certification data within the scope of restrictions imposed by the access restriction data included in the certification request from the first terminal device; A transaction proof system according to any one of claims 1 to 10.

12. the access restriction data indicating one or more of whether the second terminal device can access the transaction data, the number of times the transaction data is displayed, the duration of the display of the transaction data, and whether the transaction data is printable; 12. A transaction proof system as claimed in claim 11.

13. a transaction certification system including a registration device used by each of a plurality of transactors who conduct transactions and which registers details of the transactions, a transaction management device, a transaction certification device, a first terminal device that specifies the transaction and requests the transaction certification device to certify the details of the transaction, and a second terminal device that receives and displays certification data transmitted by the transaction certification device in response to the certification request from the first terminal device, wherein the transaction certification device receives the details of the transactions from the registration device, stores transaction data in a transaction database that indicates the details of each of the received transactions in association with an identifier that specifies each of the transactions, receives a transmission request sent from the first terminal device, retrieves from the transaction database the transaction data specified by the specification data included in the received transmission request, and transmits the transaction data to the first terminal device that originated the request as an electronic receipt, The transaction certification device A transaction management device is provided separately from the transaction management device, in response to a request for certification from the first terminal device, reads out transaction data of the specified transaction from the transaction database, certifies the transaction data, generates certification data for certifying the content of the specified transaction, and transmits the certification data to the second terminal device; storing management data in a certification database, the management data including a transaction identifier and information indicating whether certification data for the transaction has been issued to the second terminal device; the transaction certification device, upon receipt of a certification request from the first terminal device, generates the certification data on condition that the management data of the specified transaction indicates that the certification data has not been issued, and, upon transmitting the certification data to the second terminal device, changes information in the management data indicating whether the certification data has been issued to the second terminal device to "issued," The certification data is data different from the electronic receipt and is certification data in the form of a receipt. Proof of transaction device.

14. A transaction certification method in a transaction certification system, the method comprising: a registration device used by each of a plurality of traders who conduct transactions and which registers details of the transactions; a transaction management device; a transaction certification device; a first terminal device that specifies the transaction and requests the transaction certification device to certify the details of the transaction; and a second terminal device that receives and displays certification data transmitted by the transaction certification device in response to the certification request from the first terminal device, said transaction management device receives the contents of said transactions from said registration device, and stores in a transaction database transaction data indicating the contents of each of said transactions in correspondence with an identifier that designates each of said transactions; The transaction management device receives a transmission request sent from the first terminal device, retrieves from the transaction database the transaction data designated by the designation data included in the received transmission request, and transmits the data as an electronic receipt to the first terminal device that originated the request; the transaction certification device is provided separately from the transaction management device, The transaction certification device: in response to a request for certification from the first terminal device, reads out transaction data of the specified transaction from the transaction database, certifies the transaction data, generates certification data for certifying the content of the specified transaction, and transmits the certification data to the second terminal device; storing management data in a certification database, the management data including an identifier of the transaction and information indicating whether the certification data has been issued to the second terminal device; the transaction certification device, upon receipt of a certification request from the first terminal device, generates the certification data on condition that the management data of the specified transaction indicates that the certification data has not been issued, and, upon transmitting the certification data to the second terminal device, changes information in the management data indicating whether the certification data has been issued to the second terminal device to "issued," The certification data is data different from the electronic receipt and is certification data in the form of a receipt. Proof-of-Trade methods.

Images