Information terminal device and information processing program

Abstract

To make it possible to offer the service which has been achieved by modifying paper receipts even in electronic receipts.SOLUTION: A receipt server according to an embodiment comprises storage means, generation means, and update means. The storage means stores management data for managing whether to display a display element. The generation means generates a receipt screen which represents the contents of a transaction and is to be displayed on an information terminal device by adding display elements to be displayed on the basis of the management data stored by the storage means. The update means updates the management data in accordance with operations performed in the information terminal device on the receipt screen generated by the generation means.SELECTED DRAWING: Figure 6

Description

Technical Field

[0001] Embodiments of the present invention relate to a receipt server and an information processing program.

Background Art

[0002] In the case of a paper receipt using receipt paper, it is possible to press a stamp indicating that a receipt has been issued. Also, in the case of a paper receipt, it is possible to cut and collect a coupon or the like formed in the end area. However, in the case of an electronic receipt, stamping or cutting cannot be performed, and the services implemented with paper receipts cannot be provided. Under such circumstances, it has been desired to provide services realized by modifying paper receipts also in electronic receipts.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] The problem to be solved by the present invention is to provide a receipt server and an information processing program that enable the provision of services realized by modifying paper receipts also in electronic receipts.

Means for Solving the Problems

[0005] The receipt server according to the embodiment includes a storage unit, a generation unit, and an update unit. The storage unit stores management data for managing whether to display a display element. The generation unit generates a receipt screen representing the content of a transaction and to be displayed on an information terminal device, by adding a display element to be displayed based on the management data stored by the storage unit. The update unit updates the management data according to an operation on the information terminal device in the receipt screen generated by the generation unit.

Brief Description of Drawings

[0006]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Embodiments for Carrying Out the Invention

[0007] Hereinafter, an example of an embodiment will be described with reference to the drawings. FIG. 1 is a block diagram showing the schematic configuration of an electronic receipt system 100 according to the present embodiment and the main circuit configurations of an information terminal device 10 and a receipt server 20 included in the electronic receipt system 100.

[0008] The electronic receipt system 100 is configured by enabling communication among an information terminal device 10, a receipt server 20, and a POS (point-of-sale) system 30 via a communication network 40. The communication network 40 can be used alone or in an appropriate combination, such as the Internet, a VPN (virtual private network), a LAN (local area network), a public communication network, or a mobile communication network. Note that the electronic receipt system 100 typically includes a plurality of information terminal devices 10 and a plurality of POS systems 30, but only one of each is shown in FIG. 1.

[0009] The information terminal device 10 performs operations such as displaying a receipt screen for browsing the details of a transaction based on operations by users of the electronic receipt service provided by the electronic receipt system 100. When a plurality of information terminal devices 10 are included in the electronic receipt system 100, these plurality of information terminal devices 10 may be used by the same user or individually by different users. Alternatively, one information terminal device 10 may be shared by a plurality of users.

[0010] The receipt server 20 acquires and stores receipt data including information to be represented on a receipt regarding a transaction managed by the POS system 30 from the POS system 30. The receipt server 20 generates screen data for a receipt screen and instructs the information terminal device 10 to display the receipt screen along with notification of the screen data.

[0011] The POS system 30 performs processing for registering the details of transactions such as product sales in a store and accounting. When the customer who is the subject of a transaction is a user of the electronic receipt service, the POS system 30 transmits receipt data regarding the transaction to the receipt server 20.

[0012] The information terminal device 10 is typically a portable information processing device such as a smartphone, a mobile phone, or a tablet terminal. The information terminal device 10 may also be a stationary information processing device such as a desktop personal computer. The information terminal device 10 includes a processor 11, a main memory 12, an auxiliary storage unit 13, a touch panel 14, a communication unit 15, a transmission path 16, and the like. The processor 11 is connected to the main memory 12, the auxiliary storage unit 13, the touch panel 14, and the communication unit 15 via the transmission path 16.

[0013] In the information terminal device 10, by connecting the processor 11, the main memory 12, and the auxiliary storage unit 13 via the transmission path 16, a computer for performing information processing for controlling the information terminal device 10 is configured. The processor 11 corresponds to the central part of the above computer. The processor 11 controls each part in order to realize various functions as the information terminal device 10 according to information processing programs such as an operating system, middleware, and application programs.

[0014] The main memory 12 corresponds to the main storage part of the above computer. The main memory 12 includes a non-volatile memory area and a volatile memory area. The main memory 12 stores an information processing program in the non-volatile memory area. Also, the main memory 12 may store data necessary for the processor 11 to execute processing for controlling each part in the non-volatile or volatile memory area. The main memory 12 uses the volatile memory area as a work area where data is appropriately rewritten by the processor 11.

[0015] The auxiliary storage unit 13 corresponds to the auxiliary storage part of the above computer. The auxiliary storage unit 13 is, for example, an EEPROM (electric erasable programmable read-only memory). It is provided with well-known storage devices such as an HDD (hard disc drive) and an SSD (solid state drive). The auxiliary storage unit 13 stores data used when the processor 11 performs various processes and data generated by the processes in the processor 11. The auxiliary storage unit 13 stores an information processing program.

[0016] One of the information processing programs stored in the auxiliary storage unit 13 is an application program (hereinafter referred to as the client app) APA for operating as a receipt client. Typically, however, the client app APA is downloaded via, for example, the Internet and written to the auxiliary storage unit 13 in response to an operation by the user of the information terminal device 10. That is, the transfer of the information terminal device 10 to the user is performed with the client app APA not stored in the auxiliary storage unit 13. However, the information terminal device 10 in a state where the client app APA is stored in the auxiliary storage unit 13 may be transferred to the user.

[0017] The touch panel 14 functions as an input device and a display device of the information terminal device 10. The communication unit 15 is an interface for data communication via the communication network 40. As the communication unit 15, for example, a well-known communication device for performing data communication via a mobile communication network or the Internet can be used. The transmission path 16 includes an address bus, a data bus, control signal lines, etc., and transmits data and control signals exchanged between the connected components.

[0018] The receipt server 20 includes a processor 21, a main memory 22, an auxiliary storage unit 23, a communication unit 24, a transmission path 25, and the like. The processor 21, the main memory 22, the auxiliary storage unit 23, and the communication unit 24 are connected by the transmission path 25. The transmission path 25 includes an address bus, a data bus, control signal lines, and the like, and transmits data and control signals exchanged between the connected components.

[0019] In the receipt server 20, by connecting the processor 21, the main memory 22, and the auxiliary storage unit 23 with the transmission path 25, a computer for performing information processing for controlling the receipt server 20 is configured. The processor 21 corresponds to the central part of the above computer. The processor 21 controls each part in order to realize various functions as the receipt server 20 according to an information processing program.

[0020] The main memory 22 corresponds to the main storage part of the above computer. The main memory 22 includes a non-volatile memory area and a volatile memory area. The main memory 22 stores an information processing program in the non-volatile memory area. Also, the main memory 22 may store data necessary for the processor 21 to execute processing for controlling each part in a non-volatile or volatile memory area. The main memory 22 uses the volatile memory area as a work area where data is appropriately rewritten by the processor 21.

[0021] The auxiliary storage unit 23 corresponds to the auxiliary storage part of the above computer. The auxiliary storage unit 23 is, for example, an EEPROM, HDD, SSD, etc. The auxiliary storage unit 23 stores data used by the processor 21 to perform various processes and data generated by the processes in the processor 21. The auxiliary storage unit 23 may also store an information processing program. One of the information processing programs stored in the auxiliary storage unit 23 is an application program (hereinafter referred to as a server app) APB for operating as the receipt server 20. A part of the storage area of the auxiliary storage unit 23 is used as a receipt database DBA. The receipt database DBA will be described later.

[0022] The communication unit 24 is an interface for data communication via the communication network 40. As the communication unit 24, for example, a well-known communication device for performing data communication via the Internet can be used. The transmission path 25 includes an address bus, a data bus, control signal lines, etc., and transmits data and control signals exchanged between the connected components.

[0023] The receipt server 20 can use, for example, a general-purpose computer device as the basic hardware. In this case, typically, the computer device in a state where the server app APB is not stored in the auxiliary storage unit 23 and the server app APB are separately transferred to the operator of the receipt server 20. The transfer of the server app APB 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 via a network. And in this case, the server app APB is written into the auxiliary storage unit 23 according to the operation by the administrator of the receipt server 20 or the installer of the receipt server 20, etc.

[0024] FIG. 2 is a diagram schematically showing the structure of a data record DRA included in the receipt database DBA. The receipt database DBA is a set of data records DRA. One data record DRA is associated with an electronic receipt for one transaction. The data record DRA includes fields FIA, FIB, FIC, FID, FIE, and FIF. In field FIA, an electronic receipt ID is set as the identifier of the associated electronic receipt. In field FIB, a user ID is set as the identifier of the user of the associated electronic receipt. In field FIC, receipt data, which is the main content of the associated electronic receipt, is set. Note that the receipt data itself may be kept as an independent data file, and the file path of the receipt data may be set in field FIC. In field FID, first stamp data is set when the associated electronic receipt is defined as the target of the first stamp. When the associated electronic receipt is not the target of the first stamp, field FID is left blank or predetermined invalid data is set. In field FIE, second stamp data is set when the associated electronic receipt is defined as the target of the second stamp. When the associated electronic receipt is not the target of the second stamp, field FIE is left blank or predetermined invalid data is set. In field FIF, when an associated electronic receipt has an attached footer, data representing an image of the footer (hereinafter referred to as a footer image) is set. Note that the footer image may be kept as an independent data file, and the file path of the footer image data file may be set in field FIF. When an attached footer is not provided for the associated electronic receipt, field FIF is left blank or predetermined invalid data is set.

[0025] Next, the operation of the electronic receipt system 100 configured as described above will be explained. Note that the content of each of the various processes described below is an example, and changes in the order of some processes, omission of some processes, or addition of other processes are possible as appropriate. The POS system 30 registers the details of transactions such as product sales in a store and performs accounting as is well known. And when the customer is a user of the electronic receipt service for a transaction, the POS system 30 transmits receipt data including the information to be shown on the receipt for the corresponding transaction, along with the notification of the user ID assigned to the user, to the receipt server 20. The information to be shown on the receipt is, for example, the name of the store where the transaction was conducted, the date, year, month, day, and time when the transaction was conducted, the product name and unit price of the product that was the subject of the transaction, the subtotal amount, the deposit amount, the change amount, and so on.

[0026] When the processor 21 in the receipt server 20 receives receipt data from the POS system 30, it generates a new data record DRA with this receipt data set in the field FIC and adds it to the receipt database DBA. The processor 21 sets an electronic receipt ID determined according to a predetermined rule in the field FIA of the data record DRA generated here. The processor 21 sets the user ID notified together with the receipt data in the field FIC of the data record DRA generated here. If the electronic receipt associated with the data record DRA generated here is the target of the first stamp, the processor 21 sets the first stamp data including the stamp name of the first stamp and the management data indicating that it has not been set yet in the field FID. If the electronic receipt associated with the data record DRA generated here is the target of the second stamp, the processor 21 sets the second stamp data including the stamp name of the second stamp and the management data indicating that it has not been set yet in the field FIE. If the electronic receipt associated with the data record DRA generated here is to be accompanied by a footer, the processor 21 sets the footer image in the field FIF. In this embodiment, when an electronic receipt is the target of one stamp, it is the target of the first stamp. The footer image is assumed to be an image proving the right to disappear under certain conditions. The footer image is, for example, an image representing a discount coupon or a coupon ticket.

[0027] Thus, the management data included in the first stamp data and the second stamp data indicates whether to display the first stamp and the second stamp as display elements, and indicates not to display them in the initial state. Therefore, the auxiliary storage unit 23 is an example of storage means for storing such management data. Also, the data of the footer image is stored in the auxiliary storage unit 23 when it should be represented on the receipt screen, and is not stored when it should not be represented. That is, the data also functions as management data indicating whether to display the footer image as a display element. Therefore, the auxiliary storage unit 23 is an example of storage means for storing such management data.

[0028] Note that whether the first stamp is to be applied, whether the second stamp is to be applied, and whether to attach a footer may be determined by the processor 21 according to a pre-determined rule, or may be specified from the POS system 30.

[0029] When the need for activation as a client of the electronic receipt service arises in the information terminal device 10, the processor 11 starts information processing based on the client application APA (hereinafter referred to as client processing).

[0030] FIG. 3 and FIG. 4 are flowcharts of client processing by the processor 11. As ACT11 in FIG. 3, the processor 11 executes an authentication process. This authentication process is a process for authenticating that the operator of the information terminal device 10 is a user of the electronic receipt service. If the processor 11 succeeds in authentication, it proceeds to ACT12.

[0031] As ACT12, the processor 11 displays a main screen. The main screen is an operation screen for the user to select functions to be used from among various functions realized by the client processing. For example, the processor 11 instructs the touch panel 14 to display a screen predetermined as the main screen. As ACT13, the processor 11 waits for some operation to be performed. Then, if an operation such as an operation on the touch panel 14 is performed, the processor 11 determines YES and proceeds to ACT14.

[0032] As ACT14, the processor 11 checks whether the above operation is an operation for specifying the receipt viewing function. Then, if an operation other than the relevant operation is performed, the processor 11 determines NO and shifts to the process corresponding to the performed operation. Note that the process in this case is not a feature of the present embodiment, so the description thereof is omitted. On the other hand, if the receipt viewing function is specified by a predetermined operation on the touch panel 14, for example, the processor 11 determines YES and proceeds to ACT15.

[0033] As ACT15, the processor 11 requests a list screen from the receipt server 20. For example, the processor 11 transmits request data including identification data for identifying that it is a request for a list screen and, for example, the user ID acquired in ACT11 from the communication unit 15 to the communication network 40 addressed to the receipt server 20. Note that various requests described below are realized by exchanging request data including identification data for identifying the purpose of the request via the communication network 40 in the same manner as above.

[0034] When this request data is transmitted to the receipt server 20 by the communication network 40 and received by the communication unit 24, the processor 21 starts information processing based on the server application APB (hereinafter referred to as server processing). Note that when the processor 21 receives a request for a list screen from another information terminal device 10 during the execution of the server processing, it starts a new server processing by a thread different from the running server processing. That is, the processor 21 may execute a plurality of server processes in parallel. In the following description of the server processing, when simply referring to the information terminal device 10 and the user, it shall refer to the information terminal device 10 that made the request that triggered the start of the server processing described in the description and its operator.

[0035] FIG. 5 and FIG. 6 are flowcharts of server processing by the processor 21. As ACT41 in FIG. 5, the processor 21 generates a list screen. The list screen is a screen representing a list of electronic receipts managed for the user. For example, the processor 21 extracts all data records DRA in which the user ID included in the request data for requesting the list screen is set in the field FIB from the receipt database DBA. Then, for example, the processor 21 obtains the transaction date and time and the store name from the receipt data set in the field FIC of the extracted data record DRA, determines the list screen as a screen representing a list arranged thereof, and generates screen data representing the list screen. Further, the processor 21 represents each electronic receipt ID shown on the list screen, and attaches an instruction to notify the electronic receipt ID regarding the electronic receipt specified upon request of the receipt screen according to the specification of the electronic receipt on the list screen to the screen data.

[0036] As ACT42, the processor 21 instructs the information terminal device 10 to display the list screen. For example, the processor 21 transmits instruction data including identification data for identifying that it is an instruction for screen display and screen data representing the list screen from the communication unit 24 to the communication network 40 addressed to the information terminal device 10. Note that various instructions described below are realized by exchanging request data including identification data for identifying the purpose of the instruction via the communication network 40 in the same manner as described above.

[0037] After the processor 11 in the information terminal device 10 requests the list screen as ACT15 in FIG. 3, it proceeds to ACT16. As ACT16, the processor 11 waits for an instruction to display the list screen. Then, for example, when the instruction data transmitted from the receipt server 20 as described above is transmitted to the information terminal device 10 by the communication network 40 and received by the communication unit 15, the processor 11 determines YES and proceeds to ACT17.

[0038] As ACT17, the processor 11 displays a list screen. For example, the processor 11 causes the touch panel 14 to display the list screen represented by the screen data included in the instruction data. The user designates an e-receipt to be displayed from the list screen displayed on the touch panel 14 by a predetermined operation such as tapping an area where the transaction date and time and the store name related to the e-receipt are shown.

[0039] As ACT18, the processor 11 waits for some operation to be performed. Then, if an operation on the touch panel 14 or the like is performed, the processor 11 determines YES and proceeds to ACT19. As ACT19, the processor 11 checks whether the above operation is an operation for designating an e-receipt. If an operation different from the corresponding operation is performed, the processor 11 determines NO and shifts to the process corresponding to the performed operation. Note that the process in this case is not a feature of the present embodiment, so the description thereof is omitted. On the other hand, if an operation for designating an e-receipt is performed, the processor 11 determines YES and proceeds to ACT20. As ACT20, the processor 11 requests a receipt screen from the receipt server 20. The request data here includes the e-receipt ID of the designated e-receipt (hereinafter referred to as the designated receipt).

[0040] In the receipt server 20, after the processor 21 instructs to display the list screen as ACT42 in FIG. 5, it proceeds to ACT43. As ACT43, the processor 21 waits for a receipt screen to be requested. Then, if a receipt screen is requested from the information terminal device 10 as described above, the processor 21 determines YES and proceeds to ACT44.

[0041] As ACT44, the processor 21 generates a receipt screen. The receipt screen is a screen for allowing the user to visually view the specified receipt. For example, the processor 21 extracts from the receipt database DBA a data record DRA in which the electronic receipt ID included in the request data for requesting the receipt screen is set in the field FIA. For example, the processor 21 determines a receipt screen as a screen representing the details of the transaction based on the receipt data set in the field FIC of the extracted data record DRA, and generates screen data representing the receipt screen.

[0042] As ACT45, the processor 21 checks whether the specified receipt is the target of the first stamp. For example, if the first stamp data is set in the field FID of the data record DRA extracted in ACT44, the processor 21 determines YES and proceeds to ACT46. As ACT46, the processor 21 checks whether the first stamp has been set. For example, if it is indicated that the management data included in the first stamp data set in the field FID of the data record DRA extracted in ACT44 has not been set, the processor 21 determines NO and proceeds to ACT47. As described above, the management data of the first stamp data is in a state indicating that it has not been set in the initial state.

[0043] As ACT47, the processor 21 attaches a stamp instruction to the screen data generated in ACT44. The stamp instruction defines the process of receiving an operation on the information terminal device 10 for attaching the first stamp to the receipt screen. The stamp instruction is described, for example, in JavaScript (registered trademark). If the processor 21 indicates that the management data of the first stamp data has been set, it determines YES in ACT46 and proceeds to ACT48, which will be described later.

[0044] As ACT49, the processor 21 checks whether the designated receipt is the target of the second stamp. For example, if the second stamp data is set in the field FIE of the data record DRA extracted in ACT44, the processor 21 determines YES and proceeds to ACT50.

[0045] As ACT50, the processor 21 checks whether the second stamp has been set. For example, if the management data included in the second stamp data set in the field FIE of the data record DRA extracted in ACT44 is not set, the processor 21 determines NO and proceeds to ACT51. As described above, the management data of the second stamp data is in a state indicating that it is not set in the initial state.

[0046] As ACT51, the processor 21 edits the stamp instruction attached to the screen data in ACT47. The processor 21 rewrites the stamp instruction to define the process of receiving an operation on the information terminal device 10 to attach the first stamp or the second stamp to the receipt screen. Note that if the management data of the second stamp data indicates that it has been set, the processor 21 determines YES in ACT50 and proceeds to ACT52. This case will be described later.

[0047] After finishing ACT51, the processor 21 proceeds to ACT53 in FIG. 6. If the first stamp data is not set in the field FID of the data record DRA extracted in ACT44, the processor 21 determines NO in ACT45, assuming that the designated receipt is not the target of the first stamp, passes through ACT46 to ACT52, and proceeds to ACT53 in FIG. 6. Also, if the second stamp data is not set in the field FIE of the data record DRA extracted in ACT44, the processor 21 determines NO in ACT49, assuming that the designated receipt is not the target of the second stamp, passes through ACT50 to ACT52, and proceeds to ACT53 in FIG. 6.

[0048] As ACT53, the processor 21 checks whether there is a footer to be attached to the designated receipt. For example, if the data of the footer image is set in the field FIF of the data record DRA extracted in ACT44, the processor 21 determines YES and proceeds to ACT54. As ACT54, the processor 21 changes the receipt screen to include the footer image. For example, the processor 21 changes the screen data of the receipt screen to add the footer image represented by the data set in the field FIF of the data record DRA extracted in ACT44 at the end of the receipt screen when proceeding to ACT54.

[0049] As ACT55, the processor 21 attaches a footer command to the screen data changed in ACT54. The footer command defines the process of receiving an operation on the information terminal device 10 to erase the footer image from the receipt screen. The footer command is described by, for example, JavaScript (registered trademark). When the processor 21 finishes ACT55, it proceeds to ACT56. If the data of the footer image is not set in the field FIF of the data record DRA extracted in ACT44, the processor 21 determines NO in ACT53, assuming that there is no footer to be attached to the designated receipt, passes ACT54 and ACT55, and proceeds to ACT56. As ACT56, the processor 21 instructs the information terminal device 10 to display the receipt screen. The instruction data here includes the screen data of the receipt screen when proceeding to ACT56.

[0050] In the information terminal device 10, after the processor 11 requests the receipt screen in ACT20 in FIG. 3, it proceeds to ACT21. As ACT21, the processor 11 waits for an instruction to display the receipt screen. If the processor 11 determines YES when the instruction to display the receipt screen is received from the receipt server 20 as described above, it proceeds to ACT22 in FIG. 4. As ACT22, the processor 11 displays a receipt screen. For example, the processor 11 causes the receipt screen represented by the screen data included in the instruction data to be displayed on the touch panel 14.

[0051] FIG. 7 is a diagram showing a receipt screen SCA as an example. The receipt screen SCA includes regions ARA, ARB, and ARC. Region ARA is a region representing a store logo. Region ARB is a region representing information included in the receipt data. Region ARC is a region representing a footer image. FIG. 7 is an example in which a footer image representing a coupon is attached.

[0052] As ACT23 in FIG. 4, the processor 11 waits for some operation to be performed. Then, if an operation on the touch panel 14 or the like is performed, the processor 11 determines YES and proceeds to ACT24. As ACT24, the processor 11 checks whether a stamp instruction is attached to the screen data of the receipt screen. Then, if a stamp instruction is attached, the processor 11 determines YES and proceeds to ACT25.

[0053] As ACT25, the processor 11 checks whether the above operation is an operation defined by the stamp instruction. Here, it is assumed that an operation of continuously tapping within region ARA for a predetermined time (hereinafter referred to as a long press) is defined by the stamp instruction. Therefore, when the user sets a stamp on the displayed electronic receipt, the user long-presses the logo.

[0054] When such a long press is input by the touch panel 14, the processor 11 determines YES in ACT25 assuming that the defined operation has been performed, and proceeds to ACT26. As ACT26, the processor 11 displays a selection window over the receipt screen that is currently being displayed. The selection window is a window for allowing the user to select a stamp to be set.

[0055] FIG. 8 is a diagram showing a selection window WIA as an example. FIG. 8 shows an example in the case where the area ARA of the receipt screen SCA shown in FIG. 7 is long-pressed. Further, FIG. 8 shows an example in a state where the designated receipt is the target of the first and second stamps and neither the first nor the second stamp is set. For this reason, the processor 11 sets the selection window WIA as a window representing a button BUA for designating the first stamp and a button BUB for designating the second stamp. If the designated receipt is the target of the first and second stamps and only the first stamp is not set, the processor 11 sets the selection window as a window representing the button BUA and not representing the button BUB. If the designated receipt is the target of the first and second stamps and only the second stamp is not set, the processor 11 sets the selection window as a window not representing the button BUA and representing the button BUB. If the designated receipt is only the target of the first stamp, the processor 11 sets the selection window as a window representing the button BUA and not representing the button BUB. The user designates the stamp to be set by a predetermined operation such as touching the button BUA or the button BUB, for example.

[0056] As ACT27 in FIG. 4, the processor 11 waits for some operation to be performed. Then, if an operation such as an operation on the touch panel 14 is performed, the processor 11 determines YES and proceeds to ACT24. As ACT24, the processor 11 checks whether or not the above operation is an operation for designating a stamp. Then, if an operation other than the corresponding operation is performed, the processor 11 determines NO and shifts to the process according to the performed operation. Note that the process in this case is not a feature of the present embodiment, and thus the description thereof is omitted. On the other hand, if an operation for designating the stamp to be set is performed as described above, the processor 11 determines YES and proceeds to ACT29.

[0057] As ACT29, the processor 11 requests a set of stamps from the receipt server 20. The processor 11 includes in the request data here data indicating which of the first stamp and the second stamp is specified. For example, the processor 11 executes the above ACT25 to ACT29 according to the stamp command attached to the screen data of the receipt screen.

[0058] In the receipt server 20, after the processor 21 instructs the display of the receipt screen as ACT56 in FIG. 6, it proceeds to ACT57. As ACT57, the processor 21 checks whether a set of stamps is requested. If the processor 21 cannot confirm the corresponding request, it determines NO and proceeds to ACT58. As ACT58, the processor 21 checks whether footer deletion is requested. If the processor 21 cannot confirm the corresponding request, it determines NO and returns to ACT57. Thus, as ACT57 and ACT58, the processor 21 waits for a set of stamps or footer deletion to be requested. If a set of stamps is requested as described above, the processor 21 determines YES at ACT57 and proceeds to ACT59.

[0059] As ACT59, the processor 21 updates the receipt database DBA to set a stamp in response to a request. For example, if a set of the first stamp is requested, the processor 21 rewrites the management data included in the first stamp data set in the field FID of the data record DRA extracted in ACT44 to a state indicating that it has been set. For example, if a set of the second stamp is requested, the processor 21 rewrites the management data included in the second stamp data set in the field FIE of the data record DRA extracted in ACT44 to a state indicating that it has been set. Thus, by the processor 21 executing information processing based on the server application APB, the computer having the processor 21 as a central part functions as an update means.

[0060] As ACT60, the processor 21 changes the receipt screen based on the data record DRA updated as described above. For example, if the management data of the first stamp data is in a state indicating that it has been set, the processor 21 changes the receipt screen to add and represent the first stamp.

[0061] As ACT61, the processor 21 changes the stamp command attached to the screen data in response to the stamp being changed to the set state. That is, for example, when a stamp command that defines that both the first and second stamps are targeted and that either one of them can be specified is attached to the screen data, the processor 21 changes the stamp command to define that only a stamp different from the stamp set this time can be specified. Also, for example, when a stamp command that defines that either one of the first and second stamps can be specified is attached to the screen data, the processor 21 deletes the stamp command.

[0062] After that, the processor 21 repeats ACT56 and subsequent steps in the same manner as described above. As a result, the processor 21 instructs the information terminal device 10 to redisplay the receipt screen, accompanied by a notification of the receipt screen and the screen data in which the stamp instruction has been changed.

[0063] In the information terminal device 10, after the processor 11 requests a stamp set as ACT29 in FIG. 4, it proceeds to ACT33. Then, when the processor 11 is instructed to redisplay the receipt screen as described above, it determines YES and repeats the processing after ACT22 in the same manner as described above. As a result, the processor 11 causes the changed receipt screen as described above to be displayed on the touch panel 14.

[0064] FIG. 9 is a diagram showing a part of a receipt screen SCB as an example of a state in which the first stamp is set. The receipt screen SCB is an example in the case where an operation for instructing the setting of the first stamp is performed during the display of the receipt screen SCA shown in FIG. 7. In this receipt screen SCB, a stamp STA is added to the receipt screen SCA.

[0065] By the way, when no stamp instruction is attached to the screen data of the receipt screen, the processor 11 determines NO at ACT24 in FIG. 4 and proceeds to ACT30. Also, when the operation performed during the display of the receipt screen is not an operation defined by the stamp instruction, the processor 11 determines NO at ACT25 in FIG. 4 and proceeds to ACT30.

[0066] As ACT30, the processor 11 checks whether a footer instruction is attached to the screen data of the receipt screen. Then, if a footer instruction is attached, the processor 11 determines YES and proceeds to ACT31. As ACT31, the processor 11 checks whether the above operation is an operation defined by the footer instruction. Here, it is assumed that a long press within the area ARC is defined by the footer instruction.

[0067] By presenting the receipt screen SCA displayed on the touch panel 14 to the store clerk, the user can use the coupon represented in the area ARC. If the usage conditions of the coupon represented in the area ARC are met, the store clerk performs a discount based on the coupon by performing a predetermined operation such as reading the barcode in the coupon, and then instructs the user to delete the coupon. The user long-presses within the area ARC in response to the instruction from the store clerk.

[0068] When such a long press is input by the touch panel 14, the processor 11 determines YES at ACT31 assuming that a defined operation has been performed and proceeds to ACT32. Note that the processor 11 may further prompt the user to specify whether to execute the deletion, and proceed to ACT32 if execution is specified. In this case, for example, if it is specified not to execute the deletion, the processor 11 returns to the waiting state of ACT23.

[0069] As ACT32, the processor 11 requests the receipt server 20 to delete the footer. Note that if no footer command is attached, the processor 11 determines NO at ACT30, and if the performed operation is not the operation defined by the footer command, the processor 11 determines NO at ACT31, and in either case, proceeds to the process corresponding to the performed operation. Since the process in this case is not a feature of this embodiment, its description is omitted. For example, the processor 11 executes the above ACT30 to ACT32 according to the footer command attached to the screen data of the receipt screen.

[0070] If the deletion of the footer is requested as described above in the receipt server 20, the processor 21 determines YES at ACT58 in FIG. 6 and proceeds to ACT62. As ACT62, the processor 21 updates the receipt database DBA to delete the footer according to the request. For example, the processor 21 deletes the data of the footer image set in the field FIF of the data record DRA extracted in ACT44. In addition, management data indicating whether to display the footer image may be set in the field FIF or another field together with the data of the footer image, and the footer image may be made non-displayed by changing this management data. Thus, by the processor 21 executing the information processing based on the server application APB, the computer with the processor 21 as the central part functions as an update means.

[0071] As ACT63, the processor 21 changes the receipt screen based on the data record DRA updated as described above. The processor 21 deletes the footer image included in the receipt screen. As ACT64, the processor 21 deletes the footer instruction attached to the screen data. After this, the processor 21 repeats ACT56 and subsequent steps in the same manner as described above. Thereby, the processor 21 instructs the information terminal device 10 to redisplay the receipt screen, accompanied by notification of the screen data of the receipt screen from which the footer image has been deleted.

[0072] In the information terminal device 10, after the processor 11 requests deletion of the footer as ACT32 in FIG. 4, it proceeds to ACT33. Then, when the processor 11 determines YES when the display of the receipt screen is instructed again as described above, it repeats the processing after ACT22 in the same manner as described above. Thereby, the processor 11 causes the changed receipt screen to be displayed on the touch panel 14 as described above.

[0073] FIG. 10 is a diagram showing a receipt screen SCC as an example of a state in which the footer image has been deleted. The receipt screen SCC is an example when an operation to instruct deletion of the footer is performed during the display of the receipt screen SCA shown in FIG. 7. This receipt screen SCC does not have the area ARC included in the receipt screen SCA.

[0074] Now, for the receipt screen designated from the list screen, if the first stamp has been set in the past as described above, the processor 21 determines YES at ACT46 in FIG. 5 and proceeds to ACT48. As ACT48, the processor 21 changes the receipt screen to represent the first stamp. That is, even if the first stamp has been set, first at ACT44, the processor 21 generates a receipt screen in a state that does not represent the first stamp. Then, as ACT48, the processor 21 changes the receipt screen to represent the first stamp. Then, the processor 21 proceeds to ACT49.

[0075] Now, for the receipt screen designated from the list screen, if the second stamp has been set in the past as described above, the processor 21 determines YES at ACT50 in FIG. 5 and proceeds to ACT52. As ACT52, the processor 21 changes the receipt screen to represent the second stamp. That is, even if the second stamp has been set, first at ACT44, the processor 21 generates a receipt screen in a state that does not represent the second stamp. Then, as ACT50, the processor 21 changes the receipt screen to represent the second stamp. Then, the processor 21 proceeds to ACT53 in FIG. 6. Note that prior to executing ACT44, the processor 21 may check the setting status of the first stamp and the second stamp and generate a receipt screen that reflects the setting status at ACT44.

[0076] For the receipt screen designated from the list screen, if the footer image was initially attached but has been deleted as described above, the processor 21 determines NO at ACT53 in FIG. 6 and passes through ACT54 and ACT55 as described above. Therefore, in this case, the footer image is not represented on the receipt screen for which display is instructed at ACT56.

[0077] In this way, the processor 21 generates a receipt screen representing display elements that are supposed to be displayed by data having a function as management data set in the receipt database DBA. Thus, by the processor 21 executing information processing based on the server application APB, the computer with the processor 21 as the central part functions as a generation means.

[0078] As described above, for the receipt screen targeted for stamping, the receipt server 20 sets a stamp according to an operation on the information terminal device 10, and thereafter, the set stamp is represented on the receipt screen. Therefore, according to the receipt server 20, the service realized by stamping on a paper receipt can also be provided for an electronic receipt.

[0079] Also, the receipt server 20 deletes the footer image attached to the receipt screen according to an operation on the information terminal device 10, and thereafter, the receipt screen does not represent the footer image. Therefore, according to the receipt server 20, the service realized by cutting and collecting a part of a paper receipt can also be provided for an electronic receipt.

[0080] This embodiment can be variously modified as follows. It may be possible to perform only one of adding a stamp and deleting a footer image.

[0081] The number of stamps that can be added may be only one or three or more.

[0082] The position representing the stamp on the receipt screen, the shape of the stamp, etc. can be arbitrarily changed.

[0083] The process for changing the receipt screen being displayed on the information terminal device 10 in response to an instruction to set a stamp may be executed by the processor 11 in the information terminal device 10.

[0084] The image to be deleted is not limited to the footer image attached to the end of the receipt screen, and may be an image shown at the beginning or in the middle.

[0085] The process for changing the receipt screen being displayed on the information terminal device 10 in response to an instruction to delete an image may be executed by the processor 11 in the information terminal device 10.

[0086] The operation area for instructing the setting of a stamp may be any predetermined area other than the area ARA. Also, the operation may be any predetermined operation other than a long press.

[0087] The operation area for instructing the deletion of an image may be any predetermined area other than the area ARC. Also, the operation may be any predetermined operation other than a long press.

[0088] Each function realized by the processors 11 and 21 through information processing may also be realized in part or in whole by hardware that executes information processing not based on a program such as a logic circuit. Also, each of the above functions can also be realized by combining software control with the above hardware such as a logic circuit.

[0089] Although some embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be implemented in various other forms, and various omissions, replacements, and changes can be made without departing from the gist of the invention. These embodiments and their modifications are included in the scope and gist of the invention, and are also included in the invention described in the claims and its equivalent scope.

Explanation of Reference Numerals

[0090] 10… Information terminal device, 11… Processor, 12… Main memory, 13… Auxiliary storage unit, 14… Touch panel, 15… Communication unit, 16… Transmission path, 20… Receipt server, 21… Processor, 22… Main memory, 23… Auxiliary storage unit, 24… Communication unit, 25… Transmission path, 30… POS system, 40… Communication network, 100… Electronic receipt system, 200… Communication network.

Claims

1. Storage means for storing management data for managing whether to display display elements; Generating means for generating a receipt screen representing the content of a transaction and to be displayed on an information terminal device, by adding display elements to be displayed based on the management data stored by the storage means; Updating means for updating the management data according to an operation on the information terminal device in the receipt screen generated by the generating means; A receipt server comprising the above.

2. The updating means updates the management data, which represents non-display in the initial state, to represent display according to an operation on the information terminal device. The receipt server according to Claim 1.

3. When the management data represents display, the generating means represents, on the receipt screen, a stamp indicating that predetermined processing has been completed. The receipt server according to Claim 2.

4. The updating means updates the management data, which represents display in the initial state, to represent non-display according to an operation on the information terminal device. The receipt server according to Claim 1.

5. When the management data represents display, the generating means represents, on the receipt screen, an image certifying the right to disappear under predetermined conditions. The receipt server according to Claim 4.

6. An information processing program for causing a computer provided in a receipt server, together with storage means for storing management data for managing whether to display display elements, to function as: Generating means for generating a receipt screen representing the content of a transaction and to be displayed on an information terminal device, by adding display elements to be displayed based on the management data stored by the storage means; Updating means for updating the management data according to an operation on the information terminal device in the receipt screen generated by the generating means. ​

Images