JP7379564B2 - information terminal - Google Patents

Description

Embodiments of the present invention relate to a receipt server, an electronic receipt system, and a program.

2. Description of the Related Art Electronic receipt services are known that digitize receipts and allow service users to view them on mobile terminals and the like. However, no measures are taken to prevent falsification of electronic receipt data provided by conventional electronic receipt services. Therefore, the electronic receipt data cannot be used as a certification document for tax payment certification or the like. Under these circumstances, it is desired that electronic receipt data can also be used as certificate documents.

Japanese Patent Application Publication No. 2014-164353

The problem to be solved by the embodiments of the present invention is to provide a receipt server, an electronic receipt system, and a receipt server program that provide electronic receipt data that can also be used as a certificate.

The receipt server of the embodiment includes an acquisition means and an association means. The acquisition means acquires a timestamp token issued by the timestamp authority regarding the hash value of the electronic receipt data. The association means associates the time stamp token acquired by the acquisition means with the electronic receipt data.

FIG. 1 is a block diagram showing a main circuit configuration of an electronic receipt system according to an embodiment. 2 is a flowchart of control processing by the CPU of the sales data processing device in FIG. 1; 2 is a flowchart of control processing by the CPU of the receipt server in FIG. 1. 2 is a flowchart of control processing by the CPU of the information terminal in FIG. 1.

An electronic receipt system according to an embodiment will be described below with reference to the drawings.
FIG. 1 is a block diagram showing a main circuit configuration of an electronic receipt system 1 according to an embodiment. In the electronic receipt system 1, a sales data processing device 10, a receipt server 20, a time stamp server 30, and an information terminal 40 are connected to a network 50.

The sales data processing device 10 is installed in a store such as a supermarket for tasks such as purchase registration and payment of products for which payment is to be made, and is operated by a store clerk. The sales data processing device 10 is, for example, a POS (point of sales) terminal or an electronic cash register. Note that the sales data processing device 10 may be a self-operated system operated by a shopper. Alternatively, a semi-self-service system may be used in which the registration section that performs registration processing and the payment section that performs payment processing are separated, and the registration section is operated by a store clerk and the payment section is operated by a shopper. The sales data processing device 10 includes a CPU 11 , a main memory 12 , an auxiliary storage device 13 , a touch panel 14 , a customer-side touch panel 15 , a scanner 16 , a printer 17 , a network I/F (interface) 18 , and a bus 19 .

The CPU 11 corresponds to the central part of a computer that performs processing and control necessary for the operation of the sales data processing device 10. The CPU 11 controls each part of the sales data processing device 10 to realize various functions based on programs such as an operating system and application software stored in the main memory 12.
The main memory 12 corresponds to the main memory portion of the computer. The main memory 12 stores programs such as the operating system and application software. The main memory 12 also stores data that the CPU 11 refers to when performing various processes. Furthermore, the main memory 12 is used as a so-called work area in which data temporarily used by the CPU 11 is stored when performing various processes. The main memory 12 also stores a flag F.
The auxiliary storage device 13 corresponds to the auxiliary storage portion of the computer. The auxiliary storage device 13 is, for example, an EEPROM (electric erasable programmable read-only memory), an HDD (hard disc drive), or an SSD (solid state drive). The auxiliary storage device 13 stores data used by the CPU 11 in performing various processes, data generated by processing by the CPU 11, and the like. The auxiliary storage device 13 may also store programs such as the operating system or applications described above. The main memory 12 or the auxiliary storage device 13 also stores a product list that is a list of products registered as purchased products.
The programs stored in the main memory 12 or the auxiliary storage device 13 include a control program that describes control processing to be described later. As an example, the sales data processing device 10 is transferred to a user with the control program stored in the main memory 12 or the auxiliary storage device 13. However, the sales data processing device 10 may be transferred to a user without the control program being stored in the main memory 12 or the auxiliary storage device 13. Then, a control program that is separately transferred to a user may be written into the main memory 12 or the auxiliary storage device 13 under operation by the user or a service person. Transfer of the control program at this time can be realized by recording it on a removable recording medium such as a magnetic disk, magneto-optical disk, optical disk, semiconductor memory, etc., or by downloading it via a network.

The touch panel 14 functions as a display device that displays a screen for notifying the operator of various information. Further, the touch panel 14 functions as an input device that receives touch operations by the operator.
The customer-side touch panel 15 functions as a display device that displays a screen for notifying the shopper of various information. Further, the customer-side touch panel 15 functions as an input device that receives touch operations by the shopper.
The scanner 16 reads the barcode displayed on the product and outputs the product code represented by this barcode. The scanner 16 may be of a type that is held in the hand or of a type that is fixed to a cash register table or the like.
The printer 17 prints receipts and the like. The printer 17 can use various methods such as a dot impact printer, an inkjet printer, a thermal printer, a laser printer, or other printers.
Network I/F 18 is an interface for sales data processing device 10 to communicate via network 50 .
The bus 19 includes an address bus, a data bus, and the like, and transmits signals exchanged with each part of the sales data processing device 10.

The receipt server 20 includes a CPU 21, a main memory 22, an auxiliary storage device 23, a network I/F 24, and a bus 25.

The CPU 21 corresponds to the central part of the computer. The CPU 21 controls each part of the receipt server 20 to realize various functions based on programs such as an operating system and application software stored in the main memory 22. The main memory 22 corresponds to the main memory portion of the computer. Main memory 22 stores programs such as an operating system and application software. The programs stored in the main memory 22 include a control program for controlling the receipt server 20. The main memory 22 also stores data that the CPU 21 refers to when performing various processes. Furthermore, the main memory 22 is used as a so-called work area in which data temporarily used by the CPU 21 is stored when performing various processes.
The auxiliary storage device 23 corresponds to the auxiliary storage portion of the computer. The auxiliary storage device 23 is, for example, an EEPROM, HDD, or SSD. The auxiliary storage device 23 stores data used by the CPU 21 in performing various processes, data generated by processing by the CPU 21, and the like. The auxiliary storage device 23 may also store programs such as the operating system or applications described above. The auxiliary storage device 23 stores electronic receipt data and a PDF (Portable Document Format) file, which will be described later, in association with an individual user ID (identifier) assigned to each user of the electronic receipt service. Further, an individual receipt ID is assigned to each electronic receipt data and each PDF file described below. The receipt ID consists of a receipt key assigned to each electronic receipt and a type key. The type key distinguishes electronic receipt data from a PDF file, and also distinguishes the type of electronic receipt data. Details of the type key will be described later. Further, the auxiliary storage device 23 stores user information of the electronic receipt service in association with the user ID. The user information includes information indicating whether the user is using the digital evidence service. Digital evidence service is a service that allows you to prove the integrity of electronic receipt data. Users of the digital evidence service can preset conditions for applying the digital evidence service. The conditions include, for example, "the payment amount is a certain amount or more" or "the purchased products include a specific product or a specific category of products". If conditions are set, information representing the conditions is also included in the user information.
The programs stored in the main memory 22 or the auxiliary storage device 23 include a control program that describes control processing to be described later. As an example, the receipt server 20 is transferred to the user with the control program stored in the main memory 22 or the auxiliary storage device 23. However, the receipt server 20 may be transferred to the user without the control program being stored in the main memory 22 or the auxiliary storage device 23. Then, a control program that is separately transferred to a user may be written into the main memory 22 or the auxiliary storage device 23 under operation by the user or a service person. Transfer of the control program at this time can be realized by recording it on a removable recording medium such as a magnetic disk, magneto-optical disk, optical disk, semiconductor memory, etc., or by downloading it via a network.

Network I/F 24 provides an interface for receipt server 20 to communicate via network 50 .
The bus 25 includes an address bus, a data bus, and the like, and transmits signals exchanged between each part of the receipt server 20.

The time stamp server 30 receives a request to issue a time stamp token (hereinafter referred to as "TST") and issues a TST. The timestamp server 30 is, for example, a server provided by a time-stamping authority (TSA) for issuing a TST.

The information terminal 40 is a device with a communication function, and is, for example, a mobile information terminal such as a smartphone, a mobile phone, or a tablet PC (personal computer). The information terminal 40 may be a stationary computer such as a desktop PC, a notebook PC, or the like.
The information terminal 40 can output a user ID. The user ID is output by a method such as displaying a barcode containing the user ID on a screen, printing a barcode containing the user ID, or transmitting the user ID to another device.
Users of the electronic receipt service can obtain electronic receipt data from the receipt server 20 by using the information terminal 40.
The information terminal 40 includes a CPU 41, a main memory 42, an auxiliary storage device 43, a touch panel 44, a network I/F 45, and a bus 46.

The CPU 41 corresponds to the central part of the computer. The CPU 41 controls each part of the information terminal 40 to realize various functions based on programs such as an operating system and application software stored in the main memory 42 .
The main memory 42 corresponds to the main memory portion of the computer. Main memory 42 stores programs such as an operating system and application software. The programs stored in the main memory 42 include a control program for controlling the information terminal 40. The main memory 42 also stores data that the CPU 41 refers to when performing various processes. Further, the main memory 42 is used as a so-called work area in which data temporarily used by the CPU 41 is stored when performing various processes.
The auxiliary storage device 43 corresponds to the auxiliary storage portion of the computer. The auxiliary storage device 43 is, for example, an EEPROM, HDD, or SSD. The auxiliary storage device 43 stores data used by the CPU 41 when performing various processes, data generated by processing by the CPU 41, and the like. The auxiliary storage device 43 may also store programs such as the operating system or application software described above. The programs stored in the main memory 42 or the auxiliary storage device 43 include application software (hereinafter referred to as "viewing application") that describes control processing to be described later for viewing electronic receipts. As an example, the information terminal 40 is transferred to the user without the viewing application being stored in the main memory 42 or the auxiliary storage device 43. Then, the viewing application separately transferred to the user is written into the main memory 42 or the auxiliary storage device 43 under operation by the user or a service person. However, the information terminal 40 may be transferred to the user with the viewing application stored in the main memory 42 or the auxiliary storage device 43. The above-mentioned transfer of the viewing application can be realized by recording it on a removable recording medium such as a magnetic disk, magneto-optical disk, optical disk, semiconductor memory, etc., or by downloading it via a network.

The touch panel 44 functions as a display device that displays a screen for notifying the operator of the information terminal 40 of various information. Further, the touch panel 44 functions as an input device that receives touch operations by the operator.
Network I/F 45 serves as an interface for information terminal 40 to communicate via network 50 .
The bus 46 includes an address bus, a data bus, and the like, and transmits signals exchanged between each part of the information terminal 40.

The network 50 is a communication network including a mobile phone network such as 3G (3rd generation) or LTE (long term evolution), the Internet, a LAN (local area network), a leased line, or other communication lines.

The operations of the sales data processing device 10, the receipt server 20, and the information terminal 40 will be described below with reference to the drawings. Note that the content of the processing described below is an example, and various processing that can obtain similar results can be used as appropriate.

The operations of the sales data processing device 10 and the receipt server 20 when a shopper purchases a product will be explained based on FIGS. 2 and 3. FIG. 2 is a flowchart of control processing by the CPU 11. The CPU 11 executes this control processing based on a control program stored in the main memory 12 or the auxiliary storage device 13. FIG. 3 is a flowchart of control processing by the CPU 21. The CPU 21 executes this control processing based on a control program stored in the main memory 22 or the auxiliary storage device 23.

In Act 1, the CPU 11 checks whether the user ID has been read. That is, the CPU 11 checks whether the barcode including the user ID has been read by the scanner 16. If the user ID is not read, the CPU 11 determines No in Act 1 and proceeds to Act 2.

In Act 2, the CPU 11 checks whether the product code has been read. That is, the CPU 11 checks whether the barcode attached to the product has been read by the scanner 16. If the product code is not read, the CPU 11 determines No in Act 2 and proceeds to Act 3.

In Act 3, the CPU 11 checks whether an operation instructing completion of registration has been performed. That is, the CPU 11 checks whether a predetermined operation for instructing completion of registration, such as pressing a subtotal button, has been performed. Note that the operational rule is that the operation of instructing the completion of registration is performed after one or more products have been registered. The operation of the CPU 11 when an operation instructing completion of registration is performed in a state where no product is registered may be determined by the designer of the control program for the CPU 11. For example, the CPU 11 ignores an operation instructing completion of registration. Alternatively, the CPU 11 may be configured to be unable to perform an operation to instruct completion of registration when no product is registered. If the operation instructing the completion of registration is not performed, the CPU 11 determines No in Act 3 and returns to Act 1. In this way, the CPU 11 repeats Acts 1 to 3 until the user ID is read, the product code is read, or an operation instructing completion of registration is performed. If the user ID is read in the standby state in Acts 1 to 3, the CPU 11 determines Yes in Act 1 and proceeds to Act 4.

In Act 4, the CPU 11 stores the read user ID in the main memory 12 or the auxiliary storage device 13. Note that the operation when the user ID is read twice or more may be determined by the designer of the control program for the CPU 11. For example, the CPU 11 erases the stored user ID and stores the newly read user ID in the main memory 12 or the auxiliary storage device 13. After the process in Act 4, the CPU 11 returns to Act 1. If the product code is read in the standby state in Acts 1 to 3, the CPU 11 determines Yes in Act 2 and proceeds to Act 5.

In Act 5, the CPU 21 registers the read product code in the product list. That is, the CPU 21 instructs the main memory 12 or the auxiliary storage device 23 to add the read product code to the product list. After the processing in Act5, the CPU 11 returns to Act1. In the standby state of Act1 to Act3, if an operation instructing completion of registration is performed with one or more products registered in the product list, the CPU 11 determines Yes in Act3 and proceeds to Act6.

In Act 6, the CPU 11 performs payment processing based on the product list. As the payment process, a well-known process can be used as is, so a description of this process will be omitted.
In Act 7, the CPU 11 checks whether the user ID of the electronic receipt service is stored in the main memory 12 or the auxiliary storage device 13. If the user ID of the electronic receipt service is not stored, the CPU 21 determines No in Act 7 and proceeds to Act 8.

In Act 8, the CPU 11 issues a paper receipt. That is, the CPU 11 controls the printer 17 to print a receipt. After the processing in Act8, the CPU 11 returns to Act1. Note that at this time, although not shown, the CPU 11 resets the product list. If the user ID of the electronic receipt service is stored, the CPU 21 determines Yes in Act 7 and proceeds to Act 9.

In Act 9, the CPU 11 instructs the network I/F 18 to send an inquiry command including the user ID to the receipt server 20.

On the other hand, the CPU 21 of the receipt server 20 executes the control process shown in FIG. In Act 21 of FIG. 3, the CPU 21 checks whether the inquiry command has been received by the network I/F 24. If the inquiry command is not received, the CPU 21 determines No in Act 21 and proceeds to Act 22.

In Act 22, the CPU 21 checks whether the commercial transaction data has been received by the network I/F 24. Note that the commercial transaction data will be described later. If the commercial transaction data is not received, the CPU 21 determines No in Act 22 and proceeds to Act 23.

In Act 23, the CPU 21 checks whether the list request command has been received by the network I/F 24. Note that the list request command will be described later. If the list request command is not received, the CPU 21 determines No in Act 23 and proceeds to Act 24.

In Act 24, the CPU 21 checks whether the receipt request command has been received by the network I/F 24. Note that the receipt request command will be described later. If the receipt request command is not received, the CPU 21 determines No in Act 24 and proceeds to Act 25.

In Act 25, the CPU 21 checks whether the PDF request command has been received by the network I/F 24. Note that the PDF request command will be described later. If the PDF request command is not received, the CPU 21 determines No in Act 25 and returns to Act 21. In this way, the CPU 11 repeats Acts 21 to 25 until any one of the inquiry command, commercial transaction data, list request command, receipt request command, and PDF request command is received. If the inquiry command transmitted from the sales data processing device 10 is received in the standby state of Acts 21 to 25, the CPU 21 determines Yes in Act 21 and proceeds to Act 26.

In Act 26, the CPU 21 instructs the network I/F 24 to transmit the user information identified by the user ID included in the inquiry command to the sales data processing device 10. After the process in Act 26, the CPU 21 returns to Act 21.

On the other hand, the CPU 11 of the sales data processing device 10 transmits the inquiry command in Act 9 of FIG. 2, and then proceeds to Act 10.
In Act 10, the CPU 11 waits for user information to be received by the network I/F 18. If the user information transmitted from the receipt server 20 is received, the CPU 11 determines Yes in Act 10 and proceeds to Act 11.

In Act 11, the CPU 11 refers to the user information and confirms whether the user is using the digital evidence service. If the user is using the digital evidence service, the CPU 11 determines Yes in Act 11 and proceeds to Act 12.

In Act 12, the CPU 11 checks whether the conditions included in the user information are satisfied. For example, if the condition is "the payment amount is 1000 yen or more", it is checked in Act 6 whether the payment amount is 1000 yen or more. Furthermore, if the user information does not include the conditions, it is assumed that the conditions are not met. If the condition is not satisfied, the CPU 11 makes a negative determination in Act 12 and proceeds to Act 13.

In Act 13, the CPU 11 generates an image corresponding to a confirmation screen for instructing whether or not to associate TST with the electronic receipt data generated by the current shopping, and instructs the customer-side touch panel 15 to display this image. . The confirmation screen displays a first button for the shopper to touch when associating the TST, and a second button for the shopper to touch when not associating the TST.

The shopper instructs whether or not to associate the TST by touching the first button or the second button displayed on the customer-side touch panel 15.
In Act 14, the CPU 11 checks whether a predetermined operation for instructing not to associate the TST, such as touching the second button, has been performed. If the operation instructing not to associate the TST is not performed, the CPU 11 determines No in Act 14 and proceeds to Act 15.

In Act 15, the CPU 11 checks whether a predetermined operation for instructing to associate the TST, such as touching the first button, has been performed. If the operation instructing to associate the TST is not performed, the CPU 11 determines No in Act 15 and returns to Act 14. In this way, the CPU 11 repeats Acts 14 and 15 until an operation instructing not to associate the TST or an operation instructing to associate the TST is performed. If an operation instructing to associate the TST is performed in the standby state in Acts 14 and 15, the CPU 11 determines Yes in Act 15 and proceeds to Act 16. Further, if the conditions included in the user information are satisfied, the CPU 11 determines Yes in Act 12 and proceeds to Act 16 in this case as well.

In Act 16, the CPU 11 rewrites the value of the flag F stored in the main memory 12 to True.

On the other hand, if an operation instructing not to associate the TST is performed in the standby state in Acts 14 and 15, the CPU 11 determines Yes in Act 14 and proceeds to Act 17. Further, if the user is not using the digital evidence service, the CPU 11 determines No in Act 11 and proceeds to Act 17.
In Act 17, the CPU 11 rewrites the value of the flag F stored in the main memory 12 to False.

After the CPU 11 finishes setting the value of the flag F in Act 16 or Act 17 as described above, the CPU 11 proceeds to Act 18.
In Act 18, the CPU 11 generates commercial transaction data. The commercial transaction data includes a user ID, electronic receipt data, and flag F. Electronic receipt data is electronic information written on a receipt. The file format of electronic receipt data is, for example, XML (Extensible Markup Language), HTML (Hypertext Markup Language), JSON (JavaScript (registered trademark) Object Notation), CSV (Comma-Separated Values), or TSV (Tab-Separated Values). In text format.

In Act 19, the CPU 11 instructs the network I/F 18 to transmit the generated commercial transaction data to the receipt server 20. After the process in Act 19, the CPU 11 returns to Act 1. Note that at this time, although not shown, the CPU 11 resets the product list.

Now, when the CPU 21 of the receipt server 20 receives the commercial transaction data transmitted from the sales data processing device 10 in the standby state of Acts 21 to 25 in FIG. 3, it determines Yes in Act 22 and proceeds to Act 27. .
In Act 27, the CPU 21 checks whether the value of the flag F transmitted from the sales data processing device 10 is True. If the value of the flag F is False, the CPU 21 determines No in Act 27 and proceeds to Act 28.

In Act 28, the CPU 21 instructs the auxiliary storage device 23 to store the electronic receipt data included in the received commercial transaction data. At this time, the CPU 21 assigns a receipt key to the electronic receipt data. Further, the CPU 21 sets a type key with a value of 0 in the electronic receipt data. Note that a type key with a value of 0 means that a PDF file, which will be described later, does not exist regarding the electronic receipt data. Through this process, a receipt ID consisting of a receipt key and a type key is assigned to the electronic receipt data. After the process in Act 28, the CPU 21 returns to Act 21.

If the value of the flag F is True, the CPU 21 determines Yes in Act 27 and proceeds to Act 29.
In Act 29, the CPU 21 instructs the auxiliary storage device 23 to store the electronic receipt data included in the received commercial transaction data. At this time, the CPU 21 assigns a receipt key to the electronic receipt data. Further, the CPU 21 sets a type key with a value of 1 to the electronic receipt data. Note that a type key with a value of 1 means that a PDF file, which will be described later, exists regarding the electronic receipt data. Through this process, a receipt ID consisting of a receipt key and a type key is assigned to the electronic receipt data.

In Act 30, the CPU 21 generates a PDF file. The PDF file is an electronic receipt file in PDF format. The PDF file stores electronic receipt data that has been converted into a format suitable for PDF files. Note that the electronic receipt data stored in the auxiliary storage device 23 in Act 29 remains stored in the auxiliary storage device 23 as data for the user to view.

In Act 31, the CPU 21 calculates a hash value of the electronic receipt data included in the PDF file. A known method can be used to calculate the hash value.
In Act 32, the CPU 21 instructs the network I/F 24 to send a stamp request command to the time stamp server 30. The stamp request command includes the hash value calculated in Act31.

The timestamp server 30 that receives the stamp request command creates a TST. That is, the timestamp server 30 acquires time information indicating the current date and time for TST creation. The timestamp server 30 then creates a TST using the hash value included in the stamp request command and the time information. Note that the TST and its creation method in the above description are merely examples, and a well-known method can be used to create the TST. Then, the time stamp server 30 transmits the created TST to the receipt server 20 that transmitted the stamp request command.

After transmitting the stamp request command, the CPU 21 of the receipt server 20 proceeds to Act 33.
In Act 33, the CPU 21 waits for the TST to be received by the network I/F 24. In Act 33, the computer having the CPU 21 as its core operates as an acquisition control means and controls the network I/F 24 to receive the TST. The network I/F 24 receives the TST under the control of the computer. In this process, the computer and network I/F 24 operate as an acquisition means. Further, the network I/F 24 operates as a communication device. If the TST is received, the CPU 21 determines Yes in Act 33 and proceeds to Act 34.

In Act 34, the CPU 21 adds TST to the PDF file. Through this process, the TST is associated with the electronic receipt data. Thus, in Act 34, the computer having the CPU 21 as its core operates as a linking means.
In Act 35, the CPU 21 instructs the auxiliary storage device 23 to save the PDF file in which the TST is stored. At this time, the CPU 21 assigns a receipt ID to the PDF file. However, the receipt ID is obtained by changing the value of the type key constituting the receipt ID assigned to the electronic receipt data in Act 29 to 2. Thus, a type key with a value of 2 means that it is a PDF file. After the process in Act 35, the CPU 21 returns to Act 21.
As shown in the processing in Acts 27 to 35, it is determined whether or not to associate the TST depending on the value of the flag F. The value of flag F becomes True when an operation instructing to associate TST is performed on the confirmation screen. Thus, in the process of Act 27, the computer including the CPU 21 as a central part operates as a determining means for determining whether to perform an association regarding the payment in response to an instruction for each payment by the user of the electronic receipt service. Note that if the conditions included in the user information are satisfied, the CPU 21 assumes that the user has instructed to perform the association and decides to execute the association. There is no other way than that.

Next, the operations of the receipt server 20 and the information terminal 40 when a user of the electronic receipt service obtains electronic receipt data will be described based on FIGS. 3 and 4. FIG. 4 is a flowchart of control processing by the CPU 41. The CPU 41 executes this control process based on the viewing application stored in the main memory 42 or the auxiliary storage device 43. A user who wishes to obtain electronic receipt data operates the information terminal 40 to instruct execution of a viewing application. In response to this instruction, the CPU 41 starts the control process shown in FIG. 4 based on the viewing application.
In Act 41, the CPU 41 instructs the network I/F 45 to transmit a list request command including the user ID to the receipt server 20.

Now, when the CPU 21 of the receipt server 20 receives the list request command transmitted from the information terminal 40 in the standby state of Acts 21 to 25 in FIG. 3, it determines Yes in Act 23 and proceeds to Act 36.
In Act 36, the CPU 21 creates list data indicating a list of electronic receipts that are permitted to be viewed by the user identified by the user ID included in the list request command. That is, the CPU 21 creates list data showing a list of electronic receipt data whose type key is 0 or 1 among the electronic receipt data stored in association with the user ID.
In Act 37, the CPU 21 instructs the network I/F 24 to transmit the list data to the information terminal 40. After the process in Act 37, the CPU 21 returns to Act 21.

On the other hand, the CPU 41 of the information terminal 40 transmits the list request command in Act 41 of FIG. 4, and then proceeds to Act 42.
In Act 42, the CPU 41 waits for the list data to be received by the network I/F 45. If the list data transmitted from the receipt server 20 is received, the CPU 41 determines Yes in Act 42 and proceeds to Act 43.

In Act 43, the CPU 41 generates an image corresponding to a list screen showing a list of viewable electronic receipts based on the list data, and instructs the touch panel 44 to display this image. The list screen displays, for example, the receipt ID, purchase date and time, and store of purchase included in each electronic receipt data.

On the list screen, the user performs an operation on the touch panel 44 to specify the electronic receipt that he or she wishes to view. Specifically, the user performs a touch operation on the touch panel 44 to touch an area where the receipt ID, date and time of purchase, store of purchase, etc. of the electronic receipt that he or she wishes to view are displayed.
In Act 44, the CPU 41 waits for the above-described touch operation to be performed. If the corresponding touch operation is performed, the CPU 41 determines Yes in Act 44 and proceeds to Act 45.

In Act 45, the CPU 41 instructs the network I/F 45 to transmit a receipt request command to the receipt server 20. The receipt request command includes the receipt ID assigned to the electronic receipt data corresponding to the touched area on the list screen.

Now, when the CPU 21 of the receipt server 20 receives the receipt request command transmitted from the information terminal 40 in the standby state of Acts 21 to 25 in FIG. 3, it determines Yes in Act 24 and proceeds to Act 38.
In Act 38, the CPU 21 instructs the network I/F 24 to read the electronic receipt data specified by the receipt ID included in the receipt request command from the auxiliary storage device 23, and to transmit the electronic receipt data to the information terminal 40. After the process in Act 38, the CPU 21 returns to Act 21.

On the other hand, the CPU 41 of the information terminal 40 transmits the receipt request command in Act 45 of FIG. 4, and then proceeds to Act 46.
In Act 46, the CPU 41 waits for electronic receipt data to be received by the network I/F 45. If the electronic receipt data transmitted from the receipt server 20 is received, the CPU 41 determines Yes in Act 46 and proceeds to Act 47.

In Act 47, the CPU 41 checks whether a PDF file exists, that is, whether the value of the type key forming the receipt ID included in the receipt request command is 1. If the value of the type key is 0, the CPU 41 determines No in Act 47 and proceeds to Act 48.

In Act 48, the CPU 41 generates an image corresponding to the receipt screen and instructs the touch panel 44 to display this image. The receipt screen displays an electronic receipt generated based on the received electronic receipt data and a close button that the operator touches to end displaying the receipt screen.

In Act 49, the CPU 41 waits for an operation to instruct the end of displaying the receipt screen. That is, the CPU 41 checks whether a predetermined operation for instructing the end of displaying the receipt screen, such as touching a close button displayed on the touch panel 44, has been performed. If the operation instructing to end the display of the receipt screen is performed, the CPU 41 determines Yes in Act 49 and proceeds to Act 50.

In Act 50, the CPU 41 instructs the touch panel 44 to end displaying the receipt screen. After the process in Act 50, the CPU 41 returns to Act 41. If the value of the type key is 1, the CPU 41 determines Yes in Act 47 and proceeds to Act 51.

In Act 51, the CPU 41 generates an image corresponding to the receipt screen as in Act 48, and instructs the touch panel 44 to display this image. However, the receipt screen in Act 51 also displays an acquisition button for the operator to touch when acquiring a PDF file.

In Act 52, the CPU 41 confirms whether or not an operation instructing to end the display of the receipt screen has been performed. That is, the CPU 41 checks whether a predetermined operation for instructing the end of displaying the receipt screen, such as touching a close button displayed on the touch panel 44, has been performed. If the operation instructing the end of displaying the receipt screen is not performed, the CPU 41 determines No in Act 52 and proceeds to Act 53.

In Act 53, the CPU 41 checks whether an operation instructing to obtain a PDF file has been performed. That is, the CPU 41 checks whether a predetermined operation for instructing the acquisition of a PDF file, such as touching an acquisition button displayed on the touch panel 44, has been performed. If the CPU 41 does not perform an operation to instruct the acquisition of a PDF file, the process returns to Act 51. In this way, the CPU 41 repeats Acts 52 and 53 until an operation instructing to end displaying the receipt screen is performed or an operation instructing to obtain a PDF file is performed. If the operation instructing to end the display of the receipt screen is performed, the CPU 41 determines Yes in Act 52 and proceeds to Act 50. Then, the CPU 41 returns to Act 41 after finishing displaying the receipt screen, as described above. On the other hand, if an operation instructing to obtain a PDF file is performed, the CPU 41 determines Yes in Act 53 and proceeds to Act 54.

In Act 54, the CPU 41 instructs the network I/F 45 to transmit a PDF request command to the receipt server 20. The PDF request command includes the receipt ID assigned to the PDF file. The receipt ID can be obtained by changing the value of the type key that constitutes the receipt ID included in the receipt request command to 2.

Now, when the CPU 21 of the receipt server 20 receives the PDF request command transmitted from the information terminal 40 in the standby state of Acts 21 to 25 in FIG. 3, it determines Yes in Act 25 and proceeds to Act 39.
In Act 39, the CPU 21 reads the PDF file identified by the receipt ID included in the PDF request command from the auxiliary storage device 23, and instructs the network I/F 24 to transmit the PDF file to the information terminal 40. After the process in Act 39, the CPU 21 returns to Act 21.

On the other hand, the CPU 41 of the information terminal 40 transmits the PDF request command in Act 54 of FIG. 4, and then proceeds to Act 55.
In Act 55, the CPU 41 waits for the PDF file to be received by the network I/F 45. If the PDF file transmitted from the receipt server 20 is received, the CPU 41 determines Yes in Act 55 and proceeds to Act 56.

In Act 56, the CPU 41 instructs the auxiliary storage device 43 to save the obtained PDF file. After the process in Act 56, the CPU 41 returns to Act 52.

The PDF file transmitted from the receipt server 20 in this manner is stored in the auxiliary storage device 43. In the PDF file, TST is associated with electronic receipt data. Therefore, if at least one of the electronic receipt data and the TST is altered, the hash value calculated from the electronic receipt data and the hash value extracted from the TST are different. In other words, if the hash value calculated from the electronic receipt data matches the hash value extracted from the TST, it can be proven that the PDF file has not been altered. Furthermore, it can be proven that electronic receipt data included in the same PDF file existed at the date and time indicated by the time information extracted from the TST. Note that the modification referred to here is not limited to human modification, but also includes cases where data is rewritten due to computer malfunction, etc.

Further, the receipt server 20 allows the user to instruct whether or not to associate the TST for each payment. Therefore, the user does not needlessly associate TST with electronic receipt data that does not require association with TST. This prevents unnecessary increases in the amount of processing and data storage in the receipt server 20. Further, if the time stamp server 30 provides a pay-as-you-go service that charges according to the number of TSTs issued, an increase in the cost of issuing TSTs can be prevented.

Further, if the conditions preset by the user are satisfied, the receipt server 20 determines to associate the TST with the electronic receipt data without accepting an instruction from the user. Therefore, with respect to electronic receipt data for which it is clear that the user needs to associate the TST based on the conditions preset by the user, the user does not have to perform an operation to specify whether or not to associate the TST. . This can prevent unnecessary increases in the burden of operations on the user.

The above embodiment can be modified as follows.
The electronic receipt file is not limited to the PDF format, and may be any file format that can store electronic receipt data and TST.
In the above embodiment, an example was explained in which electronic receipt data and TST are associated by being stored in one file. However, electronic receipt data and TST are stored as separate files, and these files are stored as separate management data. It is also possible to associate the information by, for example,

In the above embodiment, the sales data processing device 10 sent the flag F to the electronic receipt data to the receipt server 20. Then, the CPU 21 of the receipt server 20 that received the flag F decides to associate the TST with the electronic receipt data based on the value of the flag F. However, the flag F may be interpreted as data that instructs the receipt server 20 whether or not to perform association.
In this case, in the process of Act 17, the computer including the CPU 11 as a central part operates as a determining means for determining execution of the association. Further, in the process of Act 19 when the value of the flag F is True, the CPU 11 and the network I/F 18 operate as an instruction means for instructing the receipt server 20 to associate the TST with the electronic receipt data.

A screen for the user to instruct whether or not to associate the TST may be displayed on the touch panel 14. In this case, the operator asks the shopper whether or not to associate the TST, and the operator operates the touch panel 14 according to the shopper's answer.

The receipt server 20 may determine whether the conditions included in the user information are satisfied. In this case, the processing is performed as follows, for example. The sales data processing device 10 transmits the payment amount, product list, etc. to the receipt server 20 along with an inquiry command. Upon receiving the inquiry command, the CPU 21 of the receipt server 20 determines whether the conditions are satisfied based on the content sent from the sales data processing device 10. Then, the CPU 21 transmits the determination result together with the user information to the sales data processing device 10. The CPU 11 of the sales data processing device 10 that has received the user information and the determination result may perform the determination in Act 12 based on the received determination result.

In the embodiment described above, only when the conditions included in the user information are not satisfied, it is determined whether or not to associate the TST in accordance with the instruction operation by the operator. However, the CPU 11 or the CPU 21 may determine whether or not to associate the TST only when the conditions included in the user information are satisfied, in response to an instruction operation. Further, the CPU 11 or the CPU 21 may decide to associate the TST with the electronic receipt data when a condition included in the user information is satisfied. Alternatively, the CPU 11 or the CPU 21 may decide to associate the TST with the electronic receipt data when the conditions included in the user information are not satisfied. For example, in the case of the condition that "the payment amount is 1000 yen or less", it is determined in Act 6 that TST is associated if the payment amount is not 1000 yen or less. Furthermore, the CPU 11 or the CPU 21 may determine whether or not to associate the TST based only on an instruction operation by the operator.

Although several embodiments of the invention have been described, these embodiments are presented by way of example and are not intended to limit the scope of the invention. These novel embodiments can be implemented in various other forms, and various omissions, substitutions, and changes can be made without departing from the gist of the invention. These embodiments and their modifications are included within the scope and gist of the invention, as well as within the scope of the invention described in the claims and its equivalents.
Below, the invention described in the original claims of the original application of this application will be added.
[1]
an acquisition means for acquiring a timestamp token issued by a timestamp authority regarding a hash value of electronic receipt data;
A receipt server comprising: associating means for associating the time stamp token acquired by the acquiring means with the electronic receipt data.
[2]
Further comprising a determining means for determining execution of association regarding the payment in accordance with an instruction for each payment by a user of the electronic receipt service,
The receipt server according to appendix [1], wherein the acquisition unit acquires the time stamp token when the determination unit determines to perform the association.
[3]
The acquisition means acquires the time stamp token when the electronic receipt data matches a predetermined condition.
Receipt server described in appendix [1].
[4]
In an electronic receipt system comprising a sales data processing device and a receipt server, the sales data processing device includes:
A determining means for determining execution of association regarding the payment in accordance with an instruction for each payment by a user of the electronic receipt service;
and an instructing means for instructing the receipt server to perform association with electronic receipt data related to a payment for which execution of association has been determined by the determination means, the receipt server comprising:
an acquisition unit that acquires a timestamp token issued by a timestamp bureau regarding a hash value of electronic receipt data for which association has been instructed by the instruction unit; An electronic receipt system comprising: associating means for associating with receipt data.
[5]
A computer that controls a receipt server equipped with communication equipment,
acquisition control means for controlling a communication device to acquire a timestamp token issued by a timestamp authority regarding a hash value of electronic receipt data;
A program for functioning as an association means for associating the time stamp token acquired by the acquisition control means with the electronic receipt data.

1... Electronic receipt system, 10... Sales data processing device, 11, 21, 41... CPU, 12, 22, 42... Main memory, 13, 23, 43... Auxiliary storage device, 15... Customer side touch panel, 18, 24, 45...Network I/F, 20...Receipt server, 30...Time stamp server, 40...Information terminal.

Claims (3)

an interface that acquires a timestamp token issued by a timestamp authority regarding a hash value of electronic receipt data and communicates with an electronic receipt server that stores a file that associates the timestamp token with the electronic receipt data;
a processor that causes the interface to receive the electronic receipt data from the electronic receipt server, causes the interface to receive the file from the electronic receipt server, and stores the file;
a storage device that stores the file;
a display device;
Equipped with
The processor causes the interface to receive the electronic receipt data from the electronic receipt server based on the electronic receipt request, confirms the existence of the file from a type key that constitutes a receipt ID included in the electronic receipt request, and An information terminal that displays an electronic receipt image based on receipt data and a button for acquiring the file on the display device, and receives the file based on an operation on the button. Based on the list request, the processor causes the interface to receive list data indicating a list of electronic receipts identified by the user ID included in the list request from the electronic receipt server, and causes the display device to display the list data. 2. The information terminal according to claim 1 , wherein the information terminal displays an electronic receipt list image based on . 3. The information terminal according to claim 2 , wherein the processor causes the electronic receipt data to be received based on the electronic receipt request including the receipt ID specified from the electronic receipt list image.