Electronic receipt issuance system, information processing device, and electronic receipt issuance method

Abstract

To provide an electronic receipt issuance system with high freedom degree and versatility of electronic receipt issuance, an information processing device, and an electronic receipt issuance method.SOLUTION: An electronic receipt issuance system comprises: a transaction information generation unit which generates transaction information on the basis of a commodity registered for settlement processing; a membership information acquisition unit which acquires information for identifying an electronic receipt membership when registering the commodity; a print data generation unit which generates print data for causing a printer to issue a paper receipt corresponding to the transaction information; a coordination data generation unit which generates coordination data including information specifying a format corresponding to the paper receipt and based on the transaction information when electronic receipt data is determined to be generated according to the information for identifying the electronic receipt membership; and an electronic receipt generation unit which generates electronic receipt data using the coordination data.SELECTED DRAWING: Figure 10

Description

[Technical field]

[0001] An embodiment of the present invention relates to an electronic receipt issuing system, an information processing device, and an electronic receipt issuing method. [Background technology]

[0002] Electronic receipts, which replace paper receipts, have been put to practical use. Electronic receipts are displayed on a terminal device and allow users to refer to the details of a transaction (for example, Patent Document 1).

[0003] In existing technology, for example, if the printing data used in a transaction process that includes product information registration and payment contains specific character information during the process of issuing a receipt at the end of the transaction process, electronic receipt data is generated instead of a paper receipt. Electronic receipt data is data for displaying an electronic receipt on a terminal device. The specific character information is inserted into the printing data if the user is an electronic receipt member.

[0004] The above-described process limits the timing at which electronic receipt data can be generated (electronic receipt can be issued). In other words, it is difficult to issue an electronic receipt once the receipt issuing process executed in a series of transaction processes is completed.

[0005] In order to eliminate the problems mentioned above and make electronic receipts even easier to use, there is a growing demand for highly versatile systems that allow for greater freedom in the timing of issuance, for example. Summary of the Invention [Problem to be solved by the invention]

[0006] An object of the present invention is to provide a system, an information processing device, and an electronic receipt issuing method that provide a high degree of freedom and versatility in issuing electronic receipts. [Means for solving the problem]

[0007] The electronic receipt issuing system of the embodiment includes a transaction information generation unit that generates transaction information based on products registered for payment processing, a member information acquisition unit that acquires information identifying an electronic receipt member when registering the products, a print data generation unit that generates print data for a printer to issue a paper receipt corresponding to the transaction information, an association data generation unit that, when it is determined to generate electronic receipt data according to the information identifying the electronic receipt member, generates association data based on the transaction information including information specifying a format corresponding to the paper receipt, and an electronic receipt generation unit that generates electronic receipt data using the association data. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram illustrating an example of a system configuration of the first embodiment. [Diagram 2] FIG. 2 is a block diagram showing an example of the configuration of a transaction system server. [Diagram 3] FIG. 3 is a block diagram showing an example of the configuration of the electronic receipt server. [Figure 4] FIG. 4 is a block diagram showing an example of the configuration of a tablet POS. [Diagram 5] FIG. 5 is a block diagram showing an example of information stored in the DB. [Figure 6] FIG. 6 is a diagram showing an example of HTML data stored in the DB. [Figure 7] FIG. 7 is a diagram showing an example of paper receipt print data stored in the DB. [Figure 8] FIG. 8 is a diagram showing an example of the display content of a paper receipt printed and output by the printer. [Figure 9] FIG. 9 is a diagram illustrating an example of electronic receipt linkage data stored in the DB. [Figure 10] FIG. 10 is a block diagram illustrating an example of a functional configuration of the control unit. [Figure 11]FIG. 11 is a diagram illustrating an example of a flow of processing executed by the control unit. [Figure 12] FIG. 12 is a diagram showing an example of the flow of processing executed by the control unit of the tablet POS. [Figure 13] FIG. 13 is a diagram showing an example of the flow of processing executed by the control unit of the transaction system server. [Figure 14] FIG. 14 is a diagram showing an example of a transaction completion screen displayed by the tablet POS. [Figure 15] FIG. 15 is a diagram showing an example of a balance screen displayed by the tablet POS. [Figure 16] FIG. 16 is a block diagram illustrating an example of a functional configuration of the control unit according to the second embodiment. [Figure 17] FIG. 17 is a diagram illustrating an example of electronic receipt linkage data stored in the DB according to the third embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] (First embodiment) An embodiment will be described with reference to the drawings. Fig. 1 is a diagram showing an example of the configuration of a system according to the embodiment. The system according to the embodiment includes a transaction system server 1, a DB (database) 2, an electronic receipt server 3, a tablet POS 5, a relay device 6, and a printer 7.

[0010] The tablet POS 5 is a type of POS terminal installed in a store. The POS terminal is an embodiment of a sales data processing device that processes product registration and payment for registered products. Note that "POS" is an abbreviation for "Point Of Sale" and means point-of-sale information management.

[0011] The store is also equipped with other types of POS terminals besides the tablet POS 5. Examples of other types of POS terminals include general stationary POS registers operated by store clerks, self-checkout devices, and semi-self-checkout devices. A self-checkout device is a device that allows a customer to register products and perform operations related to payment by himself / herself. A semi-self-checkout device is a device that allows a customer to perform operations related to payment by himself / herself using product information registered by a store clerk.

[0012] The relay device 6 relays data transmission and reception between the tablet POS 5 and peripheral devices such as the printer 7. For example, the relay device 6 transmits instructions received from the tablet POS 5 to the printer 7 to print a receipt.

[0013] The tablet POS 5 may be provided with a relay unit 61, which is a functional unit that performs the same function as the relay device 6. The relay device 6 and the relay unit 61 are used differently in the following manner: for example, when a peripheral device such as the printer 7 is to be used in a wired connection, the peripheral device is wired to the relay device 6, and wireless communication is performed between the relay device 6 and the tablet POS 5. Also, when a peripheral device such as the printer 7 is capable of wireless communication, wireless communication is performed between the peripheral device and the relay unit 61.

[0014] Printer 7 issues printed materials such as receipts. Printer 7 has a built-in printing unit and roll paper. The printing unit is made up of a print head and a platen roller. Roll paper is a strip of paper wound into a roll. The platen roller holds the paper pulled out from the roll paper between the print head and the platen roller, and transports the paper by rotating. The print head prints characters, logos, etc. on the paper as it is transported.

[0015] The transaction system server 1 and DB2 are interposed between the store's POS terminal (e.g., tablet POS 5) and the electronic receipt server 3, providing cloud computing to both and mediating data linkage between the two. The transaction system server 1 can refer to the information stored in DB2 and updates the information stored in DB2.

[0016] The transaction system server 1 receives information on transactions (transaction information) performed by the store's POS terminal and stores this in DB 2. It also generates HTML data, data for printing paper receipts, and data for linking with electronic receipts based on the transaction information in response to instructions received from the store's POS terminal. The transaction system server 1 sends the generated data for printing paper receipts to the printer 7, and sends the data for linking with electronic receipts to the electronic receipt server 3.

[0017] When the electronic receipt server 3 receives the electronic receipt linking data from the transaction system server 1, it generates electronic receipt data and stores it. In addition, in response to a reference request from a terminal device used by a customer, the electronic receipt server 3 provides the electronic receipt desired by the customer so that the electronic receipt can be referenced on the customer's terminal device.

[0018] 2 is a block diagram showing an example of the configuration of the transaction system server 1. The transaction system server 1 includes a CPU (Central Processing Unit) 11, a ROM (Read Only Memory) 12, a RAM (Random Access Memory) 13, a communication unit 14, a storage unit 19, etc.

[0019] The CPU 11 is an example of a processor, and controls each part of the transaction system server 1. The ROM 12 stores various programs. The RAM 13 is a workspace for expanding the programs and various data. The CPU 11, the ROM 12, and the RAM 13 are connected via a bus or the like, and constitute a control unit 10 of a computer configuration.

[0020] The communication unit 14 is a communication interface that connects the control unit 10 and an external device (for example, the tablet POS 5 or the electronic receipt server 3) so that they can communicate with each other via a network.

[0021] The storage unit 19 has a storage medium such as a hard disk drive (HDD) or a flash memory, and maintains the stored contents even when the power is cut off. The storage unit 19 stores programs executable by the CPU 11 and various setting information.

[0022] The control unit 10 executes various processes by the CPU 11 operating in accordance with programs stored in the ROM 12 or the storage unit 19 and loaded into the RAM 13. This also causes the control unit 10 to provide various functional units. The various functional units are, for example, a transaction start processing unit 101, member information processing unit 102, product registration processing unit 103, payment processing unit 104, transaction information storage processing unit 105, receipt output processing unit 106, etc., which will be described later (see FIG. 10).

[0023] 3 is a block diagram showing an example of the configuration of the electronic receipt server 3. The electronic receipt server 3 includes a CPU 31, a ROM 32, a RAM 33, a communication unit 34, a storage unit 39, and the like.

[0024] The CPU 31 is an example of a processor and controls each part of the electronic receipt server 3. The ROM 32 stores various programs. The RAM 33 is a workspace for expanding the programs and various data. The CPU 31, the ROM 32, and the RAM 33 are connected via a bus or the like to constitute the control unit 30 having a computer configuration.

[0025] The communication unit 34 is a communication interface that connects the control unit 30 and an external device (for example, the transaction system server 1) so that they can communicate with each other via a network.

[0026] The storage unit 39 has a storage medium such as a HDD or flash memory, and maintains the stored contents even when the power is cut off. The storage unit 39 stores programs executable by the CPU 31 and various setting information. The storage unit 39 stores electronic receipt member information. The electronic receipt member information is stored in DB2, for example, in the form of a table.

[0027] The electronic receipt member information stores the member information (such as name and contact information) of the electronic receipt member in association with a member code, which is a unique code in the electronic receipt member information. The member code in the electronic receipt member information is an example of identification information capable of identifying the electronic receipt member.

[0028] In addition, electronic receipt member identification information (also called a member flag) indicating whether or not a customer is an electronic receipt member in the system of this embodiment can be extracted from the member code included in the electronic receipt member information. For example, if at least a part of the member code in the electronic receipt member information is a predetermined number indicating an electronic receipt member, the control unit of each device included in the present system determines that the customer who presented this member code is an electronic receipt member.

[0029] The control unit 30 executes various processes by the CPU 31 operating in accordance with programs stored in the ROM 32 or the storage unit 39 and loaded into the RAM 33. In this way, the control unit 30 also provides, for example, an API (Application Programming Interface) 306, which will be described later (see FIG. 10).

[0030] 4 is a block diagram showing an example of the configuration of the tablet POS 5. Other types of POS terminals in a store have roughly similar configurations to the tablet POS 5. The tablet POS 5 includes a CPU 51, a ROM 52, a RAM 53, a communication unit 54, a display unit 55, an operation unit 56, a sound output unit 57, an imaging unit 58, a storage unit 59, etc.

[0031] The CPU 51 is an example of a processor and controls each part of the tablet POS 5. The ROM 52 stores various programs. The RAM 53 is a workspace for developing programs and various data. The CPU 51, the ROM 52, and the RAM 53 are connected via a bus or the like to constitute a control unit 50 having a computer configuration.

[0032] The communication unit 54 is a communication interface that connects the control unit 50 and an external device (for example, the relay device 6 or the electronic receipt server 3) so that they can communicate with each other via a network.

[0033] The display unit 55 has a display device such as an LCD (Liquid Crystal Display), and displays various information under the control of the CPU 51.

[0034] The operation unit 56 has an input device such as a touch panel that is provided on the surface of the display unit 55, and outputs operation contents input via the input device to the CPU 51. The input device of the operation unit provided in the POS terminal may be a keyboard, a pointing device, or the like.

[0035] The audio output unit 57 has a speaker and a buzzer, and outputs audio under the control of the CPU 51.

[0036] The imaging unit 58 has an imaging element such as a CCD (Charge Coupled Device) or a CMOS (Complementary MOS). The imaging unit 58 is used to capture an image of a code symbol such as a barcode or a two-dimensional code attached to a product. In other words, the imaging unit 58 acquires a code symbol such as a barcode or a two-dimensional code attached to a product. The imaging unit 58 is a type of input device. The code symbol acquired by the imaging unit 58 is decoded to become code information.

[0037] The storage unit 59 has a storage medium such as a solid state drive (SSD) or a flash memory, and maintains the stored contents even when the power is cut off. The storage unit 59 stores programs executable by the CPU 51 and various setting information.

[0038] The control unit 50 executes various processes by the CPU 51 operating in accordance with programs stored in the ROM 52 and the storage unit 59 and loaded into the RAM 53. This also causes the control unit 50 to provide various functional units. The various functional units are, for example, a transaction start processing unit 501, a member information processing unit 502, a product registration processing unit 503, a payment processing unit 504, etc., which will be described later (see FIG. 10).

[0039] 5 is a block diagram showing an example of information stored in DB 2. DB 2 (an example of a storage unit, a transaction information storage unit) stores various information referenced or updated by the transaction system server 1. The information stored in DB 2 includes, for example, a product master 21, store member information 22, transaction information 25, HTML data 26, etc.

[0040] The product master 21 is information on products handled by a store. The product master 21 stores product names, unit prices, etc. in association with product codes, for example. The product code is an example of identification information capable of identifying a product, such as a JAN code.

[0041] The store member information 22 is stored in DB2, for example, in the form of a table.

[0042] The store member information 22 stores the member information (such as name and contact information) of the store member in association with a member code, which is a unique code in the store member information 22. The member code in the store member information 22 is an example of identification information capable of identifying the store member.

[0043] The transaction information 25 is text data stored in DB2 by the transaction system server 1. The file format of the transaction information 25 in this embodiment is JSON format. The transaction information 25 includes, for example, header information, footer information, and product information. The product information includes a product code, product name, unit price, purchase quantity, and the like, and is written between the header information and the footer information. The header information or footer information includes a transaction ID. The transaction ID is an example of information capable of identifying a transaction.

[0044] The HTML data 26 is an example of structured data. The HTML data 26 is information that is generated by the control unit 10 of the transaction system server 1 by editing (converting) the transaction information 25 in JSON format, such as by adding (structuring) HTML tags, and is stored in DB2.

[0045] 6 is a diagram showing an example of the HTML data 26 stored in the DB 2. The HTML data 26 includes header information 261, product information 262, payment information 263, and footer information 264.

[0046] Header information 261 is the header information of transaction information 25 with HTML tags added. Footer information 264 is the footer information of transaction information 25 with HTML tags added. Product information 262 is the product information of transaction information 25 with HTML tags added. In the figure, one product is purchased, so there is only one product information 262, but if multiple products are purchased, the product information 262 will be continuous. Settlement information 263 is various amounts and tax rates calculated based on the product information of transaction information 25, notes regarding them, etc.

[0047] The HTML data 26 includes information used for the paper receipt print data 27 and information used for the electronic receipt linkage data 28 using HTML tags.

[0048] for example," The "class" attribute of the "tag" indicates the information used in the paper receipt printing data 27. Furthermore, "class="line"" is used to specify printing of one line. "class="feed"" is used to specify paper transport. "class="cut"" specifies cutting of the paper. "class="print-logo"" is used to specify printing of a logo. The logo is stored in DB2 or in the memory unit 19 of the transaction system server 1 as image data such as a bitmap file.

[0049] " The "smartDisabled" attributes 265 and 266 of the " tag are used to indicate that the information is not required for the electronic receipt linkage data 28. The "smartPrefix" attribute 267 of the " tag is used when adding information required for the electronic receipt linking data 28 to the beginning of the part enclosed by the tag. The "smartSuffix" attribute 268 of the " tag is used to add information required for the electronic receipt linking data 28 to the end of the section enclosed by the tag. Note that the information added by the attributes 267 and 268 is used as the " " This specifies to increase the font size of the part enclosed in the tags (the line showing the total).

[0050] Also," The "doubleWide" attribute 269 of the "tag" is used to specify whether or not to specify that the font size should be doubled (double-wide font should be used) when printing the portion enclosed by the tag.

[0051] The control unit 10 of the transaction system server 1 edits (converts) the HTML data 26 to generate paper receipt print data 27, which is temporarily stored in the RAM 13 or the like.

[0052] 7 is a diagram showing an example of paper receipt printing data 27 generated by the control unit 10. Paper receipt printing data 27 is generated by editing HTML data 26. Paper receipt printing data 27 is data used by the printer 7 to print a paper receipt.

[0053] The paper receipt printing data 27 contains header information 271, product information 272, settlement information 273, and footer information 274. The contents of the header information 271, product information 272, settlement information 273, and footer information 274 roughly correspond to the header information 261, product information 262, settlement information 263, and footer information 264 contained in the HTML data 26. The paper receipt printing data 27 also contains information 279 that corresponds to the attribute 269. The information 279, "2C", indicates that while the font used to print the other lines is the normal "N", the font used to print the line in question (the line showing the total) is double-width.

[0054] The paper receipt that is output by the printer 7 based on the paper receipt printing data 27 may look, for example, as shown in Fig. 8. Fig. 8 is a diagram showing an example of display content 70 on the paper receipt that is printed and output by the printer 7.

[0055] The display content 70 of the paper receipt includes header information 701, product information 702, payment information 703, and footer information 704. The contents of the header information 701, product information 702, payment information 703, and footer information 704 correspond to the header information 271, product information 272, payment information 273, and footer information 274.

[0056] In addition, the control unit 10 edits (converts) the transaction information 25 to generate electronic receipt linkage data 28, and temporarily stores the electronic receipt linkage data 28 in the RAM 13 or the like.

[0057] 9 is a diagram showing an example of the electronic receipt linkage data 28 generated by the control unit 10. The electronic receipt linkage data 28 is generated from the transaction information 25. The electronic receipt linkage data 28 is data transmitted to the electronic receipt server 3, and is data used by the electronic receipt server 3 to generate electronic receipt data.

[0058] The electronic receipt linking data 28 includes header information 281, product information 282, settlement information 283, and footer information 284. The contents of the header information 281, product information 282, settlement information 283, and footer information 284 generally correspond to the header information 271, product information 272, settlement information 273, and footer information 274 included in the paper receipt printing data 27. The display order of the information 281-284 is adapted to the database structure constructed in the electronic receipt server 3.

[0059] Upon receiving the electronic receipt linkage data 28, the electronic receipt server 3 generates new electronic receipt data based on the electronic receipt linkage data 28. Here, generating electronic receipt data means newly registering the electronic receipt data in the electronic receipt server 3. The electronic receipt data is data that enables a customer to refer to an electronic receipt from a terminal device, in other words, data for a terminal device used by a customer to display an electronic receipt.

[0060] 10 is a block diagram showing an example of the functional configuration of the control units 10, 30, and 50. The control unit 50 of the tablet POS 5 includes a transaction start processing unit 501, a member information processing unit 502, a product registration processing unit 503, and a payment processing unit 504. The control unit 10 of the transaction system server 1 includes a transaction start processing unit 101, a member information processing unit 102, a product registration processing unit 103, a payment processing unit 104, a transaction information storage processing unit 105, and a receipt output processing unit 106. The control unit 30 of the electronic receipt server 3 includes an API 306 for generating electronic receipt data.

[0061] Here, Fig. 11 is further shown. Fig. 11 is a diagram showing an example of the flow of processing executed by the control units 10, 30, and 50. As shown in Fig. 10 and Fig. 11, the control units 10, 30, and 50 cooperate with each other to perform processing. Note that the processing of the step numbers shown in Fig. 11 corresponds to the processing of the same step numbers shown in Fig. 12 and Fig. 13 (described later).

[0062] The transaction start processing unit 101, member information processing unit 102, product registration processing unit 103 and payment processing unit 104 provided in the transaction system server 1 operate in accordance with the operation of the transaction start processing unit 501, member information processing unit 502, product registration processing unit 503 and payment processing unit 504.

[0063] That is, the transaction start processing unit 101 and the transaction start processing unit 501 cooperate to perform the transaction start processing (steps S11, S12, S31, S32). The transaction ID is issued in the transaction start processing.

[0064] Similarly, the member information processing unit 102 and the member information processing unit 502 function as an example of a member information acquisition unit that acquires information identifying an electronic receipt member when registering a product, and cooperate to perform member information processing (steps S13, S14, S33, S34). The member information processing operates upon acquisition of a member code. In the member information processing, the member code is associated with a transaction ID, and member information associated with the member code of a store member and member information associated with the member code of an electronic receipt member are acquired.

[0065] Furthermore, the product registration processing unit 103 and the product registration processing unit 503 function as an example of a transaction information generating unit that generates transaction information based on products registered for payment processing, and cooperate to perform the product registration processing (steps S15, S16, S35, S36). The product registration processing is a process of compiling registered product information and editing the transaction information 25. Specifically, the product registration processing unit 503 accepts input of a product code via the operation unit 56 and the imaging unit 58, and the product registration processing unit 103 acquires product information (such as product name and unit price) associated with the product code, and registers the product code and the product information in the transaction information 25.

[0066] Furthermore, the payment processing unit 104 and the payment processing unit 504 cooperate to perform payment processing (also called accounting processing) according to the transaction information 25 (steps S17, S18, S37, S38). In the payment processing, the price of the purchased product is paid by cash payment, credit card payment, electronic money payment, or the like.

[0067] The payment processing unit 504 also requests the receipt output processing unit 106, which serves as a print data generating unit, to generate paper receipt print data 27 (step S22).

[0068] Furthermore, when the membership code of an electronic receipt member is acquired during a transaction, the payment processing unit 504 requests the receipt output processing unit 106, which serves as an electronic receipt generating unit, to generate electronic receipt linkage data 28 (steps S23 and S24). More specifically, in response to the request to generate the electronic receipt linkage data 28, the payment processing unit 504 determines whether the member is an electronic receipt member based on the electronic receipt member identification information.

[0069] The receipt output processor 106 operates in response to the results of the payment process, and functions as an example of a print data generator, or as part of an electronic receipt generator.

[0070] The receipt output processor 106, which serves as a print data generator, generates paper receipt print data 27 that corresponds to the transaction information 25 (steps S41 and S42).

[0071] The receipt output processing unit 106, which is a part of the electronic receipt generating unit, generates electronic receipt linking data 28 corresponding to the transaction information 25, and transmits it to the API 306 (steps S43 and S44).

[0072] The API 306 of the electronic receipt server 3 cooperates with the receipt output processing unit 106 to configure an electronic receipt generating unit, and generates data (electronic receipt data) for displaying an electronic receipt on a terminal device using the electronic receipt linkage data 28.

[0073] The transaction information storage processing unit 105 operates upon receiving the result of the settlement process (steps S19 to S21), and creates or updates the information stored in DB2 (steps S39, S40).

[0074] 12 is a diagram showing an example of the flow of processing executed by the control unit 50 of the tablet POS 5. Note that the processing of step numbers shown in FIG. 12 corresponds to the processing of the same step numbers shown in FIG.

[0075] When the operation unit 56 accepts an operation instructing the start of a transaction (step S11; Yes), the control unit 50 (transaction start processing unit 501) transmits a signal indicating a transaction start request to the transaction system server 1 (step S12).

[0076] Next, when a membership code is input by obtaining a code symbol by the imaging unit 58 or by accepting an input operation by the operation unit 56 (step S13; Yes), the control unit 50 (membership information processing unit 502) transmits the membership code to the transaction system server 1 (step S14). If a membership code is not obtained (step S13; No), the control unit 50 skips step S14 and proceeds to step S15.

[0077] For the sake of convenience, the member code is acquired and transmitted in steps S13 to S14, but in reality, it can be acquired and transmitted at any time between the start of the transaction and the settlement operation (step S17; Yes). Also, the member information processing handles both the member information of the store member and the member information of the electronic receipt member.

[0078] Next, the control unit 50 (product registration processing unit 503) waits for input of a product code (step S15; No). When the product code is input via the operation unit 56 or the imaging unit 58 (step S15; Yes), the control unit 50 transmits a product registration request to the transaction system server 1 (step S16). In the product registration request, the product code is transmitted to the transaction system server 1.

[0079] The control unit 50 accepts product registration (steps S15 to S16) while no payment operation is being performed (step S17; No). When the operation unit 56 accepts a payment operation (step S17; Yes), the control unit 50 (payment processing unit 504) transmits a signal indicating a payment request to the transaction system server 1 (step S18).

[0080] Next, the control unit 50 (payment processing unit 504) checks the remaining balance (step S19). If the payment process results in the full payment of the product to be purchased being completed and there is no remaining balance (step S19; Yes), the control unit 50 (payment processing unit 504) sends a signal indicating a transaction completion request to the transaction system server 1 (step S20).

[0081] In step S19, if there is a remaining balance (if the payment is not complete) (step S19; No), the control unit 50 performs processing for an additional payment (step S21) and returns the processing to step S 19. An additional payment is performed, for example, when a payment is made with rechargeable electronic money, but the recharge amount is insufficient, resulting in a remaining balance, and an additional payment by cash or the like is required.

[0082] Next, the control unit 50 (payment processing unit 504) sends a signal to the transaction system server 1 requesting the generation of data to print a paper receipt (step S22).

[0083] Furthermore, if the control unit 50 (payment processing unit 504) has acquired a membership code of an electronic receipt member from the customer who is the other party in the transaction before the payment operation, it considers the customer to be an electronic receipt member (step S23; Yes) and sends a signal indicating an electronic receipt linkage request to the transaction system server 1 (step S24). Upon receiving a response to the electronic receipt linkage request, the control unit 50 displays a transaction completion screen (FIG. 14, described below) (step S25). However, in this example, it is assumed that the transaction system server 1 has determined that the customer is an electronic receipt member by step S24.

[0084] If the customer is not an electronic receipt member (Step S23; No), the control unit 50 (payment processing unit 504) performs a paper receipt printing request process on the printer 7. In the paper receipt printing request process, the paper receipt printing data 27 received as a response to the request made in Step S22 is sent to the printer 7.

[0085] 13 is a diagram showing an example of the flow of processing executed by the control unit 10 of the transaction system server 1. Note that the processing with step numbers shown in FIG. 13 corresponds to the processing with the same step numbers shown in FIG.

[0086] When the control unit 10 (transaction start processing unit 101) receives a transaction start request from the tablet POS 5 (step S31; Yes), it issues a transaction ID, sends the transaction ID to the tablet POS 5, generates transaction information 25 identified by the transaction ID, and stores it in DB2 (step S32).

[0087] Next, the control unit 10 (member information processing unit 102) acquires the member information if a member code has been received from the tablet POS 5 (step S33; Yes), and associates the member code with the transaction ID (step S34). Specifically, the member code is included in the transaction information 25 (JSON format) for the corresponding transaction ID. If a member code has not been received (step S33; No), the control unit 10 skips step S34 and proceeds to step S35.

[0088] For the sake of convenience, the member information is acquired in steps S33 to S34, but in reality, it can be acquired at any time between the start of the transaction and the settlement operation (step S37; Yes). The member information processing handles both the member information of the store member and the member information of the electronic receipt member.

[0089] Next, the control unit 10 (product registration processing unit 103) waits to receive a product registration request (step S35; No). When the product registration request is received (step S35; Yes), the control unit 10 obtains product information that matches the product code included in the product registration request from the product master 21 of DB2, and includes (registers) this in the transaction information 25 (step S36).

[0090] The control unit 10 accepts product registration (steps S35 to S36) while a payment request is not received (step S37; No). When a payment request is received (step S37; Yes), the control unit 10 (payment processing unit 104) performs payment processing (step S38).

[0091] Next, the control unit 10 (transaction information storage processing unit 105) waits to receive a transaction completion request (step S39; No), and upon receiving the request (step S39; Yes), ends and stores the editing of the transaction information 25 (step S40).

[0092] Next, when the control unit 10 (receipt output processing unit 106) receives a signal indicating a request to generate paper receipt print data (step S41; Yes), it generates HTML data 26 that structures the JSON format transaction information 25, and further edits the HTML data 26 to generate paper receipt print data 27. At this time, if the control unit 10 has not received a membership code for an electronic receipt member, it sets a print flag in the paper receipt print data 27 and sends it to the tablet POS 5 (step S42). The tablet POS 5 performs paper receipt printing processing according to the setting of the print flag.

[0093] Furthermore, if a request to generate print data for a paper receipt is not received (step S41; No), the control unit 10 (receipt output processing unit 106) ends this process and returns to step S31. For example, if printing of electronic receipts is stopped, a request to generate print data for a paper receipt is not sent, and the control unit 10 does not receive a request to generate print data for a paper receipt.

[0094] When the control unit 10 (receipt output processing unit 106) further receives a signal indicating an electronic receipt linking request (step S43; Yes), it performs electronic receipt linking processing (step S44). In the electronic receipt linking processing, the control unit 10 (receipt output processing unit 106) generates electronic receipt linking data 28 from the transaction information 25 and transmits the electronic receipt linking data 28 to the electronic receipt server 3.

[0095] If an electronic receipt linkage request has not been received (step S43; No), the control unit 10 (receipt output processing unit 106) skips step S44, ends this process, and returns the process to step S31.

[0096] When the electronic receipt server 3 receives the electronic receipt linkage data 28, an API 306 for generating electronic receipt data operates. The API 306 generates electronic receipt data using the electronic receipt linkage data 28. In other words, the API 306 newly generates data for displaying an electronic receipt for this transaction on a terminal device.

[0097] 14 is a diagram showing an example of a transaction completion screen displayed by the tablet POS 5. In step S25, the control unit 50 of the tablet POS 5 causes the display unit 55 to display a transaction completion screen 551. The transaction completion screen 551 includes, for example, a message 5511, a payment statement 5512, and an operator 5513.

[0098] If the transition is made from step S24, the message 5511 may be, for example, "A paper receipt will not be issued. Please check the electronic receipt with the receipt app." If the transition is made from step S26, the message 5511 may be, for example, "A paper receipt will be issued."

[0099] Payment details 5512 are contents according to the payment details. Operator 5513 accepts an operation to close transaction completion screen 551. When operator 5513 is operated, transaction completion screen 551 is closed, and the display on display unit 55 transitions to one that accepts the start of a new transaction.

[0100] 15 is a diagram showing an example of a balance screen displayed by the tablet POS 5. In steps S18 and S21, the control unit 50 of the tablet POS 5 causes the display unit 55 to display a balance screen 552. The balance screen 552 is displayed during a payment process in which an operation for paying the price is accepted.

[0101] The balance screen 552 includes a payment statement 5521, a remaining amount 5522, and operators 5523 and 5524. The payment statement 5521 includes the total price of the purchased items, the tax amount for each tax rate, the discount amount, etc. The remaining amount 5522 displays the amount to be paid. The operator 5523 accepts the selection of a payment method. Payment methods include, for example, cash, credit card payment, electronic money payment, code payment, and gift certificates. The operator 5524 accepts input of numerical values, etc., and accepts input of the amount to be paid by the payment method selected by the operator 5523. The operator 5524 illustrated in FIG. 15 is in an inoperable state. The operator 5524 becomes operable when any of the operators 5523 is selected.

[0102] With such a system, electronic receipt data for displaying an electronic receipt can be generated according to processing in a POS terminal such as the tablet POS 5. Also, paper receipts can be issued as needed. In other words, when electronic receipt data is generated, it is possible to avoid issuing a paper receipt.

[0103] Furthermore, in this system, the API 306 that generates electronic receipt data is provided outside the series of processing flows for a transaction, making it possible to maintain the processing for generating electronic receipts and the processing for a transaction separately.

[0104] In the above embodiment, the transaction system server 1 and the electronic receipt server 3 are separate, but in practice, they may be realized as the same server.

[0105] In addition, in practice, the transaction system server 1 may be realized by a plurality of servers. In other words, the various functional units provided in the transaction system server 1 in the embodiment may be provided separately on a plurality of servers.

[0106] Furthermore, DB2 may be included in the transaction system server 1. Alternatively, some or all of the product master 21, store member information 22, electronic receipt member identification information, transaction information 25, HTML data 26, paper receipt printing data 27, and electronic receipt linkage data 28 stored in DB2 in the above embodiment may be stored in the storage unit 19 of the transaction system server 1.

[0107] Moreover, the various functional units provided in the transaction system server 1 in the embodiment may be provided in a POS terminal.

[0108] The electronic receipt issuing system according to the first embodiment described above includes a tablet POS 5 (product registration device) capable of reading information identifying an electronic receipt member from a terminal device, a transaction system server 1 (first information processing device) capable of communicating with the product registration device, and an electronic receipt server 3 (second information processing device) capable of communicating with the transaction system server 1 (first information processing device) and the terminal device, and outputs electronic receipt data in response to an output request from the terminal device.

[0109] The tablet POS5 (product registration device) includes a product registration processing unit 503 (transaction processing side transmitting unit) that receives a product code of a product to be registered for payment processing and transmits a product registration request including the product code to the first information processing device, and a member information processing unit 502 that transmits information identifying the electronic receipt member to the transaction system server 1 if information identifying the electronic receipt member is obtained from the terminal device when registering the product.

[0110] The transaction system server 1 (first information processing device) includes a product registration processing unit 103 which generates transaction information based on a product code when a product registration request is received, a payment processing unit 104 (decision unit) which decides whether to generate electronic receipt data according to information identifying an electronic receipt member, and a receipt output processing unit 106 which generates electronic receipt linkage data based on the transaction information including information identifying the electronic receipt member when it is decided to generate electronic receipt data, and transmits the electronic receipt linkage data to the electronic receipt server 3 (second information processing device).

[0111] The electronic receipt server 3 (second information processing device) includes an API 306 (electronic receipt generation unit) that generates electronic receipt data based on electronic receipt linkage data, an electronic receipt data storage unit 39 that stores the electronic receipt data in association with information identifying an electronic receipt member, and a providing unit that provides the electronic receipt data to the terminal device so that the electronic receipt data can be referenced when a reference request including information identifying an electronic receipt member is received from a terminal device.

[0112] In this way, in the electronic receipt issuing system, by separating the transaction system server and the electronic receipt server, it is possible to separate the processing related to transaction information from the processing related to electronic receipts. This makes it easier to maintain each processing. In particular, the transaction system server 1 is a multi-tenant system in which multiple businesses can share one server, and maintenance of processing related to transaction information can be performed simultaneously for multiple businesses. Furthermore, a user of the transaction system server 1 can easily realize an electronic receipt issuing system by separately installing the electronic receipt server 3.

[0113] The information for identifying the electronic receipt member may include an electronic receipt member code unique to the electronic receipt member and a member flag indicating whether or not the member is an electronic receipt member. In this case, the payment processing unit 104 of the transaction system 1 may determine whether or not to generate electronic receipt data depending on the member flag. With this configuration, it is possible to omit the process of inquiring the electronic receipt server 3 one by one about whether or not the member is an electronic receipt member based on the member code of the electronic receipt member.

[0114] The above-described embodiment can be modified as appropriate by changing a part of the configuration or function of each of the above-described devices. Therefore, the following describes a modified example of the above-described embodiment as another embodiment. The following mainly describes the differences from the above-described embodiment, and the same reference numerals are used for the points that are common to the contents already described, and detailed description is omitted. The modified examples described below may be implemented individually or in appropriate combination.

[0115] Second embodiment In this embodiment, a function of issuing an electronic receipt at a later date after the transaction is completed will be described.

[0116] For example, a customer who comes to the store may request an electronic receipt for a completed transaction by indicating the transaction ID of the transaction. In this case, the store clerk performs an operation on the tablet POS 5 to issue an electronic receipt.

[0117] Note that, here, we will use an example in which a tablet POS 5 in a sales floor or service counter accepts operations from a store clerk, but in practice, other POS terminals may be used, or a store terminal (store server) installed in the back room of the store may also be used.

[0118] 16 is a block diagram showing an example of the functional configuration of the control units 10, 30, 50. The control unit 50 of the tablet POS 5 includes an electronic receipt member identification unit 511, a transaction identification unit 512, and a post-issuance request unit 513. The control unit 10 of the transaction system server 1 includes a transaction information acquisition unit 112 and a post-issuance processing unit 113. The post-issuance processing unit 113, together with the API 306, constitutes an example of an electronic receipt generation unit.

[0119] The transaction information acquisition unit 112 acquires specific transaction information 25 from DB2 (an example of a transaction information storage unit) that stores transaction information 25 related to completed transactions. The post-issuance request unit 513 requests the electronic receipt generation unit (composed of the post-issuance processing unit 113 and the API 306) to generate electronic receipt data corresponding to the transaction information 25 acquired by the transaction information acquisition unit 112.

[0120] The electronic receipt member identification unit 511 is an example of a member information reception unit, and operates when the electronic receipt linking process is selected from the business menu, and receives the input of the membership code of the electronic receipt member. The customer presents the membership code of the electronic receipt member to the store clerk via the display screen of the customer terminal, etc.

[0121] The transaction identification unit 512 accepts input of a transaction ID provided by a customer.

[0122] The post-issuance request unit 513 sends a signal (issuance request) to the transaction system server 1, along with the transaction ID, requesting the issuance of an electronic receipt.

[0123] When the transaction information acquisition unit 112 receives the issuance request, it acquires from DB2 the transaction information 25 that matches the transaction ID.

[0124] The post-issuance processing unit 113 generates electronic receipt linkage data 28 based on the JSON format transaction information 25. Then, the post-issuance processing unit 113 transmits the electronic receipt linkage data 28 to the electronic receipt server 3.

[0125] The processing in the electronic receipt server 3 is the same as that in the first embodiment. When the electronic receipt server 3 receives the electronic receipt linking data 28, the API 306 for generating electronic receipt data operates. The API 306 generates electronic receipt data using the electronic receipt linking data 28. In other words, the API 306 newly generates data for displaying the electronic receipt of the current transaction on the terminal device.

[0126] As a result, for example, if an electronic receipt member is unable to present their membership information during a transaction, electronic receipt data can be generated after the transaction. Also, for example, transaction information 25 conducted before becoming an electronic receipt member can be made into an electronic receipt by presenting a previous paper receipt after becoming a member. Alternatively, if a customer who was a store member further becomes an electronic receipt member, the member code of the store member can be associated with the member code of the electronic receipt member, and the transaction information 25 associated with the member code of the store member can be extracted from DB2, and electronic receipt data can be generated based on this.

[0127] If HTML data 26 matching the transaction ID remains in DB 2, control unit 10 of transaction system server 1 may use it without acquiring transaction information 25.

[0128] Third embodiment 17 is a diagram showing an example of the electronic receipt linkage data 28 stored in the DB2 of this embodiment. The electronic receipt linkage data 28 of this embodiment further includes information 285 in addition to the information shown in FIG. 9. The information 285 is generated by editing the HTML data 26. In other words, the receipt output processing unit 106 of this embodiment generates the electronic receipt linkage data 28 including the information 281-284 based on the transaction information 25 and the information 285 based on the HTML data 26.

[0129] Information 285 includes information specifying a format compatible with paper receipts, such as information 287, 288 that was added to HTML data 26 using attributes 267, 268. Information 287, 288 specify that the font size of the line showing the total should be increased. In this way, information 285 generated based on HTML data 26 includes information specifying a format compatible with paper receipts.

[0130] When the electronic receipt linking data 28 includes the information 285, the API 306 generates electronic receipt data using the information 285 instead of the information 281 to 284. As a result, the electronic receipt displayed on the terminal device used by the customer in this embodiment reflects a format close to that of a paper receipt.

[0131] The control unit 30 of the electronic receipt server 3 stores (accumulates) the information 281-284 in a predetermined storage unit. For example, the information 281-284 includes item names and information. The items are, for example, transaction date (date), product name (itemname), unit price (price), total (total), product code (jancode), company ID (companyid), shop ID (shopid), etc. The information is a value corresponding to the item. The control unit 30 stores the information corresponding to the above items included in the information 281-284 in a predetermined storage unit, for example, in the form of a table including the above items. This makes it possible to accumulate the information included in the electronic receipt linkage data 28 so as to be reusable for purposes such as statistics and various analyses.

[0132] The electronic receipt issuing system according to the third embodiment described above includes a tablet POS 5 (product registration device) capable of reading information identifying an electronic receipt member from a terminal device, a transaction system server 1 (first information processing device) capable of communicating with the tablet POS 5, and an electronic receipt server 3 (second information processing device) capable of communicating with the transaction system server 1 and the terminal device, and provides electronic receipt data in response to a reference request from the terminal device.

[0133] The tablet POS 5 (product registration device) includes a product registration processing unit 503 (transaction processing side transmitting unit) that receives a product code of a product to be registered for payment processing and transmits a product registration request including the product code to the first information processing device, and a member information processing unit 502 that transmits information identifying the electronic receipt member to the transaction system server 1 if information identifying the electronic receipt member is obtained from the terminal device when registering the product.

[0134] The transaction system server 1 (first information processing device) comprises a product registration processing unit 103 which, when receiving a product registration request, generates transaction information based on the product code, a structured data generation unit which generates structured data (HTML data) capable of generating paper receipt printing data for issuing a paper receipt from the transaction information, a payment processing unit 104 (decision unit) which decides whether to generate electronic receipt data according to information which identifies an electronic receipt member, and a receipt output processing unit 106 which, when it is decided to generate electronic receipt data, generates electronic receipt linkage data based on the structured data including information which identifies the electronic receipt member and information which specifies a format corresponding to the paper receipt, and transmits the electronic receipt linkage data to the electronic receipt server 3 (second information processing device).

[0135] The electronic receipt server 3 (second information processing device) includes an API 306 (electronic receipt generation unit) that generates electronic receipt data based on electronic receipt linkage data, an electronic receipt data storage unit 39 that stores the electronic receipt data in association with information identifying an electronic receipt member, and a providing unit that provides the electronic receipt data to the terminal device so that the electronic receipt data can be referenced when a reference request including information identifying an electronic receipt member is received from a terminal device.

[0136] In this way, in the electronic receipt issuing system, by separating the transaction system server and the electronic receipt server, it is possible to separate the processing related to transaction information from the processing related to electronic receipts. This makes it easier to maintain each processing. In particular, the transaction system server 1 is a multi-tenant system in which multiple businesses can share one server, and maintenance of processing related to transaction information can be performed simultaneously for multiple businesses. Furthermore, a user of the transaction system server 1 can easily realize an electronic receipt issuing system by separately installing the electronic receipt server 3. In addition, since the transaction system server stores the transaction information in the form of structured data, it is possible to provide transaction information that is easy to process and highly versatile upon request.

[0137] The electronic receipt linking data may include at least two of the unit price of the product, the purchase date and time of the product, the purchaser attributes, and the purchase area. In this case, the electronic receipt server 3 may further include an analysis unit that analyzes the correlation between at least one of the unit price of the product, the purchase date and time of the product, the purchaser attributes, and the purchase area and any one of the others.

[0138] The information for identifying the electronic receipt member may include an electronic receipt member code unique to the electronic receipt member and a member flag indicating whether or not the member is an electronic receipt member. In this case, the payment processing unit 104 of the transaction system 1 may determine whether or not to generate electronic receipt data depending on the member flag. With this configuration, it is possible to omit the process of inquiring the electronic receipt server 3 one by one about whether or not the member is an electronic receipt member based on the member code of the electronic receipt member.

[0139] (Fourth embodiment) In this embodiment, image data used as a logo on a receipt is stored in the storage unit 39 of the electronic receipt server 3 in association with the business ID. Here, the image data is an example of standard data used to generate electronic receipt data together with the electronic receipt linking data 28. The business ID is an example of identification information included in the electronic receipt linking data 28. The business ID is included in the transaction information 25, and is also included in the HTML data 26 and the electronic receipt linking data 28.

[0140] In this embodiment, if the electronic receipt linking data 28 includes a business ID, the API 306 generates electronic receipt data so that image data matching the business ID stored in the storage unit 39 is displayed in the header of the electronic receipt. In other words, the API 306 includes image data or link information to image data in the header portion of the electronic receipt data, for example.

[0141] The business ID does not necessarily have to be included in the electronic receipt linkage data 28. If the electronic receipt linkage data 28 does not include the business ID, the same function can be achieved by, for example, doing the following: That is, the receipt output processing unit 106 sends the electronic receipt linkage data 28 together with the business ID to the electronic receipt server 3, and the API 306 uses them to generate electronic receipt data.

[0142] According to this embodiment, when a logo image is displayed on an electronic receipt, it is not necessary to send image data from the transaction system server 1. This makes it possible to reduce the amount of communication data.

[0143] The electronic receipt issuing system according to the fourth embodiment described above includes a tablet POS 5 (product registration device) capable of reading information identifying an electronic receipt member from a terminal device, a transaction system server 1 (first information processing device) capable of communicating with the product registration device, and an electronic receipt server 3 (second information processing device) capable of communicating with the transaction system server 1 and the terminal device, and provides electronic receipt data in response to a reference request from the terminal device.

[0144] The tablet POS 5 (product registration device) is equipped with a product registration processing unit 503 (transaction processing side transmitting unit) that receives the product code of the product to be registered for payment processing and transmits a product registration request including the product code and business identification information to the transaction system server 1, and a member information processing unit 502 that transmits information identifying the electronic receipt member to the transaction system server 1 if information identifying the electronic receipt member is obtained from the terminal device when registering the product.

[0145] The transaction system server 1 (first information processing device) includes a product registration processing unit 103 which generates transaction information based on a product code and business identification information when a product registration request is received, a payment processing unit 104 (decision unit) which decides whether to generate electronic receipt data according to information identifying an electronic receipt member, and a receipt output processing unit 106 which generates electronic receipt linked data based on the transaction information including information identifying the electronic receipt member and the business operator when it is decided to generate electronic receipt data, and transmits the electronic receipt linked data to the electronic receipt server 3 (second information processing device).

[0146] The electronic receipt server 3 (second information processing device) includes a standard data storage unit 39 that stores standard data (image data) associated with business identification information, an API 306 (electronic receipt generation unit) that generates electronic receipt data based on the electronic receipt linkage data and the standard data, an electronic receipt data storage unit 39 that stores the electronic receipt data in association with information identifying an electronic receipt member, and a providing unit that provides the electronic receipt data to the terminal device so that the electronic receipt data can be referenced when a reference request including information identifying an electronic receipt member is received from a terminal device.

[0147] In this way, in the electronic receipt issuing system, by separating the transaction system server and the electronic receipt server, it is possible to separate the processing related to transaction information from the processing related to electronic receipts. This makes it easier to maintain each processing. In particular, the transaction system server 1 is a multi-tenant system in which multiple businesses can share one server, and maintenance of processing related to transaction information can be performed simultaneously for multiple businesses. Furthermore, a user of the transaction system server 1 can easily realize an electronic receipt issuing system by separately installing the electronic receipt server 3. In addition, since the transaction system server stores the transaction information in the form of structured data, it is possible to provide transaction information that is easy to process and highly versatile upon request.

[0148] According to the above-mentioned configuration, if the standardized data (image data) has a larger capacity than the electronic receipt linking data, it is not necessary to transmit the standardized data from the transaction system server 1 to the electronic receipt server 3 every time electronic receipt data is generated, so that the amount of communication between the transaction system server 1 and the electronic receipt server 3 can be reduced.

[0149] The information for identifying the electronic receipt member may include an electronic receipt member code unique to the electronic receipt member and a member flag indicating whether or not the member is an electronic receipt member. In this case, the payment processing unit 104 of the transaction system 1 may determine whether or not to generate electronic receipt data depending on the member flag. With this configuration, it is possible to omit the process of inquiring the electronic receipt server 3 one by one about whether or not the member is an electronic receipt member based on the member code of the electronic receipt member.

[0150] Fifth embodiment This embodiment is a modification of the second embodiment. In the second embodiment, the post-issuance processing unit 113 generates electronic receipt linkage data 28 based on the transaction information 25 acquired by the transaction information acquisition unit 112.

[0151] In contrast, in this embodiment, if HTML data 26 matching the transaction ID is stored in DB2, the transaction information acquisition unit 112 further acquires the HTML data 26. When the transaction information acquisition unit 112 acquires the HTML data 26, the post-issuance processing unit 113 uses the HTML data 26 to generate information 285 to be included in the electronic receipt linked data 28.

[0152] Furthermore, in the case where the transaction information acquisition unit 112 does not acquire the HTML data 26, the post-issuance processing unit 113 of this embodiment structures the transaction information 25 that matches the transaction ID to generate the HTML data 26, and generates information 285 to be included in the electronic receipt linked data 28 using the HTML data 26. The post-issuance processing unit 113 may also perform a process of storing the HTML data 26 that it has generated in DB2.

[0153] According to this embodiment, even if an electronic receipt is issued at a later date after the transaction is completed, the information 285 specifying the format can be included in the electronic receipt linking data 28. This allows the format corresponding to the paper receipt to be reflected in the electronic receipt displayed on the terminal device used by the customer.

[0154] The programs executed by each device of the above-described embodiments are provided by being pre-installed in a ROM, etc. The programs executed by each device of the above-described embodiments may be provided by being recorded in an installable or executable format on a computer-readable recording medium such as a CD-ROM, a flexible disk (FD), a CD-R, or a digital versatile disk (DVD).

[0155] Furthermore, the programs executed by each device of the above-described embodiments may be stored on a computer connected to a network such as the Internet and provided by being downloaded via the network. Also, the programs executed by each device of the above-described embodiments may be provided or distributed via a network such as the Internet.

[0156] 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, substitutions, modifications, and combinations can be made without departing from the spirit of the invention. These embodiments and their modifications are included in the scope and spirit of the invention, and are included in the scope of the invention and its equivalents described in the claims.

[0157] (Additional Note) (Additional note 1) An embodiment of the present invention includes the following. An electronic receipt issuing system including a product registration device (tablet POS 5) capable of reading information for identifying an electronic receipt member from a terminal device, a first information processing device capable of communicating with the product registration device (transaction system server 1, and a second information processing device capable of communicating with the first information processing device and the terminal device (electronic receipt server 3), and outputs electronic receipt data in response to an output request from the terminal device, The product registration device includes: a transaction processing side transmitting unit 503 that receives a product code of a product to be registered for payment processing and transmits a product registration request including the product code to the first information processing device; a member information processing unit 502 that, when information identifying an electronic receipt member is acquired from the terminal device during registration of the product, transmits the information identifying the electronic receipt member to the first information processing device; The first information processing device is a product registration processing unit (103) on an information processing side that generates transaction information based on the product code when the product registration request is received; a determination unit that determines whether to generate electronic receipt data according to information identifying the electronic receipt member; a receipt output processing unit 106 that generates electronic receipt linked data based on the transaction information, including information for identifying the electronic receipt member, when it is determined that the electronic receipt data is to be generated, and transmits the electronic receipt linked data to the second information processing device; Equipped with The second information processing device an electronic receipt generating unit 306 that generates electronic receipt data based on the electronic receipt linked data; an electronic receipt data storage unit 39 that stores the electronic receipt data in association with information identifying the electronic receipt member; a providing unit that provides the electronic receipt data to the terminal device so that the electronic receipt data can be referenced when a reference request including information identifying the electronic receipt member is received from the terminal device; An electronic receipt issuing system comprising:

[0158] (Additional note 2) An electronic receipt issuing system comprising: a product registration device (tablet POS 5) capable of reading information for identifying an electronic receipt member from a terminal device; a first information processing device (transaction system server 1) capable of communicating with the product registration device; and a second information processing device (electronic receipt server 3) capable of communicating with the first information processing device and the terminal device, and providing electronic receipt data in response to a reference request from the terminal device, The product registration device includes: a transaction processing side transmitting unit 503 that receives a product code of a product to be registered for payment processing and transmits a product registration request including the product code to the first information processing device; a member information processing unit 502 that, when acquiring information for identifying an electronic receipt member from the terminal device during registration of the product, transmits the information for identifying the electronic receipt member to the first information processing device; Equipped with The first information processing device is a product registration processing unit (103) on an information processing side that generates transaction information based on the product code when the product registration request is received; a structured data generating unit that generates structured data (HTML data) capable of generating paper receipt printing data for issuing a paper receipt from the transaction information; a determination unit that determines whether to generate electronic receipt data according to information identifying the electronic receipt member; a receipt output processing unit 106 that, when it is determined to generate the electronic receipt data, generates electronic receipt linked data based on the structured data, including information for identifying the electronic receipt member and information for specifying a format corresponding to the paper receipt, and transmits the electronic receipt linked data to the second information processing device; Equipped with The second information processing device (electronic receipt server 3) an electronic receipt generating unit 306 that generates electronic receipt data based on the electronic receipt linked data; an electronic receipt data storage unit 39 that stores the electronic receipt data in association with information identifying the electronic receipt member; a providing unit that provides the electronic receipt data to the terminal device so that the electronic receipt data can be referenced when a reference request including information identifying the electronic receipt member is received from the terminal device; An electronic receipt issuing system comprising:

[0159] (Additional note 3) An electronic receipt issuing system including a product registration device (tablet POS 5) capable of reading information for identifying an electronic receipt member from a terminal device, a first information processing device capable of communicating with the product registration device (transaction system server 1, and a second information processing device capable of communicating with the first information processing device and the terminal device (electronic receipt server 3), and providing electronic receipt data in response to a reference request from the terminal device, The product registration device includes: a transaction processing side transmitting unit 503 that receives a product code of a product to be registered for payment processing and transmits a product registration request including the product code and business identification information to the first information processing device; a member information processing unit 502 that, when information identifying an electronic receipt member is acquired from the terminal device during registration of the product, transmits the information identifying the electronic receipt member to the first information processing device; The first information processing device is a product registration processing unit (103) on an information processing side that generates transaction information based on the product code and the business identification information when the product registration request is received; a determination unit that determines whether to generate electronic receipt data according to information identifying the electronic receipt member; a receipt output processing unit 106 that generates electronic receipt linked data based on the transaction information, including information for identifying the electronic receipt member and a business operator, when it is determined to generate the electronic receipt data, and transmits the electronic receipt linked data to the second information processing device; Equipped with The second information processing device is a standard data storage unit that stores standard data associated with the business operator identification information; an electronic receipt generating unit 306 that generates electronic receipt data based on the electronic receipt linked data and the standard data; an electronic receipt data storage unit 39 that stores the electronic receipt data in association with information identifying the electronic receipt member; a providing unit that provides the electronic receipt data to the terminal device so that the electronic receipt data can be referenced when a reference request including information identifying the electronic receipt member is received from the terminal device; An electronic receipt issuing system comprising: [Explanation of symbols]

[0160] 1 ...Transaction system server (an example of a server), 10 ... control unit, 101: transaction start processing unit; 102: member information processing unit; 103: product registration processing unit; 104: payment processing unit, 105: transaction information storage processing unit, 106...Receipt output processing unit (An example of a print data generation unit, and an example of an electronic receipt generation unit) 112: transaction information acquisition unit; 113: post-issuance processing unit; 11...CPU, 12...ROM, 13...RAM, 14 … Communications Department, 19...Storage section, 2 ...DB (an example of a predetermined storage device), 21 ... Product master, 22 ... Store member information, 25 … Transaction information, 26 ...HTML data (an example of structured data), 261...Header information, 262...Product information, 263...Payment information, 264...Footer information, 265~269…Attribute information within the tag 27 ... Data for printing paper receipts, 271...Header information, 272...Product information, 273...Payment information, 274...Footer information, 28 ... Electronic receipt linkage data (an example of linkage data), 281...Header information, 282...Product information, 283...Payment information, 284...Footer information, 285...Information including information specifying the format corresponding to paper receipts 3 ... Electronic receipt server (an example of a server), 30 ... control unit, 306 ... API (constituting an example of an electronic receipt generating unit), 31...CPU, 32...ROM, 33...RAM, 34...Communication section, 39...Storage section, 5 ... Tablet POS (an example of a POS terminal, a sales data processing device), 50 ... control unit, 501...transaction start processing unit, 502...member information processing unit, 503: product registration processing unit; 504: payment processing unit; 511: Electronic receipt member identification unit; 512: Transaction identification unit; 513: Post-issuance request unit; 51...CPU, 52...ROM, 53...RAM, 54 … Communications Department, 55...display section, 551 ... Transaction completion screen, 5511: Message, 5512: Payment details, 5513: Operator, 552 ...Balance screen, 5521...Payment details, 5522...Remaining amount, 5523, 5524...Operator, 56 ... operation unit, 57 ... audio output unit, 58 ... imaging unit, 59...Storage section, 6 ... relay device, 61 ... relay unit, 7 … printer, 70...display content, 701...header information, 702...product information, 703...payment information, 704...footer information. [Prior art documents] [Patent documents]

[0161] [Patent Document 1] Patent Publication No. 2021-043668

Claims

1. a transaction information generating unit that generates transaction information based on products registered for payment processing; A member information acquisition unit that acquires information for identifying an electronic receipt member when registering the product; a print data generating unit that generates print data for causing a printer to produce a paper receipt corresponding to the transaction information; a linkage data generating unit that generates linkage data based on the transaction information, including information specifying a format corresponding to the paper receipt, when it is determined that electronic receipt data is to be generated in accordance with the information identifying the electronic receipt member; an electronic receipt generating unit that generates electronic receipt data by using the link data; An electronic receipt issuing system comprising:

2. A first information processing device capable of communicating with a second information processing device that generates electronic receipt data from linking data generated based on a product code and provides the electronic receipt data in response to a reference request from a terminal device, a product registration processing unit that, when receiving a product registration request including a product code of a product to be registered for payment processing, generates transaction information based on the product code; a structured data generating unit that generates structured data capable of generating printing data for issuing a paper receipt from the transaction information; a decision unit that decides whether to generate electronic receipt data according to the information identifying the electronic receipt member when the information identifying the electronic receipt member is acquired during the registration of the product; a receipt output processing unit that, when it is determined to generate the electronic receipt data, generates linkage data based on the structured data, the linkage data including information for identifying the electronic receipt member and information for specifying a format corresponding to the paper receipt, and transmits the linkage data to the second information processing device; A first information processing device comprising:

3. A terminal device having information for identifying an electronic receipt member; a first information processing device that, when receiving a product registration request including a product code of a product to be registered for payment processing, generates structured data capable of generating print data for issuing a paper receipt based on the product code, and, when acquiring information identifying the electronic receipt member during product registration, generates linking data based on the structured data including information identifying the electronic receipt member and information specifying a format corresponding to the paper receipt; a second information processing device capable of communicating with each of the an electronic receipt generating unit that generates electronic receipt data based on the link data; an electronic receipt data storage unit that stores the electronic receipt data in association with information identifying the electronic receipt member; a providing unit that provides the electronic receipt data to the terminal device so that the electronic receipt data can be referenced when a reference request including information identifying the electronic receipt member is received from the terminal device; A second information processing device comprising:

4. The linking data includes at least two of the following: a unit price of the product, a purchase date and time of the product, purchaser attributes, and a purchase region; An analysis unit that analyzes a correlation between at least one of the unit price of the product, the purchase date and time of the product, the purchaser attribute, and the purchase region and any one of the others from the linking data. The second information processing device according to claim 3 .

5. a transaction information generating unit that generates transaction information based on products registered for payment processing; A member information acquisition unit that acquires information for identifying an electronic receipt member when registering the product; a linking data generating unit that generates linking data based on the transaction information when it is determined that electronic receipt data is to be generated according to the information identifying the electronic receipt member; a storage unit that stores in advance standard data used for generating the electronic receipt data together with the linking data in association with identification information included in the linking data; an electronic receipt generating unit that generates electronic receipt data by using the link data and the standard data; An electronic receipt issuing system comprising:

6. A terminal device having information for identifying an electronic receipt member; a first information processing device that, when receiving a product registration request including a product code and business identification information of a product to be registered for payment processing, generates transaction information based on the product code and business identification information, and, when acquiring information identifying the electronic receipt member during the product registration, generates linking data based on the transaction information including information identifying the electronic receipt member and a business operator; a second information processing device capable of communicating with each of the a standard data storage unit that stores standard data associated with the business operator identification information; an electronic receipt generating unit that generates electronic receipt data based on the link data and the standard data; an electronic receipt data storage unit that stores the electronic receipt data in association with information identifying the electronic receipt member; a providing unit that provides the electronic receipt data to the terminal device so that the electronic receipt data can be referenced when a reference request including information identifying the electronic receipt member is received from the terminal device; A second information processing device comprising:

7. The standard data has a larger capacity than the link data. The second information processing device according to claim 6.

8. A product registration device capable of reading information for identifying an electronic receipt member from a terminal device; a second information processing device that provides electronic receipt data generated from link data generated based on a product code in response to a reference request from the terminal device; A first information processing device capable of communicating with each of the above, a product registration processing unit that, when receiving a product registration request including a product code of a product to be registered for payment processing from the product registration device, generates transaction information based on the product code; a determination unit that, when information for identifying the electronic receipt member is acquired from the product registration device at the time of registering the product, determines whether or not to generate electronic receipt data according to the information for identifying the electronic receipt member; a receipt output processing unit that, when it is determined to generate the electronic receipt data, generates linkage data based on the transaction information, including information for identifying the electronic receipt member, and transmits the linkage data to the second information processing device; A first information processing device comprising:

9. The information for identifying the electronic receipt member includes an electronic receipt member code unique to the electronic receipt member and a member flag indicating whether or not the member is an electronic receipt member, the determination unit determines whether or not to generate electronic receipt data in accordance with the membership flag. The first information processing device according to claim 8.

10. a transaction information storage unit that stores transaction information in association with a transaction ID; A member information receiving unit that receives input of information for identifying an electronic receipt member; a transaction information acquiring unit that acquires the transaction information associated with the transaction ID from the transaction information storage unit when a request for generating electronic receipt data specifying the transaction ID and information identifying the electronic receipt member is received; an electronic receipt generating unit that generates electronic receipt data based on the transaction information acquired by the transaction information acquiring unit; An electronic receipt issuing system comprising:

11. a transaction information generating unit that generates transaction information based on products registered for payment processing; a processing unit that generates structured data including information for specifying a format of a paper receipt and an electronic receipt in the transaction information; a storage unit that stores the transaction information and the structured data in association with a transaction ID; A member information receiving unit that receives input of information for identifying an electronic receipt member; an acquisition unit that acquires the structured data associated with the transaction ID from the storage unit when a request for generating electronic receipt data specifying the transaction ID and information identifying the electronic receipt member is received; an electronic receipt generating unit that generates the electronic receipt data based on the structured data acquired by the acquiring unit; An electronic receipt issuing system comprising:

12. the acquiring unit acquires the transaction information associated with the transaction ID when the structured data associated with the transaction ID is not stored in the storage unit, When the acquisition unit acquires the transaction information, the electronic receipt generation unit generates the structured data by including information designating the format in the transaction information, and generates the electronic receipt data based on the structured data. The electronic receipt issuing system according to claim 11.

13. Generate transaction information based on the products registered for payment processing; When registering the product, information identifying the electronic receipt member is obtained; generating print data for causing a printer to produce a paper receipt corresponding to the transaction information; When it is determined that electronic receipt data is to be generated in accordance with the information identifying the electronic receipt member, generating linking data based on the transaction information, the linking data including information specifying a format corresponding to the paper receipt; generating electronic receipt data using the linking data; How to issue electronic receipts.

14. A product registration device capable of reading information for identifying an electronic receipt member from a terminal device; a second information processing device that provides electronic receipt data generated from link data generated based on a product code in response to a reference request from the terminal device; A method executed by a first information processing device capable of communicating with each of the generating transaction information based on the product code when a product registration request including a product code of a product to be registered for payment processing is received from the product registration device; When information for identifying the electronic receipt member is acquired from the product registration device at the time of registering the product, determining whether or not to generate electronic receipt data according to the information for identifying the electronic receipt member; When it is determined that the electronic receipt data is to be generated, linking data based on the transaction information, the linking data including information for identifying the electronic receipt member, is generated, and the linking data is transmitted to the second information processing device.

Images