Electronic receipt issuance system, electronic receipt issuance method, and program

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] Embodiments of the present invention relate to an electronic receipt issuing system , electric and an electronic receipt issuing method and program . [[BACKGROUND ART]]

[0002] Electronic receipts, which are alternatives to paper-based receipts (paper receipts), have been put into practical use. Electronic receipts are displayed on a terminal device and enable reference to transaction details (see, for example, Patent Document 1).

[0003] In existing technologies, for example, during receipt issuing processing at the end of a series of transaction processing including product information registration processing and settlement processing, if the printing data used for the processing contains specific character information, electronic receipt data is generated instead of a paper receipt. Electronic receipt data is data for displaying the electronic receipt on a terminal device. The specific character information is inserted into the printing data when the customer is an electronic receipt member.

[0004] With the above-described processing, the timing at which electronic receipt data can be generated (the electronic receipt can be issued) is limited. That is, after the receipt issuing processing executed in a series of transaction processing is completed, it is difficult to issue the electronic receipt.

[0005] In order to eliminate the above-mentioned difficulties and make electronic receipts more convenient to use, a highly versatile system that enables improving the flexibility of issuance timing has been required. [[Summary of the Invention]] [[Problem to be Solved by the Invention]]

[0006] The problem to be solved by the present invention is to provide a highly flexible and versatile Electronic receipt issuance system , electric and electronic receipt issuing method and program for issuing electronic receipts. [Means for solving the problem]

[0007] The electronic receipt issuance 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 the electronic receipt member when the products are registered; a print data generation unit that generates print data for issuing a paper receipt corresponding to the transaction information to a printer; a linkage data generation unit that generates linkage data based on the transaction information, including information specifying the format corresponding to the paper receipt, when it is decided to generate electronic receipt data according to the information identifying the electronic receipt member; and an electronic receipt generation unit that generates electronic receipt data using the linkage data. A structured data generation unit generates structured data that includes information specifying the format by structuring the transaction information, Equipped with The print data generation unit generates the print data by editing the structured data, and the linkage data generation unit generates the linkage data including information based on the transaction information and information regarding the format based on the structured data. ru. [Brief explanation of the drawing]

[0008] [Figure 1] Figure 1 shows an example of the system configuration of the first embodiment. [Figure 2] Figure 2 is a block diagram showing an example of a transaction system server configuration. [Figure 3] Figure 3 is a block diagram showing an example of the configuration of an electronic receipt server. [Figure 4] Figure 4 is a block diagram showing an example of a tablet POS configuration. [Figure 5] Figure 5 is a block diagram showing an example of the information stored in the database. [Figure 6] Figure 6 shows an example of HTML data stored in the database. [Figure 7] Figure 7 shows an example of data stored in the database for printing paper receipts. [Figure 8] Figure 8 shows an example of the content displayed on a paper receipt printed and output by a printer. [Figure 9] Figure 9 shows an example of data stored in the database for electronic receipt integration. [Figure 10]Figure 10 is a block diagram showing an example of the functional configuration of the control unit. [Figure 11] Figure 11 shows an example of the processing flow performed by the control unit. [Figure 12] Figure 12 shows an example of the processing flow executed by the control unit of a tablet POS system. [Figure 13] Figure 13 shows an example of the processing flow executed by the control unit of the transaction system server. [Figure 14] Figure 14 shows an example of a transaction completion screen displayed by a tablet POS system. [Figure 15] Figure 15 shows an example of a remaining balance screen displayed by a tablet POS system. [Figure 16] Figure 16 is a block diagram showing an example of the functional configuration of the control unit of the second embodiment. [Figure 17] Figure 17 shows an example of data for electronic receipt integration stored in the DB of the third embodiment. [Modes for carrying out the invention]

[0009] (First Embodiment) The embodiments will be described with reference to the drawings. Figure 1 shows an example of the system configuration of this embodiment. The system of this 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, etc.

[0010] Tablet POS5 is a type of POS terminal installed in stores. A POS terminal is a form of sales data processing device that handles product registration and payment for registered products. "POS" is an abbreviation for "Point of Sale," meaning point-of-sale information management.

[0011] The store is also equipped with other forms of POS terminals other than the tablet POS 5. Examples of other forms of POS terminals include general stationary POS cash registers operated by store clerks, self-checkout devices, and semi-self-checkout devices. A self-checkout device is a device that allows customers to perform operations related to product registration and payment by themselves. A semi-self-checkout device is a device that allows customers to perform payment-related operations by themselves 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 an instruction received from the tablet POS 5 to the printer 7 to cause the printer to issue a receipt.

[0013] It should be noted that 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. For the proper use of the relay device 6 and the relay unit 61, for example, when it is desired to use peripheral devices such as the printer 7 via a wired connection, these peripheral devices are connected to the relay device 6 by wire, and wireless communication is performed between the relay device 6 and the tablet POS 5. Furthermore, if peripheral devices such as the printer 7 are capable of wireless communication, wireless communication is performed between the peripheral devices and the relay unit 61.

[0014] The printer 7 issues printed matter such as receipts. The printer 7 incorporates a printing unit and roll paper. The printing unit is composed of a print head and a platen roller. Roll paper is strip-shaped paper wound into a roll. The platen roller sandwiches the paper pulled out from the roll paper between itself and the print head, and conveys the paper by rotating. The print head prints characters, logos, and the like on the conveyed paper.

[0015] The transaction system server 1 and the DB 2 are interposed between a store POS terminal (e.g., the tablet POS 5) and the electronic receipt server 3, provide cloud computing to both parties, and mediate data linkage between the two parties. The transaction system server 1 can reference information stored in the DB 2 and updates the information stored in the DB 2.

[0016] Transaction system server 1 receives transaction information from the store's POS terminal and stores it in DB2. It also generates HTML data, data for paper receipt printing, and data for electronic receipt integration based on the transaction information, in response to instructions received from the store's POS terminal. Transaction system server 1 sends the generated paper receipt printing data to printer 7 and the electronic receipt integration data to electronic receipt server 3.

[0017] When the electronic receipt server 3 receives electronic receipt linkage data from the transaction system server 1, it generates and stores electronic receipt data. Furthermore, in response to a reference request from a customer's terminal device, the electronic receipt server 3 provides the requested electronic receipt to the customer's terminal device for reference.

[0018] Figure 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, ROM (Read Only Memory) 12, 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 comprehensively controls each part of the transaction system server 1. The ROM 12 stores various programs. The RAM 13 is a workspace for displaying programs and various data. The CPU 11, ROM 12, and RAM 13 are connected via a bus or the like and constitute the control unit 10 of the computer configuration.

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

[0021] The memory unit 19 has a storage medium such as an HDD (Hard Disk Drive) or flash memory, and retains its contents even when the power is cut off. The memory unit 19 stores programs that the CPU 11 can execute, as well as various setting information.

[0022] The control unit 10 performs various processes by operating according to the programs stored in the ROM 12 and memory unit 19 and loaded into the RAM 13, which are then used by the CPU 11. In addition, the control unit 10 provides various functional units. These functional units include, for example, the transaction initiation processing unit 101 (described later, see Figure 10), the member information processing unit 102, the product registration processing unit 103, the settlement processing unit 104, the transaction information storage processing unit 105, and the receipt output processing unit 106.

[0023] Figure 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, ROM 32, RAM 33, communication unit 34, storage unit 39, etc.

[0024] The CPU 31 is an example of a processor and comprehensively controls all parts of the electronic receipt server 3. The ROM 32 stores various programs. The RAM 33 is a workspace for displaying programs and various data. The CPU 31, ROM 32, and RAM 33 are connected via a bus or the like and constitute the control unit 30 of the 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 via a network.

[0026] The memory unit 39 has a storage medium such as an HDD or flash memory and retains its contents even when the power is cut off. The memory unit 39 stores programs that the CPU 31 can execute and various setting information. The memory 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] Electronic receipt member information stores member information (such as name and contact information) of the electronic receipt member, associated with a member code, which is a unique code within that electronic receipt member information. The member code in the electronic receipt member information is an example of identification information that can identify an electronic receipt member.

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

[0029] The control unit 30 performs various processes by having the CPU 31 operate according to the programs stored in the ROM 32 and memory unit 39 and loaded into the RAM 33. In addition, the control unit 30 provides, for example, an API (Application Programming Interface) 306, which will be described later (see Figure 10).

[0030] Figure 4 is a block diagram showing an example of the configuration of the tablet POS 5. Note that other types of POS terminals in stores have a configuration that is generally similar to the tablet POS 5. The tablet POS 5 includes a CPU 51, ROM 52, RAM 53, communication unit 54, display unit 55, operation unit 56, audio output unit 57, imaging unit 58, storage unit 59, etc.

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

[0032] The communication unit 54 is a communication interface that connects the control unit 50 to external devices (such as relay equipment 6 or electronic receipt server 3) so that they can communicate 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 mounted on top of the surface of the display unit 55, and outputs the operation content entered via the input device to the CPU 51. The input device of the operation unit of 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 sound under the control of the CPU 51.

[0036] The imaging unit 58 has an image sensor such as a CCD (Charge Coupled Device) or CMOS (Complementary MOS). The imaging unit 58 is used, for example, to capture code symbols such as barcodes and two-dimensional codes attached to products. In other words, the imaging unit 58 acquires code symbols such as barcodes and two-dimensional codes attached to products. The imaging unit 58 is a type of input device. The code symbols acquired by the imaging unit 58 are decoded to obtain code information.

[0037] The memory unit 59 has a storage medium such as an SSD (Solid State Drive) or flash memory, and retains its contents even when the power is cut off. The memory unit 59 stores programs that the CPU 51 can execute, as well as various setting information.

[0038] The control unit 50 performs various processes by operating the CPU 51 according to programs stored in the ROM 52 and memory unit 59 and loaded into the RAM 53. In addition, the control unit 50 provides various functional units. These various functional units include, for example, the transaction initiation processing unit 501, member information processing unit 502, product registration processing unit 503, and settlement processing unit 504, which will be described later (see Figure 10).

[0039] Figure 5 is a block diagram showing an example of the information stored in DB2. DB2 (a storage unit, an example of a transaction information storage unit) stores various types of information that are referenced or updated by the transaction system server 1. Examples of the information stored in DB2 include product master data 21, store member information 22, transaction information 25, and HTML data 26.

[0040] Product Master 21 contains information about the products handled by the store. Product Master 21 stores information such as product name and unit price, for example, associated with the product code. The product code is an example of identifying information that can identify a product, such as a JAN code.

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

[0042] Store member information 22 stores the member information (such as name and contact information) of the store member, associated with the member code, which is a unique code within the store member information 22. The member code in store member information 22 is an example of identification information that can identify a store member.

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

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

[0045] Figure 6 shows an example of HTML data 26 stored in DB2. The HTML data 26 includes header information 261, product information 262, settlement 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 diagram, there is only one product information 262 because only one product is purchased, but if multiple products are purchased, product information 262 will be repeated. Settlement information 263 consists of various amounts and tax rates calculated based on the product information of transaction information 25, as well as any related notes.

[0047] The HTML data 26 includes information used for paper receipt printing data 27 and information used for electronic receipt integration data 28, using HTML tags.

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

[0049] " The "smartDisabled" attribute 265,266 of the " tag is used to indicate that the information is unnecessary for the electronic receipt integration data 28. The "smartPrefix" attribute 267 of the " tag is used to add the necessary information for the electronic receipt integration data 28 to the beginning of the part enclosed by the tag. Furthermore, The "smartSuffix" attribute 268 of the " tag is used to add information necessary for electronic receipt integration data 28 to the end of the part enclosed by the tag. Note that the information added here by attributes 267 and 268 is used when displaying the electronic receipt. This specifies that the font size of the section enclosed by the tag (the line showing the total) should be increased.

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

[0051] The control unit 10 of the transaction system server 1 edits (converts) the HTML data 26 to generate data 27 for printing paper receipts and temporarily stores it in RAM 13 or the like.

[0052] Figure 7 shows an example of paper receipt printing data 27 generated by the control unit 10. The paper receipt printing data 27 is generated by editing the HTML data 26. The paper receipt printing data 27 is the data that the printer 7 uses to print paper receipts.

[0053] The paper receipt printing data 27 includes header information 271, product information 272, settlement information 273, and footer information 274. The contents of header information 271, product information 272, settlement information 273, and footer information 274 generally correspond to the header information 261, product information 262, settlement information 263, and footer information 264 included in the HTML data 26. In addition, the paper receipt printing data 27 includes information 279 corresponding to attribute 269. The information 279, "2C," indicates that while the font used for printing other lines is the normal "N" font, the font used for printing this line (the total line) is double-width.

[0054] The paper receipt output by the printer 7 based on the paper receipt printing data 27 will be, for example, like the one shown in Figure 8. Figure 8 is a diagram showing an example of the display content 70 of the paper receipt printed and output by the printer 7.

[0055] The contents 70 displayed on the paper receipt include header information 701, product information 702, settlement information 703, and footer information 704. The contents of header information 701, product information 702, settlement information 703, and footer information 704 correspond to header information 271, product information 272, settlement information 273, and footer information 274.

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

[0057] Figure 9 shows an example of electronic receipt linkage data 28 generated by the control unit 10. The electronic receipt linkage data 28 is generated from transaction information 25. The electronic receipt linkage data 28 is data that is sent to the electronic receipt server 3 and is used by the electronic receipt server 3 to generate electronic receipt data.

[0058] The data 28 for electronic receipt integration 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 data 27 for paper receipt printing. The display order of each piece of information 281-284 is adjusted to match the database structure built on the electronic receipt server 3.

[0059] When the electronic receipt server 3 receives the electronic receipt linkage data 28, it generates new electronic receipt data based on the electronic receipt linkage data 28. Generating electronic receipt data means registering the electronic receipt data with the electronic receipt server 3. Electronic receipt data is data that allows customers to access electronic receipts from their terminal devices; in other words, it is data that enables the terminal device used by the customer to display the electronic receipt.

[0060] Figure 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 initiation 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 initiation 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, we further show Figure 11. Figure 11 is a diagram showing an example of the processing flow executed by control units 10, 30, and 50. As shown in Figures 10 and 11, control units 10, 30, and 50 work together to perform processing. Note that the processing with the step numbers shown in Figure 11 corresponds to the processing with the same step numbers shown in Figures 12 and 13 (described later).

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

[0063] In other words, the transaction initiation processing unit 101 and the transaction initiation processing unit 501 work together to perform the transaction initiation process (steps S11, S12, S31, S32). The transaction ID is issued during the transaction initiation process.

[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 electronic receipt members when registering products, and they cooperate in processing member information (steps S13, S14, S33, S34). Member information processing is performed upon acquisition of the member code. In member information processing, the member code is associated with the transaction ID, and member information associated with the member code of store members and member information associated with the member code of electronic receipt members 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 generation unit that generates transaction information based on the products registered for settlement processing, and cooperate in performing product registration processing (steps S15, S16, S35, S36). The product registration processing is the process of compiling the registered product information and editing the transaction information 25. Specifically, the product registration processing unit 503 receives input of a product code via the operation unit 56 and the imaging unit 58, the product registration processing unit 103 obtains product information (such as product name and unit price) associated with the product code, and registers the product code and product information in the transaction information 25.

[0066] Furthermore, the settlement processing unit 104 and the settlement processing unit 504 work together to perform settlement processing (also called accounting processing) according to the transaction information 25 (steps S17, S18, S37, S38). In the settlement processing, payment for the purchased goods is made by cash payment, credit card payment, electronic money payment, etc.

[0067] Furthermore, the settlement processing unit 504 requests the receipt output processing unit 106, which acts as a data generation unit for printing, to generate data 27 for printing paper receipts (step S22).

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

[0069] The receipt output processing unit 106 operates based on the results of the payment processing and functions as an example of a data generation unit for printing, or as part of an electronic receipt generation unit.

[0070] The receipt output processing unit 106, which acts as a data generation unit for printing, generates paper receipt printing data 27 corresponding to the transaction information 25 (steps S41, S42).

[0071] The receipt output processing unit 106, as part of the electronic receipt generation unit, generates electronic receipt linkage data 28 corresponding to the transaction information 25 and sends it to the API 306 (steps S43, S44).

[0072] The API 306 of the electronic receipt server 3, in cooperation with the receipt output processing unit 106, constitutes an electronic receipt generation unit, and generates data (electronic receipt data) for displaying electronic receipts on terminal devices using the electronic receipt linkage data 28.

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

[0074] Figure 12 shows an example of the processing flow executed by the control unit 50 of the tablet POS 5. Note that the processing with the step numbers shown in Figure 12 corresponds to the processing with the same step numbers shown in Figure 11.

[0075] When the control unit 50 (transaction initiation processing unit 501) receives an operation from the operation unit 56 to instruct the initiation of a transaction (step S11; Yes), it sends a signal to the transaction system server 1 indicating a request to initiate a transaction (step S12).

[0076] Next, the control unit 50 (member information processing unit 502) receives a member code via the acquisition of a code symbol by the imaging unit 58 or by the acceptance of an input operation by the operation unit 56 (step S13; Yes), and sends the member code to the transaction system server 1 (step S14). If a member code is not acquired at this point (step S13; No), the control unit 50 skips step S14 and proceeds to step S15.

[0077] For the sake of explanation, the acquisition and transmission of the member code is shown in steps S13-S14, but in reality, it can be done at any time between the start of the transaction and the settlement operation (step S17; Yes). Furthermore, the member information processing handles both the member information of store members and the member information of electronic receipt members.

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

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

[0080] Next, the control unit 50 (settlement processing unit 504) checks the remaining balance (step S19). If the settlement process completes the payment of the full amount for the purchased goods and there is no remaining balance (step S19; Yes), the control unit 50 (settlement processing unit 504) sends a signal to the transaction system server 1 indicating a transaction completion request (step S20).

[0081] If, in step S19, there is a remaining balance (payment is not completed) (step S19; No), the control unit 50 processes the additional payment (step S21) and returns the process to step S19. Additional payments are made, for example, when a payment is made using a rechargeable electronic money, but the charged amount is insufficient, resulting in a remaining balance and requiring an additional payment in cash or other means.

[0082] Next, the control unit 50 (settlement processing unit 504) sends a signal to the transaction system server 1 indicating a request to generate data for printing paper receipts (step S22).

[0083] Furthermore, if the control unit 50 (settlement processing unit 504) has obtained the electronic receipt member code from the customer who is the counterparty to this transaction before the settlement operation, it deems that the customer is an electronic receipt member (step S23; Yes) and sends a signal to the transaction system server 1 indicating an electronic receipt linkage request (step S24). Upon receiving a response to the electronic receipt linkage request, the control unit 50 displays a transaction completion screen (Figure 14, described later) (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] Furthermore, if the customer is not an electronic receipt member (step S23; No), the control unit 50 (payment processing unit 504) processes a request for paper receipt printing to 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] Figure 13 shows an example of the processing flow executed by the control unit 10 of the transaction system server 1. Note that the processing with the step numbers shown in Figure 13 corresponds to the processing with the same step numbers shown in Figure 11.

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

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

[0088] For the sake of explanation, the acquisition of member information is shown in steps S33-S34, but in reality, it can be done at any time between the start of the transaction and the settlement operation (step S37; Yes). Furthermore, the member information processing handles both the member information of store members and the member information of electronic receipt members.

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

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

[0091] Next, the control unit 10 (transaction information storage processing unit 105) waits for a transaction completion request to be received (step S39; No), and when it is received (step S39; Yes), it finishes editing the transaction information 25 and saves it (step S40).

[0092] Next, when the control unit 10 (receipt output processing unit 106) receives a signal indicating a request to generate data for printing paper receipts (step S41; Yes), it generates HTML data 26 that structures the transaction information 25 in JSON format, and then generates paper receipt printing data 27 by editing the HTML data 26. At this time, if the control unit 10 has not received the member code of the electronic receipt member, it sets a print flag in the paper receipt printing 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 data for printing paper receipts is not received (step S41; No), the control unit 10 (receipt output processing unit 106) terminates this process and returns to step S31. For example, if the issuance of electronic receipts is stopped, a request to generate data for printing paper receipts is not sent, and the control unit 10 does not receive a request to generate data for printing paper receipts.

[0094] Furthermore, when the control unit 10 (receipt output processing unit 106) 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 no electronic receipt linkage request is received (step S43; No), the control unit 10 (receipt output processing unit 106) skips step S44, terminates this process, and returns to step S31.

[0096] When the electronic receipt server 3 receives the electronic receipt linkage data 28, API 306 for generating electronic receipt data is activated. API 306 uses the electronic receipt linkage data 28 to generate electronic receipt data. In other words, API 306 generates new data for displaying the electronic receipt for the current transaction on the terminal device.

[0097] Figure 14 shows 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 the transaction completion screen 551. The transaction completion screen 551 includes, for example, a message 5511, payment details 5512, and an operator 5513.

[0098] Message 5511, if the transition occurred from step S24, might be something like, "A paper receipt will not be issued. Please check your electronic receipt in the receipt app." If the transition occurred from step S26, message 5511 might be something like, "A paper receipt will be issued."

[0099] The payment details 5512 reflect the details of the payment. The operator 5513 accepts the operation to close the transaction completion screen 551. When the operator 5513 is operated, the transaction completion screen 551 closes, and the display on the display unit 55 transitions to one that accepts the start of a new transaction.

[0100] Figure 15 shows an example of the 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 the balance screen 552. The balance screen 552 is displayed during the settlement process when accepting an operation to pay the amount due.

[0101] The balance screen 552 includes payment details 5521, remaining balance 5522, and operators 5523 and 5524. Payment details 5521 includes the total price of purchased items, tax amounts by tax rate, and discount amounts. Remaining balance 5522 displays the amount to be paid. 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. Operator 5524 accepts numerical input, and accepts the input of the amount to be paid using the payment method selected by operator 5523. Operator 5524, as illustrated in Figure 15, is in an inoperable state. Operator 5524 becomes operable when one of the operators 5523 is selected.

[0102] With this type of system, electronic receipt data can be generated in response to processing at POS terminals such as the Tablet POS5, allowing for the display of electronic receipts. Paper receipts can also be issued as needed. In other words, if electronic receipt data is generated, paper receipts can be avoided.

[0103] Furthermore, as in this system, having API 306, which generates electronic receipt data, located outside the main transaction processing flow allows for individual maintenance of the electronic receipt generation process and the transaction process.

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

[0105] Furthermore, in implementation, the transaction system server 1 may be implemented using multiple servers. In other words, the various functional units provided by the transaction system server 1 in the embodiment may be provided on multiple servers.

[0106] Furthermore, DB2 may be included in the transaction system server 1. Alternatively, the storage unit 19 of the transaction system server 1 may store 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 that DB2 stores in the above embodiment.

[0107] Furthermore, the various functional units provided by the transaction system server 1 in this embodiment may also be provided in the POS terminal.

[0108] The electronic receipt issuing system according to the first embodiment described above comprises a tablet POS 5 (product registration device) capable of reading information identifying electronic receipt members 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 output requests from the terminal device.

[0109] The tablet POS 5 (product registration device) includes a product registration processing unit 503 (transaction processing side transmission unit) that receives the 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, when information identifying an electronic receipt member is obtained from the terminal device during product registration, transmits the information identifying the electronic receipt member to the transaction system server 1.

[0110] The transaction system server 1 (first information processing device) includes a product registration processing unit 103 that generates transaction information based on the product code when it receives a product registration request, a settlement processing unit 104 (decision unit) that decides whether or not to generate electronic receipt data according to information identifying the electronic receipt member, and a receipt output processing unit 106 that, if it decides to generate electronic receipt data, generates electronic receipt linkage data based on the transaction information, including information identifying the electronic receipt member, 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) comprises 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 the electronic receipt member, and a provision unit that, when it receives a reference request from a terminal device that includes information identifying the electronic receipt member, provides the electronic receipt data to the terminal device in a referable manner.

[0112] In this way, by separating the transaction system server and the electronic receipt server in the electronic receipt issuance system, the processing related to transaction information and the processing related to electronic receipts can be separated. This makes it easier to maintain each process. In particular, the transaction system server 1 is a multi-tenant system in which multiple businesses can share a single server, and maintenance of the transaction information processing can be performed simultaneously for multiple businesses. Furthermore, users of the transaction system server 1 can easily implement an electronic receipt issuance system by separately setting up the electronic receipt server 3.

[0113] The information used to identify an electronic receipt member may include an electronic receipt member code unique to that member and a member flag indicating whether or not the member is an electronic receipt member. In this case, the settlement processing unit 104 of the transaction system 1 may decide whether or not to generate electronic receipt data based on the member flag. With this configuration, the process of querying the electronic receipt server 3 each time to determine whether or not the member is an electronic receipt member based on the member code of the electronic receipt member can be omitted.

[0114] The embodiments described above can also be modified and implemented as appropriate by changing some of the configurations or functions of each of the devices described above. Therefore, the following describes modifications of the embodiments described above as other embodiments. In the following, we will mainly describe the differences from the embodiments described above, and the same reference numerals will be used for parts that are common to the content already described, and detailed explanations will be omitted. Furthermore, the modifications described below may be implemented individually or in combination as appropriate.

[0115] (Second Embodiment) This embodiment describes a function for issuing an electronic receipt at a later date after the transaction has been completed.

[0116] For example, suppose a customer who has come into the store requests the issuance of an electronic receipt for a completed transaction, perhaps by showing the transaction ID of that transaction. In this case, the store clerk performs the operation to issue the electronic receipt on the tablet POS5.

[0117] Here, we will explain using the example of a tablet POS5 in the sales area or service counter that accepts operations from store staff, but in practice, other POS terminals or even a store terminal (store server) located in the back room of the store may be used.

[0118] Figure 16 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 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) which 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 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. It operates when electronic receipt linkage processing is selected from the business menu and accepts the input of the electronic receipt member's member code. The customer presents the electronic receipt member's member code to the store clerk via the display screen of the customer terminal or the like.

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

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

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

[0124] The post-issuance processing unit 113 generates electronic receipt linkage data 28 based on transaction information 25 in JSON format. The post-issuance processing unit 113 then sends 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 in the first embodiment. When the electronic receipt server 3 receives the electronic receipt linkage data 28, the API 306 for generating electronic receipt data is activated. The API 306 uses the electronic receipt linkage data 28 to generate electronic receipt data. In other words, the API 306 generates new data for displaying the electronic receipt for 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 from transactions made before becoming an electronic receipt member can be converted into an electronic receipt by presenting the previous paper receipt after becoming a member. Alternatively, if a customer who was a store member becomes an electronic receipt member, the transaction information 25 associated with the store member's membership code can be extracted from DB2 by linking the store member's membership code with the electronic receipt member's membership code, and electronic receipt data can be generated based on this.

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

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

[0129] Information 285 includes information that specifies the format corresponding to a paper receipt, and for example, it includes information 287 and 288 that were added in HTML data 26 using attributes 267 and 268. Information 287 and 288 specify that the font size of the row showing the total should be increased. Thus, information 285, generated based on HTML data 26, includes information that specifies the format corresponding to a paper receipt.

[0130] If the data 28 for electronic receipt linkage includes information 285, API 306 generates the electronic receipt data using information 285 instead of information 281-284. As a result, in this embodiment, the electronic receipt displayed on the terminal device used by the customer will reflect a format similar to that of a paper receipt.

[0131] The control unit 30 of the electronic receipt server 3 stores (accumulates) information 281 to 284 in a predetermined storage unit. For example, information 281 to 284 includes item names and information. Items include, for example, transaction date (date), item name (itemname), unit price (price), total, product code (jancode), business ID (companyid), store ID (shopid), etc. The information is the value corresponding to the item. The control unit 30 stores the information corresponding to the items contained in information 281 to 284 in a predetermined storage unit, for example, in the form of a table containing the above items. This makes it possible to store the information contained in the electronic receipt linkage data 28 in a way that allows it to be reused for statistical and various analysis purposes.

[0132] The electronic receipt issuing system according to the third embodiment described above comprises a tablet POS 5 (product registration device) capable of reading information identifying electronic receipt members 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 reference requests from the terminal device.

[0133] The tablet POS 5 (product registration device) includes a product registration processing unit 503 (transaction processing side transmission unit) that receives the 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, when information identifying an electronic receipt member is obtained from the terminal device during product registration, transmits information identifying the electronic receipt member to the transaction system server 1.

[0134] The transaction system server 1 (first information processing device) includes a product registration processing unit 103 that generates transaction information based on the product code when it receives a product registration request, a structured data generation unit that generates structured data (HTML data) capable of generating data for printing paper receipts from the transaction information, a settlement processing unit 104 (decision unit) that determines whether or not to generate electronic receipt data according to information identifying the electronic receipt member, and a receipt output processing unit 106 that, if it is decided to generate electronic receipt data, generates electronic receipt linkage data based on the structured data, including information identifying the electronic receipt member and information specifying the 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) comprises 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 the electronic receipt member, and a provision unit that, when it receives a reference request from a terminal device that includes information identifying the electronic receipt member, provides the electronic receipt data to the terminal device in a referable manner.

[0136] In this way, by separating the transaction system server and the electronic receipt server in the electronic receipt issuance system, the processing related to transaction information and the processing related to electronic receipts can be separated. This makes it easier to maintain each process. In particular, transaction system server 1 is a multi-tenant system in which multiple businesses can share a single server, and maintenance of transaction information processing can be performed simultaneously for multiple businesses. Furthermore, users of transaction system server 1 can easily implement an electronic receipt issuance system by separately setting up electronic receipt server 3. In addition, since the transaction system server stores transaction information in the form of structured data, it can provide transaction information that is easy to process as needed and has high versatility.

[0137] Furthermore, the data for electronic receipt integration may include at least two of the following: the unit price of the product, the date and time of purchase, the purchaser's attributes, and the purchase region. 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 date and time of purchase, the purchaser's attributes, and the purchase region, and any one of the others.

[0138] The information used to identify an electronic receipt member may include an electronic receipt member code unique to that member and a member flag indicating whether or not the member is an electronic receipt member. In this case, the settlement processing unit 104 of the transaction system 1 may decide whether or not to generate electronic receipt data based on the member flag. With this configuration, the process of querying the electronic receipt server 3 each time to determine whether or not the member is an electronic receipt member based on the member code of the electronic receipt member can be omitted.

[0139] (Fourth Embodiment) In this embodiment, image data used as a logo on the receipt is stored in the storage unit 39 of the electronic receipt server 3, associated with the business ID. Here, the image data is an example of standardized data used to generate electronic receipt data together with the electronic receipt linkage data 28. The business ID is an example of identification information included in the electronic receipt linkage 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 linkage data 28.

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

[0141] Note that 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 functionality can be achieved, for example, as follows: The receipt output processing unit 106 sends the electronic receipt linkage data 28 along 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 configuring the system to display a logo image on an electronic receipt, it is no longer necessary to send image data from the transaction system server 1. This reduces the amount of communication data.

[0143] The electronic receipt issuing system according to the fourth embodiment described above comprises a tablet POS 5 (product registration device) capable of reading information identifying electronic receipt members 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 reference requests from the terminal device.

[0144] The tablet POS5 (product registration device) includes a product registration processing unit 503 (transaction processing side transmission unit) that receives the product code of a product to be registered for payment processing and sends 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, when information identifying an electronic receipt member is obtained from the terminal device during product registration, sends information identifying the electronic receipt member to the transaction system server 1.

[0145] The transaction system server 1 (first information processing device) includes a product registration processing unit 103 that generates transaction information based on the product code and business identification information when it receives a product registration request, a settlement processing unit 104 (decision unit) that decides whether or not to generate electronic receipt data according to information identifying the electronic receipt member, and a receipt output processing unit 106 that, if it is decided to generate electronic receipt data, generates electronic receipt linkage data based on the transaction information, including information identifying the electronic receipt member and the business operator, and transmits the electronic receipt linkage 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 electronic receipt linkage data and standard data, an electronic receipt data storage unit 39 that stores the electronic receipt data in association with information that identifies the electronic receipt member, and a provision unit that, when it receives a reference request from a terminal device that includes information that identifies the electronic receipt member, provides the electronic receipt data to the terminal device in a referable manner.

[0147] In this way, by separating the transaction system server and the electronic receipt server in the electronic receipt issuance system, the processing related to transaction information and the processing related to electronic receipts can be separated. This makes it easier to maintain each process. In particular, transaction system server 1 is a multi-tenant system in which multiple businesses can share a single server, and maintenance of transaction information processing can be performed simultaneously for multiple businesses. Furthermore, users of transaction system server 1 can easily implement an electronic receipt issuance system by separately setting up electronic receipt server 3. In addition, since the transaction system server stores transaction information in the form of structured data, it can provide transaction information that is easy to process as needed and has high versatility.

[0148] Furthermore, with the above configuration, if the standardized data (image data) is larger in size than the data for electronic receipt linkage, it is not necessary to send the standardized data from the transaction system server 1 to the electronic receipt server 3 each time electronic receipt data is generated, thus reducing the amount of communication between the transaction system server 1 and the electronic receipt server 3.

[0149] The information used to identify an electronic receipt member may include an electronic receipt member code unique to that member and a member flag indicating whether or not the member is an electronic receipt member. In this case, the settlement processing unit 104 of the transaction system 1 may decide whether or not to generate electronic receipt data based on the member flag. With this configuration, the process of querying the electronic receipt server 3 each time to determine whether or not the member is an electronic receipt member based on the member code of the electronic receipt member can be omitted.

[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, the transaction information acquisition unit 112 acquires HTML data 26 that matches the transaction ID if it is stored in DB2. When the transaction information acquisition unit 112 acquires 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 linkage data 28.

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

[0153] According to this embodiment, even when an electronic receipt is issued at a later date after the transaction is completed, the electronic receipt linkage data 28 can include information 285 specifying the format. As a result, the electronic receipt displayed on the customer's terminal device will reflect the format corresponding to the paper receipt.

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

[0155] Furthermore, the programs executed by each 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. Alternatively, the programs executed by each of the above-described embodiments may be provided or distributed via a network such as the Internet.

[0156] While several embodiments of the present invention have been described, these embodiments are presented as examples only and are not intended to limit the scope of the invention. These novel embodiments can be carried out in a variety of other forms, and various omissions, substitutions, modifications, and combinations are possible without departing from the spirit of the invention. These embodiments and their variations are included in the scope and spirit of the invention, as well as in the claims of the invention and its equivalents.

[0157] (Note) (Additional note 1) One embodiment of the present invention includes the following: An electronic receipt issuing system comprising a product registration device (tablet POS 5) capable of reading information 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, wherein the system outputs electronic receipt data in response to an output request from the terminal device, The aforementioned product registration device is A transaction processing side transmission unit 503 receives the 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, The system includes a member information processing unit 502 that, when registering the aforementioned product, obtains information identifying the electronic receipt member from the terminal device, and transmits the information identifying the electronic receipt member to the first information processing device, The first information processing device is When the aforementioned product registration request is received, the information processing side product registration processing unit 103 generates transaction information based on the aforementioned product code, A determination unit that determines whether or not to generate electronic receipt data according to the information identifying the electronic receipt member, When it is decided to generate the aforementioned electronic receipt data, the receipt output processing unit 106 generates electronic receipt linkage data based on the transaction information, which includes information identifying the electronic receipt member, and transmits the electronic receipt linkage data to the second information processing device, Equipped with, The second information processing device is An electronic receipt generation unit 306 generates electronic receipt data based on the aforementioned electronic receipt linkage data, An electronic receipt data storage unit 39 stores the electronic receipt data in association with information that identifies the electronic receipt member, When a reference request including information identifying the electronic receipt member is received from the terminal device, the providing unit provides the electronic receipt data to the terminal device in a referable manner. An electronic receipt issuing system equipped with the following features.

[0158] (Additional note 2) An electronic receipt issuing system comprising a product registration device (tablet POS 5) capable of reading information 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, wherein the system provides electronic receipt data in response to a reference request from the terminal device, The aforementioned product registration device is A transaction processing side transmission unit 503 receives the 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, When registering the aforementioned product, if information identifying the electronic receipt member is obtained from the terminal device, the member information processing unit 502 transmits the information identifying the electronic receipt member to the first information processing device, Equipped with, The first information processing device is When the aforementioned product registration request is received, the information processing side product registration processing unit 103 generates transaction information based on the aforementioned product code, A structured data generation unit generates structured data (HTML data) that can generate data for printing paper receipts to issue paper receipts from the aforementioned transaction information, A determination unit that determines whether or not to generate electronic receipt data according to the information identifying the electronic receipt member, When it is decided to generate the aforementioned electronic receipt data, the receipt output processing unit 106 generates electronic receipt linkage data based on the structured data, which includes information identifying the electronic receipt member and information specifying the format corresponding to the paper receipt, and transmits the electronic receipt linkage data to the second information processing device. Equipped with, The second information processing device (electronic receipt server 3) is: An electronic receipt generation unit 306 generates electronic receipt data based on the aforementioned electronic receipt linkage data, An electronic receipt data storage unit 39 stores the electronic receipt data in association with information that identifies the electronic receipt member, When a reference request including information identifying the electronic receipt member is received from the terminal device, the providing unit provides the electronic receipt data to the terminal device in a referable manner. An electronic receipt issuing system equipped with the following features.

[0159] (Additional note 3) An electronic receipt issuing system comprising a product registration device (tablet POS 5) capable of reading information 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, wherein the system provides electronic receipt data in response to a reference request from the terminal device, The aforementioned product registration device is A transaction processing side transmission unit 503 receives the 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, The system includes a member information processing unit 502 that, when registering the aforementioned product, obtains information identifying the electronic receipt member from the terminal device, and transmits the information identifying the electronic receipt member to the first information processing device, The first information processing device is When the aforementioned product registration request is received, the information processing side product registration processing unit 103 generates transaction information based on the aforementioned product code and business identification information, A determination unit that determines whether or not to generate electronic receipt data according to the information identifying the electronic receipt member, When it is decided to generate the aforementioned electronic receipt data, the receipt output processing unit 106 generates electronic receipt linkage data based on the transaction information, including information identifying the electronic receipt member and the business operator, and transmits the electronic receipt linkage 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 aforementioned business identification information, An electronic receipt generation unit 306 generates electronic receipt data based on the electronic receipt linkage data and the standard data, An electronic receipt data storage unit 39 stores the electronic receipt data in association with information that identifies the electronic receipt member, When a reference request including information identifying the electronic receipt member is received from the terminal device, the providing unit provides the electronic receipt data to the terminal device in a referable manner. An electronic receipt issuing system equipped with the following features. [Explanation of Symbols]

[0160] 1. Transaction system server (an example of a server), 10 ... Control unit, 101...Transaction Initiation Processing Unit, 102...Member Information Processing Unit, 103...Product Registration Processing Unit, 104... Settlement processing unit, 105... Transaction information storage processing unit, 106...Receipt output processing unit (Examples of a data generation unit for printing and an electronic receipt generation unit are shown.) 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 specified 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...Settlement information, 264...Footer information, 265~269... Attribute information within tags 27...Data for printing paper receipts, 271...Header information, 272...Product information, 273...Settlement information, 274...Footer information, 28...Data for electronic receipt integration (example of data for integration), 281...Header information, 282...Product information, 283...Settlement information, 284...Footer information, 285... Information including information that specifies the format corresponding to paper receipts. 3. Electronic receipt server (an example of a server), 30...Control unit, 306...API (Constitutes an example of an electronic receipt generation 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 Initiation Processing Unit, 502...Member Information Processing Unit, 503...Product registration processing unit, 504...Payment processing unit, 511...Electronic Receipt Member Identification Department, 512...Transaction Identification Department, 513...Post-Issuance Request Department 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 balance, 5523, 5524...Operator, 56...Operation unit, 57...Audio output unit, 58...Imaging unit, 59...Storage section, 6... relay equipment, 61... relay unit, 7…Printer, 70...display content, 701...Header information, 702...Product information, 703...Settlement information, 704...Footer information. [Prior art documents] [Patent Documents]

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

Claims

1. A transaction information generation unit generates transaction information based on the products registered for settlement processing, When registering the aforementioned product, a member information acquisition unit acquires information to identify the electronic receipt member, A print data generation unit generates print data for a printer to issue a paper receipt corresponding to the transaction information, When it is decided to generate electronic receipt data according to the information identifying the electronic receipt member, the linked data generation unit generates linked data based on the transaction information, which includes information specifying the format corresponding to the paper receipt. An electronic receipt generation unit that generates electronic receipt data using the aforementioned data for linkage, A structured data generation unit generates structured data that includes information specifying the format by structuring the transaction information, Equipped with, The print data generation unit edits the structured data to generate the print data, The aforementioned data generation unit generates the data for linkage, including information based on the transaction information and information regarding the format based on the structured data. Electronic receipt issuance system.

2. Transaction information is generated based on the products registered for payment processing. When registering the aforementioned product, information identifying the electronic receipt member is obtained, The aforementioned transaction information is structured to generate structured data that includes information specifying the format corresponding to a paper receipt. Edit the aforementioned structured data to generate print data for issuing the aforementioned paper receipt to the printer, If it is decided to generate electronic receipt data according to the information identifying the electronic receipt member, the following linkage data is generated based on the transaction information, including information specifying the format, and information regarding the format based on the structured data. Electronic receipt data is generated using the aforementioned data for linkage. How to issue an electronic receipt.

3. A transaction information generation function that generates transaction information based on goods registered for settlement processing, When registering the aforementioned product, a member information acquisition function is used to acquire information that identifies the electronic receipt member, A structured data generation function generates structured data that structures the aforementioned transaction information and includes information specifying the format corresponding to a paper receipt, A print data generation function that edits the aforementioned structured data to generate print data for issuing the aforementioned paper receipt to a printer, When it is decided to generate electronic receipt data according to the information identifying the electronic receipt member, the linked data generation function generates linked data based on the transaction information, including information based on the transaction information and information about the format based on the structured data, including information specifying the format. An electronic receipt generation function that generates electronic receipt data using the aforementioned data for linkage, A program to implement this on the computer in the electronic receipt issuance system.

Images