Transaction processing system, information processing apparatus, and information processing program
The transaction processing system addresses the issue of applying electronic receipt services by incorporating various processing means to facilitate identifier acquisition and linking, ensuring that electronic receipt services can be applied even if the identifier is not obtained during the transaction.
Patent Information
- Application Number
- JP2023199179
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-11-24
- Publication Date
- 2025-06-05
- Estimated Expiration
- 2043-11-24
AI Technical Summary
Existing transaction processing systems fail to enable the application of electronic receipt services when an identifier for the electronic receipt service cannot be obtained during a transaction, due to issues like communication errors.
A transaction processing system comprising a receipt management device, a transaction processing device, and a transaction management device, equipped with various processing means that allow for identifier acquisition, inquiry, response, notification, collection, generation, journal acquisition, extraction, and processing to facilitate the linking and application of electronic receipt services.
Enables the application of electronic receipt services even if the identifier for the electronic receipt service cannot be obtained during the transaction, by allowing for later application and ensuring seamless transaction processing.
Smart Images

Figure 2025085357000001_ABST
Abstract
Description
[Technical field]
[0001] An embodiment of the present invention relates to a transaction processing system, an information processing device, and an information processing program. [Background technology]
[0002] In recent years, so-called electronic receipt services, which allow users to view digitized receipts on information terminals such as smartphones, have become widespread. Users of these electronic receipt services can use the service by registering as users of the service. Many stores also offer store services such as point services to attract customers. Users of such store services can use the store services by registering as users of the store services. If the electronic receipt service and the store service are provided by different service providers, the user registration for each service will be done separately. A different identifier will be assigned to the same user for each service.
[0003] Therefore, a user can perform settings in advance to link the identifiers of the respective services, so that both services can be used by presenting either one of the identifiers. As an example, a membership card recording the user's identifier for a store service is distributed to the user, and if an identifier for the electronic receipt service is linked to the identifier read from the membership card during a transaction, the electronic receipt service is applied using that identifier.
[0004] In this case, the linking of the identifiers of both services is managed by a transaction management device separate from the transaction processing device that reads the identifier from the membership card, and the transaction processing device that acquires the identifier inquires about that identifier to the transaction management device and acquires the identifier for the linked electronic receipt service from the transaction management device.
[0005] For this reason, if the above inquiry cannot be performed normally due to some reason such as a communication error, the transaction processing device cannot obtain an identifier for the electronic receipt service, and the electronic receipt service cannot be applied. For these reasons, it has been desirable to be able to apply the electronic receipt service later, even if it is not possible to obtain an identifier for the electronic receipt service when processing a transaction. [Prior art documents] [Patent documents]
[0006] [Patent Document 1] Patent Publication No. 2022-60421 Summary of the Invention [Problem to be solved by the invention]
[0007] The problem to be solved by the embodiments of the present invention is to provide a transaction processing system, an information processing device, and an information processing program that enable an electronic receipt service to be applied later even in a situation where an identifier for the electronic receipt service cannot be obtained when processing a transaction. [Means for solving the problem]
[0008] A transaction processing system according to an embodiment is comprised of a receipt management device that manages transaction details and provides an electronic receipt service that enables the details to be electronically confirmed, a transaction processing device, and a transaction management device, and is equipped with a transaction processing means, an identifier acquisition means, an inquiry means, a response means, a notification means, a collection means, a generation means, a journal acquisition means, an extraction means, and a processing means. The transaction processing means processes a transaction. The identifier acquisition means acquires a first identifier of a transactor who performs a transaction to be processed by the transaction processing means. The inquiry means is provided in the transaction processing device, and inquires of the transaction management device regarding the first identifier acquired by the identifier acquisition means. In response to the inquiry by the inquiry means, if a second identifier is linked to the first identifier that is the subject of the inquiry, the response means notifies the transaction processing device of the second identifier, and if a second identifier is not linked to the first identifier that is the subject of the inquiry, notifies the transaction processing device of that effect. Each time processing by the transaction processing means is completed, if the notification means can confirm that a response has been made by the response means, the notification means notifies the transaction management device of a transaction file showing details of the completed transaction. The collection means collects the transaction files notified by the notification means. The generation means generates a journal file showing details of each of a plurality of transactions processed by the transaction processing means during a predetermined period. The journal acquisition means acquires the journal file generated by the generation means. The extraction means extracts, from among the plurality of transactions included in the journal file acquired by the journal acquisition means, a transaction that is different from the transaction related to the transaction file collected by the collection means and in which a second identifier is linked to the first identifier acquired by the identifier acquisition means. The processing means performs processing to make the transaction details extracted by the extraction means available for confirmation by an electronic receipt service. [Brief description of the drawings]
[0009] [Figure 1] FIG. 1 is a block diagram showing a schematic configuration of a transaction processing system according to an embodiment. [Diagram 2] 2 is a block diagram showing the main circuit configuration of the receipt server in FIG. 1. [Diagram 3]FIG. 2 is a block diagram showing a main circuit configuration of the head office server in FIG. 1. [Figure 4] FIG. 2 is a block diagram showing the main circuit configuration of the member server in FIG. 1. [Diagram 5] FIG. 2 is a block diagram showing a main circuit configuration of the POS terminal in FIG. [Figure 6] FIG. 2 is a block diagram showing a main circuit configuration of the conversion server in FIG. [Figure 7] FIG. 4 is a sequence diagram showing the operation of the transaction processing system for one transaction in the first case. [Figure 8] Schematic diagram showing the main items of data described in a transaction file. [Figure 9] FIG. 11 is a sequence diagram showing the operation of the transaction processing system for one transaction in the second case. [Figure 10] FIG. 11 is a sequence diagram showing the operation of the transaction processing system for one transaction in the third case. [Figure 11] FIG. 11 is a sequence diagram showing the operation of the transaction processing system for one transaction in the fourth case. [Figure 12] FIG. 11 is a sequence diagram showing the operation of the transaction processing system during recovery operation. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0010] Hereinafter, an example of an embodiment will be described with reference to the drawings. First, in this embodiment, a user who performs a transaction at a store must register as a user of the store service and obtain an identifier for the store service (hereinafter referred to as a store membership code) before using the store service provided by the store. In addition, when using an electronic receipt service for a transaction at a store, the user must register as a user of the electronic receipt service and obtain an identifier for the electronic receipt service (hereinafter referred to as a receipt membership code), and must perform settings to link the receipt membership code with the store membership code. Note that the store service is, for example, a point service that awards points in proportion to the transaction amount. The store service is not limited to a point service. The providers of the store service and the electronic receipt service are each arbitrary. In this embodiment, the store service and the electronic receipt service are each provided by different providers. The store membership code is an example of a first identifier. The receipt membership code is an example of a second identifier.
[0011] When using the electronic receipt service, a user installs dedicated application software compatible with the electronic receipt service, a so-called electronic receipt app, on an information terminal such as a smartphone or tablet computer. The user then uses the electronic receipt app to perform the above-mentioned user registration for the electronic receipt service. For example, when the electronic receipt app is launched on an information terminal, the receipt member code is displayed in the form of a machine-readable code such as a barcode or a two-dimensional code on the top screen displayed on the display device of the information terminal. Hereinafter, a user who has completed user registration for the electronic receipt service is referred to as an electronic receipt member.
[0012] When using a store service, the user installs dedicated application software corresponding to the member service, so-called store member app, on an information terminal such as a smartphone or tablet. The user then uses the store member app to perform the above-mentioned user registration for the store service. The store member code is displayed in the form of a machine-readable code such as a barcode or a two-dimensional code on a top screen displayed on a display device of an information terminal when the store member app is started on the information terminal. Alternatively, the store member code may be recorded on a member card issued to the user by the store upon user registration. The member card may be a magnetic card on which the store member code is magnetically recorded. Alternatively, the member card may be a contact or contactless IC card on which the store member code is stored in the memory of an IC (integrated circuit) chip. The member card may also be a card-shaped medium made of paper, plastic, or the like on which the store member code is printed in the form of a machine-readable code. In the following, a user who has completed user registration for a store service is referred to as a store member.
[0013] The type of store is not particularly limited. It may be a store that sells products, such as a supermarket, a convenience store, or a specialized retail store, or it may be a store that provides services, such as a barber shop, a rental shop, or a bowling alley. In short, any store may be used as long as it conducts transactions related to the sale of products or the provision of services with users who are the subjects of the transactions. It is assumed that the user will check the details of the transaction after the transaction is completed. If the transaction is a purchase or sale of products, the details of the transaction are expected to include the name and price of the item traded, the total amount of the transaction, payment information for the total amount, the date and time of the transaction, etc. In the following, an example will be described in which the transaction to be processed is the display and sale of products in a store.
[0014] In this embodiment, a system constructed for use in a multi-store company consisting of a plurality of stores and a headquarters that oversees these stores will be illustrated. [Description of Transaction Processing System 100] FIG. 1 is a block diagram showing a schematic configuration of a transaction processing system 100 according to this embodiment.
[0015] The transaction processing system 100 includes a receipt management system 10, a headquarters system 20, a store system 30, and a conversion server 40. The transaction processing system 100 is configured by enabling communication between the receipt management system 10, the headquarters system 20, and the conversion server 40 via a communication network NWA, between the headquarters system 20 and the store system 30 via a communication network NWB, and between the headquarters system 20 and the conversion server 40 via a communication network NWC. The communication networks NWA, NWB, and NWC are, for example, the Internet, an intranet, or a virtual private network (VPN). Although FIG. 1 shows the communication networks NWA, NWB, and NWC as independent networks, two or more of the communication networks may be the same network.
[0016] The receipt management system 10 is an information processing system operated by a provider of an electronic receipt service. The receipt management system 10 includes a receipt server 11. The receipt server 11 performs information processing to display a screen showing transaction details (hereinafter referred to as an electronic receipt screen) on an information terminal 200 on which an electronic receipt app is installed, and to enable an electronic receipt member to view the details. The receipt server 11 may provide a service in an on-premise environment, or may provide a service in a cloud computing environment.
[0017] The receipt server 11 accumulates and manages receipt data showing details of transactions made by electronic receipt members at stores that support the electronic receipt service. In response to a request from the information terminal 200 via the communication network NWD, the receipt server 11 transmits data for displaying an electronic receipt screen on the information terminal 200 to the information terminal 200 via the communication network NWD. In other words, the receipt server 11 is an example of a receipt management device.
[0018] The communication network NWD is a wide area network that allows data transfer between the receipt server 11 and the information terminal 200. As the communication network NWD, for example, the Internet, a mobile communication network, a public communication network, etc. can be used alone or in appropriate combination.
[0019] The headquarters system 20 is an information processing system constructed in the headquarters. The headquarters system 20 includes a headquarters server 21, a member server 22, and communication servers 23, 24, and 25. The headquarters server 21, the member server 22, and the communication servers 23, 24, and 25 can communicate with each other via a headquarters intra-network 26. The headquarters intra-network 26 is typically a LAN (local area network). Access to the headquarters intra-network 26 by the headquarters server 21, the member server 22, and the communication servers 23, 24, and 25 may be by either wired access or wireless access.
[0020] The headquarters server 21 is an information processing device that collects information related to transactions processed by the store system 30 from the store system 30 and processes the information to collectively manage multiple transactions carried out at the store. The headquarters server 21 also provides a service of appropriately generating and outputting data related to the headquarters' operations. Data related to the headquarters' operations includes, for example, sales data and loss data by store. The headquarters server 21 is an example of a transaction management device.
[0021] The member server 22 is an information processing device that processes information to manage information on users who have become store members. User information is, for example, the value of service points owned by the user. Specifically, the member server 22 accumulates points for each store member that are granted to the store member according to the amount of a transaction when the store member makes a transaction at a store. When a store member requests to exchange points, the member server 22 subtracts the requested points from the accumulated points of the store member and provides the store member with a special benefit equivalent to the points subtracted. The special benefit may be, for example, a discount on the transaction amount or the issuance of a gift certificate.
[0022] The communication server 23 is an information processing device that performs processing for communication via the communication network NWA. The communication server 24 is an information processing device that performs processing for communication via the communication network NWC. The communication server 25 is an information processing device that performs processing for communication via the communication network NWB.
[0023] The store system 30 is an information processing system installed in a store. Although only one store system 30 is shown in FIG. 1, the store system 30 is installed in each of the multiple stores. All transactions processed by these multiple store systems 30 are managed by the headquarters server 21. However, although only one headquarters system 20 is shown in FIG. 1, the transaction processing system 100 may include multiple headquarters systems 20. When the transaction processing system 100 includes multiple headquarters systems 20, each of these multiple headquarters systems 20 collectively manages transactions performed in different store groups. In other words, the multiple store systems 30 belong to one of several store groups and are associated with the headquarters system 20 corresponding to that store group. As a specific example, the multiple headquarters systems 20 are installed in multiple headquarters that respectively manage different chains. Then, the multiple store systems 30 installed in multiple stores belonging to one chain are associated with the headquarters system 20 installed in the headquarters of the chain.
[0024] The store system 30 includes a store server 31, multiple POS (point of sales) terminals 32, and a communication server 33. The store server 31, the multiple POS terminals 32, and the communication server 33 are capable of communicating with each other via an in-store network 34 provided within the store. The in-store network 34 is typically a LAN. Access to the in-store network 34 by the store server 31, the multiple POS terminals 32, and the communication server 33 may be by either wired access or wireless access.
[0025] The store server 31 is an information processing device that performs information processing to appropriately generate and output data related to the operation of the store by collecting information related to transactions processed by the POS terminals 32 from the POS terminals 32 and processing the information. The data related to the operation of the store is, for example, sales data by product, inventory data, etc.
[0026] The POS terminal 32 is an information processing device that performs information processing for processing transactions by users at a store. For example, the POS terminal 32 performs a registration process for registering a product that the user is going to purchase as a transaction product. The POS terminal 32 also performs an accounting process for calculating the price of the transaction product and settling the price. The POS terminal 32 may be a face-to-face POS terminal in which the operations related to the registration process and the operations for the accounting process are both performed by a store clerk, or may be a self-service POS terminal in which both operations are performed by the user. Alternatively, the POS terminal 32 may be a shared POS terminal in which the operations for the registration process are performed by a store clerk and the operations for the accounting process are performed by the user. The POS terminal 32 is an example of a transaction processing device. The communication server 33 is an information processing device that performs processing for communication via the communication network NWB.
[0027] The conversion server 40 is an information processing device that performs information processing to convert data included in a transaction file showing transaction details into receipt data in a format suitable for processing by the receipt server 11 in response to requests from the headquarters server 21 and the POS terminal 32. The conversion server 40 is an example of a conversion device. The conversion server 40 may provide a service in an on-premise environment, or may provide a service in a cloud computing environment.
[0028] [Description of Receipt Server 11] FIG. 2 is a block diagram showing the main circuit configuration of the receipt server 11. The receipt server 11 includes a processor 111, a main memory unit 112, an auxiliary memory unit 113, communication units 114 and 115, and a transmission path 116. The processor 111 is capable of communicating with the main memory unit 112, the auxiliary memory unit 113, the communication units 114, and the communication unit 115 via the transmission path 116.
[0029] The processor 111, main memory unit 112, and auxiliary memory unit 113 are connected via a transmission line 116 to form a computer that performs information processing to realize the functions of the receipt server 11. The processor 111 corresponds to the central part of the computer. The processor 111 executes information processing for controlling each part to realize various functions of the receipt server 11 according to information processing programs such as an operating system and application programs. The processor 111 is, for example, a CPU (central processing unit). The processor 111 is preferably a multi-core processor that includes multiple processor cores and is capable of executing multiple processes in parallel. Alternatively, the processor 111 may be configured to perform distributed processing using multiple CPUs.
[0030] The main memory unit 112 corresponds to the main memory portion of the computer. The main memory unit 112 includes a read-only memory area and a rewritable memory area. The main memory unit 112 stores the information processing program in the read-only memory area. The main memory unit 112 may store data required for the processor 111 to execute processes for controlling each part in a read-only or rewritable memory area. The main memory unit 112 uses the rewritable memory area as a work area where data is appropriately rewritten by the processor 111. The read-only memory area is, for example, a ROM (read only memory). The rewritable memory area is, for example, a RAM (random access memory).
[0031] The auxiliary storage unit 113 corresponds to the auxiliary storage portion of the computer. The auxiliary storage unit 113 may be, for example, an electronic erasable programmable read-only memory (EEPROM), a hard disk drive (HDD), a solid state drive (SSD), or any other well-known storage device. The auxiliary storage unit 113 stores data used by the processor 111 in performing various processes and data created by the processes in the processor 111. The auxiliary storage unit 113 may also store the above-mentioned application programs. In this embodiment, the auxiliary storage unit 113 stores a receipt management program PRA. The receipt management program PRA is an application program that manages electronic receipt data and describes information processing for providing an electronic receipt service using the electronic receipt data.
[0032] A part of the storage area of the auxiliary storage unit 113 is used as an area for storing the receipt file FIA and the linkage table group TGA. The receipt file FIA is a data file including multiple electronic receipt data registered as targets of the electronic receipt service. The receipt file FIA may be divided into multiple data files. The linkage table group TGA is a collection of linkage tables related to multiple store services. The linkage table is a data table for managing the linkage between the store membership code and the receipt membership code in the corresponding store service. In other words, the linkage table describes the store membership code for which the linkage has been set and the receipt membership code linked to the store membership code in association with each other. Note that, when the transaction processing system 100 includes multiple headquarters systems 20, different store services may be provided by some or all of the operators of the multiple headquarters systems 20. In such a situation where multiple store services are provided for the transaction processing system 100, multiple linkage tables are prepared for each store service, and the multiple linkage tables are included in the linkage table group TGA.
[0033] The communication unit 114 performs communication processing for data communication via the communication network NWA. As the communication unit 114, a well-known communication device that complies with the communication method of the communication network NWA can be used. The communication unit 115 performs communication processing for data communication via the communication network NWD. As the communication unit 115, a well-known communication device that complies with the communication method of the communication network NWA can be used. The transmission path 116 includes an address bus, a data bus, a control signal line, etc., and transmits data and control signals exchanged between each of the connected components.
[0034] The basic hardware of the receipt server 11 may be, for example, a general-purpose server device. The receipt server 11 is generally transferred with the receipt management program PRA stored in the auxiliary storage unit 113. However, the receipt management program PRA may be transferred separately from the hardware in a state where the receipt management program PRA is not stored in the auxiliary storage unit 113, or where a different version of the same type of application program is stored in the auxiliary storage unit 113. The receipt server 11 may be configured by writing the receipt management program PRA to the auxiliary storage unit 113 in response to the operation of an arbitrary operator. The receipt management program PRA may be transferred by recording it on a removable recording medium such as a magnetic disk, magneto-optical disk, optical disk, or semiconductor memory, or by communication via a network.
[0035] [Description of Headquarters Server 21] FIG. 3 is a block diagram showing the main circuit configuration of the head office server 21. As shown in FIG. The head office server 21 includes a processor 211, a main memory unit 212, an auxiliary memory unit 213, a communication unit 214, and a transmission path 215. The processor 211, the main memory unit 212, the auxiliary memory unit 213, and the communication unit 214 are capable of communicating with each other via the transmission path 215.
[0036] The functions of the processor 211, main memory unit 212, auxiliary memory unit 213, and transmission path 215 are generally the same as those of the processor 111, main memory unit 112, auxiliary memory unit 113, and transmission path 116, so a description thereof will be omitted. However, the auxiliary memory unit 213 stores a transaction management program PRB instead of the receipt management program PRA. The transaction management program PRB is an application program that describes the procedures for information processing for managing transactions processed by the store system 30 installed in a store included in the group of stores that are subject to centralized management. As a result, a computer configured by connecting the processor 211, main memory unit 212, and auxiliary memory unit 213 via the transmission path 215 performs information processing for managing transactions processed by the store system 30.
[0037] A part of the storage area of the auxiliary storage unit 213 is used as an area for storing the transaction file group FGA instead of the receipt file FIA and the linkage table group TGA. The transaction file group FGA represents details of the transactions to be managed, and is a collection of transaction files sent from the POS terminal 32 each time a transaction is completed, and is a collection of multiple transaction files. The communication unit 214 performs communication processing for data communication via the headquarter network 26. As the communication unit 214, a well-known communication device that complies with the communication method of the headquarter network 26 can be used.
[0038] Now, for example, a general-purpose server device can be used as the basic hardware of headquarters server 21. Headquarters server 21 is generally transferred in a state in which transaction management program PRB is stored in auxiliary storage unit 213. However, the hardware in a state in which transaction management program PRB is not stored in auxiliary storage unit 213, or in a state in which a different version of the same type of application program is stored in auxiliary storage unit 213, and the transaction management program PRB may be transferred separately. Headquarters server 21 may be configured by writing transaction management program PRB to auxiliary storage unit 213 in response to the operation of any operator. The transaction management program PRB may be transferred by recording it on a removable recording medium such as a magnetic disk, a magneto-optical disk, an optical disk, or a semiconductor memory, or by communication via a network.
[0039] [Explanation of Member Server 22] FIG. 4 is a block diagram showing the main circuit configuration of the member server 22. As shown in FIG. The member server 22 includes a processor 221, a main memory unit 222, an auxiliary memory unit 223, a communication unit 224, and a transmission path 225. The processor 221, the main memory unit 222, the auxiliary memory unit 223, and the communication unit 224 are capable of communicating with each other via the transmission path 225.
[0040] The functions of the processor 221, main memory unit 222, auxiliary memory unit 223, communication unit 224, and transmission path 225 are generally the same as those of the processor 111, main memory unit 112, auxiliary memory unit 113, communication unit 214, and transmission path 116, so a description thereof will be omitted. However, the auxiliary memory unit 223 stores a member management program PRC instead of the receipt management program PRA. The member management program PRC is an application program that describes the procedures for information processing for managing store members related to store services provided by the operator of the head office system 20 to which the member server 22 belongs. As a result, the computer configured by connecting the processor 221, main memory unit 222, and auxiliary memory unit 223 via the transmission path 225 processes information for managing store members.
[0041] In addition, a part of the storage area of the auxiliary memory unit 223 is used as an area for storing the member database DBA and the linkage table TAA instead of the receipt file FIA and the linkage table group TGA. The member database DBA is a collection of multiple data records associated with each of the store members to be managed. The data records of the member database DBA include various information regarding the associated store members, such as store member codes, personal information, or information regarding the usage status of store services. The linkage table TAA is a copy of the linkage table included in the above-mentioned linkage table group TGA, which is related to store services provided by the operator of the headquarters system 20 to which the member server 22 belongs. Thus, the auxiliary memory unit 223 is an example of a storage device that stores a store member code as a first identifier and a receipt member code as a second identifier that is preset to be linked to the store member code in association with each other.
[0042] Now, for example, a general-purpose server device can be used as the basic hardware of the member server 22. The member server 22 is generally transferred in a state in which the member management program PRC is stored in the auxiliary storage unit 223. However, the member management program PRC may be transferred separately from the hardware in a state in which the member management program PRC is not stored in the auxiliary storage unit 223, or in a state in which a different version of the same type of application program is stored in the auxiliary storage unit 223. The member server 22 may be configured by writing the member management program PRC to the auxiliary storage unit 223 in response to the operation of any operator. The member management program PRC may be transferred by recording it on a removable recording medium such as a magnetic disk, a magneto-optical disk, an optical disk, or a semiconductor memory, or by communication via a network.
[0043] [Explanation of POS terminal 32] FIG. 5 is a block diagram showing the main circuit configuration of the POS terminal 32. As shown in FIG. The POS terminal 32 includes a processor 321, a main memory unit 322, an auxiliary memory unit 323, a clock 324, a keyboard 325, a display 326, a scanner 327, a printer 328, a card reader 329, a change machine 3210, a communication unit 3211, and a transmission path 3212. The processor 321 can communicate with the main memory unit 322, the auxiliary memory unit 323, the clock 324, the keyboard 325, the display 326, the scanner 327, the printer 328, the card reader 329, the change machine 3210, and the communication unit 3211 via the transmission path 3212.
[0044] The functions of the processor 321, main memory unit 322, auxiliary memory unit 323, and transmission path 3212 are generally the same as those of the processor 111, main memory unit 112, auxiliary memory unit 113, and transmission path 116, so a detailed description will be omitted. However, the auxiliary memory unit 323 stores a transaction processing program PRD instead of the receipt management program PRA. The transaction processing program PRD is an application program that describes the information processing procedures for registration processing and accounting processing. As a result, the computer formed by connecting the processor 321, main memory unit 322, and auxiliary memory unit 323 via the transmission path 3212 processes information for transaction processing.
[0045] In addition, a part of the storage area of the auxiliary memory unit 323 is used as an area for storing the transaction data DAA and the journal file FIB instead of the receipt file FIA and the association table group TGA. The transaction data DAA indicates information such as a list of registered transaction products for a transaction being processed. The journal file FIB indicates details of all transactions processed during a predetermined period. The transaction data DAA is generated by the processor 321 for each transaction and written to the auxiliary memory unit 323. The journal file FIB is generated by the processor 321 at the first transaction of the period and written to the auxiliary memory unit 323. The journal file FIB is updated at the second and subsequent transactions of the period. The period may be appropriately determined by, for example, the creator of the transaction processing program PRD or the administrator of the POS terminal 32. In the following, the period is assumed to be one business day of the store.
[0046] The POS terminal 32 may also include other devices, such as a touch panel, a cashless payment terminal, etc. The clock 324 constantly performs a timekeeping operation and outputs date and time information indicating the date and time. The keyboard 325 includes a plurality of keys for receiving operations from an operator and inputting various specifications by the operator, such as specification of a product to be registered as a transaction product, specification of a payment method to be applied, etc. As the keyboard 325, for example, an existing input device such as that provided in another existing POS terminal can be used.
[0047] The display 326 displays various screens showing various information to be presented to the operator, such as a list showing the names and prices of registered trading products, or the amount to be settled, etc. As the display 326, an existing display device such as a liquid crystal display device can be used.
[0048] The scanner 327 reads machine-readable codes such as bar codes, two-dimensional codes, etc. As the scanner 327, an existing reading device such as a reflective device that uses infrared or laser reflection, or a device that performs image processing on an image captured by a camera can be used.
[0049] The printer 328 generates printed matter such as paper receipts by printing various images, such as a receipt image showing transaction details, onto receipt paper. The printer 328 can be any existing printing device of various types, such as a thermal type, a dot impact type, or an inkjet type. The card reader 329 reads data recorded on a card medium. As the card reader 329, existing reading devices of various types, such as a magnetic type, a contact communication type, a close-proximity wireless communication type, or a camera type, can be used.
[0050] The change machine 3210 deposits and dispenses cash. The change machine 3210 can be an existing deposit / withdrawal device that takes in currency inserted by an operator and stores it in an internal storage, and sends currency to be paid out to the operator from the storage and discharges it to the outside. The communication unit 3211 performs communication processing for data communication via the in-store network 34. As the communication unit 3211, a well-known communication device that complies with the communication method of the in-store network 34 can be used.
[0051] The basic hardware of the POS terminal 32 may be the same as that of another existing POS terminal. The transfer is performed with the transaction processing program PRD stored in auxiliary storage unit 323. However, the transaction processing program PRD may be transferred separately from the hardware in a state where the transaction processing program PRD is not stored in auxiliary storage unit 323, or where a different version of the same type of application program is stored in auxiliary storage unit 323. Then, POS terminal 32 may be configured by writing the transaction processing program PRD to auxiliary storage unit 323 in response to an operation by an arbitrary operator. The transaction processing program PRD may be transferred by recording it on a removable recording medium such as a magnetic disk, a magneto-optical disk, an optical disk, or a semiconductor memory, or by communication via a network.
[0052] [Description of Conversion Server 40] FIG. 6 is a block diagram showing the main circuit configuration of the conversion server 40. As shown in FIG. The conversion server 40 includes a processor 401, a main memory unit 402, an auxiliary memory unit 403, communication units 404 and 405, and a transmission path 406. The processor 401, the main memory unit 402, the auxiliary memory unit 403, and the communication units 404 and 405 are capable of communicating with each other via the transmission path 406.
[0053] The functions of the processor 401, main memory unit 402, auxiliary memory unit 403, communication unit 404, and transmission path 406 are generally the same as those of the processor 111, main memory unit 112, auxiliary memory unit 113, communication unit 114, and transmission path 116, so a detailed description will be omitted. However, the auxiliary memory unit 403 stores a conversion processing program PRE instead of the receipt management program PRA. The conversion processing program PRE is an application program that describes the information processing procedures for converting data contained in a transaction file into receipt data. As a result, the computer formed by connecting the processor 401, main memory unit 402, and auxiliary memory unit 403 via the transmission path 406 performs information processing for the above conversion. The communication unit 405 performs communication processing for data communication via the communication network NWC. As the communication unit 405, a well-known communication device that complies with the communication method of the communication network NWC can be used.
[0054] [Operation of transaction processing system 100] The operation of transaction processing system 100 will be explained below for several cases. In addition, there may be cases where communication between the headquarters system 20 and the store system 30 cannot be performed normally due to some circumstances, such as a failure in the communication network NWB; this state is referred to as an offline state, and a state in which the communication can be performed normally is referred to as an online state.
[0055] (First case) The first case is when a customer processes a transaction for which the electronic receipt service is applied online. In the first case, the customer has completed user registration for both the store service and the electronic receipt service, and has also completed the linking of the store membership code with the receipt membership code.
[0056] FIG. 7 is a sequence diagram showing the operation of transaction processing system 100 for one transaction in the first case. Before the processing of a transaction begins at POS terminal 32, the customer who is the transactor of the transaction presents his / her membership card to have the store membership code recorded on the membership card read by card reader 329. The action to have card reader 329 read the store membership code recorded on the membership card may be performed by the customer or by a store clerk who receives the membership card from the customer. In response, card reader 329 reads the store membership code from the membership card.
[0057] When the store membership code is read by the card reader 329 in this manner, the processor 321 proceeds to ACT 301 in the information processing based on the transaction processing program PRD. As ACT 301, the processor 321 acquires a store membership code from the card reader 329. The processor 321 then stores the acquired store membership code in the main memory unit 322 or the auxiliary memory unit 323. In this manner, the processor 321 executes information processing based on the transaction processing program PRD, and the computer with the processor 321 as its central part functions as an identifier acquisition means.
[0058] As ACT302, the processor 321 inquires of the member server 22 about the acquired store membership code. For example, the processor 321 causes the communication unit 3211 to send inquiry data in a predetermined form including the store membership code to the member server 22 via the in-store network 34. This inquiry data is transmitted to the member server 22 via the in-store network 34, the communication server 33, the communication network NWB, the communication server 25, and the headquarters network 26, and is received by the communication unit 224. Thus, the processor 321 executes information processing based on the transaction processing program PRD, and the computer with the processor 321 as its central part functions as an inquiry means.
[0059] When the inquiry data is received by the communication unit 224, the processor 221 proceeds to ACT 221 in information processing based on the member management program PRC. As ACT221, the processor 221 searches the association table TAA for the store membership code included in the inquiry data. In this first case, since the association between the store membership code and the receipt membership code has already been set, the processor 221 can find the corresponding store membership code from the association table TAA. The processor 221 then reads out the receipt membership code that is written in the association table TAA in association with the store membership code.
[0060] In ACT222, the processor 221 responds to the inquiry. For example, the processor 221 causes the communication unit 224 to send response data in a predetermined form including the receipt membership code read out as described above to the headquarters network 26, addressed to the POS terminal 32 that made the inquiry. This response data is transmitted to the POS terminal 32 that made the inquiry via the headquarters network 26, the communication server 25, the communication network NWB, the communication server 33, and the in-store network 34, and is received by the communication unit 3211. When the response data is received by the communication unit 3211, the processor 321 proceeds to ACT303. As ACT 303 , the processor 321 stores the receipt membership code included in the response data in the main memory unit 322 or the auxiliary memory unit 323 .
[0061] The operator of the POS terminal 32 performs a predetermined operation to specify one of the commodities to be traded. The operation is, for example, an operation to cause the scanner 327 to scan a barcode displayed on the commodities. The operation is, for example, pressing a key associated with the commodities among the keys included in the keyboard 325. The operation is, for example, key input of a numeric string representing the commodity code of the commodities on the keyboard 325. Once the operation is performed, the processor 321 proceeds to ACT 304.
[0062] In ACT304, the processor 321 performs a registration process. For example, the processor 321 generates transaction data DAA including the product code of the product specified as described above, and stores it in the auxiliary storage unit 323. The processor 321 then adds the product codes of products specified thereafter to the transaction data. When the start of a transaction is specified, for example, by a predetermined operation on the keyboard 325, the processor 321 proceeds to ACT305. Note that the specific process in the registration process may be the same as the process performed in another existing POS terminal, for example. If the store membership code was not obtained in ACT301, the processor 321 may obtain the store membership code during the execution of this registration process, similar to ACT301.
[0063] The processor 321 as ACT 305 calculates the price of all the traded products registered by the registration process and performs accounting processing to settle the price. The specific processing in this accounting processing may be the same as the processing performed in another existing POS terminal, for example. Thus, the processor 321 executes information processing based on the transaction processing program PRD, and the computer with the processor 321 as its central part functions as a transaction processing means.
[0064] In ACT306, processor 321 updates journal file FIB. If the transaction currently being processed is the first transaction on a business day, processor 321 generates a new journal file FIB showing details of the transaction currently being processed. If the transaction currently being processed is the second or subsequent transaction on a business day, processor 321 updates the journal file FIB already generated as described above to further show details of the transaction currently being processed. In this way, processor 321 executes information processing based on transaction processing program PRD, and the computer with processor 321 as its core portion functions as a generating means.
[0065] The processor 321 includes at least the transaction number, transaction date and time, store code, and register number in the transaction details shown in the journal file FIB. If the store membership code has been obtained, the processor 321 includes the store membership code in the transaction details shown in the journal file FIB.
[0066] The transaction number is an identifier that is generated for each transaction to individually identify the transaction processed by the POS terminal 32. The processor 321, for example, includes in the journal file FIB, as the transaction number, an identifier that is determined according to a predetermined rule so as not to overlap with the identifiers of other transactions that have already been processed.
[0067] The transaction date and time is the date and time when the target transaction is processed. The transaction date and time is, for example, the date and time when the settlement of the transaction is completed. That is, for example, when the settlement of the target transaction is completed, the processor 321 obtains the date and time data output by the clock 324, and includes this date and time data in the journal file FIB as the transaction date and time data. The transaction date and time may be any other date and time, such as the time when the transaction processing starts.
[0068] The store code is an identifier of the store in which the POS terminal 32 is installed. That is, the processor 321 includes, for example, an identifier that is predetermined so that the store in which the POS terminal 32 is installed can be distinguished from other stores and that is stored in the auxiliary storage unit 323 in advance as the store code in the journal file FIB.
[0069] The register number is an identifier of the POS terminal 32. That is, the processor 321 includes, in the journal file FIB, an identifier that is determined in advance so that the POS terminal 32 in which the processor 321 is equipped can be distinguished from other POS terminals 32 installed in the same store and that is stored in advance, for example, in the auxiliary storage unit 323, as the register number.
[0070] As ACT307, the processor 321 notifies the headquarters server 21 of the completion of the transaction. For example, the processor 321 generates a transaction file showing details related to only this transaction, and transmits notification data in a predetermined form including this transaction file from the communication unit 3211 to the in-store network 34, addressed to the headquarters server 21. In this way, the processor 321 executes information processing based on the transaction processing program PRD, and the computer with the processor 321 as its central part functions as a notification means.
[0071] FIG. 8 is a schematic diagram showing main items of data described in a transaction file. As shown in the figure, the transaction file describes data for one transaction, which are specified by the following items: transaction number, transaction date and time, store code, register number, responsible person information, purchase data, subtotal amount, tax data, total data, payment data, and store membership code. The transaction file is, for example, a data file in which the data for each of these items is described in CSV (comma separated values) format. The transaction number, transaction date and time, store code, and register number are the same as the data included in the journal file FIB.
[0072] The responsible person information describes information about the store clerk who operated the POS terminal 32 that processed the target transaction. For example, the processor 321 receives an operation for signing in by the store clerk as an operator and identifies the employee code and name as the store clerk's identifier. Then, the processor 321 includes, for example, the employee code and name thus identified in the transaction file as responsible person information.
[0073] The purchase data describes data representing the product code, product name, unit price, number of items, etc., for each of the products in the target transaction. That is, the processor 321 generates data representing each of the relevant data based on the result of the registration process for the target transaction, for example, and includes this data in the transaction file as purchase data.
[0074] The subtotal amount is the total amount excluding tax for all transaction items in the target transaction. In other words, the processor 321 includes data representing the amount in question as the subtotal amount in the transaction file, based on the results of accounting processing for the target transaction, for example.
[0075] The tax data describes data on the tax levied on the target transaction. That is, the processor 321 generates data representing the taxable amount, tax rate, tax amount, etc. for each tax category based on the results of accounting processing for the target transaction, and includes this data in the transaction file as tax data.
[0076] The total data describes the total points and total amount for all trading items in the target transaction. That is, the processor 321 counts the number of all trading items registered by the registration process for the target transaction to obtain the total points, calculates the total amount as the sum of the unit prices of those trading items, and includes the data representing the total points and total amount in the transaction file as total data.
[0077] Regarding the payment data, data indicating the payment method applied to the payment and the details of the payment are described. That is, for example, if 1000 yen is paid in cash for a total amount of 500 yen and 500 yen is paid as change, the processor 321 will include data indicating "payment method: cash, payment amount: 1000 yen, change: 500 yen" as payment data in the transaction file based on the results of accounting processing for the target transaction.
[0078] Regarding the store membership code, a store membership code for identifying the customer of the target transaction is described. That is, the processor 321 includes the store membership code acquired in ACT 301 in FIG. 7, for example, in the transaction file. Note that the items in the transaction file are not limited to those shown in Fig. 8. Other items may be added, and some of the items shown in Fig. 8 may be omitted.
[0079] This notification data is transmitted to the headquarters server 21 via the in-store network 34, the communication server 33, the communication network NWB, the communication server 25, and the headquarters network 26, and is received by the communication unit 214. When the notification data is received by the communication unit 214, the processor 211 proceeds to ACT211.
[0080] As ACT211, the processor 211 adds the transaction files included in the notification data to the transaction file group FGA. Transaction files are collected by sequentially adding the transaction files included in the notification data transmitted at each transaction completion to the transaction file group FGA. Thus, the processor 211 executes information processing based on the transaction management program PRB, and the computer with the processor 211 as the central part functions as a collection means.
[0081] In addition, when the transaction completion notification is issued, the system may be offline, and the notification data may not be transmitted to the head office server 21. In this case, the processor 321 checks whether the notification data has been received by the head office server 21, and if it is not possible to confirm that the data has been received normally, the processor 321 resends the notification data. This process may be similar to that performed in other existing POS systems, and illustrations and detailed explanations thereof will be omitted.
[0082] After notifying the completion of the transaction in ACT 307, the processor 321 in the POS terminal 32 proceeds to ACT 308. In ACT308, the processor 321 requests the conversion server 40 to convert the transaction file. For example, the processor 321 causes the communication unit 3211 to send request data in a predetermined form, including the transaction file and the receipt membership code saved in ACT303, to the in-store network 34, addressed to the conversion server 40. This request data is transmitted to the conversion server 40 via the in-store network 34, the communication server 33, the communication network NWB, the communication server 25, the headquarters network 26, the communication server 24, and the communication network NWC, and is received by the communication unit 405. When the request data is received by the communication unit 405, the processor 401 proceeds to ACT401 in information processing based on the conversion processing program PRE.
[0083] As ACT401, the processor 401 performs a conversion process to convert the transaction file into receipt data. For example, the processor 401 replaces data included in the transaction file with data suitable for display on an electronic receipt screen. As an example, the processor 401 replaces data described in the transaction file regarding a store code with text data representing the store name. The processor 401 also deletes data included in the transaction file that is not displayed on the electronic receipt screen. As an example, the processor 401 deletes a name included in the responsible person information. As an example, the processor 401 adds information that is not included in the transaction file. As an example, the processor 401 adds a receipt membership code that was included with the transaction file to the request data.
[0084] The processor 401 may inquire of the member server 22 to obtain the receipt member code linked to the store member code written in the transaction file. Alternatively, the processor 401 may inquire of the receipt server 11 to obtain the receipt member code. In addition, for example, a copy of the association table group TGA may be stored in the auxiliary storage unit 403, and the processor 401 may read the receipt member code from this copied and stored association table group TGA. If the processor 401 obtains the receipt member code in this manner, the processor 321 does not need to include the receipt member code in the request data.
[0085] In ACT402, the processor 401 requests the receipt server 11 to add a receipt. For example, the processor 401 causes the communication unit 404 to send request data in a predetermined form, including the receipt data obtained by the conversion process of ACT401, to the communication network NWA, addressed to the receipt server 11. This request data is transmitted to the receipt server 11 via the communication network NWA, and is received by the communication unit 114. When the request data is received by the communication unit 114, the processor 111 proceeds to ACT101 in information processing based on the receipt management program PRA. In ACT101, the processor 111 updates the receipt file FIA to include the receipt data included in the request data, thereby enabling the processor 111 to subsequently view a receipt screen that corresponds to the receipt data added here.
[0086] Thus, in the first case, receipt data for a transaction is added to the receipt file FIA in response to a request from the POS terminal 32 after the transaction has been processed. In this first case, the transaction file for that transaction is collected by the head office server 21, and the journal file FIB is updated to indicate details of that transaction.
[0087] (Second case) The second case is when a customer wishes to use a store service but has not set up a link between the store membership code and the receipt membership code. Fig. 9 is a sequence diagram showing the operation of transaction processing system 100 for one transaction in the second case. Note that the same operations as those in Fig. 7 are denoted by the same reference numerals, and detailed description thereof will be omitted.
[0088] ACT301, ACT302, and ACT221 are performed in the same manner as in the first case. However, because the store membership code is not linked to the receipt membership code, the processor 221 in the member server 22 cannot find the store membership code that is the subject of the inquiry from the association table TAA. In this case, the processor 221 proceeds to ACT225.
[0089] The processor 221 responds to the above inquiry as ACT 225. For example, the processor 221 causes the communication unit 224 to send response data in a form predetermined to notify that there is no linkage to the POS terminal 32 that made the inquiry, to the intra-headquarters network 26. Thus, the processor 211 executes the processing of ACT 225 and ACT 222 in Fig. 7 based on the transaction management program PRB, and the computer with the processor 211 as the central part functions as a response means.
[0090] This response data is transmitted to the POS terminal 32 that made the inquiry via the headquarters network 26, the communication server 25, the communication network NWB, the communication server 33, and the in-store network 34, and is received by the communication unit 3211. When the response data is received by the communication unit 3211, the processor 321 proceeds to a state of waiting for the designation of a product without performing ACT303. The processor 321 then performs the registration process as ACT304 and the transaction process as ACT305 in the same manner as in the first case, and proceeds to ACT311.
[0091] As ACT 311, the processor 321 issues a paper receipt showing the details of the transaction. For example, the processor 321 generates a receipt image showing the details of the transaction and commands the printer 328 to print this receipt image. In response to this command, the printer prints the receipt image on receipt paper and ejects it, thereby issuing a paper receipt.
[0092] After this, ACT306, ACT307, and ACT211 are performed in the same manner as in the first case. However, since the processor 321 has not obtained the receipt membership code, it does not request conversion as in ACT308 in Fig. 7, and ACT401, ACT402, and ACT101 are not performed.
[0093] Thus, in the second case, a paper receipt showing details of the transaction is issued by the POS terminal 32, and the receipt data is not added to the receipt file FIA. In the second case, the POS is online and the POS terminal 32 has received a normal response from the member server 22, so a transaction file relating to the transaction is collected by the head office server 21. The journal file FIB is also updated to show details of the transaction.
[0094] (Case 3) Fig. 10 is a sequence diagram showing the operation of transaction processing system 100 for one transaction in the third case. Note that the same operations as those in Fig. 7 and Fig. 9 are denoted by the same reference numerals, and detailed description thereof will be omitted. The third case is when the customer does not wish to use the store's services.
[0095] Since the customer does not wish to use the store's services, he or she does not present the membership card. The operator then begins to specify the product. For this reason, 301, ACT221, ACT222, and ACT303 in FIG. 7 are not performed. And ACT304, ACT305, ACT311, ACT306, ACT307, and ACT211 are performed in the same manner as in the first and second cases. In this third case, the processor 321 has not obtained the receipt membership code either, so it does not request conversion as ACT308 in FIG. 7, and ACT401, ACT402, and ACT101 are not performed.
[0096] Thus, in the third case, a paper receipt showing details of the transaction is issued by the POS terminal 32, and the receipt data is not added to the receipt file FIA. In the third case, the POS terminal 32 does not inquire of the member server 22, and does not confirm that the line is open, so the transaction file is collected by the head office server 21. The journal file FIB is also updated to show details of the transaction.
[0097] (Case 4) Fig. 11 is a sequence diagram showing the operation of transaction processing system 100 for one transaction in the fourth case. Note that the same operations as those in Fig. 7 and Fig. 9 are denoted by the same reference numerals, and detailed description thereof will be omitted. The fourth case is when a customer desires to apply for a store service in an offline state.
[0098] ACT301 and ACT302 are performed in the same manner as in the first case. However, since the system is offline, the inquiry data is not transmitted to the member server 22. Alternatively, the inquiry data is transmitted to the member server 22, and ACT221 and ACT222 are executed, but the response data is not transmitted to the POS terminal 32.
[0099] Therefore, even though a predetermined time has elapsed since making an inquiry in ACT302, processor 321 is unable to confirm that response data has been received, and determines that a timeout has occurred in ACT321. Processor 321 then performs ACT304, ACT305, ACT311, and ACT306 in the same manner as in the first and second cases. In this fourth case, processor 321 has not obtained the receipt membership code either, so it does not request conversion in ACT308 in Fig. 7, and ACT401, ACT402, and ACT101 are not performed. In addition, processor 321 has confirmed that it is offline, so it does not notify completion in ACT307.
[0100] Thus, in the fourth case, a paper receipt showing the details of the transaction is issued by the POS terminal 32, and the receipt data is not added to the receipt file FIA. Also, in the fourth case, the transaction file is not collected by the headquarters server 21. Also, the journal file FIB is updated to show the details of the transaction.
[0101] (Recovery action) In the second case, the electronic receipt service will not be applied to the transaction in question, despite the customer's wishes. Therefore, at a predetermined timing, such as after the store closes for one business day, the following recovery operation is performed.
[0102] FIG. 12 is a sequence diagram showing the operation of transaction processing system 100 in a recovery operation. When the above timing occurs, the processor 321 in the POS terminal 32 proceeds to ACT 321. In ACT321, the processor 321 transmits the journal file FIB to the headquarters server 21. For example, the processor 321 causes the communication unit 3211 to send transmission data of a predetermined form including the journal file FIB to the in-store network 34, addressed to the headquarters server 21. This transmission data is transmitted to the headquarters server 21 via the in-store network 34, the communication server 33, the communication network NWB, the communication server 25, and the headquarters network 26, and is received by the communication unit 214. When the transmission data is received by the communication unit 214, the processor 211 proceeds to ACT215.
[0103] As described above, the journal file FIB is newly generated for the first transaction of one business day, and is updated in any of the first to fourth cases. In other words, at the time of transmission, the journal file FIB represents details of all transactions processed by the POS terminal 32 in one business day.
[0104] The processor 211 as ACT 215 stores the journal file FIB included in the received transmission data in the main memory unit 212 or the auxiliary memory unit 213. Thus, the processor 211 executes information processing based on the transaction management program PRB, and the computer with the processor 211 as its central part functions as a journal acquisition means.
[0105] As ACT216, the processor 211 extracts all transactions that were performed in an offline state from among the transactions included in the journal file FIB. For example, the processor 211 extracts a transaction that was performed in an offline state from among the transactions included in the journal file FIB as a transaction that is different from any of the transactions related to the transaction files included in the transaction file group FGA. For example, the processor 211 selects one transaction included in the journal file FIB, and if the transaction file in which the transaction number, transaction date and time, store code, register number, and store member code included in the journal file FIB as data representing the details of the transaction are described as data related to each item of the transaction number, transaction date and time, store code, register number, and store member code is not included in the transaction file group FGA, the processor 211 determines that the transaction was performed in an offline state. The processor 211 then performs the same determination on all transactions included in the journal file FIB to extract all transactions that were performed in an offline state.
[0106] In ACT217, the processor 211 extracts transactions made by receipt members from the transactions extracted in ACT216. For example, the processor 211 selects one of the transactions extracted in ACT216, and checks, for example, with the member server 22, whether the receipt member code is linked to the store member code included in the journal file FIB as data representing the details of the transaction. If the processor 211 confirms that the receipt member code is linked, it determines that the transaction is a transaction made by a receipt member. The processor 211 then performs the same determination on all of the transactions extracted in ACT216, thereby extracting transactions made by receipt members. Note that during this process, the processor 211 acquires each of the receipt member codes that have been confirmed to be linked to the store member code.
[0107] The journal file shows details of all transactions processed in one business day. The transaction file group FGA does not include transaction files related to transactions processed in an offline state. Thus, the processor 211 extracts all transactions processed in an offline state by receipt members from among all transactions processed at the POS terminal 32 in one business day. In other words, the processor 211 extracts transactions whose receipt data is not included in the receipt file FIA, even though there is a possibility that an electronic receipt service may be applied, as transactions to be subject to subsequent computerization (hereinafter referred to as computerized transactions). Thus, the processor 211 executes information processing based on the transaction management program PRB, and the computer with the processor 211 as its central part functions as an extraction means.
[0108] In ACT218, the processor 211 requests the conversion server 40 to convert the transaction files for each of the electronic transactions. For example, the processor 321 extracts data for each item of the transaction file from the details shown in the journal file for each of the electronic transactions, and generates a transaction file for each electronic transaction. The processor 211 then causes the communication unit 214 to send request data in a predetermined form including all of these transaction files to the intra-headquarters network 26, addressed to the conversion server 40. The processor 211 includes in the request data, in association with each of the transaction files, the receipt member code found in ACT217 for the transaction related to that transaction file.
[0109] This request data is transmitted to the conversion server 40 via the headquarters network 26, the communication server 24, and the communication network NWC, and is received by the communication unit 405. When the request data is received by the communication unit 405, the processor 401 proceeds to ACT 411 in information processing based on the conversion processing program PRE.
[0110] As ACT411, the processor 401 performs conversion processing similar to that of ACT401 on the transaction files relating to each electronic transaction, converting them into receipt data for each electronic transaction.
[0111] In ACT 412, the processor 401 requests the receipt server 11 to add a receipt for the electronic transaction. For example, the processor 401 causes the communication unit 404 to send request data in a predetermined form that includes all receipt data obtained for each electronic transaction by the conversion process of ACT 401 to the communication network NWA, addressed to the receipt server 11. This request data is transmitted to the receipt server 11 via the communication network NWA, and is received by the communication unit 114. When the request data is received by the communication unit 114, the processor 111 proceeds to ACT 111 in information processing based on the receipt management program PRA.
[0112] In ACT111, the processor 111 updates the receipt file FIA to include each receipt data included in the request data, thereby enabling the processor 111 to subsequently view a receipt screen corresponding to each receipt data added here. In other words, the processor 211 makes a request as ACT 218 to enable details of electronic transactions to be confirmed by the electronic receipt service. Thus, the processor 211 executes information processing based on the transaction management program PRB, and the computer with the processor 211 as its central part functions as a processing means.
[0113] As described above, in transaction processing system 100, head office server 21 collects transaction files related to transactions that have already been processed, but does not collect transaction files related to transactions processed in an offline state. In addition, POS terminal 32 generates a journal file showing details of all transactions processed in one business day and sends it to head office server 21. Head office server 21 identifies digitized transactions as transactions processed in an offline state as the difference between the transactions included in the journal file and the transactions related to the collected transaction file, and adds the receipt data related to the digitized transaction to the electronic receipt service.
[0114] As a result, even if a receipt membership code cannot be obtained when processing a transaction due to an offline state and the electronic receipt service cannot be applied at the end of the processing of the transaction, the electronic receipt service can be applied later.
[0115] This embodiment can be modified in various ways as follows. The association table TAA may be stored in a storage device provided in the headquarters server 21, the store server 31, or any other information processing device, and the processor 321 may obtain the receipt membership code by querying the processor provided in the device.
[0116] The receipt data may be generated by the processor 321 in the POS terminal 32. In response to a request from the POS terminal 32, the receipt data may be generated by the store server 31 or any information processing device provided in the store system 30.
[0117] The processor 211 in the head office server 21 may generate the receipt data.
[0118] In response to a request from the head office server 21, receipt data may be generated by any information processing device provided in the head office system 20.
[0119] Although some embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be implemented in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their modifications are included in the scope and spirit of the invention, and are included in the scope of the invention and its equivalents described in the claims. [Explanation of symbols]
[0120] 10... receipt management system, 11... receipt server, 20... headquarters system, 21... headquarters server, 22... member server, 23, 24, 25, 33... communication server, 26... headquarters network, 30... store system, 31... store server, 32... POS terminal, 34... store network, 40... conversion server, 100... transaction processing system, 111, 211, 221, 321, 401... processor, 112, 212, 222 ,322,402...main memory unit, 113,213,223,323,403...auxiliary memory unit, 114,115,214,224,404,405,3211...communication unit, 116,215,225,406,3212...transmission path, 200...information terminal, 324...clock, 325...keyboard, 326...display, 327...scanner, 328...printer, 329...card reader, 3210...change machine.
Claims
1. A transaction processing system comprising a receipt management device that manages transaction details and provides an electronic receipt service that enables the details to be electronically confirmed, a transaction processing device, and a transaction management device, a transaction processing means provided in the transaction processing device for processing a transaction; an identifier acquisition means provided in the transaction processing device, for acquiring a first identifier of a trader who performs a transaction to be processed by the transaction processing means; a query means provided in the transaction processing device for querying the transaction management device regarding the first identifier acquired by the identifier acquisition means; a response means provided in the transaction management device, which, in response to an inquiry by the inquiry means, notifies the transaction processing device of the second identifier if a second identifier is linked to the first identifier that is the subject of the inquiry, and notifies the transaction processing device of that fact if a second identifier is not linked to the first identifier that is the subject of the inquiry; a notification means provided in the transaction processing device, for notifying the transaction management device of a transaction file showing details of the completed transaction each time a process by the transaction processing means is completed if it is confirmed that a response has been made by the response means; a collection means provided in the transaction management device for collecting transaction files notified by the notification means; a generating means provided in the transaction processing device for generating a journal file showing details of each of a plurality of transactions processed by the transaction processing means during a predetermined period; a journal acquisition means provided in the transaction management device and configured to acquire the journal file generated by the generation means; an extraction means provided in the transaction management device for extracting, from among a plurality of transactions included in the journal file acquired by the journal acquisition means, a transaction that differs from a transaction related to the transaction file collected by the collection means and that has a second identifier linked to a first identifier acquired by the identifier acquisition means; a processing means provided in the transaction management device, for performing processing to enable the transaction details extracted by the extraction means to be confirmed by the electronic receipt service; A transaction processing system comprising:
2. a conversion device that converts the format of the data included in the journal file into a predetermined format that enables the receipt management device to electronically confirm transaction details, and then transmits the converted data to the receipt management device; said processing means transmits data representing transaction details included in a journal file and extracted by said extraction means to said conversion device; 2. The transaction processing system of claim 1.
3. The first identifier is an identifier for identifying a user of a store where a transaction is performed, the second identifier is an identifier for identifying a user of the electronic receipt service, the response means determines that the second identifier is linked to the first identifier that is the subject of the query by the query means when the second identifier is stored in a storage device that stores a first identifier and a second identifier that is preset to be linked to the first identifier in association with each other and the second identifier is stored in the storage device in association with the first identifier that is the subject of the query by the query means; 2. The transaction processing system of claim 1.
4. the notification means includes in a transaction file a transaction identifier for identifying the completed transaction, a store identifier for identifying the store where the completed transaction was made, a device identifier for identifying the transaction processing device that processes the completed transaction, a first identifier for the completed transaction acquired by the identifier acquisition means, and timing information that indicates the timing at which the completed transaction was processed by the transaction processing device; the generating means includes in a journal file, for each of a plurality of transactions, a transaction identifier for identifying the transaction, a store identifier for identifying the store where the transaction was made, a device identifier for identifying the transaction processing device that processes the transaction, a first identifier acquired by the identifier acquiring means for the transaction, and timing information indicating the timing at which the transaction was processed by the transaction processing device; When a transaction identifier, a store identifier, a device identifier, a first identifier, and timing information contained in a journal file relating to a transaction do not match any of the information contained in any of the transaction files collected by the collection means, the extraction means determines that the transaction is different from the transaction relating to the transaction file collected by the collection means.
2. The transaction processing system of claim 1.
5. a receipt management device that manages transaction details and provides an electronic receipt service that enables the details to be electronically confirmed; A transaction management device; transaction processing means for processing the transaction; an identifier acquiring means for acquiring a first identifier of a trader who performs a transaction to be processed by the transaction processing means; a query means for querying a transaction management device regarding the first identifier acquired by the identifier acquisition means; a notification means for notifying the transaction management device of a transaction file showing details of the completed transaction if it has been confirmed that a response to the inquiry made by the inquiry means has been made each time the transaction processing means completes processing; and a generating means for generating a journal file showing details of each of a plurality of transactions processed by the transaction processing means during a predetermined period; a transaction processing device comprising: An information processing device used as the transaction management device in a transaction processing system comprising: a response means for, in response to the inquiry by said inquiry means, notifying said transaction processing device of said second identifier if a second identifier is linked to the first identifier that is the subject of the inquiry, and for notifying said transaction processing device of that effect if a second identifier is not linked to the first identifier that is the subject of the inquiry; a collection means for collecting the transaction file notified by the notification means; a journal acquisition means for acquiring the journal file generated by the generation means; an extraction means for extracting, from among a plurality of transactions included in the journal file acquired by the journal acquisition means, a transaction that is different from a transaction related to the transaction file collected by the collection means and in which a second identifier is linked to a first identifier acquired by the identifier acquisition means; a processing means for performing processing to enable the transaction details extracted by the extraction means to be confirmed by the electronic receipt service; An information processing device comprising:
6. a receipt management device that manages transaction details and provides an electronic receipt service that enables the details to be electronically confirmed; A transaction management device; transaction processing means for processing the transaction; an identifier acquiring means for acquiring a first identifier of a trader who performs a transaction to be processed by the transaction processing means; a query means for querying a transaction management device regarding the first identifier acquired by the identifier acquisition means; a notification means for notifying the transaction management device of a transaction file showing details of the completed transaction if it has been confirmed that a response to the inquiry made by the inquiry means has been made each time the transaction processing means completes processing; and a generating means for generating a journal file showing details of each of a plurality of transactions processed by the transaction processing means during a predetermined period; a transaction processing device comprising: A computer provided in an information processing device used as the transaction management device in a transaction processing system comprising: a response means for, in response to the inquiry by said inquiry means, notifying said transaction processing device of said second identifier if a second identifier is linked to the first identifier that is the subject of the inquiry, and for notifying said transaction processing device of that effect if a second identifier is not linked to the first identifier that is the subject of the inquiry; a collection means for collecting the transaction file notified by the notification means; a journal acquisition means for acquiring the journal file generated by the generation means; an extraction means for extracting, from among a plurality of transactions included in the journal file acquired by the journal acquisition means, a transaction that is different from a transaction related to the transaction file collected by the collection means and in which a second identifier is linked to a first identifier acquired by the identifier acquisition means; a processing means for performing processing to enable the transaction details extracted by the extraction means to be confirmed by the electronic receipt service; An information processing program that enables the system to function as such.
Citation Information
Patent Citations
Electronic cash transaction processing system
JP1999306438A
Information processing device, printing controller, server device, and program
JP2016053844A
Electronic receipt and program of the same, as well as electronic receipt system
JP2018206254A
Transaction data processing device, program and transaction data processing method
JP2020095739A
Merchandise sales data processing device and program
JP2022060421A