RECEIPT SERVER, INFORMATION PROCESSING METHOD, PROGRAM RECORDING MEDIUM, AND SERVER SYSTEM

In one embodiment, a receipt server includes an acquisition unit and an output unit. The acquisition unit acquires receipt data on a commercial transaction, identified by transaction identification information included in settlement sales data reported from a settlement terminal to a settling agent that assists settlement of the commercial transaction, from a receipt storage unit that stores receipt data generated by the settlement terminal at a time of settlement of the commercial transaction. The output unit outputs information, relating to a purchased commercial product included in the receipt data acquired by the acquisition unit to a settlement server of the settling agent.

FIELD

Embodiments of the present invention relate generally to a receipt server, an information processing method, a program recording medium, and a server system including a receipt server.

BACKGROUND

In recent years, electronic settlement in which settlement of transactions is electronically processed has attracted attention. Electronic settlement includes, for example, credit card settlement, electronic money settlement, and code settlement using a bar code, a two-dimensional code, or the like. When electronic settlement is executed in a brick-and-mortar shop, settlement sales data is output from a settlement terminal to a server of a settling agent. The settlement sales data includes information on a person making the settlement, information on a transaction date and time, information on a transaction shop, a settlement amount, etc. However, the settlement sales data does not include information of a commercial product purchased by the person making the settlement. Therefore, the settling agent can grasp information on who utilized the electronic settlement where, when, and for how much money, but cannot grasp information on what was purchased. There is a demand for a service for providing a settling agent with information on a commercial product purchased by a person making the settlement using electronic settlement.

DETAILED DESCRIPTION

In one embodiment, a receipt server includes an acquisition unit and an output unit. The acquisition unit acquires receipt data on a commercial transaction, identified by transaction identification information included in settlement sales data reported from a settlement terminal to a settling agent that assists settlement of the commercial transaction, from a receipt storage unit that stores receipt data generated by the settlement terminal at a time of settlement of the commercial transaction. The output unit outputs information, relating to a purchased commercial product included in the receipt data acquired by the acquisition unit, to a settlement server of the settling agent.

Hereinafter, an embodiment of a receipt server and a server system will be described with reference to the accompanying drawings.

First Embodiment

FIG.1is a system diagram showing an outline of the embodiment. A system of this embodiment includes a plurality of point-of-sales (POS) terminals10, a receipt server20, a plurality of settlement servers30, and a communication network40. The communication network40comprises one or more networks, such as the Internet, a telephone network, a local area network (LAN), and the like.

Each of the POS terminals10is a computer terminal disposed in a shop and utilized for registration and settlement of a commercial product purchased by a customer. The shop may be of any business category. The shop may be a retail shop, such as a mass merchandiser, a specialized shop, or the like, or may be an eating and drinking establishment. Each POS terminal10is connected to the communication network40. Each POS terminal10may be directly connected to the communication network40or one or more POS terminals10may be connected to the communication network40via a relay server.

The receipt server20is a server computer managed by a corporate entity that manages an electronic receipt service. The electronic receipt service is a service to digitize print data of a receipt issued from the POS terminal10at the time of checkout in the shop, and to allow the making the settlement to view the receipt as an image through a communication terminal owned by the customer. The communication terminal is typically a smartphone. The communication terminal may be a tablet terminal, a personal computer, or the like. The receipt server20is connected to the communication network40. The receipt server20provides the customer with the electronic receipt service in cooperation with each POS terminal10connected to the communication network40.

A user who utilizes the electronic receipt service installs a dedicated application program, a so-called electronic receipt application, on a portable communication terminal, for example, a smartphone. By installing the electronic receipt application on the communication terminal, a receipt ID that functions as an identifier of the user is issued. The receipt ID is displayed on a display of the communication terminal in the form of, for example, a bar code. When the receipt ID is read by a scanner of the POS terminal10at a time of settlement of the commercial transaction in which the user is the customer, receipt data indicating details of the commercial transaction is digitized and transmitted from the POS terminal10to the receipt server20. The receipt data includes the receipt ID. The user accesses the receipt server20using the electronic receipt application of the communication terminal. As a result, a receipt image based on the receipt data including the set receipt ID is downloaded from the receipt server20on the communication terminal. The user can view the downloaded receipt image through the communication terminal.

Each of the settlement servers30is a server computer managed by a settling agent that assists settlement of commercial transactions by electronic settlement.

Electronic settlement includes, for example, credit card settlement, electronic money settlement, and code settlement using a bar code, a two-dimensional code, or the like. Each settlement server30is connected to the communication network40. Each settlement server30assists electronic settlement executed by each POS terminal10through the communication network40.

The settlement server30issues a settlement number each time an electronic settlement assisted by the settlement server30is executed by the POS terminal10. The settlement number is, typically, a serial number. The settlement number is called an approval number, a transaction serial number, a slip number, or the like, depending on the settling agent. The settlement number is included in the receipt data of the commercial transaction electronically settled, together with the settlement title, the settlement amount, and the like.

The settlement title is a title representing a type of the settlement amount. If the settlement amount is a payment amount of a cash settlement, the settlement title is, for example, “cash”. If the settlement amount is a payment amount of a credit card settlement, the settlement title is, for example, “trust” or “credit”. If the settlement amount is a payment amount of an electronic money settlement, the settlement title is a proper noun indicating, for example, the kind of electronic money. If the settlement amount is a payment amount of a code settlement, the settlement title is a proper noun indicating, for example, the kind of code settlement.

Herein, the receipt server20and the settlement servers30constitute a server system100. Specifically, the server system100is a computer network system in which the receipt server20and the settlement servers30are connected through the communication network40. The server system100may include a server other than the receipt server20and the settlement servers30.

Next, the POS terminal10, the receipt server20, and the settlement servers30will be explained in detail.

The POS terminal10has a function as a commercial product registration unit11, a function as a settlement processing unit12, and a function as a receipt processing unit13. The commercial product registration unit11functions to register sales data of the commercial product purchased by the customer in a memory. In this function, a total amount of commercial transactions with the customer is calculated. The function as the commercial product registration unit11is well known; therefore, detailed explanations thereof are omitted.

The settlement processing unit12functions to settle the commercial transactions based on payment data relative to the total amount of commercial transactions. In the case of cash payment, the settlement processing unit12executes a cash settlement process. In the case of credit card payment, the settlement processing unit12executes a credit card settlement process. In the case of electronic money payment, the settlement processing unit12executes an electronic money settlement process. In the case of code settlement payment, the settlement processing unit12executes a code settlement process. The cash settlement process, the credit card settlement process, the electronic money settlement process, and the code settlement process are all well-known processes; therefore, detailed explanations thereof are omitted. When the commercial transaction is settled by electronic settlement assisted by the settlement server30, the settlement sales data is output from the POS terminal10to the settlement server30, in the same manner as in the conventional art. The settlement sales data includes information on the customer making the settlement, information on a transaction date and time, information on a transaction shop, information on a settlement number and a settlement amount, etc.

The receipt processing unit13functions to process receipt data generated each time a commercial transaction is settled. The receipt processing unit13processes the receipt data using a POS side setting table131shown inFIG.2. The POS side setting table131is downloaded from, for example, the receipt server20, on each POS terminal10.

The POS side setting table131is a data table in which a settlement title is set to each agent code. An agent code is a unique code set for each of the settling agents in order to individually identify each settling agent. The settlement title is a title representing a settlement amount in an electronic settlement that is being supported by the settlement server30of the settling agent specified by the corresponding agent code.

FIG.3is a flowchart showing a main procedure in the receipt processing unit13. This process is started each time a commercial transaction is settled by the settlement processing unit12. When a commercial transaction is settled, the receipt processing unit13acquires receipt data indicating details of the commercial transaction as ACT1. The receipt data is generated by the settlement processing unit12. The receipt data includes a transaction date and time, a transaction number, registered commercial product data, a total amount, a settlement title, a settlement amount, etc. In the case in which the receipt ID has already been read with the scanner of the POS terminal10at the time of settlement of a commercial transaction, the receipt ID is included in the receipt data. In the case in which the commercial transaction is settled by electronic settlement, the settlement number is included in the receipt data.

The receipt processing unit13confirms whether the receipt ID is included in the receipt data as ACT2. If the receipt ID is included in the receipt data, the receipt processing unit13determines YES in ACT2, and proceeds to ACT6. The process in ACT6and the subsequent acts will be described later.

If the receipt ID is not included in the receipt data, the receipt processing unit13determines NO in ACT2, and proceeds to ACT3. The receipt processing unit13acquires the settlement title included in the receipt data as ACT3. The receipt processing unit13confirms, as ACT4, whether the settlement title is set in the POS side setting table131, namely, whether the title represents the settlement amount of the electronic settlement. If the settlement title is not set in the POS side setting table131, namely, if the settlement is not an electronic settlement, the receipt processing unit13determines NO in ACT4, and proceeds to ACT5. The receipt processing unit13controls a printer of the POS terminal10and outputs the receipt data to a receipt paper sheet as ACT5.

On the other hand, if the settlement title is set in the POS side setting table131, the receipt processing unit13determines YES in ACT4, and proceeds to ACT6.

Thus, if the receipt processing unit13acquires the receipt data including the receipt ID or acquires the receipt data not including the receipt ID but including the settlement title of electronic settlement, the receipt processing unit13proceeds to ACT6. The receipt processing unit13digitizes the receipt data as ACT6. Specifically, the receipt processing unit13converts the receipt data of an unstructured format to receipt data of a structured format, namely, so-called electronic receipt data, in accordance with predetermined conversion rules.

Upon completion of the digitization of the receipt data, the receipt processing unit13transmits the digitized receipt data to the receipt server20as ACT7. The receipt data is transmitted to the receipt server20through the communication network40.

Thus, when the receipt data is printed out to a receipt paper sheet, or digitized and transmitted to the receipt server20, the receipt processing unit13ends the process of the procedure shown in the flowchart ofFIG.3.

FIG.4is a block diagram showing a main circuit configuration of the receipt server20. The receipt server20includes a processor21, a main memory22, an auxiliary storage device23, a clock24, and a communication interface25. In the receipt server20, the processor21, the main memory22, the auxiliary storage device23, the clock24, and the communication interface25are connected through a system bus26. The system bus26includes an address bus, a data bus, and the like. The receipt server20constitutes a computer by connecting the processor21with the main memory22, the auxiliary storage device23, the clock24, and the communication interface25through the system bus26.

The processor21corresponds to a central portion of the computer. The processor21controls the respective components to implement various functions as the receipt server20in accordance with an operating system or an application program. The processor21may be processing circuitry, for example, a central processing unit (CPU), a graphics processing unit (GPU), an application specific integrated circuit (ASIC), or a programmable logic device (e.g., a simple programmable logic device (SPLD), a complex programmable logic device (CPLD), a field programmable gate array (FPGA), or the like). The processor21is not necessarily limited to a single processing circuit, but may be configured by a combination of a plurality of processing circuits.

The main memory22corresponds to a main storage portion of the computer mentioned above. The main memory22includes a non-volatile memory region and a volatile memory region. The main memory22stores an operating system or an application program in the non-volatile memory region. The main memory22stores data necessary for the processor21to execute processes of the respective components in the volatile memory region. The main memory22also uses the volatile memory region as a work area in which data is rewritten by the processor21as appropriate. The non-volatile memory region is, for example, a read only memory (ROM). The volatile memory region is, for example, a random access memory (RAM).

The auxiliary storage device23corresponds to an auxiliary storage portion of the computer. The auxiliary storage device23may be one known storage device or a combination of two or more known storage devices, such as an electrically erasable programmable read-only memory (EEPROM), a hard disc drive (HDD), a solid state drive (SSD), and the like. The auxiliary storage device23stores data to be used by the processor21when performing various processes, data generated by the processes performed by the processor21, and the like. In some cases, the auxiliary storage device23may store application programs.

The application programs stored in the main memory22or the auxiliary storage device23include a control program described later. A method of installing the control program on the main memory22or the auxiliary storage device23is not particularly limited. The control program may be recorded in a removable recording medium or distributed through communications via the network, so that the control program can be installed on the main memory22or the auxiliary storage device23. The recording medium may be of any type, such as a CD-ROM or a memory card, as long as it can store programs and can be read by a device.

The clock24functions as a time information source of the receipt server20. The processor21acquires a current date and time based on the time information counted by the clock24.

The communication interface25is connected to the communication network40. The receipt server20performs data communications with the POS terminals10and the settlement servers30connected to the communication network40through the communication interface25. The receipt server20also performs data communications with communication terminals that have had the electronic receipt application installed, through the communication interface25.

The receipt server20having the configuration described above uses parts of the storage area of the auxiliary storage device23as a region for a server side setting table231, a region for a first file232, and a region for a second file233.

FIG.5is a schematic diagram showing a data structure of the server side setting table231. As illustrated, the server side setting table231is a data table in which the settlement title and an output flag are set to each agent code. The output flag is one-bit data to identify whether the settling agent specified by the corresponding agent code is a settling agent of a target of provision of purchase information. The purchase information is a commercial product code, a trade name, a price, and the like, of a commercial product purchased by the customer, namely, a so-called purchased commercial product. In this embodiment, an output flag indicating the settling agent of the target of provision of purchase information is “1”, and an output flag indicating a settling agent other than the target of provision of purchase information is “0”.

The first file232and the second file233function as receipt storage units to store receipt data received from the POS terminals10. The processor21sorts the receipt data received from the POS terminals10into the first file232or the second file233, or both the first file232and the second file233, with reference to the server side setting table231.

FIG.6is a flowchart showing a procedure of a receipt data sorting process executed by the processor21of the receipt server20. The processor21stands by for receiving receipt data as ACT11. Upon receipt of the receipt data, the processor21determines YES in ACT11, and proceeds to ACT12. The processor21confirms whether the receipt ID is included in the receipt data as ACT12. If the receipt ID is included in the receipt data, the processor21determines YES in ACT12, and proceeds to ACT13. The processor21stores the receipt data in the first file232as ACT13. The processor21then proceeds to ACT14.

If the receipt ID is not included in the receipt data, the processor21determines NO in ACT12. The processor21skips the process of ACT13, and proceeds to ACT14. The processor21acquires the settlement title included in the receipt data as ACT14. Then, the processor21confirms, as ACT231, whether the settlement title is set in the server side setting table231, namely, whether the title represents the settlement amount of the electronic settlement. If the settlement title is not set in the server side setting table231, namely, if the settlement is not an electronic settlement, the processor21determines NO in ACT15, and ends the sorting process.

If the settlement title is set in the server side setting table231, namely, if the settlement is an electronic settlement, the processor21checks an output flag corresponding to the settlement title set in the server side setting table231as ACT16. If the output flag is “0”, namely, in the case of electronic settlement relating to a settling agent other than the target of provision of purchase information, the processor21determines NO in ACT16, and ends the sorting process.

If the output flag is “1”, namely, if it is a case of electronic settlement relating to a settling agent of the target of provision of purchase information, the processor21determines YES in ACT16, and proceeds to ACT17. The processor21stores the receipt data in the second file233as ACT17. Thus, the processor21ends the sorting process.

Through the sorting process, the receipt data including the receipt ID, namely, the receipt data relating to commercial transactions of customers who receives the electronic receipt service, is stored in the first file232. The receipt data on commercial transactions settled by electronic settlement relating to the settling agent of the target of provision of purchase information is stored in the second file233. Even when the receipt data relates to a commercial transaction of a customer who receives the electronic receipt service, the receipt data on commercial transaction settled by electronic settlement relating to the settling agent of the target of provision of purchase information is stored in both the first file232and the second file233. In the following, the receipt data stored in the first file232is referred to as first receipt data Ra (seeFIG.7). The receipt data stored in the second file233is referred to as second receipt data Rb (seeFIG.8).

The first file232and the second file233constitute receipt storage units. The first file232constitutes a first receipt storage unit and the second file233constitutes a second receipt storage unit.

The processor21that executes the sorting process constitutes a processing unit. Specifically, the processor21causes the first receipt storage unit (the first file232) to store receipt data with second identification information (a receipt ID) that identifies the user of the electronic receipt, and causes the second receipt storage unit (the second file233) to store receipt data with information indicating that the commercial transaction was settled with the assistance of the settling agent (the settlement title).

FIG.7is a schematic diagram showing a structure of the first receipt data Ra stored in the first file232. As illustrated, the first receipt data Ra includes at least a receipt ID, a shop code, a transaction date and time, a register number, a transaction number, registered commercial product data, a total amount, a settlement title, a settlement amount, etc. The shop code is an identifier of the shop where the POS terminal10that transmits the first receipt data Ra is located. The transaction date and time is a date and time when the commercial transaction was settled by the POS terminal10. The register number is an identifier of the POS terminal10. The transaction number is a serial number issued for a commercial transaction settled by the POS terminal10. The registered commercial product data is information on a commercial product registered as a purchased commercial product, and includes a commercial product code, a price, the number of sold products, a sales amount, etc. The registered commercial product data may include a trade name instead of the commercial product code. Alternatively, the registered commercial product data may include both a commercial product code and a trade name. The total amount is a sum of the sales amounts included in the registered commercial product data. The settlement title and the settlement amount are the settlement title and the settlement amount of payment data for the total amount. The first receipt data Ra relating to the electronically settled commercial transaction further includes a settlement number.

FIG.8is a schematic diagram showing a structure of the second receipt data Rb stored in the second file233. As illustrated, the second receipt data Rb includes at least a shop code, a transaction date and time, a register number, a transaction number, registered commercial product data, a total amount, a settlement title, a settlement amount, a settlement number, etc. The second receipt data Rb relating to a commercial transaction of a customer who receives the electronic receipt service includes a receipt ID.

Another set of second receipt data Rbb shown inFIG.8represents second receipt data after a purchase information delivery process (described later) is executed. The second receipt data Rbb is data including a user ID and a terminal ID in addition to the second receipt data Rb. The user ID and the terminal ID are described later.

FIG.9is a block diagram showing a main circuit configuration of the settlement server30. The settlement server30includes a processor31, a main memory32, an auxiliary storage device33, a clock34, and a communication interface35. In the settlement server30, the processor31, the main memory32, the auxiliary storage device33, the clock34, and the communication interface35are connected through a system bus36. The system bus36includes an address bus, a data bus, and the like. The settlement server30constitutes a computer by connecting the processor31with the main memory32, the auxiliary storage device33, the clock34, and the communication interface35through the system bus36.

The processor31corresponds to a central portion of the computer. The processor31controls the respective components to implement various functions as the settlement server30in accordance with an operating system or an application program. The processor31is, for example, a CPU.

The main memory32corresponds to a main storage portion of the computer mentioned above. The main memory32includes a non-volatile memory region and a volatile memory region. The main memory32stores an operating system or an application program in the non-volatile memory region. The main memory32stores data necessary for the processor31to execute processes of the respective components in the volatile memory region. The main memory32also uses the volatile memory region as a work area in which data is rewritten by the processor31as appropriate. The non-volatile memory region is, for example a ROM. The volatile memory region is, for example a RAM.

The auxiliary storage device33corresponds to an auxiliary storage portion of the computer. The auxiliary storage device33may be one known storage device or a combination of two or more known storage devices, such as an EEPROM, an HDD, an SSD, and the like. The auxiliary storage device33stores data to be used by the processor31when performing various processes, data generated by the processes performed by the processor31, and the like. In some cases, the auxiliary storage device33may store application programs.

The application programs stored in the main memory32or the auxiliary storage device33include a control. program described later. A method of installing the control program on the main memory32or the auxiliary storage device33is not particularly limited. The control program may be recorded in a removable recording medium or distributed through communications via the network, so that the control program can be installed on the main memory32or the auxiliary storage device33. The recording medium may be of any type, such as a CD-ROM or a memory card, as long as it can store programs and can be read by a device.

The clock34functions as a time information source of the settlement server30. The processor31acquires a current date and time based on the time information counted by the clock34.

The communication interface35is connected to the communication network40. The settlement server30performs data communications with the POS terminals10and the receipt server20connected to the communication network40through the communication interface35.

The settlement server30having the configuration described above uses a part of the storage area of the auxiliary storage device33as a region for a settlement information file331. The settlement information file331is a data file to store settlement sales data transmitted from the POS terminals10to the settlement server30.

FIG.10is a schematic diagram showing a structure of settlement sales data Rc stored in the settlement information file331. The settlement sales data Rc includes a shop code, a transaction date and time, a settlement number, a settlement amount, a user ID, and a terminal ID. The user ID is an identifier of a customer who utilizes the electronic settlement. The terminal ID is an identifier of a communication terminal, such as a smartphone.

The customer who utilizes the electronic settlement carries out user registration in advance for a settling agent. Through the user registration, a unique user ID is issued from the settling agent. The user ID is stored in a medium for electronic settlement, such as a credit card, an electronic money card, a smartphone, or the like. When executing electronic settlement, the POS terminal10fetches the user ID from the medium. The POS terminal10transmits the settlement sales data Rc including the user ID to the settlement server30of the corresponding settling agent. If the medium is a communication terminal, the POS terminal10also fetches a terminal ID from the communication terminal. The POS terminal10transmits the settlement sales data Rc further including the terminal ID to the settlement server30. If the medium is not a communication terminal, the terminal ID of the settlement sales data Rc relating to the electronic settlement is NULL data.

The other settlement sales data Rcc shown inFIG.10is settlement sales data after the purchase information delivery process described later is executed. The settlement sales data Rcc is data including one or more pieces of registered commercial product data in addition to the settlement sales data Rc.

Thus, the settlement sales data RC before the purchase information delivery process is executed does not include registered commercial product data. Therefore, the settling agent can grasp information on who utilized the electronic settlement where, when, and for how much money, from the settlement sales data Rc of the settlement information file331, but cannot grasp information on the commercial product purchased by the person making the settlement, namely, purchase information. The purchase information is stored in the receipt server20. Therefore, in the present embodiment, a control program to realize a process of acquiring purchase information from the receipt server20, namely, a so-called purchase information acquisition application, is implemented in the settlement server30. Furthermore, in cooperation with the purchase information acquisition application, a control program to realize a process of supplying necessary purchase information in reply to the settlement server30, namely, a so-called purchase information reply application, is implemented in the receipt server20.

FIG.11is a flowchart showing a procedure of a main information process executed by the processor31of the settlement server30in accordance with the purchase information acquisition application.FIG.12is a flowchart showing a procedure of a main information process executed by the processor21of the receipt server20in accordance with the purchase information reply application. Hereinafter, main operations of the server system100of the first embodiment will be explained with reference to the drawings. The operations explained below are mere examples. The procedure of the operations is not particularly limited, as long as similar effects and advantages can be obtained.

The system is activated each time settlement sales data Rc is stored in the settlement information file331. The purchase information acquisition application may be activated at a preset time, for example, at 0 minutes of every hour.

When the purchase information acquisition application is activated, the processor31of the settlement server30starts the process of the procedure shown in the flowchart ofFIG.11. First, as ACT21, the processor31confirms whether the settlement sales data which is a target of the process is stored in the settlement information file331. The settlement sales data that is a target of the process is the settlement sales data Rc to which registered commercial product data is not added. The settlement sales data Rcc to which registered commercial product data was added is not a target of the process.

If the settlement sales data Rc that is a target of the process is stored in the settlement information file331, the processor31determines YES in Act21, and proceeds to ACT22. The processor31acquires the settlement sales data Rc from the settlement information file331as ACT22. Then, the processor31acquires a settlement number from the settlement sales data Rc as ACT23. Furthermore, the processor31acquires a user ID and a terminal ID from the settlement sales data Rc as ACT24.

The processor31transmits a purchase information request command to the receipt server20as ACT25. The purchase information request command includes the settlement number, the user ID, and the terminal ID acquired from the settlement sales data Rc. The purchase information request command is transmitted to the receipt server20through the communication network40.

The purchase information reply application resides in the receipt server20. The processor21of the receipt server20stands by for a purchase information request command as ACT31shown inFIG.12. Upon receipt of the purchase information request command through the communication network40, the processor21determines YES in ACT31, and proceeds to ACT32. The processor21acquires the settlement number from the purchase information request command as ACT32. Then, as ACT33, the processor21searches the second file233using the settlement number as a search key.

The processor21determines, as ACT34, whether the second receipt data Rb including the settlement number as the search key is present or not. If the corresponding second receipt data Rb is not stored in the second file233, the processor21determines NO in ACT34, and proceeds to ACT35. As ACT35, the processor21transmits an error reply command to the settlement server30, which is the source of the purchase information request command.

For example, if a failure occurs in a communication between the POS terminal10and the receipt server20, the settlement sales data of the electronically settled commercial transaction is transmitted to the settlement server30, while the receipt data of the commercial transaction is not stored in the second file233. Such a case is determined to be an error.

If the second receipt data Rb including the settlement number as the search key is stored in the second file233, the processor21determines YES in ACT34, and proceeds to ACT36. The processor21acquires registered commercial product data from the second receipt data Rb as ACT36. Then, as ACT37, the processor21transmits a normal reply command to the settlement server30, which is the source of the purchase information request command. The normal reply command includes the registered commercial product data acquired in the process of ACT36.

The processor21detects the user ID and the terminal ID from the purchase information request command as ACT38. Then, the processor21adds, as ACT39, the user ID and the terminal ID to the second receipt data Rb including the settlement number as the search key.

In this way, the processor21ends the reply process with respect to the purchase information request command. Then, upon receipt of a next purchase information request command, the processor21executes the process of ACT32to ACT38in the same manner as described above.

Explanations will return toFIG.11.

The normal reply command or the error reply command is received by the settlement server30, which is the source of the purchase information request command, through the communication network40. The processor31of the settlement server30that receives the purchase information request command stands by for a reply command as ACT26. In this standby state, if the processor31receives an error reply command, it determines NO in ACT26, and returns to ACT2.

If the processor31receives a normal reply command, it determines YES in ACT26, and proceeds to ACT27. As ACT27, the processor31adds the registered commercial product data included in the normal reply command to the settlement sales data Rc of the target of the process acquired in the process of ACT22. Thus, the settlement sales data Rc becomes the settlement sales data Rcc. Thereafter, the processor31returns to ACT21.

The processor31confirms whether other settlement sales data Rc which is a target of the process is stored in the settlement information file331. If the settlement sales data Rc which is a target of the process is stored, the settlement sales data Rc is processed in the same manner as described above in ACT22to ACT27. If the settlement sales data Rc which is a target of the process is not stored, the processor31ends the information process of the procedure shown in the flowchart ofFIG.11.

Herein, the processor31of the settlement server30constitutes an inquiry unit by executing the process of ACT21to ACT25shown inFIG.11. Specifically, the processor31executes an inquiry to the receipt server20with the transaction identification information (settlement number) included in the settlement sales data Rc reported from the settlement terminal (the POS terminal10).

The processor31also constitutes a storage unit by executing the process of ACT26and Act27shown inFIG.11. Specifically, the processor31stores information regarding the purchased commercial product (registered commercial product data) output from the receipt server20in reply to the inquiry in association with the settlement sales data Rc including the transaction identification information (settlement number).

The processor21of the receipt server20constitutes an acquisition unit by executing the process of ACT31to ACT36shown inFIG.12. Specifically, the processor21acquires the receipt data on the commercial transaction, identified by the transaction identification information (the settlement number) included in the settlement sales data reported from the settlement terminal to the settling agent that assists settlement of the commercial transaction, from the receipt storage unit (the second file233) that stores the receipt data (the second receipt data Rb) generated by the settlement terminal (the POS terminal10) at the time of settlement of the commercial transaction.

The processor21also constitutes an output unit by executing the process of ACT37shown inFIG.12. Specifically, the processor21outputs information relating to a purchased commercial product included in the receipt data (the second receipt data Rb) acquired by the acquisition unit to the settlement server30of the settling agent.

Furthermore, the processor21constitutes a detection unit and an addition unit by executing the process of ACT38and ACT39shown inFIG.12. Specifically, the processor21detects first identification information (the user ID and the terminal ID) set to the person making the settlement of the commercial transaction identified by the transaction identification information (the settlement number). Then, the processor21adds the first identification information (the user ID and the terminal ID) to the receipt data (the second receipt data Rb) stored in the receipt storage unit (the second file233) and acquired by the acquisition unit.

As described above in detail, in the server system100, the settlement server30, in which the purchase information acquisition application is implemented, cooperates with the receipt server20, in which the purchase information reply application is implemented. Through the cooperation, the settlement sales data Rc stored in the settlement information file331of the settlement server30becomes the purchase settlement sales data Rcc including purchase information provided from the receipt server20, namely, registered commercial product data. Therefore, the settling agent can grasp information on what was purchased, in addition to the information on who utilized the electronic settlement where, when, and for how much money.

Thus, the receipt server20can realize a service for providing the settling agent with the information on the commercial product purchased by the person making the settlement using the electronic settlement.

Furthermore, the receipt server20is configured to provide the settlement server30with the information relating to the purchased commercial product in reply to a request command from the settlement server30. Therefore, since the receipt server20may provide only the settlement server30that made a request with the information relating to the purchased commercial product, a burden imposed on the information provision is light.

Moreover, the receipt server20includes the server side setting table231. The receipt server20can store in the second file233only the receipt data of the electronic settlement relating to the settling agent to which the output flag “1” is set, namely, the settling agent which is a target of provision of purchase information. Therefore, the storage capacity of the second file233can be saved. In addition, if a settling agent which is not a target of provision of purchase information requests provision of purchase information, or if a settling agent which is a target of provision of purchase information reports that the provision of purchase information is unnecessary, it suffices only that the value of the output flag is changed. Therefore, it is possible to address a request from the settling agents easily and quickly.

The receipt server20has a function of adding the user ID and the terminal ID included in the purchase information request command to the second receipt data Rb stored in the second file233to create the second receipt data Rbb. The user ID or the terminal ID added to the second receipt data Rb is effective as an identifier of the person making the settlement who utilizes the electronic settlement.

On the other hand, the second receipt data Rb does not necessarily include a receipt ID, which is an identifier of the person who utilizes the electronic receipt. Thus, according to the present embodiment, the POS terminal10digitizes not only receipt data including a receipt ID, but also receipt data including a settlement title set to the POS side setting table131, even if the receipt data does not include a receipt ID, and transmits the digitized data to the receipt server20. Regardless of whether the receipt data includes a receipt ID or not, the receipt server20stores the second receipt data Rb including the settlement title in the second file233.

Therefore, the server system100includes means for associating the user ID or the terminal ID with the receipt ID of the person making the settlement identified by the user ID or the terminal ID. The means may be provided by the receipt server20or the settlement server30. By associating the user ID or the terminal ID with the receipt ID, the second receipt data Rbb to which the user ID and the terminal ID were added can be used in place of the first receipt data Ra that can receive the electronic receipt service. Therefore, even a person making the settlement who is not a target of the electronic receipt service at the time of electronic settlement can receive the electronic receipt service by associating the user ID or the terminal ID.

Second Embodiment

The first embodiment is an example in which the processor21of the receipt server20outputs information relating to the purchased commercial product in real time each time the processor21receives a purchase information request command from the settlement server30. Therefore, in accordance with an increase in purchase information request commands, there is concern about an increase in a process load of the processor21. The second embodiment is an example in which the processor21collectively outputs information relating to the purchased commercial products to the settlement server30by a batch process.

The second embodiment differs from the first embodiment in a part of the procedure executed by the processor31of the settlement server30explained with reference toFIG.11, and a part of the procedure executed by the processor21of the receipt server20explained with reference toFIG.12. The other parts explained with reference toFIGS.1to10are common to the first and second embodiments, and they are also used in the second embodiment.

FIG.13is a flowchart showing a procedure of a main information process executed by the processor31of the settlement server30in accordance with the purchase information acquisition application.FIG.14is a flowchart showing a procedure of a main information process executed by the processor21of the receipt server20in accordance with the purchase information reply application. Hereinafter, main operations of the server system100of the second embodiment will be explained with reference to the drawings. The operations explained below are mere examples. The procedure of the operations is not particularly limited, as long as similar effects and advantages can be obtained.

The purchase information acquisition application is activated at a preset time, for example, at 0:00 a.m. When the purchase information acquisition application is activated, the processor31of the settlement server30starts the process of the procedure shown in the flowchart ofFIG.13. First, as ACT41, the processor31confirms whether the settlement sales data, which is a target of the process, is stored in the settlement information file331. The settlement sales data, i.e., a target of the process, is the settlement sales data Rc to which registered commercial product data was not added. The settlement sales data Rcc to which registered commercial product data was added is not a target of the process. If the settlement sales data Rc, i.e., a target of the process, is not stored in the settlement information file331, the processor31determines NO in ACT41, and ends the process.

If the settlement sales data Rc, i.e., a target of the process, is stored in the settlement information file331, the processor31determines YES in ACT41, and proceeds to ACT42. The processor31acquires the settlement sales data Rc, i.e., a target of the process, from the settlement information file331as ACT42. Then, the processor31acquires a settlement number from the settlement sales data Rc as ACT43. Furthermore, the processor31acquires a user ID and a terminal ID from the settlement sales data Rc as ACT44.

The processor31produces a request record as ACT45. The request record includes the settlement number, the user ID, and the terminal ID acquired from the settlement sales data Rc. The processor31stores the request record in a request file as ACT46. The request file is cleared before the process is started.

As ACT47, the processor31confirms whether further settlement sales data Rc, which is a target of the process, is stored in the settlement information file331. If the settlement sales data Rc is stored, the processor31determines YES in ACT47, and returns to ACT42. Then, the processor31executes the process in ACT42and the subsequent acts in the same manner as described above. Therefore, request records produced based on the settlement sales data Rc, which is a target of the process, are accumulated in the request file.

If the processor31confirms that the settlement sales data Rc, i.e., a target of the process, is not stored in the settlement information file331, the processor31determines NO in ACT47, and proceeds to ACT48. The processor31transmits a request file to the receipt server20as ACT48. The request file is transmitted to the receipt server20through the communication network40.

The purchase information reply application is also activated at a preset time, for example, at 2:00 a.m. When the purchase information reply application is activated, the processor21of the receipt server20confirms as ACT61inFIG.14whether the request file is received. If the request file is not received, the processor21determines NO in ACT61, and ends the process.

If the request file is received, the processor21determines YES in ACT61, and proceeds to ACT62. The processor21acquires the request record from the request file as ACT62. Then, the processor21acquires a settlement number from the request record as ACT63. As ACT64, the processor21searches the second file233using the settlement number as a search key.

The processor21determines, as ACT65, whether the second receipt data Rb including the settlement number as the search key is present or not. If the corresponding second receipt data Rb is not stored in the second file233, the processor21determines NO in ACT65, and proceeds to ACT70.

If the second receipt data Rb including the settlement number as the search key is stored in the second file233, the processor21determines YES in ACT65, and proceeds to ACT66. The processor21acquires registered commercial product data from the second receipt data Rb as ACT66. As ACT67, the processor21adds the registered commercial product data to the request record detected from the request file in the process of ACT62.

The processor21detects the user ID and the terminal ID from the request record as ACT68. Then, the processor21adds, as ACT69, the user ID and the terminal ID to the second receipt data Rb including the settlement number as the search key. Thus, the second receipt data Rb becomes the second receipt data Rbb to which the user ID and the terminal ID were added.

The processor21confirms, as ACT70, whether another request record is present in the request file. If a request record is present, the processor21determines YES in ACT70, and returns to ACT62. Then, the processor21executes the process in ACT62and the subsequent acts in the same manner as described above.

Thus, if the process from ACT62to ACT69was executed for all of the request records stored in the request file, the processor21determines NO in ACT70, and proceeds to ACT71. The processor21produces, as ACT71, a reply file with the request data to which the registered commercial product data was added. Then, as ACT72, the processor21transmits a reply file to the settlement server30, which is the source of the request file. In this way, the processor21ends the information process of the procedure shown inFIG.14.

The reply file transmitted from the receipt server20is transmitted to the settlement server30, which is the source of the request file through the communication network40.

Explanations will return toFIG.13.

The processor31of the settlement server30that transmitted the request file stands by for a reply file as ACT49. Upon receipt of the reply file, the processor31determines YES in ACT49, and proceeds to ACT50. The processor31acquires request data from the reply file as ACT50. As ACT51, the processor31adds the registered commercial product data, to which the request data was added, to the settlement sales data Rc identified by the request data. Thus, the settlement sales data Rc becomes the settlement sales data Rcc to which the registered commercial product data was added.

The processor31confirms, as ACT52, whether other request data is present in the reply file or not. If present, the processor31determines YES in ACT52, and returns to ACT50. Specifically, the processor31acquires the registered commercial product data from the request data, and repeats the process of adding it to the corresponding settlement sales data Rc.

If no other request data is present in the reply file, the processor31determines NO in ACT52. The processor31ends the information process of the procedure shown in the flowchart ofFIG.13.

Therefore, also in the second embodiment with the configuration described above, the settling agent can grasp information on what was purchased, in addition to the information on who utilized the electronic settlement where, when, and for how much money. Thus, the receipt server20can realize a service for providing the settling agent with the information on the commercial product purchased by the person making the settlement using the electronic settlement.

Moreover, the receipt server20performs the information provision service for the settlement server30by a batch process. Therefore, even if the amount of requests for purchase information is increased, the process load of the receipt server20will not considerably increase.

In the second embodiment, the processor31of the settlement server30may execute the process of ACT41to ACT47and the process of ACT48to ACT52at different timings. Specifically, each time the processor31detects the settlement sales data Rc of the target of process, the processor31produces request data based on the settlement sales data Rc. The processor31accumulates the request data in the request file. Thereafter, for example, at a preset time, the processor31transmits the request file to the receipt server20. Upon receipt of a reply file from the receipt server20, the processor31adds the registered commercial product data to the settlement sales data Rc based on the data in the reply file. With this configuration, a similar effect can also be obtained.

The embodiments are not limited to the above-described embodiments of the server system100including the receipt server20and the settlement server30.

In the above embodiments, the receipt server20is described as an example of the receipt server that provides an electronic receipt service. The receipt server20does not necessarily correspond to the electronic receipt service. For example, the receipt server may be specialized in storing receipt data which includes a settlement title of a predetermined settling agent in the second file233, and supplying registered commercial product data, i.e., purchase information from the corresponding receipt data in reply to the purchase information request command from the settlement server30. Such a receipt server does not require the first file232. Furthermore, the processor21does not require ACT12and ACT13of the procedure in the flowchart shown inFIG.6.

In the above embodiment, the transaction identification information included in the settlement sales data is described as a settlement number. Some settling agent may not issue a settlement number for a commercial transaction with electronic settlement. In this case, a shop code and a transaction date and time, or a transaction date and time and a transaction amount, may be used as the transaction identification information.

However, the transaction date and time included in the settlement sales data Rc may be a date and time when the settlement server30acquired the settlement sales data Rc. In such a case, since the clock of the POS terminal10and the clock34of the settlement server30do not necessarily coincide, the transaction date and time in the settlement sales data Rc and the transaction date and time in the receipt data may not coincide. Therefore, the scope of the searches of the receipt server20need to have a slight margin in transaction date and time, not perfect matching.

The above embodiment is an example in which a setting table that does not store an output flag is provided as the POS side setting table131in the POS terminal10. As another embodiment, an equivalent of the server side setting table231that stores an output flag may be provided as the POS side setting table in the POS terminal10. This can eliminate waste of transmission of receipt data settled by electronic settlement relating to a settling agent that is not a target of provision of purchase information to the receipt server20from the POS terminal10. As a result, an effect of reducing the communication traffic of the communication network40can be obtained.

In the above embodiment, the POS terminal10is described as having functions of the commercial product registration unit11, the settlement processing unit12, and the receipt processing unit13. For example, the settlement terminal dedicated to electronic settlement connected to the POS terminal10may have the functions of the settlement processing unit12and the receipt processing unit13. In this case, the POS side setting table131may be provided in the settlement terminal instead of the POS terminal10.

The program concerning the present embodiment may be transferred in a state of being stored in an electronic device or in a state of not being stored in an electronic device. In the latter case, the program may be transferred via a network or may be transferred in a state of being stored in a recording medium. The recording medium is a non-transitory tangible medium. The recording medium is a computer-readable medium. The recording medium may be of any type, such as a CD-ROM or a memory card, as long as it can store programs and can be read by the computer.