Settlement terminal and program

Abstract

To realize a service for providing a settling agent with information on a commodity purchased by a person making the settlement using electronic settlement.SOLUTION: 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 during settlement of the commercial transaction. The output unit outputs information relating to a purchased commodity included in the receipt data acquired by the acquisition unit, to a settlement server of the settling agent.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] Embodiments of the present invention relate to a receipt server, its program, and a server system including the receipt server.

Background Art

[0002] In recent years, electronic payment that electronically processes transaction settlements has attracted attention. Electronic payment includes, for example, credit card payment, electronic money payment, code payment using a barcode or a two-dimensional code, etc. When electronic payment is made at a physical store, settlement sales data is output from the settlement terminal to the server of the settlement business operator. The settlement sales data includes information on the settler, information on the transaction date and time, information on the transaction store, information on the settlement amount, etc. However, information on the products purchased by the settler is not included. Therefore, although the settlement business operator can grasp information such as who used electronic payment when, where, and how much, they cannot grasp information on what was purchased. A service that provides information on products purchased by a settler using electronic payment to the settlement business operator is desired.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] The problem to be solved by the embodiments of the present invention is to provide a receipt server and a server system that can realize a service for providing information on products purchased by a settler using electronic payment to the settlement business operator.

Means for Solving the Problems

[0005] In one embodiment, the receipt server includes an acquisition unit and an output unit. The acquisition unit acquires receipt data of a commercial transaction identified by transaction identification information included in settlement sales data notified from a settlement terminal to a settlement operator who supports the settlement of the commercial transaction, from a receipt storage unit that stores the receipt data generated by the settlement terminal at the time of settlement of the commercial transaction. The output unit outputs information related to the purchased goods included in the receipt data acquired by the acquisition unit to the settlement server of the settlement operator.

Brief Description of the Drawings

[0006]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Embodiments for Carrying Out the Invention

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

[0008] [First Embodiment] FIG. 1 is a system diagram showing an overview of an embodiment. This system includes a plurality of POS (Point Of Sales) terminals 10, one receipt server 20, a plurality of settlement servers 30, and a communication network 40. The communication network 40 is composed of one or more networks such as the Internet, a telephone network, or a LAN (Local Area Network).

[0009] Each POS terminal 10 is a computer terminal installed in each store and used for registering and settling the goods purchased by customers. The store is not limited by its business type. The store may be a retail store such as a supermarket or a specialty store, or a restaurant. Each POS terminal 10 is connected to the communication network 40 respectively. Each POS terminal 10 may be directly connected to the communication network 40, or one or more POS terminals 10 may be connected to the communication network 40 via a relay server.

[0010] The receipt server 20 is a server computer managed by an enterprise entity that operates an electronic receipt service. The electronic receipt service is a service that digitizes the printed data of receipts issued from the POS terminal 10 during accounting at a store and enables a customer, who is the payer, to view the receipt as an image on a communication terminal owned by the customer. The communication terminal is typically a smartphone. The communication terminal may also be a tablet terminal, a personal computer, or the like. The receipt server 20 is connected to the communication network 40. The receipt server 20 collaborates with each POS terminal 10 connected to the communication network 40 to provide an electronic receipt service to customers.

[0011] A user who uses the electronic receipt service installs a dedicated application program, so-called an electronic receipt app, on a portable communication terminal, such as a smartphone. By installing the electronic receipt app on the communication terminal, a receipt ID, which serves as an identifier for the user, is issued. The receipt ID is displayed on the display of the communication terminal in the form of, for example, a barcode. When the receipt ID is read by the scanner of the POS terminal 10 at the time of settlement of a business transaction in which the user is the customer, the receipt data indicating the details of the business transaction is digitized and transmitted from the POS terminal 10 to the receipt server 20. The receipt data includes the receipt ID. The user accesses the receipt server 20 with the electronic receipt app on the communication terminal. Then, a receipt image based on the receipt data including the receipt ID set in the communication terminal is downloaded from the receipt server 20. The user can view the downloaded receipt image on the communication terminal.

[0012] Each payment server 30 is a server computer managed by a payment service provider that supports the settlement of business transactions by electronic payment. Electronic payment includes credit card payment, electronic money payment, code payment using a barcode or a two-dimensional code, and the like. Each payment server 30 is connected to the communication network 40. Each payment server 30 supports the electronic payment executed at each POS terminal 10 through the communication network 40.

[0013] Each time an electronic payment supported by the payment server 30 is executed on the POS terminal 10, the payment server 30 assigns a payment number. The payment number is typically a sequential number. The payment number is referred to as an approval number, a transaction serial number, an invoice number, etc. by the payment service provider. The payment number is included in the receipt data of the commercial transaction that has been electronically paid, together with the payment name, the payment amount, etc.

[0014] The payment name is a name that represents the type of the payment amount. When the payment amount is the amount paid in cash payment, the payment name is, for example, "Cash Total". When the payment amount is the amount paid in credit card payment, the payment name is, for example, "Credit Total" or "Credit Card Total". When the payment amount is the amount paid in electronic money payment, the payment name is, for example, a unique name indicating the type of electronic money. When the payment amount is the amount paid in code payment, the payment name is, for example, a unique name indicating the type of code payment.

[0015] Here, the receipt server 20 and each payment server 30 constitute the server system 100. That is, the server system 100 is a computer network system in which the receipt server 20 and each payment server 30 are connected by a communication network 40. Note that the server system 100 may include servers other than the receipt server 20 and the payment server 30.

[0016] Next, the POS terminal 10, the receipt server 20, and the payment server 30 will be described in detail. The POS terminal 10 has functions as a product registration unit 11, a payment processing unit 12, and a receipt processing unit 13. The product registration unit 11 is a function of registering the sales data of the products purchased by the customer in the memory. By this function, the total amount of the commercial transaction with the customer is calculated. Since the function as the product registration unit 11 is well-known, a detailed description will be omitted.

[0017] The settlement processing unit 12 has a function of settling commercial transactions based on payment data for the total amount of commercial transactions. In the case of cash payment, the settlement processing unit 12 executes cash settlement processing. In the case of credit card payment, the settlement processing unit 12 executes credit card settlement processing. In the case of electronic money payment, the settlement processing unit 12 executes electronic money settlement processing. In the case of code settlement payment, the settlement processing unit 12 executes code settlement processing. Since cash settlement processing, credit card settlement processing, electronic money settlement processing, and code settlement processing are all well-known processes, detailed descriptions thereof are omitted. When a commercial transaction is settled by electronic settlement supported by the settlement server 30, settlement sales data is output from the POS terminal 10 to the settlement server 30 in the same manner as in the conventional case. The settlement sales data includes information on the customer who is the settler, information on the transaction date and time, information on the transaction store, settlement number, settlement amount information, and the like.

[0018] The receipt processing unit 13 has a function of processing receipt data generated for each settlement of a commercial transaction. The receipt processing unit 13 processes the receipt data using the POS-side setting table 131 having the data structure shown in FIG. 2. The POS-side setting table 131 is downloaded from the receipt server 20 to each POS terminal 10, for example.

[0019] The POS-side setting table 131 is a data table in which settlement names are set for each merchant code. The merchant code is a unique code set for each settlement merchant in order to individually identify each settlement merchant. The settlement name is a name representing the settlement amount in electronic settlement supported by the settlement server 30 of the settlement merchant specified by the corresponding merchant code.

[0020] Figure 3 is a flowchart showing the main processing procedure of the receipt processing unit 13. This process is started every time a commercial transaction is settled by the settlement processing unit 12. That is, when a commercial transaction is settled, the receipt processing unit 13 acquires, as ACT1, receipt data indicating the details of the commercial transaction. The receipt data is generated by the settlement processing unit 12. The receipt data includes the transaction date and time, transaction number, registered product data, total amount, settlement name, settlement amount, etc. Also, if the receipt ID is read by the scanner of the POS terminal 10 at the time of settlement of the commercial transaction, the receipt ID is included in the receipt data. Also, when the commercial transaction is settled by electronic payment, the settlement number is included in the receipt data.

[0021] The receipt processing unit 13 checks, as ACT2, whether the receipt ID is included in the receipt data. If the receipt ID is included in the receipt data, the receipt processing unit 13 determines YES in ACT2 and proceeds to ACT6. The processing after ACT6 will be described later.

[0022] If the receipt ID is not included in the receipt data, the receipt processing unit 13 determines NO in ACT2 and proceeds to ACT3. The receipt processing unit 13 acquires, as ACT3, the settlement name included in the receipt data. The receipt processing unit 13 checks, as ACT4, whether the settlement name is set in the POS-side setting table 131, that is, whether it is a name representing the settlement amount of electronic payment. If the settlement name is not set in the POS-side setting table 131, that is, if it is not electronic payment, the receipt processing unit 13 determines NO in ACT4 and proceeds to ACT5. The receipt processing unit 13 controls the printer of the POS terminal 10 as ACT5 and prints out the receipt data on the receipt paper.

[0023] On the other hand, if the settlement name is set in the POS-side setting table 131, the receipt processing unit 13 determines YES in ACT4 and proceeds to ACT6. In this way, when the receipt processing unit 13 acquires receipt data including a receipt ID or acquires receipt data that does not include a receipt ID but includes an electronic payment settlement name, it proceeds to ACT6. The receipt processing unit 13 performs electronic conversion of the receipt data as ACT6. That is, the receipt processing unit 13 converts the unstructured-form receipt data into structured-form receipt data, so-called electronic receipt data, according to a predetermined conversion rule.

[0024] After finishing the electronic conversion of the receipt data, the receipt processing unit 13 transmits the electronically converted receipt data to the receipt server 20 as ACT7. The receipt data is transmitted to the receipt server 20 through the communication network 40.

[0025] In this way, when the receipt data is printed and output on receipt paper or electronically converted and transmitted to the receipt server 20, the receipt processing unit 13 ends the processing of the procedure shown in the flowchart of FIG. 3.

[0026] FIG. 4 is a block diagram showing the main circuit configuration of the receipt server 20. The receipt server 20 includes a processor 21, a main memory 22, an auxiliary storage device 23, a clock 24, and a communication interface 25. The receipt server 20 connects the processor 21, the main memory 22, the auxiliary storage device 23, the clock 24, and the communication interface 25 with a system bus 26. The system bus 26 includes an address bus, a data bus, and the like. The receipt server 20 constitutes a computer by connecting the processor 21, the main memory 22, the auxiliary storage device 23, the clock 24, and the communication interface 25 with the system bus 26.

[0027] The processor 21 corresponds to the central part of the above computer. The processor 21 controls each part to realize various functions as the receipt server 20 according to an operating system or an application program. The processor 21 is, for example, a CPU (Central Processing Unit).

[0028] The main memory 22 corresponds to the main storage part of the above computer. The main memory 22 includes a non-volatile memory area and a volatile memory area. In the non-volatile memory area, the main memory 22 stores an operating system or an application program. In the volatile memory area, the main memory 22 stores data necessary for the processor 21 to execute processes for controlling each part. Also, the main memory 22 uses the volatile memory area as a work area where data is appropriately rewritten by the processor 21. The non-volatile memory area is, for example, a ROM (Read Only Memory). The volatile memory area is, for example, a RAM (Random Access Memory).

[0029] The auxiliary storage device 23 corresponds to the auxiliary storage part of the above computer. As the auxiliary storage device 23, for example, well-known storage devices such as EEPROM (registered trademark) (Electric Erasable Programmable Read-Only Memory), HDD (Hard Disc Drive), or SSD (Solid State Drive) are used alone or in combination. The auxiliary storage device 23 stores data used when the processor 21 performs various processes, data generated by the processes in the processor 21, and the like. The auxiliary storage device 23 may also store an application program.

[0030] The application program stored in the main memory 22 or the auxiliary storage device 23 includes a control program described later. The method of installing the control program in the main memory 22 or the auxiliary storage device 23 is not particularly limited. The control program can be recorded on a removable recording medium, or distributed through communication via a network and installed in the main memory 22 or the auxiliary storage device 23. The form of the recording medium is not limited as long as it can store a program and can be read by the device, such as a CD-ROM, a memory card, etc.

[0031] The clock 24 functions as a time information source for the receipt server 20. The processor 21 acquires the current date and time based on the time information measured by the clock 24.

[0032] The communication interface 25 connects to the communication network 40. The receipt server 20 performs data communication with the POS terminal 10 and the settlement server 30 connected to the communication network 40 via the communication interface 25. Also, the receipt server 20 performs data communication with a communication terminal installed with an electronic receipt application via the communication interface 25.

[0033] The receipt server 20 with such a configuration divides a part of the storage area of the auxiliary storage device 23 into an area as the server - side setting table 231, an area as the first file 232, and an area as the second file 233.

[0034] FIG. 5 is a schematic diagram showing the data structure of the server - side setting table 231. As shown in the figure, the server - side setting table 231 is a data table in which a settlement name and an output flag are set for each merchant code. The output flag is 1 - bit data for identifying whether the settlement merchant specified by the corresponding merchant code is a settlement merchant for which purchase information is to be provided. The purchase information is the product purchased by the customer, that is, the product code, product name, price, etc. of the so - called purchased product. In this embodiment, the output flag indicating a settlement merchant for which purchase information is to be provided is set to "1", and the output flag indicating a settlement merchant for which purchase information is not to be provided is set to "0".

[0035] The first file 232 and the second file 233 function as a receipt storage unit for storing the receipt data received from each POS terminal 10. The processor 21 refers to the server - side setting table 231 and distributes the storage destination of the receipt data received from each POS terminal 10 to the first file 232, the second file 233, or both the first file 232 and the second file 233.

[0036] FIG. 6 is a flowchart showing the procedure of the receipt data distribution process executed by the processor 21 of the receipt server 20. The processor 21 is waiting for receipt of receipt data as ACT11. When the receipt data is received, the processor 21 determines YES in ACT11 and proceeds to ACT12. The processor 21 checks whether the receipt ID is included in the receipt data as ACT12. If the receipt ID is included in the receipt data, the processor 21 determines YES in ACT12 and proceeds to ACT13. The processor 21 stores the receipt data in the first file 232 as ACT13. Then the processor 21 proceeds to ACT14.

[0037] If the receipt ID is not included in the receipt data, the processor 21 determines NO in ACT12. The processor 21 skips the process of ACT13 and proceeds to ACT14. The processor 21 obtains the settlement name included in the receipt data as ACT14. Then the processor 21 checks whether the settlement name is set in the server-side setting table 231, that is, whether it is a name representing the settlement amount of the electronic payment, as ACT15. If the settlement name is not set in the server-side setting table 231, that is, if it is not an electronic payment, the processor 21 determines NO in ACT15 and ends this distribution process.

[0038] If the settlement name is set in the server-side setting table 231, that is, if it is an electronic payment, the processor 21 checks the output flag set in the server-side setting table 231 corresponding to the settlement name as ACT16. Here, if the output flag is "0", that is, in the case of an electronic payment related to a settlement merchant not subject to purchase information provision, the processor 21 determines NO in ACT16 and ends this distribution process.

[0039] When the output flag is "1", that is, in the case of electronic payment related to the payment operator for which purchase information is to be provided, the processor 21 determines YES in ACT16 and proceeds to ACT17. The processor 21 stores the receipt data in the second file 233 as ACT17. Thus, the processor 21 finishes this allocation process.

[0040] Through such an allocation process, the receipt data including the receipt ID, that is, the receipt data related to the transaction of the customer who receives the electronic receipt service, is stored in the first file 232. The receipt data related to the transaction settled by electronic payment related to the payment operator for which purchase information is to be provided is stored in the second file 233. Note that even for the transaction of the customer who receives the electronic receipt service, the receipt data related to the transaction settled by electronic payment related to the payment operator for which purchase information is to be provided is stored in both the first file 232 and the second file 233. Hereinafter, the receipt data stored in the first file 232 is referred to as first receipt data Ra (see FIG. 7). The receipt data stored in the second file 233 is referred to as second receipt data Rb (see FIG. 8).

[0041] Here, the first file 232 and the second file 233 constitute a receipt storage unit. The first file 232 constitutes a first receipt storage unit, and the second file 233 constitutes a second receipt storage unit.

[0042] Also, the processor 21 that executes the allocation process constitutes a processing unit. That is, the processor 21 stores the receipt data including the second identification information (receipt ID) for identifying the electronic receipt user in the first receipt storage unit (the first file 232), and stores the receipt data including the information (payment name) indicating that it is a transaction settled with the support of the payment operator in the second receipt storage unit (the second file 233).

[0043] FIG. 7 is a schematic diagram showing the structure of the first receipt data Ra stored in the first file 232. As shown in the figure, the first receipt data Ra includes at least a receipt ID, a store code, a transaction date and time, a cash register number, a transaction number, registered product data, a total amount, a settlement name, a settlement amount, etc. The store code is an identifier of the store where the POS terminal 10 that transmitted the first receipt data Ra is installed. The transaction date and time is the date and time when the commercial transaction was settled at the POS terminal 10. The cash register number is an identifier of the POS terminal 10. The transaction number is a sequential number assigned to the commercial transaction settled at the POS terminal 10. The registered product data is information related to the products registered as purchased products, and consists of a product code, a price, a sales quantity, a sales amount, etc. The registered product data may include a product name instead of the product code. Alternatively, the registered product data may include both a product code and a product name. The total amount is the sum of the sales amounts included in the registered product data. The settlement name and the settlement amount are the settlement name and the settlement amount of the payment data for the total amount. Note that the first receipt data Ra related to an electronically settled commercial transaction further includes a settlement number.

[0044] FIG. 8 is a schematic diagram showing the structure of the second receipt data Rb stored in the second file 233. As shown in the figure, the second receipt data Rb includes at least a store code, a transaction date and time, a cash register number, a transaction number, registered product data, a total amount, a settlement name, a settlement amount, a settlement number, etc. Note that the second receipt data Rb related to a commercial transaction of a customer who receives an electronic receipt service includes a receipt ID.

[0045] The other second receipt data Rbb shown in FIG. 8 shows the second receipt data after the purchase information delivery process described later is performed. The second receipt data Rbb is data obtained by adding a user ID and a terminal ID to the second receipt data Rb. The user ID and the terminal ID will be described later.

[0046] FIG. 9 is a block diagram showing the main circuit configuration of the settlement server 30. The settlement server 30 includes a processor 31, a main memory 32, an auxiliary storage device 33, a clock 34, and a communication interface 35. The settlement server 30 connects the processor 31 to the main memory 32, the auxiliary storage device 33, the clock 34, and the communication interface 35 via a system bus 36. The system bus 36 includes an address bus, a data bus, and the like. The settlement server 30 constitutes a computer by connecting the processor 31 to the main memory 32, the auxiliary storage device 33, the clock 34, and the communication interface 35 via the system bus 36.

[0047] The processor 31 corresponds to the central part of the above computer. The processor 31 controls each part in order to realize various functions as the settlement server 30 according to an operating system or an application program. The processor 31 is, for example, a CPU.

[0048] The main memory 32 corresponds to the main storage part of the above computer. The main memory 32 includes a non-volatile memory area and a volatile memory area. The main memory 32 stores an operating system or an application program in the non-volatile memory area. The main memory 32 stores data necessary for the processor 31 to execute processes for controlling each part in the volatile memory area. The main memory 32 also uses the volatile memory area as a work area where data is appropriately rewritten by the processor 31. The non-volatile memory area is, for example, a ROM. The volatile memory area is, for example, a RAM.

[0049] The auxiliary storage device 33 corresponds to the auxiliary storage part of the above computer. As the auxiliary storage device 33, for example, well-known storage devices such as EEPROM, HDD, or SSD are used alone or in combination of a plurality. The auxiliary storage device 33 stores data used when the processor 31 performs various processes, data generated by the processes in the processor 31, and the like. The auxiliary storage device 33 may store an application program.

[0050] The application program stored in the main memory 32 or the auxiliary storage device 33 includes a control program described later. The method of installing the control program in the main memory 32 or the auxiliary storage device 33 is not particularly limited. The control program can be recorded on a removable recording medium or distributed by communication via a network and installed in the main memory 32 or the auxiliary storage device 33. The form of the recording medium is not limited as long as it can store a program and can be read by the device, such as a CD-ROM, a memory card, etc.

[0051] The clock 34 functions as a time information source of the settlement server 30. The processor 31 acquires the current date and time based on the time information measured by the clock 34.

[0052] The communication interface 35 connects to the communication network 40. The settlement server 30 performs data communication with the POS terminal 10 and the receipt server 20 connected to the communication network 40 via the communication interface 35.

[0053] The settlement server 30 having such a configuration designates a part of the storage area of the auxiliary storage device 33 as an area as the settlement information file 331. The settlement information file 331 is a data file for storing the settlement sales data transmitted from each POS terminal 10 to the settlement server 30.

[0054] FIG. 10 is a schematic diagram showing the structure of the settlement sales data Rc stored in the settlement information file 331. The settlement sales data Rc includes a store 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 uses electronic payment. The terminal ID is an identifier of a communication terminal such as a smartphone.

[0055] A customer who uses electronic payment registers with the payment provider in advance. Through this user registration, a unique user ID is issued by the payment provider. The user ID is stored in a medium for electronic payment such as a credit card, an electronic money card, or a smartphone. When executing an electronic payment, the POS terminal 10 captures the user ID from the medium. Then, the POS terminal 10 transmits the settlement sales data Rc including the user ID to the settlement server 30 of the corresponding payment provider. Here, when the medium is a communication terminal, the POS terminal 10 also captures the terminal ID from the communication terminal. Then, the POS terminal 10 further includes this terminal ID and transmits the settlement sales data Rc to the settlement server 30. Incidentally, the terminal ID of the settlement sales data Rc related to electronic payment when the medium is not a communication terminal becomes NULL data.

[0056] The other settlement sales data Rcc shown in FIG. 10 shows the settlement sales data after the purchase information delivery process described later is performed. The settlement sales data Rcc is data obtained by adding one or more registered product data to the settlement sales data Rc.

[0057] Thus, the settlement sales data Rc before the execution of the purchase information transfer process does not include registered product data. Therefore, the settlement operator can grasp information such as who, when, and where used electronic settlement and how much from the settlement sales data Rc in the settlement information file 331, but cannot grasp information on the products purchased by the settler, so-called purchase information. The purchase information is stored in the receipt server 20. Therefore, in this embodiment, a control program, so-called purchase information acquisition application, for realizing the process of acquiring purchase information from the receipt server 20 is installed in the settlement server 30. Also, a control program, so-called purchase information response application, for realizing the process of responding with necessary purchase information to the settlement server 30 in conjunction with this purchase information acquisition application is installed in the receipt server 20.

[0058] FIG. 11 is a flowchart showing the main information processing procedure executed by the processor 31 of the settlement server 30 according to the purchase information acquisition application. FIG. 12 is a flowchart showing the main information processing procedure executed by the processor 21 of the receipt server 20 according to the purchase information response application. Hereinafter, with reference to each figure, the main operations of the server system 100 according to the first embodiment will be described. Note that the operations described below are examples. The operation procedure is not particularly limited as long as the same operational effects can be obtained.

[0059] It is activated every time the settlement sales data Rc is stored in the settlement information file 331. The purchase information acquisition application may be activated at a preset time, for example, at 0 minutes every hour.

[0060] When the purchase information acquisition application is activated, the processor 31 of the settlement server 30 starts processing according to the procedure shown in the flowchart of FIG. 11. First, the processor 31 checks whether the settlement sales data to be processed as ACT21 is stored in the settlement information file 331. The settlement sales data to be processed is the settlement sales data Rc without the registered product data added. The settlement sales data Rcc with the registered product data added is not the object to be processed.

[0061] When the settlement sales data Rc to be processed is stored in the settlement information file 331, the processor 31 determines YES in ACT21 and proceeds to ACT22. The processor 31 obtains the settlement sales data Rc from the settlement information file 331 as ACT22. Then the processor 31 obtains the settlement number from the settlement sales data Rc as ACT23. Also, the processor 31 obtains the user ID and the terminal ID from the settlement sales data Rc as ACT24.

[0062] The processor 31 transmits a purchase information request command to the receipt server 20 as ACT25. The purchase information request command includes the settlement number, the user ID, and the terminal ID obtained from the settlement sales data Rc. The purchase information request command is transmitted to the receipt server 20 via the communication network 40.

[0063] In the receipt server 20, a purchase information response application is resident. And the processor 21 of the receipt server 20 is waiting for a purchase information request command as ACT31 in FIG. 12. When receiving the purchase information request command via the communication network 40, the processor 21 determines YES in ACT31 and proceeds to ACT32. The processor 21 obtains the settlement number from the purchase information request command as ACT32. Then the processor 21 searches the second file 233 using this settlement number as a search key as ACT33.

[0064] The processor 21 discriminates the presence or absence of the second receipt data Rb including the settlement number as the search key as ACT34. If the corresponding second receipt data Rb is not stored in the second file 233, the processor 21 determines NO in ACT34 and proceeds to ACT35. The processor 21 transmits an error response command to the settlement server 30 that is the transmission source of the purchase information request command as ACT35.

[0065] For example, when a communication failure occurs between the POS terminal 10 and the receipt server 20, although the settlement sales data of the electronically settled commercial transaction is transmitted to the corresponding settlement server 30, the receipt data of that commercial transaction is not stored in the second file 233. In such a case, an error occurs.

[0066] When the second receipt data Rb including the settlement number as the search key is stored in the second file 233, the processor 21 determines YES in ACT34 and proceeds to ACT36. As ACT36, the processor 21 acquires the registered product data from the second receipt data Rb. Then, as ACT37, the processor 21 transmits a normal response command to the settlement server 30 that is the source of the purchase information request command. The normal response command includes the registered product data obtained in the process of ACT36.

[0067] As ACT38, the processor 21 detects the user ID and the terminal ID from the purchase information request command. Then, as ACT39, the processor 21 adds the user ID and the terminal ID to the second receipt data Rb including the settlement number as the search key.

[0068] Thus, the processor 21 ends the response process for the purchase information request command. Then, when the processor 21 receives the next purchase information request command, it executes the processes of ACT32 to ACT38 in the same manner as described above.

[0069] Return to the description of FIG. 11. The normal response command or the error response command is received by the settlement server 30 that is the source of the purchase information request command via the communication network 40. The processor 31 of the settlement server 30 that transmitted the purchase information request command is waiting for the response command as ACT26. In this waiting state, when an error response command is received, the processor 31 determines NO in ACT26 and returns to ACT21.

[0070] On the one hand, when the processor 31 receives a normal response command, it determines YES in ACT26 and proceeds to ACT27. The processor 31 adds the registered product data included in the normal response command as ACT27 to the settlement sales data Rc of the processing target obtained in the process of ACT22. As a result, the settlement sales data Rc becomes the settlement sales data Rcc. Then, the processor 31 returns to ACT21.

[0071] The processor 31 also checks whether there is other settlement sales data Rc of the processing target stored in the settlement information file 331. If the settlement sales data Rc of the processing target is stored, the processor 31 executes the processes of ACT22 to ACT27 for the settlement sales data Rc in the same manner as described above. If the settlement sales data Rc of the processing target is not stored, the processor 31 ends the information processing of the procedure shown in the flowchart of FIG. 11.

[0072] Here, the processor 31 of the settlement server 30 constitutes an inquiry unit by executing the processes of ACT21 to ACT25 in FIG. 11. That is, the processor 31 makes an inquiry to the receipt server 20 using the transaction identification information (settlement number) included in the settlement sales data Rc notified from the settlement terminal (POS terminal 10).

[0073] Also, the processor 31 constitutes a storage unit by executing the processes of ACT26 and ACT27 in FIG. 11. That is, the processor 31 stores the information (registered product data) related to the purchased product output from the receipt server 20 in response to the inquiry in association with the settlement sales data Rc including the transaction identification information (settlement number).

[0074] The processor 21 of the receipt server 20 constitutes an acquisition unit by executing the processes of ACT31 to ACT36 in FIG. 12. That is, the processor 21 acquires receipt data of a commercial transaction identified by transaction identification information (settlement number) included in settlement sales data notified from the settlement terminal to a settlement business operator that supports the settlement of the commercial transaction, from a receipt storage unit (second file 233) that stores receipt data (second receipt data Rb) generated by the settlement terminal (POS terminal 10) at the time of settlement of the commercial transaction.

[0075] Also, the processor 21 constitutes an output unit by executing the process of ACT37 in FIG. 12. That is, the processor 21 outputs information (registered product data) related to the purchased product included in the receipt data (second receipt data Rb) acquired by the acquisition unit to the settlement server 30 of the settlement business operator.

[0076] Furthermore, the processor 21 constitutes a detection unit and an addition unit by executing the processes of ACT38 and ACT39 in FIG. 12. That is, the processor 21 detects first identification information (user ID, terminal ID) set for the settler of the commercial transaction identified by the transaction identification information (settlement number). Then, the processor 21 adds the first identification information (user ID, terminal ID) to the receipt data (second receipt data Rb) stored in the receipt storage unit (second file 233) and acquired by the acquisition unit.

[0077] As described in detail above, in the server system 100, the settlement server 30 implementing the purchase information acquisition application and the receipt server 20 implementing the purchase information response application operate in conjunction. And by this conjunction, the settlement sales data Rc stored in the settlement information file 331 of the settlement server 30 becomes settlement sales data Rcc including the purchase information provided from the receipt server 20, that is, the registered product data. Therefore, the settlement business operator can grasp not only information such as who used electronic settlement when, where, and how much, but also information on what was purchased.

[0078] In this way, the receipt server 20 can realize a service that provides information on products purchased by a payer using electronic payment to a payment service provider.

[0079] Moreover, the receipt server 20 is configured to provide information related to the purchased product to the payment server 30 in response to a request command from the payment server 30. Therefore, the receipt server 20 only needs to provide information related to the purchased product to the requested payment server 30, and the processing burden required for information provision is small.

[0080] In addition, the receipt server 20 includes a server-side setting table 231. Then, the receipt server 20 stores only the receipt data of electronic payment related to the payment service provider whose output flag is set to "1", that is, the payment service provider targeted for purchase information provision, in the second file 233. Therefore, the storage capacity of the second file 233 can be saved. Also, when a payment service provider that was not targeted for purchase information provision requests the provision of purchase information, or when a payment service provider that was targeted for purchase information provision requests the non-necessity of purchase information, it is only necessary to switch the value of the output flag. Therefore, it is possible to easily and quickly respond to the requests of payment service providers.

[0081] By the way, the receipt server 20 has 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 file 233 to obtain the second receipt data Rbb. The user ID or terminal ID added to the second receipt data Rb is valid as an identifier of a payer who uses electronic payment.

[0082] On the other hand, the second receipt data Rb does not necessarily include the receipt ID which is the identifier of the electronic receipt user. That is, in the present embodiment, each POS terminal 10 digitizes receipt data including the settlement name set in the POS-side setting table 131 and transmits it to the receipt server 20, not limited to receipt data including the receipt ID, even if it does not include the receipt ID. Then, regardless of whether the receipt ID is included or not, the receipt server 20 stores the second receipt data Rb including the settlement name in the second file 233.

[0083] Therefore, the server system 100 includes means for associating the user ID or terminal ID with the receipt ID of the settler identified by the ID. This means may be mainly the receipt server 20 or mainly the settlement server 30. By associating the user ID or terminal ID with the receipt ID, the second receipt data Rbb with the user ID and terminal ID added can become the first receipt data Ra capable of receiving the electronic receipt service. Therefore, for example, even a settler who is not subject to the electronic receipt service at the time of electronic settlement can later receive the electronic receipt service by associating the user ID or terminal ID.

[0084] [Second Embodiment] In the first embodiment, an example was given where the processor 21 of the receipt server 20 responds to the purchase information request command from the settlement server 30 each time and outputs the information related to the purchased goods in real time. For this reason, there is a concern that the processing load of the processor 21 increases as the purchase information request commands increase. Therefore, the second embodiment exemplifies the case where the processor 21 outputs the information related to the purchased goods to the settlement server 30 in a batch process.

[0085] The differences between the second embodiment and the first embodiment lie in part of the processing procedures executed by the processor 31 of the settlement server 30 described with reference to FIG. 11 and in part of the processing procedures executed by the processor 21 of the receipt server 20 described with reference to FIG. 12. Since the other parts described with reference to FIGS. 1 to 10 are common to the first embodiment, they are also used as they are in the second embodiment.

[0086] FIG. 13 is a flowchart showing the main information processing procedure executed by the processor 31 of the settlement server 30 according to the purchase information acquisition application. FIG. 14 is a flowchart showing the main information processing procedure executed by the processor 21 of the receipt server 20 according to the purchase information response application. Hereinafter, with reference to each figure, the main operations of the server system 100 according to the second embodiment will be described. Note that the operations described below are examples. The operation procedures are not particularly limited as long as the same operational effects can be obtained.

[0087] The purchase information acquisition application starts at a preset time, for example, 0:00 am. When the purchase information acquisition application starts, the processor 31 of the settlement server 30 starts processing according to the procedure shown in the flowchart of FIG. 13. First, the processor 31 checks whether the settlement sales data to be processed as ACT41 is stored in the settlement information file 331. The settlement sales data to be processed is the settlement sales data Rc without registered product data added. The settlement sales data Rcc with registered product data added is not subject to processing. If the settlement sales data Rc to be processed is not stored in the settlement information file 331, the processor 31 determines NO in ACT41 and ends this processing.

[0088] If the settlement sales data Rc to be processed is stored in the settlement information file 331, the processor 31 determines YES in ACT41 and proceeds to ACT42. The processor 31 obtains the settlement sales data Rc to be processed from the settlement information file 331 as ACT42. Then the processor 31 obtains the settlement number from the settlement sales data Rc as ACT43. Also, the processor 31 obtains the user ID and the terminal ID from the settlement sales data Rc as ACT44.

[0089] The processor 31 creates a request record as ACT45. The request record includes the settlement number, the user ID, and the terminal ID obtained from the settlement sales data Rc. The processor 31 stores the request record in the request file as ACT46. Note that the request file has been cleared prior to the start of this process.

[0090] The processor 31 checks whether there is still settlement sales data Rc to be processed stored in the settlement information file 331 as ACT47. If the settlement sales data Rc is stored, the processor 31 determines YES in ACT47 and returns to ACT42. Then the processor 31 executes the processes after ACT42 in the same manner as described above. Therefore, the request records created based on the settlement sales data Rc to be processed are accumulated in the request file.

[0091] If it is confirmed that the settlement sales data Rc to be processed is not stored in the settlement information file 331, the processor 31 determines NO in ACT47 and proceeds to ACT48. The processor 31 sends the request file to the receipt server 20 as ACT48. The request file is sent to the receipt server 20 via the communication network 40.

[0092] On the other hand, when the purchase information response application is also launched at a preset time, for example, 2:00 am, when the purchase information response application is launched, the processor 21 of the receipt server 20 checks whether it has received a request file as ACT61 in FIG. 14. If the request file has not been received, the processor 21 determines NO in ACT61 and ends this process.

[0093] If the request file has been received, the processor 21 determines YES in ACT61 and proceeds to ACT62. The processor 21 obtains a request record from the request file as ACT62. Then the processor 21 obtains a settlement number from the request record as ACT63. The processor 21 searches the second file 233 using this settlement number as a search key as ACT64.

[0094] The processor 21 determines whether there is second receipt data Rb including the settlement number as a search key as ACT65. If the corresponding second receipt data Rb is not stored in the second file 233, the processor 21 determines NO in ACT65 and proceeds to ACT70.

[0095] If the second receipt data Rb including the settlement number as a search key is stored in the second file 233, the processor 21 determines YES in ACT65 and proceeds to ACT66. The processor 21 obtains registered product data from the second receipt data Rb as ACT66. Then the processor 21 adds the registered product data to the request record detected from the request file in the process of ACT62 as ACT67.

[0096] The processor 21 detects the user ID and the terminal ID from the request record as ACT68. Then the processor 21 adds the user ID and the terminal ID to the second receipt data Rb including the settlement number as a search key as ACT69. As a result, the second receipt data Rb becomes the second receipt data Rbb with the user ID and the terminal ID added.

[0097] The processor 21 checks whether there is another request record in the request file as ACT70. If there is a request record, the processor 21 determines YES in ACT70 and returns to ACT62. Then, the processor 21 executes the processing after ACT62 in the same manner as described above.

[0098] Thus, if the processing from ACT62 to ACT69 has been executed for all the request records stored in the request file, the processor 21 determines NO in ACT70 and proceeds to ACT71. The processor 21 creates a response file with the request data to which the registered product data is added as ACT71. Then, the processor 21 transmits the response file to the payment server 30, the source of the request file, as ACT72. With this, the processor 21 ends the information processing of the procedure shown in FIG. 14.

[0099] The response file transmitted from the receipt server 20 is transmitted by the payment server 30, the source of the request file, via the communication network 40.

[0100] Return to the description of FIG. 13. The processor 31 of the payment server 30 that has transmitted the request file is waiting for a response file as ACT49. When the response file is received, the processor 31 determines YES in ACT49 and proceeds to ACT50. The processor 31 acquires the request data from the response file as ACT50. Then, the processor 31 adds the registered product data attached to the request data to the settlement sales data Rc specified by the request data as ACT51. As a result, the settlement sales data Rc becomes the settlement sales data Rcc to which the registered product data is added.

[0101] The processor 31 checks whether there is any other request data in the response file as ACT52. If it exists, the processor 31 determines YES in ACT52 and returns to ACT50. That is, the processor 31 repeatedly performs the process of obtaining the registered product data from the request data and adding it to the corresponding settlement sales data Rc.

[0102] If there is no other request data in the response file, the processor 31 determines NO in ACT52. The processor 31 ends the information processing of the procedure shown in the flowchart of FIG. 13.

[0103] Also in the second embodiment having such a configuration, the settlement operator can grasp not only information on who used electronic payment when and where, but also information on what was purchased. That is, the receipt server 20 can realize a service of providing the settlement operator with information on products purchased by the settler using electronic payment.

[0104] Moreover, the receipt server 20 performs the service of providing information to the settlement server 30 by batch processing. Therefore, even when the required amount of purchase information increases, the processing load of the receipt server 20 does not increase significantly.

[0105] In this second embodiment, the processor 31 of the settlement server 30 may perform the processes of ACT41 to ACT47 and the processes of ACT48 to ACT52 at different timings. That is, the processor 31 creates request data based on the settlement sales data Rc every time it detects the settlement sales data Rc to be processed, in the same manner as in the first embodiment. Then, the processor 31 stores the request data in the request file. Thereafter, for example, when a preset time arrives, the processor 31 transmits the request file to the receipt server 20. And when receiving the response file from the receipt server 20, the processor 31 adds the registered product data to the settlement sales data Rc based on the data of the response file. Even if such a configuration is adopted, the same effect can be achieved.

[0106] Although the embodiments of the server system 100 including the receipt server 20 and the settlement server 30 have been described above, such embodiments are not limited thereto.

[0107] In the above embodiment, the receipt server 20 is exemplified as a receipt server that provides an electronic receipt service. The receipt server 20 does not necessarily need to support the electronic receipt service. For example, it may be a receipt server specialized in saving receipt data including the settlement name of a predetermined settlement operator in the second file 233 and responding with registered product data, which is purchase information, from the corresponding receipt data in response to a purchase information request command from the settlement server 30. For such a receipt server, the first file 232 becomes unnecessary. Also, for the processor 21, ACT12 and ACT13 among the procedures shown in the flowchart of FIG. 6 become unnecessary.

[0108] In the above embodiment, the transaction identification information included in the settlement sales data Rc has been described as the settlement number. Depending on the settlement operator, there may be cases where a settlement number is not issued for an electronic payment commercial transaction. In such a case, the store code and the transaction date and time, or the transaction date and time and the transaction amount, may be used as the transaction identification information.

[0109] However, the transaction date and time included in the settlement sales data Rc may be the date and time when the settlement server 30 acquired the settlement sales data Rc. In such a case, since the clock of the POS terminal 10 and the clock 34 of the settlement server 30 do not necessarily match, there is a possibility that the transaction date and time of the settlement sales data Rc and the transaction date and time of the receipt data may deviate. Therefore, the receipt server 20 needs to have a slightly wider search range for the transaction date and time instead of an exact match.

[0110] In the above-described embodiment, the case where the POS terminal 10 is provided with the setting table 131 that does not store the output flag as the POS-side setting table was exemplified. As another embodiment, a POS-side setting table equivalent to the server-side setting table 231 that stores the output flag may be provided in the POS terminal 10. By doing so, it is possible to eliminate the waste of transmitting receipt data settled by electronic payment related to payment service providers not subject to purchase information provision from the POS terminal 10 to the receipt server 20. As a result, it is possible to reduce the communication traffic volume of the communication network 40.

[0111] In the above-described embodiment, the POS terminal 10 has been described as having functions as the product registration unit 11, the payment processing unit 12, and the receipt processing unit 13. For example, the functions as the payment processing unit 12 and the receipt processing unit 13 may be provided in a dedicated payment terminal connected to the POS terminal 10. In this case, the POS-side setting table 131 will be provided in the payment terminal instead of the POS terminal 10.

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

Explanation of Reference Numerals

[0113] 10... POS terminal, 11... Product registration unit, 12... Payment processing unit, 13... Receipt processing unit, 20... Receipt server, 21, 31... Processor, 22, 32... Main memory, 23, 33... Auxiliary storage device, 24, 34... Clock, 25, 35... Communication interface, 26, 36... System bus, 30... Payment server, 40... Communication network, 131... POS-side setting table, 231... Server-side setting table, 232... First file, 233... Second file, 331... Payment information file.

Claims

1. An acquisition unit that acquires receipt data of a commercial transaction identified by transaction identification information included in settlement sales data notified from the settlement terminal to a settlement operator that supports the settlement of the commercial transaction, from a receipt storage unit that stores the receipt data generated by the settlement terminal at the time of settlement of the commercial transaction; An output unit that outputs information related to purchased goods included in the receipt data acquired by the acquisition unit to a settlement server of the settlement operator; A receipt server comprising:

2. The acquisition unit acquires receipt data of a commercial transaction identified by the transaction identification information included in a request command from the settlement server, The output unit outputs information related to the purchased goods to the settlement server that is the source of the request command. The receipt server according to claim 1.

3. A detection unit that detects first identification information set for a settler of a commercial transaction identified by the transaction identification information; An addition unit that adds the first identification information to the receipt data stored in the receipt storage unit and acquired by the acquisition unit; The receipt server according to claim 1 or 2, further comprising:

4. The receipt storage unit includes a first receipt storage unit and a second receipt storage unit, A processing unit that stores receipt data including second identification information for identifying an electronic receipt user in the first receipt storage unit, and stores receipt data including information indicating that it is a commercial transaction settled with the support of a settlement operator in the second receipt storage unit; Further comprising The acquisition unit acquires receipt data from the second receipt storage unit. The receipt server according to any one of claims 1 to 3.

5. A receipt server according to any one of claims 1 to 4; An inquiry unit that inquires of the receipt server using transaction identification information included in settlement sales data notified from a settlement terminal; and a storage unit that stores information related to purchased goods output from the receipt server in response to the inquiry in association with the settlement sales data including the transaction identification information. A settlement server having A server system comprising:

6. On a computer, A function of causing the computer to acquire receipt data of a commercial transaction identified by transaction identification information included in settlement sales data notified from a settlement terminal to a settlement operator that supports the settlement of the commercial transaction, from a receipt storage unit that stores the receipt data generated by the settlement terminal at the time of settlement of the commercial transaction; A function for outputting information related to purchased goods included in the acquired receipt data to the settlement server of the settlement operator, A program for realizing the same.

Images