Transaction processing system, input processing device, settlement device and program

Abstract

To provide a transaction processing system of semi-self type that prevents settlement from being delayed due to an accounting machine at the destination of transmission that has gone down.SOLUTION: An input processing device transmits settlement information to a destination settlement device among three or more settlement devices that has been set as being the destination of transmission. The input processing device verifies the state of the destination settlement device. A settlement device notifies the input processing device about the state verification of the destination settlement device. When the result of having verified the state of the destination settlement device that was responded for this notification from the input processing device satisfies a condition for a change of transmission destination of settlement information, the settlement device notifies the input processing device of the change of transmission destination. The input processing device changes the transmission destination of settlement information when the change of transmission destination is notified from the settlement device.SELECTED DRAWING: Figure 27

Description

[Technical field]

[0001] An embodiment of the present invention relates to a transaction processing system, an input processing device and a settlement device of the system, and respective programs of the input processing device and the settlement device. [Background technology]

[0002] In recent years, semi-self-service transaction processing systems have become known as transaction processing systems for mass retailers. This type of transaction processing system separates an input processing device that inputs and registers data on the products to be bought and sold for each transaction, from a payment device that executes payment processing for the transaction based on the data registered by the input processing device. The system is arranged so that a store clerk operates the input processing device and a customer operates the payment device.

[0003] In a semi-self-service transaction processing system, the time required for data input is shorter than in a full-self-service transaction processing system in which the customer inputs the product data by himself / herself, because the customer operates the payment device. On the other hand, it is expected that customers who are not familiar with the operation will have difficulty in making a payment because the customer operates the payment device. Therefore, a semi-self-service transaction processing system generally has, for example, three or more payment devices for one input processing device. The three or more payment devices have a transfer order of payment information set in advance.

[0004] The input processing device transmits information necessary for settlement of the transaction to the payment device (first payment device) that is first in the transfer order. If the first payment device has already completed the payment of the previous customer and is able to process the payment, it processes the payment of the transaction based on that information. If the payment of the previous customer is still in progress and payment processing is not possible, the first payment device transmits information necessary for settlement of the transaction to the payment device (second payment device) that is second in the transfer order. The second payment device processes the payment of the transaction based on the information received from the first payment device. If the second payment device is also unable to process the payment, the second payment device transmits information necessary for settlement of the transaction to the payment device (third payment device) that is third in the transfer order. The third payment device processes the payment of the transaction based on the information received from the second payment device. In this way, conventional semi-self-service type transaction processing systems efficiently operate three or more payment devices to enable the settlement of many transactions in a short period of time.

[0005] However, the destination to which the input processing device transmits the information necessary for the settlement of a transaction is limited to the first payment device. Therefore, if the first payment device goes down and is unable to receive the information necessary for the settlement of a transaction, not only the first payment device but also the second or third payment device will be unable to process the settlement of the transaction, resulting in a problem of delay in settlement. [Prior art documents] [Patent documents]

[0006] [Patent Document 1] JP 2013-242839 A 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 that can prevent settlement delays. [Means for solving the problem]

[0008] In one embodiment, the transaction processing system includes an input processing device that creates payment information necessary for settlement of a transaction with a customer based on input data, and three or more payment devices that execute settlement processing of the transaction based on the payment information. A transfer order of the payment information is set for each of the three or more payment devices. The input processing device includes a transmission means, a status confirmation means, and a change means. The transmission means transmits the payment information to a destination payment device set as a destination among the three or more payment devices. The status confirmation means confirms the status of the destination payment device. When the change means receives a notification of a destination change from another payment device other than the destination payment device, it changes the destination of the payment information to the other payment device. The three or more payment devices include a confirmation notification means and a change notification means. The confirmation notification means notifies the input processing device of the status confirmation of the destination payment device. When the status confirmation result of the destination payment device, which is responded to by the input processing device in response to the notification of the status confirmation from the input processing device, satisfies a destination change condition for the payment information, the change notification means notifies the input processing device of the destination change. [Brief description of the drawings]

[0009] [Figure 1] FIG. 1 is a schematic diagram showing a schematic configuration of a transaction processing system according to a first embodiment. [Diagram 2] FIG. 2 is a block diagram showing the main circuit configuration of the registration machine. [Diagram 3] FIG. 3 is a block diagram showing the main circuit configuration of the accounting machine. [Figure 4] FIG. 4 is a schematic diagram showing the data structure of the connection state table. [Diagram 5] FIG. 5 is a schematic diagram showing the accounting machine status flags of the register machine. [Figure 6] FIG. 6 is a flowchart showing a first information processing procedure executed by the processor of the registration machine. [Figure 7] FIG. 7 is a flowchart showing a first information processing procedure executed by the processor of the registration machine. [Figure 8] FIG. 8 is a flowchart showing a fourth information processing procedure executed by the processor of the first payment machine. [Figure 9] FIG. 9 is a flowchart showing the procedure of the fifth information processing executed by the processor of the second payment machine. [Figure 10] FIG. 10 is a flowchart showing a sixth information processing procedure executed by the processors of the first and second payment machines. [Figure 11] FIG. 11 is a flowchart showing the procedure of the second information processing executed by the processor of the registration machine. [Figure 12] FIG. 12 is a flowchart showing the seventh information processing procedure executed by the processors of the first and second payment machines. [Figure 13] FIG. 13 is a flowchart showing a third information processing procedure executed by the processor of the registration machine. [Figure 14] FIG. 14 is a sequence diagram of commands exchanged between the registration machine and the first and second payment machines. [Figure 15] FIG. 15 is a sequence diagram of commands exchanged between the registration machine and the first and second payment machines. [Figure 16] FIG. 16 is a sequence diagram of commands exchanged between the registration machine and the first and second payment machines. [Figure 17] FIG. 17 is a conceptual diagram of a transaction processing system according to the second embodiment. [Figure 18] FIG. 18 is a schematic diagram showing the data structure of the connection state table. [Figure 19] FIG. 19 is a sequence diagram of commands exchanged between the first and second registration machines and the first, second and third payment machines. [Figure 20] FIG. 20 is a conceptual diagram of a transaction processing system according to the third embodiment. [Figure 21] FIG. 21 is a schematic diagram showing the data structure of the connection state table. [Figure 22] FIG. 22 is a schematic diagram showing the data structure of the checkout machine status table. [Figure 23] FIG. 23 is a flowchart showing the main steps of the first information processing executed by the processor of the registration machine. [Figure 24]FIG. 24 is a flowchart showing the procedure of the second information processing executed by the processor of the registration machine. [Diagram 25] FIG. 25 is a flow chart showing the seventh information processing procedure executed by the processor of the payment machine. [Figure 26] FIG. 26 is a flowchart showing the procedure of the third information processing executed by the processor 31 of the registration machine. [Figure 27] FIG. 27 is a sequence diagram of commands exchanged between the registration machine and the first, second, third and fourth payment machines. [Figure 28] FIG. 28 is a sequence diagram of commands exchanged between the registration machine and the first, second, third and fourth payment machines. [Figure 29] FIG. 29 is a sequence diagram of commands exchanged between the registration machine and the first, second, third and fourth payment machines. [Diagram 30] FIG. 30 is a sequence diagram of commands exchanged between the registration machine and the first, second, third and fourth payment machines. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] Hereinafter, an embodiment of a semi-self-service type transaction processing system will be described with reference to the drawings. The semi-self-service type transaction processing system includes an input processing device and multiple payment devices. The input processing device is a device for inputting data on the products to be bought and sold in each transaction and registering the product sales data. The payment device is a device for acquiring payment information required for the settlement of the transaction, including the product sales data, from the input processing device and executing the settlement process of the transaction based on the payment information. In the following embodiments, the input processing device is referred to as a registration machine and the payment device is referred to as a checkout machine.

[0011] (First embodiment) [Transaction processing system configuration] The configuration of transaction processing system 100 according to the first embodiment will be described with reference to Figures 1 to 5. Note that the configuration described below is an example. As long as the same effect can be achieved, part of the configuration can be modified as appropriate.

[0012] 1 is a schematic diagram showing the general configuration of a transaction processing system 100. The transaction processing system 100 includes a registration machine 11, an accounting machine 12, a server 13, and a network 14 connecting these. There are no particular limitations on the type of network 14, but a wired or wireless LAN (local area network) is generally used.

[0013] The registration machine 11 is operated by a store clerk 21 who plays a role called a checker. The payment machine 12 is operated by a consumer who purchases products at the store, a so-called customer 22. In FIG. 1, the registration machine 11 is attached to a work table 23. The work table 23 has a rectangular top. A number of work tables 23 are arranged so that the longitudinal directions of the tops are approximately parallel to each other, thereby forming a passage for the customers 22, a so-called checkout lane.

[0014] The registration machine 11 and the payment machine 12 are arranged for each checkout lane in the store. For each checkout lane, one registration machine 11 and multiple payment machines 12 are arranged. Various data signals are exchanged between the registration machine 11 and the payment machine 12 arranged in the same checkout lane via the network 14. The data signals may be exchanged via the server 13 or may not be exchanged via the server 13.

[0015] FIG. 1 shows an example in which two registration machines 11 (11-1, 11-2) and four accounting machines 12 (12-1, 12-2, 12-3, 12-4) are arranged for two checkout lanes. One of the two registration machines 11, registration machine 11-1, forms a group with two of the four accounting machines 12, accounting machine 12-1 and accounting machine 12-2. The other registration machine 11-2 forms a group with the remaining two, accounting machine 12-3 and accounting machine 12-4. Each accounting machine 12 performs payment processing for transactions processed by a registration machine 11 in the same group. That is, payment machine 12-1 and payment machine 12-2 perform payment processing for transactions processed by registration machine 11-1. Payment machine 12-3 and payment machine 12-4 perform payment processing for transactions processed by registration machine 11-2. The payment processing of transactions does not differ between groups. Therefore, the following explanation will focus on the group consisting of one registration machine 11-1 and two payment machines 12-1 and 12-2. The explanation of the group consisting of the other registration machine 11-2 and the other two payment machines 12-3 and 12-4 will be omitted here because it would be redundant.

[0016] The server 13 includes a product master file 15. The product master file 15 may be stored in a storage device built into the server 13, or may be stored in a storage device externally connected to the server 13.

[0017] The product master file 15 is a data file that stores a product record created for each product sold in the store. The product record is a data record that describes product data such as the product code, product name, unit price, attributes, etc.

[0018] The product code is a unique code set for each product to identify the product. Usually, each product is provided with a barcode or two-dimensional code representing the product code. Alternatively, a radio frequency identification (RFID) tag storing the product code may be provided. The registration machine 11 can input the product code of the product being bought and sold in a transaction by reading the barcode, two-dimensional code, or RFID tag provided on the product with a reading device.

[0019] The product name and unit price are the name of the product identified by the product code and the price per item. The attribute is, for example, information about the tax on the product. Information about taxes includes tax rate, tax type (tax excluded, tax included, tax exempt), etc.

[0020] 2 is a block diagram showing the main circuit configuration of the registration machine 11-1. The registration machine 11-1 includes a processor 31, a main memory 32, an auxiliary storage device 33, a clock 34, a communication unit 35, a keyboard 36, a scanner 37, a touch panel 38, a customer display 39, a printer 40, and a system transmission path 41. The system transmission path 41 includes an address bus, a data bus, a control signal line, and the like. The system transmission path 41 connects the processor 31 to each of the other parts directly or via a signal input / output circuit, and transmits data signals exchanged between them.

[0021] The registration machine 11-1 constitutes a computer by connecting the processor 31, the main memory 32, the auxiliary storage device 33, the clock 34, and the communication unit 35 via a system transmission line 41. The registration machine 11-1 also connects devices such as a keyboard 36, a scanner 37, a touch panel 38, a customer display 39, and a printer 40 to the computer via the system transmission line 41.

[0022] The processor 31 corresponds to the central part of the computer. The processor 31 controls each part to realize various functions of the registration machine 11-1 according to an operating system or an application program. The processor 31 is, for example, a CPU (Central Processing Unit).

[0023] The main memory 32 corresponds to the main storage portion of the computer. The main memory 32 includes a nonvolatile memory area and a volatile memory area. The main memory 32 stores an operating system or an application program in the nonvolatile memory area. The main memory 32 may store data required for the processor 31 to execute processes for controlling each part in the nonvolatile or volatile memory area. The main memory 32 uses the volatile memory area as a work area where data is appropriately rewritten by the processor 31. The nonvolatile memory area is, for example, a ROM (Read Only Memory). The volatile memory area is, for example, a RAM (Random Access Memory).

[0024] The auxiliary storage device 33 corresponds to the auxiliary storage portion of the computer. For example, an EEPROM (Electric Erasable Programmable Read-Only Memory), an HDD (Hard Disk Drive), or an SSD (Solid State Drive) can be the auxiliary storage device 33. The auxiliary storage device 33 stores data used by the processor 31 when performing various processes, data created by the processes in the processor 31, etc. The auxiliary storage device 33 may also store the above application programs.

[0025] The clock 34 keeps track of the date and time. The processor 31 processes the date and time kept by the clock 34 as the current date and time.

[0026] The communication unit 35 performs data communication between the server 13 and the payment machines 12-1 and 12-2 of the same group, which are connected via the network 14. The communication unit 35 can also perform data communication between the registration machine 11-2, the payment machine 12-3, or the payment machine 12-4 of another group, which are connected via the network 14.

[0027] The keyboard 36 is an input device on which various keys necessary for inputting data relating to the product to be purchased by the customer are arranged.

[0028] The scanner 37 is an example of a reading device capable of reading code symbols such as bar codes, two-dimensional codes, etc. The scanner 37 may be of a type that reads code symbols by scanning with laser light, or of a type that reads code symbols from images captured by an imaging device.

[0029] The touch panel 38 is a device that combines an input device and a display device, and displays information to a store clerk who is an operator of the registration device 11-1, and receives operational inputs from the store clerk.

[0030] The customer display 39 displays information to the customer 22 whose purchase data is registered in the registration machine 11-1.

[0031] The printer 40 issues receipts by printing various characters or images on receipt paper. This type of printer 40 may be, for example, a thermal printer or a dot matrix printer.

[0032] For example, an existing POS terminal can be used as the hardware of the registration machine 11-1. The devices connected to the registration machine 11-1 are not limited to the keyboard 36, scanner 37, touch panel 38, customer display 39, and printer 40 shown in Fig. 2. Devices required for the purpose of the registration machine 11-1 may be added, or some devices may be omitted.

[0033] In the registration machine 11-1 configured as above, the processor 31 has the functions of creation means 311, transmission means 312, status confirmation means 313, change means 314, and recovery means 315. The creation means 311 has a function of creating payment information necessary for settling a transaction with the customer 22 based on product-related data input via a reading device or input device. The transmission means 312 has a function of transmitting the payment information to one of the two payment machines 12-1, 12-2 that is set as the destination.

[0034] The settlement information includes items such as a transaction number, transaction date and time, terminal ID, product sales data, total number of items, and total amount. The transaction number is a consecutive number that is issued for each transaction to identify each transaction with the customer 22. The transaction date and time is the date and time when the transaction was performed. The terminal ID is identification information set in the registration machine 11-1 that processed the transaction. A unique terminal ID is set in advance in each registration machine 11 (11-1, 11-2, ...). Incidentally, a unique terminal ID is also set in each accounting machine 12 (12-1, 12-2, 12-3, 12-4, ...). The product sales data includes items such as the product code, product name, unit price, sales number, sales amount, and attributes of the product purchased by the customer 22. The settlement information includes the product sales data of all the products purchased by the customer 22 in the transaction. The total number of items is the total value of the sales points of the product sales data in one transaction. The total amount is the total amount of the sales amounts of the product sales data in one transaction.

[0035] Such payment information is uniquely identified by the transaction number, transaction date and time, and terminal ID. In other words, the transaction number, transaction date and time, and terminal ID function as transaction identification information that can identify the payment information. Note that the transaction identification information is not limited to the transaction number, transaction date and time, and terminal ID. As long as the payment information can be identified, other items may be added, or some items may be omitted. Furthermore, the data structure of the payment information is not limited to the above items. Other items may be added, or some items may be omitted.

[0036] The status confirmation means 313 is a function that confirms the status of one of the two payment machines 12-1, 12-2 that is set as the destination. The change means 314 is a function that, upon receiving a notification of a change of destination from the other payment machine of the two payment machines 12-1, 12-2 that is not set as the destination, changes the destination of the payment information to the other payment machine. The restoration means 315 is a function that, upon receiving a notification of a change of destination from one of the payment machines that is set as the destination, returns the destination of the payment information to that payment machine.

[0037] The functions of the creation means 311, the transmission means 312, the status confirmation means 313, the change means 314 and the recovery means 315 are all realized by first information processing, second information processing and third information processing executed by the processor 31 in accordance with the registered program. The first information processing, second information processing and third information processing will be described later.

[0038] The registered program is a type of application program stored in the main memory 32 or the auxiliary storage device 33. There is no particular limitation on the method for installing the registered program in the main memory 32 or the auxiliary storage device 33. The registered program can be recorded on a removable recording medium, or distributed by communication via the network 14, and installed in the main memory 32 or the auxiliary storage device 33. The recording medium may be in any form, such as a CD-ROM or memory card, as long as it can store a program and is readable by the device.

[0039] Figure 3 is a block diagram showing the main circuit configuration of the payment machine 12. One payment machine 12-1 and the other payment machine 12-2 have the same configuration. Therefore, in Figure 3, one payment machine 12-1 and the other payment machine 12-2 will not be distinguished from each other and will be described as the payment machine 12.

[0040] The accounting machine 12 includes a processor 51, a main memory 52, an auxiliary storage device 53, a clock 54, a communication unit 55, a change machine interface 56, a scanner 57, a touch panel 58, a printer 59, a reader / writer 60, a signal lamp 61, and a system transmission path 62. The system transmission path 62 includes an address bus, a data bus, a control signal line, etc. The system transmission path 62 connects the processor 51 to each of the other components directly or via a signal input / output circuit, and transmits data signals exchanged between them.

[0041] The accounting machine 12 constitutes a computer by connecting the processor 51, main memory 52, auxiliary storage device 53, clock 54, and communication unit 55 via a system transmission path 62. The accounting machine 12 also connects device interfaces or devices, such as a change machine interface 56, scanner 57, touch panel 58, printer 59, reader / writer 60, and patrol lamp 61, to the computer via the system transmission path 62.

[0042] The processor 51 corresponds to the central part of the computer. The processor 51 controls each part to realize various functions of the payment machine 12 according to an operating system or an application program. The processor 51 is, for example, a CPU.

[0043] The main memory 52 corresponds to the main storage portion of the computer. The main memory 52 includes a nonvolatile memory area and a volatile memory area. The main memory 52 stores an operating system or an application program in the nonvolatile memory area. The main memory 52 may store data required for the processor 51 to execute processes for controlling each part in the nonvolatile or volatile memory area. The main memory 52 uses the volatile memory area as a work area where data is appropriately rewritten by the processor 51. The nonvolatile memory area is, for example, a ROM. The volatile memory area is, for example, a RAM.

[0044] The auxiliary storage device 53 corresponds to the auxiliary storage portion of the computer. For example, an EEPROM, a HDD, or an SSD can be the auxiliary storage device 53. The auxiliary storage device 53 stores data used by the processor 51 when performing various processes, data created by the processes in the processor 51, etc. The auxiliary storage device 53 may also store the above-mentioned application programs.

[0045] The clock 54 keeps track of the date and time. The processor 51 processes the date and time kept by the clock 54 as the current date and time.

[0046] The communication unit 55 performs data communication with the server 13 connected via the network 14 or with the registration machine 11-1 in the same checkout lane. The communication unit 55 can also perform data communication with the registration machine 11-2 or the payment machines 12-3 and 12-4 of another group connected via the network 14.

[0047] The change machine interface 56 constitutes an interface with an automatic change machine (not shown). The change machine interface 56 inputs amount data of the currency inserted into the automatic change machine from the automatic change machine. The change machine interface 56 outputs change data from the accounting machine 12 to the automatic change machine. Having input the change data, the automatic change machine automatically pays out currency equivalent to the change data as change.

[0048] The scanner 57 is an example of a reading device that reads code symbols such as bar codes, two-dimensional codes, etc. The scanner 57 may be a type that reads code symbols by scanning with laser light, or a type that reads code symbols from images captured by an imaging device.

[0049] The touch panel 58 is a device that combines an input device and a display device. The touch panel 58 displays information to the customer 22 who is the operator of the payment machine 12, and accepts operational inputs by the customer 22.

[0050] The printer 59 issues receipts by printing various characters or images on receipt paper. As this type of printer 59, for example, a thermal printer or a dot matrix printer can be used.

[0051] The reader / writer 60 has a function of reading data recorded on a medium such as a card or a smartphone, and a function of writing data to the above-mentioned medium. Cards may include payment cards such as credit cards, debit cards, electronic money cards, and prepaid cards, as well as membership cards such as member's cards and point cards. The reader / writer 60 may be a magnetic, contact, or non-contact device, or may include multiple types of devices.

[0052] The patrol lamp 61 has light-emitting bodies of two colors, for example, red and blue. The patrol lamp 61 is provided on the top of a pole that is erected in the vicinity of the payment machine 12 in correspondence with the payment machine 12, and lights up or flashes, for example, in red or blue, depending on the status of the corresponding payment machine 12.

[0053] As the hardware for such a payment machine 12, for example, a POS terminal in an existing full-self-service transaction processing system, a so-called self-checkout register, can be used. Note that the devices connected to the payment machine 12 are not limited to the scanner 57, touch panel 58, printer 59, reader / writer 60, and patrol lamp 61 shown in Fig. 3. Devices required for the purpose of the payment machine 12 may be added, or some devices may be omitted.

[0054] In the payment machine 12 configured as above, the processor 51 has the functions of a settlement means 511, a confirmation notification means 512, and a change notification means 513. The settlement means 511 is a function that executes settlement processing based on the settlement information.

[0055] The confirmation notification means 512 is a function that notifies the registration machine 11-1 that is part of the same group of the status confirmation of the payment machine 12. For example, after the system is started up, the processor 51 periodically notifies the registration machine 11-1 of the status confirmation of the payment machine 12 at the monitoring time interval set in the monitoring timer. For example, the processor 51 may notify the registration machine 11-1 of the status confirmation of the payment machine 12 when the settlement process of the transaction is completed.

[0056] The change notification means 513 is a function that notifies the register 11-1 of a change in destination if the result of the status check of the payment machine 12, which is returned from the register 11-1 in response to the status check notification, satisfies the conditions for changing the destination of the payment information. The conditions for changing the destination will be described later.

[0057] The functions of the payment means 511, the confirmation notification means 512 and the change notification means 513 are all realized by a fourth information process, a fifth information process, a sixth information process and a seventh information process executed by the processor 51 in accordance with the payment program. The fourth to seventh information processes will be described later.

[0058] The payment program is a type of application program stored in main memory 52 or auxiliary storage device 53. There is no particular limitation on the method of installing the payment program in main memory 52 or auxiliary storage device 53. The payment program can be recorded on a removable recording medium, or distributed by communication via network 14, and installed in main memory 52 or auxiliary storage device 53. The recording medium may be in any form, such as a CD-ROM or memory card, as long as it can store the program and is readable by the device.

[0059] 4 is a schematic diagram showing the main data structure of the connection status table 71 held by each of the registration machine 11-1 and the payment machines 12-1 and 12-2 that make up the same group. The connection status table 71 is stored, for example, in the auxiliary storage devices 33 and 53. The registration machine 11-1 and the payment machines 12-1 and 12-2 that make up the same group have connection status tables 71 with the same contents.

[0060] 4, connection status table 71 describes data records 711, 712, and 713, each of which is composed of the following elements: terminal ID, group number, payment machine number, and transfer order N. Data record 711 is a data record relating to registration machine 11-1. Data record 712 is a data record relating to one payment machine, 12-1. Data record 713 is a data record relating to the other payment machine, 12-2.

[0061] The terminal ID is unique identification information set for each of the registration machine 11-1, the payment machine 12-1, and the payment machine 12-2. At least the registration machine 11 and the payment machine 12 incorporated in the transaction processing system 100 are set with different terminal IDs.

[0062] The group number is a number set for each group to identify a group consisting of one registration device 11 and two accounting devices 12. Therefore, the group number in the connection status table 71 for one group is common. The group numbers may or may not be consecutive numbers. It is sufficient that the group numbers do not overlap with the group numbers of other groups.

[0063] The accounting machine number is a consecutive number starting from "1" that is assigned to each accounting machine in order to individually identify the two accounting machines 12-1 and 12-2 that make up the same group. Note that the accounting machine number for the registration machine 11-1, which also makes up the same group, is set to "0."

[0064] The transfer priority N is a consecutive number starting from "1" that indicates the transfer priority N for the two payment machines 12-1 and 12-2 of the payment information sent from the registration machine 11-1 that constitutes the same group. In this embodiment, the transfer priority N of the payment machine 12-1 with the payment machine number "1" is set to first, and the transfer priority N of the payment machine 12-2 with the payment machine number "2" is set to second. The transfer priority N of the payment machine 12-2 with the payment machine number "2" may also be set to first, and the transfer priority N of the payment machine 12-1 with the payment machine number "1" may also be set to second. The transfer priority N is set to "0" for the registration machine 11-1. In the following, for ease of explanation, the payment machine 12-1 with the payment machine number "1" will be referred to as the first payment machine 12-1, and the payment machine 12-2 with the payment machine number "2" will be referred to as the second payment machine 12-2. The first payment device 12-1 is first in the transfer order, and therefore can be called a parent device or a master device, etc. The second payment device 12-2 is second in the transfer order, and therefore can be called a child device or a satellite device, etc.

[0065] FIG. 5 is a schematic diagram showing the payment machine status flag 81 possessed by the registration machine 11-1. The payment machine status flag 81 is stored, for example, in a volatile memory area of ​​the main memory 32. The payment machine status flag 81 is an area for storing a value capable of determining whether the first payment machine 12-1, which has the first transfer priority N, is the destination to which payment information is to be sent. The value is one-bit data of "0" or "1". In this embodiment, the value of the payment machine status flag 81 is "0" when the first payment machine 12-1 is the destination to which payment information is to be sent, and the value of the payment machine status flag 81 is "1" when the first payment machine 12-1 is not the destination to which payment information is to be sent. The value of the payment machine status flag 81 may be "1" when the first payment machine 12-1 is the destination to which payment information is to be sent, and the value of the payment machine status flag 81 is "0" when the first payment machine 12-1 is not the destination to which payment information is to be sent.

[0066] [Transaction processing system functions] The main functions of transaction processing system 100 will be described with reference to Figures 6 to 16. Note that the processes and procedures related to the functions described below are merely examples. The contents of the procedures or processes can be changed as appropriate as long as the same effect can be achieved.

[0067] First, the first function related to settlement of a transaction will be described. In the registration machine 11-1, the first function relates to the functions of the creation means 311 and the transmission means 312. In the first payment machine 12-1 and the second payment machine 12-2, the first function relates to the function of the payment means 511. The functions of the creation means 311 and the transmission means 312 are based on the first information processing. The function of the payment means 511 is based on the fourth information processing or the fifth information processing.

[0068] 6 and 7 are flow charts showing the procedure of the first information processing executed by the processor 31 of the registration machine 11-1 according to the registration program. The customer 22 places the products to be purchased from the products displayed in the sales area in a shopping basket or the like, and heads to the checkout lane. When the customer 22 arrives at the checkout lane, the store clerk 21 acting as a checker performs an operation to declare the start of registration on the registration machine 11-1. This operation starts up the registration program of the registration machine 11-1, and the processor 31 starts the first information processing, the procedure of which is shown in the flow charts of FIG. 6 and FIG. 7.

[0069] As ACT1, the processor 31 causes the touch panel 38 to display a registration screen. The registration screen is a screen in which, for example, a details area and a total area are arranged, and further an icon of a subtotal button is arranged. The details area is an area for displaying the product name, quantity, unit price, and amount in list form in a series of numerical order. The total area is an area for displaying the total of the quantities (points) and the total amount (yen) displayed in the details area. The subtotal button is an operator that the store clerk 21 touches to instruct output of a subtotal for the products purchased by the customer 22.

[0070] The processor 31 that controlled the display of the registration screen waits for data relating to the product to be input as ACT2. Many products are affixed with a barcode that indicates the product code, which is the identification information of the product. The store clerk 21 operates the scanner 37 to read the barcode affixed to the product purchased by the customer 22. When the barcode is read by the scanner 37, the product code of the purchased product is input to the registration machine 11-1. On the other hand, some products, such as fresh foods, may not have a barcode. When the purchased product does not have a barcode, the store clerk 21 touches a product button corresponding to the purchased product from among the product buttons displayed on the touch panel 38. When the product button is touched, the product code of the product corresponding to that product button is input to the registration machine 11-1.

[0071] When the product code is input, the processor 31 proceeds to YES in ACT2. The processor 31 executes product sales data processing in ACT3. That is, the processor 31 acquires product data such as the product name, unit price, attributes, etc. from the product record of the product identified by the product code input via the scanner 37 or touch panel 38. The processor 31 then registers the product sales data including items such as the product code, product name, unit price, sales quantity, sales amount, attributes, etc. in the transaction memory. The transaction memory is part of the volatile memory area in the main memory 32.

[0072] After completing the product sales data processing, the processor 31 checks whether the subtotal button has been pressed (ACT4). The store clerk sequentially performs operations to input the product codes of the products purchased by the customer 22. Then, when the product codes of all the purchased products have been input, the store clerk touches the subtotal button.

[0073] If the subtotal button is not pressed and the product code of the next product is entered, the processor 31 proceeds to NO in ACT4, and then to YES in ACT2. That is, the processor 31 executes product sales data processing in ACT3. As a result, the product sales data of the purchased product is registered in the transaction memory.

[0074] When the subtotal button is input, processor 31 proceeds to YES in ACT4. Processor 31 displays the subtotal screen in ACT5. The subtotal screen is a screen on which a total area is arranged, and icons such as a payment button are also arranged. The total area is the same as the total area on the registration screen. The payment button is an operator that clerk 21 touches to instruct payment of the amount. After checking the subtotal screen, clerk 21 touches the payment button.

[0075] After controlling the display of the master plan screen, processor 31 waits for the payment button to be pressed in ACT 6. If the payment button is pressed by the store clerk 21, processor 31 proceeds to YES in ACT 6. Processor 31 creates payment information in ACT 7. That is, processor 31 creates the payment information required for settling the transaction based on the product sales data of each purchased item registered in the transaction memory, the total number of items, and the total amount, as well as transaction-specific data such as the transaction number, transaction date and time, and the terminal ID of the registered machine.

[0076] Once the payment information has been created, processor 31 proceeds to ACT8 in Fig. 7. In ACT8, processor 31 obtains payment machine status flag 81. In ACT9, processor 31 checks whether the value of payment machine status flag 81 is "0" or "1".

[0077] If the value of the payment machine status flag 81 is "0", meaning that the first payment machine 12-1 is the destination for sending the payment information, processor 31 proceeds to YES in ACT 9. In ACT 10, processor 31 refers to the connection status table 71 and selects the terminal ID of the first payment machine 12-1, whose transfer priority N is set to 1st.

[0078] If the value of the payment machine status flag 81 is "1", meaning that the first payment machine 12-1 is not the destination for sending the payment information, processor 31 proceeds to NO in ACT 9. In ACT 11, processor 31 refers to the connection status table 71 and selects the terminal ID of the second payment machine 12-2, whose transfer priority N is set to second.

[0079] Upon completing the processing of ACT10 or ACT11, processor 31 proceeds to ACT12. In ACT12, processor 31 controls communication unit 35 to transmit payment information to the payment machine identified by the terminal ID acquired in the processing of ACT10 or ACT11 as the destination. With this control, if the terminal ID of first payment machine 12-1 is selected in ACT10, payment information is transmitted to network 14 with first payment machine 12-1 as the destination. If the terminal ID of second payment machine 12-2 is selected in ACT11, payment information is transmitted to network 14 with second payment machine 12-2 as the destination.

[0080] Processor 31, which controlled the transmission of the payment information, checks whether a transmission error has occurred in ACT13. For example, if the destination accounting machine 12 is down or if a communication failure has occurred on network 14, the transmission of the payment information will result in an error. If an error occurs in the transmission of the payment information, processor 31 proceeds to YES in ACT13. Processor 31 notifies the user of the transmission error of the payment information in ACT14. For example, processor 31 notifies the user by displaying a transmission error message on touch panel 38.

[0081] If there is no error in sending the payment information, the processor 31 proceeds to YES in ACT 13. The processor 31 checks whether or not a payment possible notification command has been received from the payment machine 12 in ACT 15. Incidentally, when payment information is sent to either payment machine 12-1 or 12-2, a payment possible notification command or a busy notification command is returned from either payment machine 12.

[0082] If the processor 31 receives a busy notification command instead of a payment possible notification command, the processor 31 proceeds to NO in ACT 15 and returns to ACT 8. The processor 31 then executes the processes from ACT 8 onwards in the same manner as described above.

[0083] If the processor 31 receives the payment possible notification command, it proceeds to YES in ACT15. The processor 31 notifies the payment destination in ACT16. That is, if the sender of the payment possible notification command is the first payment machine 12-1, the processor 31 notifies that the first payment machine 12-1 is the payment destination. If the sender of the payment possible notification command is the second payment machine 12-2, the processor 31 notifies that the second payment machine 12-2 is the payment destination. The notification may be given to the store clerk 21 using the touch panel 38, or to the customer 22 using the customer display 39. The customer 22 moves to the location of the first payment machine 12-1 or the second payment machine 12-2 notified as the payment destination, and operates the payment machine 12 to perform the payment himself.

[0084] With this, processor 31 ends the first information processing. Here, the processor 31 of the registration device 11-1 realizes the function of the creation means 311 by the processing of ACT7. Moreover, the same processor 31 realizes the function of the transmission means 312 by the processing of ACT8 to ACT12.

[0085] FIG. 8 is a flow chart showing the procedure of the fourth information processing executed by the processor 51 of the first accounting machine 12-1 according to the payment program. The processor 51 waits for payment information in ACT21. When the communication unit 55 receives the payment information transmitted from the registration machine 11-1, the processor 51 proceeds to YES in ACT21. The processor 51 checks whether the first accounting machine 12-1 is capable of executing the payment process in ACT22. For example, if the payment process of the previous customer is not completed, the first accounting machine 12-1 cannot execute the payment process of the next customer. Also, if a printer error such as a paper jam or paper out in the printer 59, or a change machine error such as a coin jam or out of change in the change machine, occurs, the first accounting machine 12-1 cannot execute the payment process.

[0086] If the first payment machine 12-1 is capable of executing the payment process, the processor 51 proceeds to YES in ACT 22. The processor 51 controls the communication unit 55 to send a payment possible notification command to the registration machine 11-1 in ACT 23. By this control, the payment possible notification command is sent to the registration machine 11-1.

[0087] Processor 51 executes the payment process as ACT24. Specifically, processor 51 sets the screen of touch panel 58 as a payment method selection screen. The payment method selection screen is a screen on which operators for selecting a payment method, such as a cash button, a credit button, an electronic money button, etc., are arranged. A customer who moves to the location where first accounting machine 12-1 is installed touches a button corresponding to the desired payment method. That is, a customer who wishes to pay by cash touches the cash button, a customer who wishes to pay by credit card touches the credit button, and a customer who wishes to pay by electronic money touches the electronic money button.

[0088] Processor 51, which has controlled the display of the payment method selection screen, waits for one of the payment methods to be selected. Then, when a payment method is selected, processor 51 executes a settlement process corresponding to that payment method. For example, when cash is selected as the payment method, processor 51 executes a process of subtracting the total amount from the amount inserted into the automatic change machine, calculating the change, and dispensing it from the automatic change machine. For example, when a credit card is selected as the payment method, processor 51 authenticates the credit card read by reader / writer 60, and confirms the total amount as the credit settlement amount on the condition that it is approved by server 13. For example, when electronic money is selected as the payment method, processor 51 subtracts the total amount from the balance of the electronic money medium read by reader / writer 60.

[0089] When the payment process for each payment method is completed in this way, processor 51 controls printer 59 as ACT 25 to issue a transaction receipt. The transaction receipt prints payment information, such as the transaction number, transaction date and time, terminal ID, product sales data, total number of items, total amount, etc.

[0090] On the other hand, if the first payment machine 12-1 is unable to execute the payment process, the processor 51 proceeds to NO in ACT22. In ACT26, the processor 51 refers to the connection status table 71 and obtains the transfer priority N associated with the terminal ID of the own machine. Next, in ACT27, the processor 51 selects another payment machine 12-2 whose transfer priority N is set to be equal to the transfer priority N obtained by adding "1" to the transfer priority N. Then, in ACT28, the processor 51 controls the communication unit 55 to send the payment information to the selected other payment machine 12-2. Through this control, the payment information is sent (transferred) to the network 14 with the second payment machine 12-2, which is second in the transfer priority N, as the destination.

[0091] Processor 51, which controlled the transmission (transfer) of the payment information, checks whether a transmission error has occurred in ACT29. For example, if the destination accounting machine 12-2 is down, an error occurs in the transmission of the payment information. If an error occurs in the transmission of the payment information, processor 51 proceeds to YES in ACT29. Processor 51 controls communication unit 55 to send a busy notification command to registration machine 11-1 in ACT30. This control causes the busy notification command to be sent to registration machine 11-1.

[0092] With this, processor 51 ends the fourth information processing. Here, the processor 51 of the first payment machine 12-1 realizes the function as a payment means 511 by the processing of ACT24. Also, the processor 51 of the first payment machine 12-1 realizes the function as a transfer means by the processing of ACT25 to ACT27.

[0093] FIG. 9 is a flow chart showing the procedure of the fifth information processing executed by the processor 51 of the second accounting machine 12-2 according to the payment program. The processor 51 waits for payment information in ACT31. When the communication unit 55 receives the payment information transmitted from the first accounting machine 12-1, the processor 51 proceeds to YES in ACT31. The processor 51 checks whether the second accounting machine 12-2 is capable of executing the payment process in ACT32. For example, if the payment process of the previous customer is not completed, the second accounting machine 12-2 cannot execute the payment process of the next customer. In addition, if a printer error such as a paper jam or paper out in the printer 59, or a change machine error such as a coin jam or out of change in the change machine, occurs, the second accounting machine 12-2 cannot execute the payment process.

[0094] If the second payment machine 12-2 is capable of executing the payment process, the processor 51 proceeds to YES in ACT32. The processor 51 executes the same processes as ACT23 to ACT25 in Fig. 8 in ACT33 to ACT35. That is, the processor 51 controls the communication unit 55 to send a payment possible notification command to the registration machine 11-1 in ACT33. The processor 51 also executes the payment process in ACT34. Thereafter, the processor 51 controls the printer 59 to issue a transaction receipt in ACT35.

[0095] On the other hand, if the second payment device 12-2 cannot execute the payment process, processor 51 proceeds to NO in ACT 32. Processor 51 refers to the connection status table 71 in ACT 36, and obtains the transfer priority N associated with the terminal ID of its own device. Then, processor 51 checks whether the transfer priority N is the lowest among the transfer priorities N of the records described in the connection status table 71 in ACT 37.

[0096] When there are two payment machines 12 belonging to a group, the transfer priority N set for the second payment machine 12-2, i.e., second place, is the lowest. If the transfer priority N is the lowest, the processor 51 proceeds to YES in ACT37. The processor 51 controls the communication unit 55 to send a busy notification command to the registration machine 11-1 in ACT38. With this control, a payment possible notification command is sent to the registration machine 11-1.

[0097] Note that if there are three or more payment machines 12 belonging to the group, the transfer priority N set for the second payment machine 12-2 is not the lowest. If the transfer priority N is not the lowest, the processor 51 proceeds to NO in ACT37. In ACT39, the processor 51 selects another payment machine 12 whose transfer priority N is set to be equal to the transfer priority N plus "1". Then, in ACT40, the processor 51 controls the communication unit 55 to send the payment information to the selected other payment machine 12 as the destination. Through this control, the payment information is sent (transferred) to the network 14 with the payment machine 12 with the lower transfer priority N as the destination.

[0098] The processor 51, which controlled the transmission (transfer) of the payment information, checks whether a transmission error has occurred in ACT 41. If an error occurs in the transmission of the payment information, the processor 51 proceeds to YES in ACT 41. The processor 51 controls the communication unit 55 to transmit a busy notification command to the registration device 11-1 in ACT 42. With this control, the busy notification command is transmitted to the registration device 11-1.

[0099] With this, processor 51 ends the fifth information processing. Here, the processor 51 of the second payment machine 12-2 realizes the function of payment means 511 by the processing of ACT34. Also, the processor 51 of the second payment machine 12-2 realizes the function of transfer means by the processing of ACT36 to ACT40.

[0100] As is clear from the above explanation of the first function, when the registration machine 11-1 designates the first payment machine 12-1 as the destination of payment information, i.e. when the value of the payment machine status flag 81 is "0", the payment information created by the registration machine 11-1 is sent to the first payment machine 12-1. At this time, if the first payment machine 12-1 is in a state where it can execute payment processing, a payment possible notification command is sent from the first payment machine 12-1 to the registration machine 11-1. This allows the store clerk 21 at the registration machine 11-1 to instruct the customer 22 to carry out the transaction at the first payment machine 12-1. The customer 22 moves to the location where the first payment machine 12-1 is installed and performs the operations for the transaction by himself. In response to this operation, the first payment machine 12-1 executes the payment process.

[0101] On the other hand, when the first payment machine 12-1 is in a state where it cannot execute the payment process, the payment information is transferred from the first payment machine 12-1 to the second payment machine 12-2. At this time, when the second payment machine 12-2 is in a state where it can execute the payment process, a payment possible notification command is sent from the second payment machine 12-2 to the registration machine 11-1. This allows the store clerk 21 at the registration machine 11-1 to instruct the customer 22 to carry out the payment at the second payment machine 12-2. The customer 22 moves to the location where the second payment machine 12-2 is installed and performs the operations for the payment by himself. In response to this operation, the second payment machine 12-2 executes the payment process.

[0102] In this way, the transaction processing system 100 can settle a transaction with a customer 22 whose sales data for purchased items has been registered and processed by the registration machine 11-1, as long as at least one of the first payment machine 12-1 or the second payment machine 12-2 is in a state where it can execute payment processing.

[0103] However, when the payment information is sent (transferred) from the first payment machine 12-1 to the second payment machine 12-2 but the second payment machine 12-2 is in a state where it cannot execute the payment process, a busy notification command is sent from the second payment machine 12-2 to the registration machine 11-1. Also, if an error occurs in sending the payment information to the second payment machine 12-2 due to a communication abnormality between the first payment machine 12-1 and the second payment machine 12-2, a busy notification command is sent from the first payment machine 12-1 to the registration machine 11-1. The registration machine 11-1, which receives the busy notification command, again sends the payment information to the first payment machine 12-1. Therefore, at least in the first payment machine 12-1, for example, the payment with the previous customer is completed and it becomes possible to execute the payment process, and the transaction processing system 100 is able to settle the transaction with customer 22.

[0104] However, if the first payment machine 12-1 is down and payment information cannot be sent from the registration machine 11-1 to the first payment machine 12-1, the payment information will not be sent (transferred) to the second payment machine 12-2 even if the second payment machine 12-2 is operating normally. As a result, the transaction processing system 100 will not be able to settle the transaction with the customer 22.

[0105] Next, we will explain the second function possessed by transaction processing system 100 to resolve such problems. In registration machine 11-1, the second function involves the functions of status confirmation means 313, change means 314, and recovery means 315. In first payment machine 12-1 and second payment machine 12-2, the second function involves the functions of confirmation notification means 512 and change notification means 513. The function of status confirmation means 313 is based on the second information processing. The functions of change means 314 and recovery means 315 are based on the third information processing. The function of confirmation notification means 512 is based on the sixth information processing. The function of change notification means 513 is based on the seventh information processing.

[0106] 10 is a flow chart showing the procedure of the sixth information processing executed by the processor 51 of the first payment machine 12-1 and the second payment machine 12-2 in accordance with the payment program. In ACT51, the processor 51 checks whether it is time to send a payment machine confirmation notification. After being started up in payment machine mode, the processor 51 starts a monitoring timer (not shown). Then, each time the count value of this monitoring timer reaches a set value, the processor 51 proceeds to YES in ACT51. In ACT52, the processor 51 controls the communication unit 55 to send a confirmation start notification command to the registration machine 11-1. With this control, the confirmation start notification command is sent to the registration machine 11-1.

[0107] With this, processor 51 ends the sixth information processing. In this way, the first payment machine 12-1 and the second payment machine 12-2 periodically transmit a confirmation start notification command to the registration machine 11-1 in the same group at a time interval according to the set value of the monitoring timer. The set value of the monitoring timer is arbitrary. For example, an appropriate value is set by the system administrator.

[0108] Here, the processor 51 of the first payment machine 12-1 and the second payment machine 12-2 realizes the function of a confirmation notification means 512 by processing ACT51 and ACT52.

[0109] 11 is a flow chart showing the procedure of the second information processing executed by the processor 31 of the registration machine 11-1 in accordance with the registration program. The processor 31 waits for a confirmation start notification command in ACT61. When the processor 31 receives the confirmation start notification command via the communication unit 35, the process proceeds to YES in ACT61. The processor 31 refers to the connection status table 71 in ACT62 and selects the terminal ID whose transfer priority N is set to 1st. The processor 31 controls the communication unit 35 to send a status confirmation command to the payment machine 12 identified by the selected terminal ID, that is, the first payment machine 12-1 in ACT63. This control causes the status confirmation command to be sent to the first payment machine 12-1.

[0110] The processor 31 that controlled the sending of the status check command checks whether a transmission error has occurred in ACT64. For example, if the first payment device 12-1 is down, the sending of the status check command will result in an error. If an error occurs in the sending of the status check command, the processor 31 proceeds to YES in ACT64 and moves to the processing of ACT67. The processing after ACT67 will be described later.

[0111] The processor 51 of the first payment machine 12-1, which has received the status confirmation command, collects information necessary for status confirmation, so-called payment machine information. The processor 51 then controls the communication unit 55 to send an acknowledgement command including the payment machine information to the registration machine 11-1. This control causes the acknowledgement command to be sent to the registration machine 11-1. The acknowledgement command includes the payment machine information. The payment machine information is, for example, information identifying whether the operating mode of the first payment machine 12-1 is payment machine mode or training mode, information identifying whether an error has occurred in the printer 59, information identifying whether an error has occurred in the change machine connected to the change machine interface 56, etc. It should be noted that the payment machine information is not limited to the information described above.

[0112] If there is no error in sending the status confirmation command, the processor 31 proceeds to YES in ACT64. The processor 31 waits for an acknowledgement command from the first payment machine 12-1 in ACT65. When the processor 31 receives the acknowledgement command via the communication unit 35, the processor 31 proceeds to YES in ACT65. The processor 31 stores the payment machine information included in the acknowledgement command in temporary memory of the main memory 32 in ACT66. The processor 31 then proceeds to ACT67.

[0113] In this way, if the transmission of the status check command results in an error, or if the processor 31 stores the payment machine information in the response command to the status check command in the temporary memory, it proceeds to the process of ACT67.

[0114] Processor 31 acquires the payment machine status flag 81 in ACT67. Then, processor 31 controls communication unit 35 to send a confirmation end notification command to the sender of the confirmation start notification command in ACT68. With this control, if the sender of the confirmation start notification command is the first payment machine 12-1, the confirmation end notification command is sent to the first payment machine 12-1. If the sender of the confirmation start notification command is the second payment machine 12-2, the confirmation end notification command is sent to the second payment machine 12-2. The confirmation end notification command includes the payment machine status flag 81 acquired in the processing of ACT67. Also, if payment machine information is stored in temporary memory in ACT66, that payment machine information is also included in the confirmation end notification command. Then, the temporary memory is cleared.

[0115] With this, processor 31 ends the second information processing. In this way, each time the registration machine 11-1 receives a confirmation start notification command that is periodically sent from the first payment machine 12-1 or the second payment machine 12-2 in the same group, it acquires the payment machine information of the first payment machine 12-1, which is set to be first in the transfer order. The registration machine 11-1 then sends a confirmation end notification command to the first payment machine 12-1 or the second payment machine 12-2, which are the senders of the confirmation start notification command, which includes the acquired payment machine information and the current payment machine status flag 81. If the registration machine 11-1 is unable to acquire payment machine information from the first payment machine 12-1, it sends a confirmation end notification command that includes the payment machine status flag 81. In addition to the payment machine status flag 81, the registration machine 11-1 may also include information indicating that the payment machine information could not be acquired.

[0116] Here, the processor 31 of the registration device 11-1 realizes the function of the status confirmation means 313 by executing the processes of ACT62 to ACT68.

[0117] 12 is a flow chart showing the procedure of the seventh information processing executed by processor 51 of first payment machine 12-1 and second payment machine 12-2 in accordance with the payment program. Processor 51 waits for a confirmation completion notification command in ACT71. When processor 51 receives the confirmation completion notification command via communication unit 55, it proceeds to YES in ACT71. Processor 51 refers to connection status table 71 in ACT72 to obtain the transfer priority N associated with the terminal ID of its own machine.

[0118] Processor 51 checks whether transfer priority N is first in ACT73. If transfer priority N is first, i.e., if it is the first payment machine 12-1, processor 51 proceeds to YES in ACT73. Processor 51 checks the payment machine status flag 81 included in the confirmation completion notification command in ACT74. If the payment machine status flag 81 is "0", i.e., if the registration machine 11-1 has designated the first payment machine 12-1 as the destination for sending payment information, processor 51 proceeds to NO in ACT74, ending the seventh information processing.

[0119] If the payment machine status flag 81 is "1", that is, if the registration machine 11-1 has not set the first payment machine 12-1 as the destination for sending payment information, the processor 51 proceeds to YES in ACT74. The processor 51 controls the communication unit 55 to send a master declaration command to the registration machine 11-1 in ACT75. With this control, the master declaration command is sent to the registration machine 11-1. Having controlled the sending of the master declaration command, the processor 51 ends the seventh information processing.

[0120] On the other hand, if the transfer priority N is not first, i.e., if it is the second payment machine 12-2, processor 51 proceeds to NO in ACT 73. Processor 51 checks the payment machine status flag 81 included in the confirmation completion notification command in ACT 76. If the payment machine status flag 81 is "1", i.e., if the registration machine 11-1 has not set the first payment machine 12-1 as the destination for sending payment information, in other words, if the second payment machine 12-2 is the destination, processor 51 proceeds to YES in ACT 76, ending the seventh information processing.

[0121] If the payment machine status flag 81 is "0", i.e., if the registration machine 11-1 has designated the first payment machine 12-1 as the destination for sending payment information, the processor 51 proceeds to NO in ACT75. The processor 51 checks whether the confirmation completion notification command contains payment machine information for the first payment machine 12-1 in ACT77. If the payment machine information is not included, the processor 51 proceeds to NO in ACT77 and moves on to the processing of ACT75 described above. That is, the processor 51 controls the communication unit 55 to send a master declaration command to the registration machine 11-1, and ends the seventh information processing.

[0122] If the confirmation completion notification command includes payment machine information, the processor 51 proceeds to YES in ACT 77. The processor 51 analyzes the payment machine information in ACT 78. The processor 51 then determines whether the first payment machine 12-1 is ready for a transaction.

[0123] As described above, the payment machine information includes, for example, information identifying whether the operating mode of the first payment machine 12-1 is payment machine mode or training mode, information identifying whether an error has occurred in the printer 59, information identifying whether an error has occurred in the change machine connected to the change machine interface 56, etc. The processor 51 determines that the first payment machine 12-1 is capable of payment if the operating mode of the first payment machine 12-1 is payment machine mode and no errors have occurred in the printer 59 or the change machine. The processor 51 determines that the first payment machine 12-1 is not capable of payment if the operating mode of the first payment machine 12-1 is training mode or if an error has occurred in the printer 59 or the change machine. If the processor 51 determines that the first payment device 12-1 is available for payment, it proceeds to YES in ACT78 and ends the seventh information processing.

[0124] If the processor 51 determines that the first payment device 12-1 is not able to perform the transaction, it proceeds to NO in ACT78 and executes the process of ACT75 described above. That is, the processor 51 controls the communication unit 55 to send a master declaration command to the registration device 11-1, and ends the seventh information processing.

[0125] In this way, the first accounting machine 12-1, which is first in the transfer order, sends a master declaration command to the registration machine 11-1 if the payment machine status flag 81 included in the confirmation completion notification command is "1". When the payment machine status flag 81 is "1", the destination of the payment information is not set to the first accounting machine 12-1 in the registration machine 11-1. This type of event can occur when the first accounting machine 12-1 goes down. After that, when the first accounting machine 12-1 recovers, the first accounting machine 12-1 again sends a confirmation start notification command to the registration machine 11-1. Then, the confirmation start notification command, which is a response command to this confirmation start notification command, includes "1" as the payment machine status flag 81. Therefore, the first accounting machine 12-1 sends a master declaration command to the registration machine 11-1. That is, when the payment machine status flag 81 included in the confirmation completion notification command is "1" in the first accounting machine 12-1, the destination change condition is satisfied.

[0126] On the other hand, the second payment machine 12-2, which is second in the transfer order, does not send a master declaration command to the registration machine 11-1 if the payment machine status flag 81 included in the confirmation completion notification command is "1", that is, if the destination of the payment information in the registration machine 11-1 has been changed to the second payment machine 12-2.

[0127] On the other hand, if the accounting machine status flag 81 is "0", a master declaration command is sent to the register 11-1 if the following destination change conditions are met. The first condition is when the confirmation completion notification command does not include the payment machine information. If the confirmation completion notification command does not include the payment machine information, it means that the first payment machine 12-1 has gone down. Therefore, the second payment machine 12-2 sends a master declaration command to the registration machine 11-1.

[0128] The second condition is when, as a result of analyzing the payment machine information included in the confirmation completion notification command, the first payment machine 12-1 recognizes that the transaction is not possible. In this case, the second payment machine 12-2 also sends a master declaration command to the registration machine 11-1.

[0129] Here, the processor 31 of the first payment machine 12-1 and the second payment machine 12-2 realizes the function of the change notification means 513 by executing the processing of ACT75. Note that, in order to distinguish between the change notification means 513 of the first payment machine 12-1 and the change notification means 513 of the second payment machine 12-2, the change notification means 513 of the second payment machine 12-2 may be rephrased as the first change notification means 513, and the change notification means 513 of the first payment machine 12-1 may be rephrased as the second change notification means 513.

[0130] 13 is a flow chart showing the procedure of the third information processing executed by the processor 31 of the registration device 11-1 according to the registration program. The processor 31 waits for a master declaration command in ACT81. When the processor 31 receives the master declaration command via the communication unit 35, the process proceeds to YES in ACT81. The processor 31 checks whether the registration device 11-1 is idle in ACT82. Idle means a state in which the processor 31 is not executing the first information processing or the second information processing. If the registration device 11-1 is not idle, the processor 31 proceeds to NO in ACT82 and ends the third information processing.

[0131] If the register 11-1 receives the master declaration command while the register 11-1 is idle, the processor 31 proceeds to YES in ACT 82. The processor 31 checks the register status flag 81 in ACT 83.

[0132] If the payment machine status flag 81 is "0", the processor 31 proceeds to YES in ACT83. The processor 31 changes the payment machine status flag 81 from "0" to "1" in ACT84. If the payment machine status flag 81 is "1", the processor 31 proceeds to NO in ACT83. The processor 31 changes the payment machine status flag 81 from "1" to "0" in ACT85. With this, the processor 31 ends the third information processing.

[0133] In this way, when the registration machine 11-1 receives a master declaration command while the payment machine status flag 81 is "0", it changes the payment machine status flag 81 from "0" to "1". When the payment machine status flag 81 is "0", it is the second payment machine 12-2 that sends the master declaration command. Then, when the payment machine status flag 81 is changed from "0" to "1", the processor 31 of the registration machine 11-1 proceeds to NO in ACT9 of the first information processing, and executes the processing of ACT11. That is, the processor 31 selects the terminal ID of the second payment machine 12-2, whose transfer priority N is set to second, from the connection status table 71. Then, the processor 31 sends the payment information to the second payment machine 12-2, identified by this terminal ID, as the destination.

[0134] In this way, when a master declaration command is sent from the second payment machine 12-2, the destination of the payment information is automatically changed from the first payment machine 12-1 to the second payment machine 12-2. The second payment machine 12-2 sends a master declaration command when the first or second condition described above is satisfied. Therefore, when the first payment machine 12-1 goes down or becomes unable to perform a transaction, the transaction processing system 100 automatically changes the destination of the payment information from the first payment machine 12-1 to the second payment machine 12-2. Therefore, even if the first payment machine 12-1 goes down, the payment processing of the customer 22 is not delayed.

[0135] Furthermore, when the registration machine 11-1 receives a master declaration command while the payment machine status flag 81 is "1", it changes the payment machine status flag 81 from "1" to "0". When the payment machine status flag 81 is "1", it is the first payment machine 12-1 that sends the master declaration command. Then, when the payment machine status flag 81 is changed from "1" to "0", the processor 31 of the registration machine 11-1 proceeds to YES in ACT9 of the first information processing, and executes the processing of ACT10. That is, the processor 31 selects from the connection status table 71 the terminal ID of the first payment machine 12-1, whose transfer priority N is set to 1st. The processor 31 then transmits the payment information to the first payment machine 12-1, identified by this terminal ID, as the destination.

[0136] In this way, when a master declaration command is sent from the first payment machine 12-1, the destination of the payment information is automatically changed from the second payment machine 12-2 to the first payment machine 12-1. The first payment machine 12-1 sends a master declaration command when the first payment machine 12-1, which was down, recovers, as described above. Therefore, when the first payment machine 12-1 recovers from being down, the transaction processing system 100 can quickly change the destination of the payment information back to the first payment machine 12-1.

[0137] Here, the processor 31 of the registration device 11-1 realizes the function of a change means 314 by executing the process of ACT84. The processor 31 also realizes the function of a recovery means 315 by executing the process of ACT85.

[0138] Next, a sequence of commands exchanged between the register 11-1 and the first and second payment machines 12-1 and 12-2 in the above-mentioned second function will be described. Figure 14 is a sequence diagram when, for example, a printer error occurs in the first payment machine (payment machine 1) 12-1. If no printer error occurs initially, the first payment machine 12-1 sends a confirmation start notification command (Pa) to the registration machine 11-1. Upon receiving this confirmation start notification command (Pa), the registration machine 11-1 sends a status confirmation command (Pb) to the first payment machine 12-1, and upon receiving a confirmation response command (Pc) from the first payment machine 12-1, it sends a confirmation end notification command (Pd) including payment machine information and a payment machine status flag 81 to the first payment machine 12-1. At this time, since the payment machine status flag 81 is "0", the first payment machine 12-1 does not send a master declaration command to the registration machine 11-1.

[0139] Meanwhile, the second payment machine (payment machine 2) 12-2 sends a confirmation start notification command (Qa) to the registration machine 11-1. Upon receiving this confirmation start notification command (Qa), the registration machine 11-1 sends a status confirmation command (Qb) to the first payment machine 12-1, and upon receiving an acknowledgement command (Qc) from the first payment machine 12-1, it sends a confirmation end notification command (Qdx) including the payment machine information and the payment machine status flag 81 to the second payment machine 12-2. At this time, the payment machine status flag 81 is "0" and the payment machine information does not satisfy the destination change condition, so the second payment machine 12-2 does not send a master declaration command to the registration machine 11-1.

[0140] At this point, the payment information is sent from the registration machine 11-1 to the first payment machine 12-1. Then, if the first payment machine 12-1 is in a state where payment is possible, the payment process is carried out at the first payment machine 12-1. If the first payment machine 12-1 is in a busy state, for example, the payment information is transferred from the first payment machine 12-1 to the second payment machine 12-2. Then, the payment process is carried out at the second payment machine 12-2.

[0141] Let us then assume that a printer error occurs in the first payment machine 12-1. In this case, the payment machine information included in the confirmation completion notification command (Qdy) sent from the registration machine 11-1 to the second payment machine 12-2 satisfies the destination change condition. Therefore, the second payment machine 12-2 sends a master declaration command (Qe) to the registration machine 11-1. As a result, the destination of the payment information is changed from the first payment machine 12-1 to the second payment machine 12-2. Thereafter, the payment process is carried out in the second payment machine 12-2.

[0142] 15 is a sequence diagram when the first payment machine 12-1 goes down. Because the first payment machine 12-1 is down, it does not send the confirmation start notification command (Pa). As a result, the status confirmation command (Pb), confirmation response command (Pc), and confirmation end notification command (Pd) that were performed between the registration machine 11-1 and the first payment machine 12-1 in response to the confirmation start notification command (Pa) are not exchanged either.

[0143] Meanwhile, a confirmation start notification command (Qa) is sent from the second payment machine 12-2. Then, upon receiving this confirmation start notification command (Qa), the registration machine 11-1 sends a status confirmation command (Qb) to the first payment machine 12-1. However, the sending of the status confirmation command (Qb) results in an error, and the confirmation response command (Qc) cannot be received. Therefore, the confirmation end notification command (Qdz) sent from the registration machine 11-1 to the second payment machine 12-2 does not include payment machine information, and the destination change condition is satisfied. Therefore, the second payment machine 12-2 sends a master declaration command (Qe) to the registration machine 11-1. As a result, from that point on, payment information is sent from the registration machine 11-1 to the second payment machine 12-2. Then, the payment process is executed by the second payment machine 12-2.

[0144] 16 is a sequence diagram when the first payment machine 12-1 recovers from a downtime. Before the first payment machine 12-1 recovers, the payment machine status flag 81 included in the confirmation completion notification command (Qdz) sent from the registration machine 11-1 to the second payment machine 12-2 is "1." Therefore, the second payment machine 12-2 does not send a master declaration command (Qe).

[0145] When the first payment machine 12-1 recovers, the first payment machine 12-1 resumes sending the confirmation start notification command (Pa). Upon receiving this confirmation start notification command (Pa), the registration machine 11-1 sends a status confirmation command (Pb) to the first payment machine 12-1, and upon receiving a confirmation response command (Pc) from the first payment machine 12-1, it sends a confirmation end notification command (Pd) including payment machine information and a payment machine status flag 81 to the first payment machine 12-1. At this time, since the payment machine status flag 81 is "1", the first payment machine 12-1 sends a master declaration command (Pe) to the registration machine 11-1. As a result, the destination of the payment information is returned from the second payment machine 12-2 to the first payment machine 12-1.

[0146] Thereafter, the confirmation end notification command (Qdx) sent from the registration machine 11-1 to the second payment machine 12-2 in response to the confirmation start notification command (Qa) from the second payment machine 12-2 contains information about the normal state of the payment machine. In addition, the payment machine status flag 81 has also been changed to "0." Therefore, the second payment machine 12-2 does not send a master declaration command (Qe).

[0147] In the sequence example shown in Figures 14 to 16, each of the payment machines 12-1, 12-2 is shown to transmit a confirmation start notification command (Pa, Qa) after a confirmation end notification command (Pd, Qd) is transmitted from the registration machine 11-1. However, in reality, there may be cases where the registration machine 11-1 receives a confirmation start notification command (Pa, Qa) from one payment machine before transmitting a confirmation end notification command (Pd, Qd) to the other payment machine. In such a case, after transmitting the confirmation end notification command (Pd, Qd) to one payment machine, the registration machine 11-1 executes processing according to the confirmation start notification command (Pa, Qa) from the other payment machine, that is, transmitting a status confirmation command, receiving a confirmation response command, and transmitting a confirmation end notification command.

[0148] As described above in detail, according to transaction processing system 100, even if first payment machine 12-1 goes down and it becomes impossible to send payment information from registration machine 11 to first payment machine 12-1, the destination of the payment information is immediately changed to second payment machine 12-2. The same applies if a printer error, change machine error, or other problem occurs in first payment machine 12-1 making payment impossible. Therefore, even if an abnormality occurs in first payment machine 12-1, which is the destination of the payment information, it is possible to prevent delays in transaction settlement. As a result, a transaction processing system with high processing efficiency can be provided.

[0149] Furthermore, when the first payment machine 12-1 is restored to operation, the destination of the payment information can be quickly returned to the first payment machine 12-1. Generally, in semi-self-service transaction processing systems, there is a tendency for the first payment machine 12-1 to be the payment machine that provides the most efficient movement of customers. Therefore, the impact of an abnormality in the first payment machine 12-1 can be minimized.

[0150] The register 11 uses the 1-bit data of the accounting machine status flag 81 as information for identifying the accounting machine to which the payment information is to be sent. Therefore, there is no impact on the memory capacity of the register 11.

[0151] In this embodiment, the processor 31 of the registration machine 11 is described as executing the second information processing and the third information processing according to a registration program. The program for executing the second information processing and the third information processing is not limited to the registration program. The processor 31 may execute the second information processing and the third information processing according to a program other than the registration program. Similarly, the program for the processor 51 of the payment machine 12 to execute the fifth information processing to the seventh information processing is not limited to the payment program. The processor 51 may execute the fifth information processing to the seventh information processing according to a program other than the payment program.

[0152] The payment machines 12 that send the confirmation start notification command may be only those payment machines 12 that are not set as the destination of payment information in the registration machine 11. For example, when the first payment machine 12-1 is the destination, as in this embodiment, only the second payment machine 12-2 periodically sends the confirmation start notification command. Then, when the confirmation end notification command in response to this confirmation start notification command satisfies the destination change condition, the second payment machine 12-2 sends a master declaration command to the registration machine 11-1. Then, the second payment machine 12-2 stops sending the confirmation start notification command. After that, when the first payment machine 12-1 recovers, the destination returns to the first payment machine 12-1, so the second payment machine 12-2 resumes sending the confirmation start notification command. Even with such a configuration, the same effect as this embodiment can be achieved.

[0153] Second Embodiment 17 is a conceptual diagram of a transaction processing system 200 according to the second embodiment. The transaction processing system 200 includes two registration machines 11 (11-1, 11-2) and three accounting machines 12 (12-1, 12-2, 12-3). Each registration machine 11 and each accounting machine 12 are connected via a network 14. Although not shown, a server 13 is also connected to the network 14, as in the first embodiment.

[0154] Transaction processing system 200 forms one group with one registration machine 11-1 and two payment machines 12-1 and 12-2. Transaction processing system 200 also forms one group with the other registration machine 11-2 and two payment machines 12-2 and 12-3. In other words, one registration machine 11-1 and the other registration machine 11-2 share payment machine 12-2. Therefore, like the first embodiment, the second embodiment is also a transaction processing system in which one registration machine and two payment machines are grouped together.

[0155] The hardware configuration of each of the registration machines 11-1, 11-2 and each of the payment machines 12-1, 12-2, 12-3 is the same as in the first embodiment. Therefore, in the second embodiment, Figures 2 and 3 will be used as they are and the explanation will be omitted. Also, like the first embodiment, each of the registration machines 11-1, 11-2 has a payment machine status flag 81. In the following explanation, the payment machine status flag possessed by the registration machine 11-1 will be referred to as payment machine status flag 811, and the payment machine status flag possessed by the registration machine 11-2 will be referred to as payment machine status flag 812 to distinguish between them.

[0156] 18 is a schematic diagram showing the main data structure of the connection status table 72 held by each of the registration machines 11-1, 11-2 and each of the payment machines 12-1, 12-2, 12-3. The connection status table 72 is stored, for example, in the auxiliary storage devices 33, 53. Each of the registration machines 11-1, 11-2 and each of the payment machines 12-1, 12-2, 12-3 in the two groups that share the payment machine 12-2 has a connection status table 72 with the same contents.

[0157] As shown in FIG. 18, the connection status table 72 describes data records 721, 722, 723, 724, 725, and 726, each of which is composed of the elements of a terminal ID, a group number, a payment machine number, and a transfer order N. Data record 721 is a data record relating to the registration machine 11-1. Data record 722 is a data record relating to the payment machine 12-1. Data record 723 is a data record relating to the payment machine 12-2. Data record 724 is a data record relating to the registration machine 11-2. Data record 725 is a data record relating to the payment machine 12-3. Data record 726 is a data record relating to the payment machine 12-2. In this way, for the payment machine 12-2 shared by two groups, data records 723 and 726 corresponding to each group are described in the connection status table 72.

[0158] The terminal ID is unique identification information set for each of the registration machines 11-1 and 11-2 and the payment machines 12-1, 12-2, and 12-3.

[0159] The group number is a number assigned to each group to identify a group consisting of one registration machine 11 and two accounting machines 12. Therefore, the group numbers of data records 721, 722, and 723 for registration machine 11-1, accounting machine 12-1, and accounting machine 12-2 constituting one group are common. The group numbers of data records 724, 725, and 726 for registration machine 11-2, accounting machine 12-3, and accounting machine 12-2 constituting the other group are common.

[0160] The accounting machine number is a consecutive number starting from "1" that is assigned to each accounting machine in order to individually identify the two accounting machines 12-1 and 12-2 that make up the same group. Note that the accounting machine number for the registration machine 11-1, which also makes up the same group, is set to "0."

[0161] The transfer priority N is a consecutive number starting from "1" that indicates the transfer priority N for the two payment machines 12 of the payment information sent from the registration machine 11 that constitutes the same group. In this embodiment, for the group to which one registration machine 11-1 belongs, the transfer priority N of the payment machine 12-1 with the payment machine number "1" is set to be first, and the transfer priority N of the payment machine 12-2 with the payment machine number "2" is set to be second. For the group to which the other registration machine 11-2 belongs, the transfer priority N of the payment machine 12-3 with the payment machine number "3" is set to be first, and the transfer priority N of the payment machine 12-2 with the payment machine number "2" is set to be second. In the following, for ease of explanation, one registration machine 11-1 will be referred to as the first registration machine 11-1, and the other registration machine 11-2 will be referred to as the second registration machine 11-2. Furthermore, the payment machine 12-1 with the payment machine number "1" will be referred to as the first payment machine 12-1, the payment machine 12-2 with the payment machine number "2" will be referred to as the second payment machine 12-2, and the payment machine 12-3 with the payment machine number "3" will be referred to as the third payment machine 12-3. The first payment machine 12-1 and the third payment machine 12-3 have the first highest transfer order, and therefore can also be referred to as parent machines or master machines, etc. The second payment machine 12-2 has the second highest transfer order, and therefore can also be referred to as a child machine or satellite machine, etc. Furthermore, the transfer order of the second payment machine 12-2 shared by two groups may be first in one group and second in the other group.

[0162] The functions of transaction processing system 200 are basically the same as those of transaction processing system 100 of the first embodiment. Therefore, the flow charts of Figures 6 to 13 described in the first embodiment are also used in the second embodiment as they are, and the description thereof will be omitted.

[0163] However, in the second embodiment, the second payment machine 12-2 is shared by two groups. For this reason, the connection status table 72 describes, as data records related to the second payment machine 12-2, a data record 723 for the group with group number "1" and a data record 726 for the group with group number "2". As a result, the second payment machine 12-2 not only periodically sends a confirmation start notification command to the first registered machine 11-1 which belongs to the group with group number "1", but also periodically sends a confirmation start notification command to the second registered machine 11-2 which belongs to the group with group number "2".

[0164] Figure 19 is a sequence diagram of commands exchanged between the first registration machine (registration machine 1) 11-1 and the second registration machine (registration machine 2) 11-2, and the first payment machine (payment machine 1) 12-1, the second payment machine (payment machine 2) 12-2, and the third payment machine (payment machine 3) 12-3. As shown in the figure, the second payment machine 12-2 sends a confirmation start notification command (Qa) to the first registration machine 11-1, which belongs to the group with group number "1". In response to this confirmation start notification command (Qa), the first registration machine 11-1 sends a status confirmation command (Qb) to the first payment machine 12-1, and upon receiving an acknowledgement command (Qc) from the first payment machine 12-1, it sends a confirmation end notification command (Qd) including payment machine information and payment machine status flag 811 to the second payment machine 12-2. At this time, if the destination change condition is not satisfied, the second payment machine 12-2 does not send a master declaration command (Qe) to the first registered machine 11-1. If the payment machine status flag 811 is "0" and the confirmation completion notification command (Qd) does not contain payment machine information or the payment machine information indicates that an error has occurred in the first payment machine 12-1, and the destination change condition is satisfied, the second payment machine 12-2 sends a master declaration command (Qe) to the first registered machine 11-1.

[0165] Meanwhile, the second payment machine 12-2 also sends a confirmation start notification command (Ra) to the second registration machine 11-2, which belongs to the group with group number "2". Upon receiving this confirmation start notification command (Ra), the second registration machine 11-2 sends a status confirmation command (Rb) to the third payment machine 12-3, and upon receiving a confirmation response command (Rc) from the third payment machine 12-3, it sends a confirmation end notification command (Rd) including payment machine information and a payment machine status flag 812 to the second payment machine 12-2. At this time, if the destination change condition is not satisfied, the second payment machine 12-2 does not send a master declaration command (Re) to the second registration machine 11-2. If the accounting machine status flag 81 is "0" and the confirmation completion notification command (Rd) does not contain accounting machine information, or the accounting machine information indicates that an error has occurred in the third accounting machine 12-3, and the destination change condition is satisfied, the second accounting machine 12-2 sends a master declaration command (Re) to the second registration machine 11-2.

[0166] In the second embodiment configured as described above, as in the first embodiment, it is possible to prevent delays in payment even if an abnormality occurs in the first or third payment machine 12-1 or 12-3, which are set as the destination of payment information. Furthermore, it is possible to reduce the number of payment machines required for the two groups, which has the advantage of reducing equipment costs.

[0167] (Third embodiment) In the first and second embodiments, description has been given of transaction processing systems 100, 200 in which a group is made up of one registration machine 11 and two accounting machines 12. In the third embodiment, description will be given of a transaction processing system in which a group is made up of one registration machine 11 and three or more accounting machines 12.

[0168] [Transaction processing system configuration] 20 is a conceptual diagram of a transaction processing system 300 according to the third embodiment. The transaction processing system 300 includes one registration machine 11 and four accounting machines 12-1, 12-2, 12-3, and 12-4. The registration machine 11 and each of the accounting machines 12-1, 12-2, 12-3, and 12-4 are connected via a network 14. Although not shown, a server 13 is also connected to the network 14, as in the first embodiment.

[0169] The transaction processing system 300 comprises one group consisting of a registration machine 11 and four accounting machines 12-1, 12-2, 12-3, and 12-4. The number of accounting machines 12 may be three or more. Also, for example, a group consisting of three accounting machines 12 and a group consisting of four accounting machines 12 may be mixed to form one transaction processing system.

[0170] The hardware configuration of the registration machine 11 and each of the accounting machines 12-1, 12-2, 12-3, and 12-4 is the same as that in the first embodiment. Therefore, in the third embodiment, Figures 2 and 3 are used as they are, and the description will be omitted.

[0171] 21 is a schematic diagram showing the main data structure of the connection status table 73 held by each of the registration machine 11 and each of the payment machines 12-1, 12-2, 12-3, and 12-4 constituting one group. The connection status table 73 is stored in the auxiliary storage devices 33 and 53, for example.

[0172] As shown in Figure 21, the connection status table 73 describes data records 731, 732, 733, 734, and 735, each of which is composed of the following elements: terminal ID, group number, payment machine number, and transfer order N. Data record 731 is a data record related to the registration machine 11. Data record 732 is a data record related to payment machine 12-1. Data record 733 is a data record related to payment machine 12-2. Data record 734 is a data record related to payment machine 12-3. Data record 735 is a data record related to payment machine 12-4.

[0173] The terminal ID is unique identification information set for each terminal of the registration machine 11-1 and each of the payment machines 12-1, 12-2, 12-3, and 12-4.

[0174] The group number is a number set for each group to identify the group consisting of one registration machine 11 and four accounting machines 12-1, 12-2, 12-3, 12-4. Therefore, the group number in the connection status table 73 for one group is common. The group numbers may or may not be consecutive numbers. It is sufficient that the group numbers do not overlap with the group numbers of other groups.

[0175] The accounting machine number is a consecutive number starting from "1" assigned to each accounting machine in order to individually identify the four accounting machines 12-1, 12-2, 12-3, and 12-4 that make up the same group. Note that the accounting machine number for the registration machine 11 that also makes up the same group is assigned the number "0."

[0176] The transfer priority N is a consecutive number starting from "1" that indicates the transfer priority N for the four payment machines 12-1, 12-2, 12-3, and 12-4 of the payment information sent from the registration machine 11 that constitutes the same group. In this embodiment, the transfer priority N of the payment machine 12-1 with the payment machine number "1" is set to 1st, the transfer priority N of the payment machine 12-2 with the payment machine number "2" is set to 2nd, the transfer priority N of the payment machine 12-3 with the payment machine number "3." is set to 3rd, and the transfer priority N of the payment machine 12-4 with the payment machine number "4" is set to 4th. The transfer priority N is set to "0" for the registration machine 11.

[0177] In the following, for ease of explanation, the payment machine 12-1 with the payment machine number "1" will be referred to as the first payment machine 12-1, the payment machine 12-2 with the payment machine number "2" will be referred to as the second payment machine 12-2, the payment machine 12-3 with the payment machine number "3" will be referred to as the third payment machine 12-3, and the payment machine 12-4 with the payment machine number "4" will be referred to as the fourth payment machine 12-4. The first payment machine 12-1 has the first highest transfer order, so it can also be referred to as the parent machine or master machine, etc. The second payment machine 12-2, the third payment machine 12-3, and the fourth payment machine 12-4 are all second or lower in the transfer order, so they can also be referred to as child machines or satellite machines, etc.

[0178] 22 is a schematic diagram showing the data structure of a payment machine status table 82 held by the registration machine 11. The payment machine status table 82 is stored, for example, in a volatile memory area of ​​the main memory 32. The payment machine status table 82 is a data table for identifying the order of the payment machine set as the destination of payment information among the payment machines 12-1, 12-2, 12-3, 12-4, which are ranked 1st to 4th in the transfer priority N.

[0179] The payment machine status table 82 stores a payment machine status flag for each transfer priority N. The payment machine status flag is one bit of data, either "0" or "1". In this embodiment, the value of the payment machine status flag 81 indicating that the payment machine is set as a destination is "1", and the value of the payment machine status flag 81 indicating that the payment machine is not set as a destination is "0". There is only one payment machine set as a destination. Therefore, the payment machine status flag 81 stored in the payment machine status table 82 is such that the payment machine status flag 81 corresponding to any one of the transfer priorities N is "1", and the payment machine status flag 81 corresponding to the other transfer priorities N is "0". By default, the payment machine status flag 81 with the first transfer priority N is "1", and the payment machine status flags 81 with the second to fourth transfer priorities N are "0". Below, a payment machine with a payment machine status flag 81 set to "1" as a transfer priority N is referred to as a destination payment machine 12-X. The value of the payment machine status flag 81 may be set to "1" to indicate that the payment machine has been set as a destination, and the value of the payment machine status flag 81 may be set to "0" to indicate that the payment machine has not been set as a destination. The payment machine status table 82 is an example of a storage means.

[0180] [Transaction processing system functions] The first function of transaction processing system 300 is similar to that of transaction processing system 100 of the first embodiment, except for the processes of ACT8 to ACT11 executed by processor 31 of registration machine 11 in accordance with the first information process. Therefore, the flow charts of Figures 6, 8 and 9 described in the first embodiment are also adopted in the third embodiment as they are, and the description thereof will be omitted.

[0181] 23 is a flowchart showing the main steps of the process after ACT7 executed by the processor 31 of the registration device 11 in accordance with the first information process. Note that the same reference numerals are used to denote parts common to those in FIG. 7 described in the first embodiment.

[0182] That is, after processor 31 creates the payment information in ACT7 of Figure 6, it proceeds to ACT91 of Figure 23. In ACT91, processor 31 searches the payment machine status table 82 to identify the transfer priority for which the payment machine status flag is "1". Then, in ACT92, processor 31 refers to the connection status table 73 to select the destination payment machine 12-X for which that transfer priority has been set. Then, in ACT12, processor 31 controls the communication unit 35 to send the payment information to the destination payment machine 12-X. Thereafter, processor 31 executes the same processes as ACT13 to ACT16 described in the first embodiment.

[0183] In this way, when the registration machine 11 creates the payment information, it selects a destination payment machine 12-X based on the information in the connection status table 73 and the payment machine status table 82, and transmits the payment information to the destination payment machine 12-X.

[0184] Here, the processor 31 realizes the function of the creation means 311 by executing the process of ACT7 in Fig. 6. Also, the processor 31 realizes the function of the transmission means 312 by executing the processes of ACT91, ACT92, and ACT12 in Fig. 23.

[0185] For example, when the first payment machine 12-1 is the destination payment machine, the payment information is sent from the registration machine 11 to the first payment machine 12-1. At this time, if the first payment machine 12-1 is capable of accepting payments, the customer 22 can use the first payment machine 12-1 to settle the transaction.

[0186] On the other hand, if the first payment machine 12-1 is, for example, in a busy state, the payment information is transmitted from the first payment machine 12-1 to the second payment machine 12-2. Also, if the second payment machine 12-2 is, for example, in a busy state, the payment information is transmitted from the second payment machine 12-2 to the third payment machine 12-3. Therefore, as long as any payment machine belonging to the same group is available for payment, the customer 22 can settle the transaction.

[0187] However, if the destination accounting machine, the first accounting machine 12-1, is down, the payment information is not sent to all accounting machines in the same group, and the customer 22 cannot settle the transaction. In order to eliminate such a malfunction, the transaction processing system 300 also has a second function. The basic part of this second function is also the same as that of the transaction processing system 100 of the first embodiment. That is, in order to realize the second function, the processor 31 of the registration machine 11 has the functions of a status confirmation means 313, a change means 314, and a recovery means 315. The processors 51 of the first accounting machine 12-1, the second accounting machine 12-2, the third accounting machine 12-3, and the fourth accounting machine 12-4 have the functions of a confirmation notification means 512 and a change notification means 513. The function as the status confirmation means 313 is based on the second information processing. The functions as the change means 314 and the recovery means 315 are based on the third information processing. The function as the confirmation notification means 512 is based on the sixth information processing. The function as the change notification means 513 is based on the seventh information processing.

[0188] The sixth information processing procedure executed by the processor 51 of the first payment machine 12-1, the second payment machine 12-2, the third payment machine 12-3 and the fourth payment machine 12-4 is the same as in the first embodiment. Therefore, the third embodiment also adopts Figure 10. In the following, the first payment machine 12-1, the second payment machine 12-2, the third payment machine 12-3 and the fourth payment machine 12-4 will be collectively referred to as payment machine 12-K.

[0189] Processor 51 of payment machine 12-K controls communication unit 55 to send a confirmation start notification command (ACT 52) to registration machine 11 every time the timing for a payment machine confirmation notification (ACT 51) arrives. Through this control, the confirmation start notification command is periodically sent from payment machine 12-K to registration machine 11.

[0190] Here, the processor 51 of the payment device 12-K realizes the function of confirmation notification means 512 by the processing of ACT51 and ACT52.

[0191] 24 is a flow chart showing the procedure of the second information processing executed by the processor 31 of the registration machine 11. The processor 31 waits for a confirmation start notification command in ACT101. When the processor 31 receives the confirmation start notification command via the communication unit 35, it proceeds to YES in ACT101. The processor 31 refers to the payment machine status table 82 in ACT102, and detects the transfer priority N for which the payment machine status flag is set to "1". Next, the processor 31 refers to the connection status table 73 in ACT103, and identifies the terminal ID of the payment machine for which the transfer priority N detected in the processing of ACT102 is set, i.e., the destination payment machine 12-X.

[0192] The processor 31 controls the communication unit 35 to send a status check command to the destination billing machine 12-X as ACT 104. By this control, the status check command is sent to the destination billing machine 12-X.

[0193] The processor 31, which controlled the transmission of the status check command, checks whether a transmission error has occurred in ACT105. For example, if the destination accounting machine 12-X is down, the transmission of the status check command will result in an error. If an error occurs in the transmission of the status check command, the processor 31 proceeds to YES in ACT105 and moves to the processing of ACT108. The processing after ACT108 will be described later.

[0194] The processor 51 of the destination payment machine 12-X, which receives the status confirmation command, collects the information necessary for status confirmation, so-called payment machine information. The processor 51 then controls the communication unit 55 to send an acknowledgement command including the payment machine information to the registration machine 11. This control causes the acknowledgement command to be sent to the registration machine 11. The acknowledgement command includes the payment machine information. The content of the payment machine information is the same as in the first embodiment.

[0195] If the sending of the status confirmation command does not result in an error, the processor 31 proceeds to YES in ACT105. The processor 31 waits for an acknowledgement command from the destination payment machine 12-X in ACT106. When the acknowledgement command is received via the communication unit 35, the processor 31 proceeds to YES in ACT106. The processor 31 stores the payment machine information included in the acknowledgement command in a temporary memory of the main memory 32 in ACT107. The processor 31 then proceeds to ACT108.

[0196] In this way, the processor 31 proceeds to ACT108 when an error occurs in sending the status check command or when the payment machine information in the response command to the status check command is stored in temporary memory.

[0197] The processor 31 acquires data from the payment machine status table 82 in ACT108. The processor 31 then controls the communication unit 35 to send a confirmation end notification command to the payment machine 12-K that sent the confirmation start notification command in ACT109. With this control, if the sender of the confirmation start notification command is the first payment machine 12-1, the confirmation end notification command is sent to the first payment machine 12-1. If the sender of the confirmation start notification command is the second payment machine 12-2, the confirmation end notification command is sent to the second payment machine 12-2. If the sender of the confirmation start notification command is the third payment machine 12-3, the confirmation end notification command is sent to the third payment machine 12-3. If the sender of the confirmation start notification command is the fourth payment machine 12-4, the confirmation end notification command is sent to the fourth payment machine 12-4. The confirmation end notification command includes the data from the payment machine status table 82 acquired in the processing of ACT108. Furthermore, if payment machine information is stored in the temporary memory in ACT107, that payment machine information is also included in the confirmation completion notification command, and the temporary memory is cleared.

[0198] With this, processor 31 ends the second information processing. In this way, the registration machine 11 acquires the payment machine information of the destination payment machine 12-X each time it receives a confirmation start notification command that is periodically transmitted from a payment machine 12-K in the same group. The registration machine 11 then sends a confirmation end notification command to the payment machine 12-K that sent the confirmation start notification command, which includes the acquired payment machine information and the current data in the payment machine status table 82. If payment machine information cannot be acquired from the destination payment machine 12-X, it sends a confirmation end notification command that includes only the data in the payment machine status table 82. In addition to the data in the payment machine status table 82, information indicating that payment machine information could not be acquired may be included.

[0199] Here, the processor 31 of the registration device 11 realizes the function of a status confirmation means 313 by executing the processes of ACT102 to ACT109.

[0200] 25 is a flow chart showing the procedure of the seventh information processing executed by processor 51 of payment machine 12-K in accordance with the payment program. Processor 51 waits for a confirmation completion notification command in ACT111. When processor 51 receives the confirmation completion notification command via communication unit 55, it proceeds to YES in ACT111. Processor 51 refers to connection status table 71 in ACT112, and obtains transfer priority N associated with its own terminal ID. Processor 51 also searches for data in payment machine status table 82 included in the confirmation completion notification command in ACT113, and detects transfer priority M whose payment machine status flag is set to "1".

[0201] The processor 51 checks whether the transfer order M matches the transfer order N in ACT114. If the transfer order M matches the transfer order N, that is, if the own machine is the destination accounting machine 12-X, the processor 51 proceeds to YES in ACT114 and ends the seventh information processing.

[0202] If the transfer priority M does not match the transfer priority N, the processor 51 proceeds to NO in ACT 114. The processor 51 checks whether the transfer priority M is higher than the transfer priority N in ACT 115. If the transfer priority M is higher than the transfer priority N, that is, if the destination payment machine 12-X is a payment machine with a lower transfer priority than the own machine, the processor 51 proceeds to YES in ACT 115 and moves to the processing of ACT 118. The processing after ACT 118 will be described later.

[0203] If transfer priority M is lower than transfer priority N, i.e., if the destination payment machine 12-X is a payment machine with a higher transfer priority than the own machine, the processor 51 proceeds to NO in ACT115. The processor 51 checks whether or not the confirmation completion notification command contains payment machine information for the destination payment machine 12-X in ACT116. If the payment machine information is not included, the processor 51 proceeds to NO in ACT116 and moves to processing in ACT118.

[0204] If the confirmation completion notification command includes payment machine information, the processor 51 proceeds to YES in ACT116. The processor 51 analyzes the payment machine information in ACT117. The processor 51 then determines whether the destination payment machine 12-X is in a state where payment is possible, in the same manner as described as the processing of ACT78 in the first embodiment. If the destination payment machine 12-X is in a state where payment is possible, the processor 51 proceeds to YES in ACT117, and ends the seventh information processing. If the destination payment machine 12-X is not in a state where payment is possible, the processor 51 proceeds to NO in ACT117, and moves to ACT118.

[0205] In this way, processor 51 proceeds to ACT118 if transfer priority M is lower than transfer priority N, if the confirmation completion notification command does not include accounting machine information for destination accounting machine 12-X, or if destination accounting machine 12-X is in a state where accounting is not possible. Processor 51 controls communication unit 55 to send a master declaration command to registration machine 11 as ACT118. This control causes the master declaration command to be sent to registration machine 11. The master declaration command includes the terminal ID of the sending accounting machine 12-K. Having controlled the sending of the master declaration command, processor 51 ends the seventh information processing.

[0206] That is, if the transfer priority M of the destination accounting machine 12-X is higher than its own transfer priority N, the second accounting machine 12-2, third accounting machine 12-3 or fourth accounting machine 12-4 checks whether the confirmation completion notification command contains accounting machine information of the destination accounting machine 12-X. If the accounting machine information is not included, the second accounting machine 12-2, third accounting machine 12-3 or fourth accounting machine 12-4 sends a master declaration command to the registration machine 11. Also, if the accounting machine information is included but the accounting machine information satisfies the destination change condition, the second accounting machine 12-2, third accounting machine 12-3 or fourth accounting machine 12-4 sends a master declaration command to the registration machine 11.

[0207] Here, the processor 51 of the second, third or fourth payment machine 12-2, 12-3 or 12-4 realizes the function of a change notification means 513 by the processing of ACT116 to ACT118.

[0208] On the other hand, the first, second or third payment machine 12-1, 12-2 or 12-3 sends a master declaration command to the registration machine 11 if the transfer priority M of the destination payment machine 12-X is lower than its own transfer priority N.

[0209] Here, the processor 51 of the first payment machine 12-1, the second payment machine 12-2 or the third payment machine 12-3 executes the processing of ACT115 and ACT118 to realize the function of change notification means 513. The former change notification means 513 may be rephrased as first change notification means 513, and the latter change notification means 513 may be rephrased as second change notification means 513.

[0210] 26 is a flow chart showing the procedure of the third information processing executed by the processor 31 of the registration device 11 according to the registration program. The processor 31 waits for a master declaration command in ACT121. When the processor 31 receives the master declaration command via the communication unit 35, the process proceeds to YES in ACT121. The processor 31 checks whether the registration device 11 is idle in ACT122. Idle means a state in which the processor 31 is not executing the first information processing or the second information processing. If the registration device 11 is not idle, the processor 31 proceeds to NO in ACT122 and ends the third information processing.

[0211] If the master declaration command is received while the register 11 is idle, the processor 31 proceeds to YES in ACT 122. In ACT 123, the processor 31 sets all the payment machine status flags in the payment machine status table 82 to "0".

[0212] Processor 31 obtains the terminal ID of the payment machine 12-K that sent the master declaration command in ACT 124. Next, processor 31 refers to the connection status table 73 in ACT 125, and obtains the transfer priority N of the payment machine 12-K in which that terminal ID is set. Then, processor 31 sets the payment machine status flag corresponding to transfer priority N to "1" in ACT 126. With this, processor 31 ends the third information processing.

[0213] In this way, when the destination payment machine 12-X is the first payment machine 12-1, that is, when the payment machine status flag for the first payment machine in the transfer order is "1", the registration machine 11, upon receiving a master declaration command from the second payment machine 12-2, which is second in the transfer order, changes the payment machine status flag for the first payment machine in the transfer order in the payment machine status table 82 to "0" and the payment machine status flag for the second payment machine in the transfer order to "1". As a result, the registration machine 11 selects the second payment machine 12-2 as the destination payment machine 12-X by processing ACT91 and ACT92 in Figure 23, and sends the payment information to the second payment machine 12-2. Then, if the second payment machine 12-2 is available for payment, the customer 22 can use the second payment machine 12-2 to settle the transaction.

[0214] Furthermore, when the destination payment machine 12-X is the second payment machine 12-2, that is, when the payment machine status flag for the second highest in the transfer order is "1", if the registration machine 11 receives a master declaration command from the third payment machine 12-3, which is third in the transfer order, it changes the payment machine status flag for the second highest in the transfer order in the payment machine status table 82 to "0" and the payment machine status flag for the third highest in the transfer order to "1". As a result, in the registration machine 11, the third payment machine 12-3 is selected as the destination payment machine 12-X by processing ACT91 and ACT92 in Figure 23, and the payment information is sent to that third payment machine 12-3. Then, if the third payment machine 12-3 is available for payment, the customer 22 can use the third payment machine 12-3 to settle the transaction.

[0215] On the other hand, when the destination payment machine 12-X is the second payment machine 12-2, that is, when the payment machine status flag for the second highest in the transfer order is "1", if the registration machine 11 receives a master declaration command from the first payment machine 12-1, which is the first highest in the transfer order, it changes the payment machine status flag for the second highest in the transfer order in the payment machine status table 82 to "0" and the payment machine status flag for the first highest in the transfer order to "1". As a result, in the registration machine 11, the first payment machine 12-1 is selected as the destination payment machine 12-X by the processing of ACT91 and ACT92 in Figure 23, and the payment information is sent to that first payment machine 12-1. Then, if the first payment machine 12-1 is available for payment, the customer 22 can use the first payment machine 12-1 to settle the transaction.

[0216] Here, the processor 31 of the registration device 11 realizes the functions of a change means 314 and a recovery means 315 by executing the processes of ACT123 to ACT126.

[0217] Next, in the above-mentioned second function, the sequence of commands exchanged between the registration machine 11 and the first, second, third, and fourth payment machines 12-1, 12-2, 12-3, and 12-4 will be described. 27 is a sequence diagram when the destination accounting machine, the first accounting machine 12-1, goes down. Because the first accounting machine 12-1 is down, it does not send the confirmation start notification command (Pa). As a result, the status confirmation command (Pb), confirmation response command (Pc), and confirmation end notification command (Pd) that were performed between the registration machine 11 and the first accounting machine 12-1 in response to the confirmation start notification command (Pa) are not exchanged either.

[0218] Meanwhile, a confirmation start notification command (Qa) is sent from the second payment machine 12-2. Then, upon receiving this confirmation start notification command (Qa), the registration machine 11 sends a status confirmation command (Qb) to the first payment machine 12-1. However, the sending of the status confirmation command (Qb) results in an error, and the confirmation response command (Qc) cannot be received. For this reason, the confirmation end notification command (Qdz) sent from the registration machine 11 to the second payment machine 12-2 does not include payment machine information. Furthermore, the transfer priority M (=1) of the first payment machine 12-1, which is the destination payment machine, is smaller than the transfer priority N (=2) of the second payment machine 12-2. Therefore, since the destination change condition is satisfied, the second payment machine 12-2 sends a master declaration command (Qe) to the registration machine 11. As a result, the second payment machine 12-2 becomes the destination payment machine 12-X.

[0219] After that, when a confirmation start notification command (Sa) is sent from the third payment machine 12-3, the registration machine 11 sends a status confirmation command (Sb) to the second payment machine 12-2. Then, when the registration machine 11 receives an acknowledgement command (Sc) from the second payment machine 12-2, it sends a confirmation end notification command (Sd) including the payment machine information and data from the payment machine status table 82 to the third payment machine 12-3. At this time, the transfer priority M (= 2) of the second payment machine 12-2, which is the destination payment machine, is lower than the transfer priority N (= 3) of the third payment machine 12-3. Then, if the payment machine information does not satisfy the destination change condition, the third payment machine 12-3 does not send a master declaration command to the registration machine 11. The same applies when a confirmation start notification command (Ta) is sent from the fourth payment machine 12-4.

[0220] Figure 28 is a sequence diagram when the second payment machine 12-2 also goes down. Because the first payment machine 12-1 and the second payment machine 12-2 are down, they do not send confirmation start notification commands (Pa, Qa). As a result, the exchange of the status confirmation command (Pb), confirmation response command (Pc), and confirmation end notification command (Pd) between the registration machine 11 and the first payment machine 12-1, and the exchange of the status confirmation command (Qb), confirmation response command (Qc), and confirmation end notification command (Qd) between the registration machine 11 and the second payment machine 12-2 are also not performed.

[0221] Meanwhile, a confirmation start notification command (Sa) is sent from the third payment machine 12-3. Then, upon receiving this confirmation start notification command (Sa), the registration machine 11 sends a status confirmation command (Sb) to the second payment machine 12-2, which is the destination payment machine. However, the sending of the status confirmation command (Sb) results in an error, and the confirmation response command (Sc) cannot be received. For this reason, the confirmation end notification command (Sd) sent from the registration machine 11 to the third payment machine 12-3 does not include payment machine information. In addition, the transfer priority M (=2) of the second payment machine 12-2, which is the destination payment machine, is smaller than the transfer priority N (=3) of the third payment machine 12-3. Therefore, since the destination change condition is satisfied, the third payment machine 12-3 sends a master declaration command (Se) to the registration machine 11. As a result, the third payment machine 12-3 becomes the destination payment machine 12-X.

[0222] Thereafter, when a confirmation start notification command (Ta) is sent from the fourth payment machine 12-4, the registration machine 11 sends a status confirmation command (Tb) to the third payment machine 12-3. Then, when the registration machine 11 receives a confirmation response command (Tc) from the third payment machine 12-3, it sends a confirmation end notification command (Td) including payment machine information and data from the payment machine status table 82 to the fourth payment machine 12-4. At this time, the transfer priority M (=3) of the destination payment machine, the third payment machine 12-3, is smaller than the transfer priority N (=4) of the fourth payment machine 12-4. Then, if the payment machine information does not satisfy the destination change condition, the fourth payment machine 12-4 does not send a master declaration command to the registration machine 11.

[0223] Figure 29, like Figure 28, is a sequence diagram showing a case where not only the first accounting machine 12-1 but also the second accounting machine 12-2, which was the destination accounting machine, goes down, and a confirmation start notification command (Ta) is sent first from the fourth accounting machine 12-4 to the registration machine 11.

[0224] As shown in the figure, upon receiving the confirmation start notification command (Ta) from the fourth payment machine 12-4, the registration machine 11 sends a status confirmation command (Tb) to the second payment machine 12-2. However, the transmission of the status confirmation command (Tb) results in an error, and the confirmation response command (Tc) cannot be received. For this reason, the confirmation end notification command (Td) sent from the registration machine 11 to the fourth payment machine 12-4 does not include payment machine information. In addition, the transfer priority M (=2) of the second payment machine 12-2, which is the destination payment machine, is smaller than the transfer priority N (=4) of the fourth payment machine 12-4. Therefore, since the destination change condition is satisfied, the fourth payment machine 12-4 sends a master declaration command (Te) to the registration machine 11. As a result, the fourth payment machine 12-4 becomes the destination payment machine 12-X.

[0225] After that, when a confirmation start notification command (Sa) is sent from the third payment machine 12-3, the registration machine 11 sends a status confirmation command (Sb) to the fourth payment machine 12-4. Then, when the registration machine 11 receives a confirmation response command (Sc) from the fourth payment machine 12-4, it sends a confirmation end notification command (Sd) including payment machine information and data from the payment machine status table 82 to the third payment machine 12-3. At this time, the transfer priority M (=4) of the fourth payment machine 12-4, which is the destination payment machine, is higher than the transfer priority N (=3) of the third payment machine 12-3. Therefore, since the destination change condition is satisfied, the third payment machine 12-3 sends a master declaration command (Se) to the registration machine 11. As a result, the third payment machine 12-3 becomes the destination payment machine 12-X.

[0226] FIG. 30 is a sequence diagram when the first accounting machine 12-1, which was down, recovers, when the third accounting machine 12-3 is the destination accounting machine 12-X. The recovered first accounting machine 12-1 sends a confirmation start notification command (Pa) to the registration machine 11. Upon receiving this confirmation start notification command (Pa), the registration machine 11 sends a status confirmation command (Pb) to the third accounting machine 12-3. Then, when the registration machine 11 receives an acknowledgement command (Pc) from the third accounting machine 12-3, it sends a confirmation end notification command (Pd) including the accounting machine information and data from the accounting machine status table 82 to the first accounting machine 12-1. At this time, the transfer priority M (=3) of the third accounting machine 12-3, which is the destination accounting machine, is higher than the transfer priority N (=1) of the first accounting machine 12-1. Therefore, since the destination change condition is satisfied, the first accounting machine 12-1 sends a master declaration command (Pe) to the registration machine 11. As a result, the first payment device 12-1 becomes the destination payment device 12-X.

[0227] Thereafter, when a confirmation start notification command (Sa) is sent from the third payment machine 12-3, the registration machine 11 sends a status confirmation command (Sb) to the first payment machine 12-1. Then, when the registration machine 11 receives a confirmation response command (Sc) from the first payment machine 12-1, it sends a confirmation end notification command (Sd) including payment machine information and data from the payment machine status table 82 to the third payment machine 12-3. At this time, the transfer priority M (=1) of the first payment machine 12-1, which is the destination payment machine, is lower than the transfer priority N (=3) of the third payment machine 12-3. Then, if the payment machine information does not satisfy the destination change condition, the third payment machine 12-3 does not send a master declaration command to the registration machine 11.

[0228] In the sequence example shown in Figures 27 to 30, the payment machine 12-K is shown to send a confirmation start notification command (Pa, Qa, Sa, Ta) after a confirmation end notification command (Pd, Qd, Sd, Td) is sent from the registration machine 11. However, in reality, the registration machine 11 may receive a confirmation start notification command from another payment machine 12-K before sending a confirmation end notification command to one payment machine 12-K. In such a case, after sending a confirmation end notification command to one payment machine 12-K, the registration machine 11 executes processing in response to the confirmation start notification command from the other payment machine 12-K, that is, sending a status confirmation command, receiving a confirmation response command, and sending a confirmation end notification command.

[0229] As described above in detail, with the transaction processing system 300, even if the destination accounting machine 12-X goes down and it becomes impossible to send payment information to the destination accounting machine 12-X from the registration machine 11, it is possible to immediately set another accounting machine 12-K as the destination accounting machine 12-X. The same applies if a failure such as a printer error or change dispenser error occurs in the destination accounting machine 12-X and payment becomes impossible. Therefore, even if an abnormality occurs in the destination accounting machine 12-X, it is possible to prevent delays in transaction settlement. As a result, a transaction processing system with high processing efficiency can be provided.

[0230] Furthermore, when a payment machine 12-K that is higher in the transfer order than the current destination payment machine 12-X recovers, the recovered payment machine 12-K can be quickly returned to the destination payment machine 12-X. Generally, in semi-self-service type transaction processing systems, there is a tendency to give higher transfer orders to payment machines that have good customer movement efficiency. Therefore, it is possible to minimize the impact of an abnormality in the payment machine 12-1 that is higher in the transfer order.

[0231] In the third embodiment, one or more accounting machines may be shared by different groups, as in the second embodiment. In that case, the shared accounting machine will also send a confirmation start notification command (Qa, Ra) to the registration machine 11 of each group.

[0232] Although several embodiments of the present invention have been described above, 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 gist of the invention. These embodiments and their modifications are included within the scope of the invention and the scope of the invention and its equivalents described in the claims. [Explanation of symbols]

[0233] 11, 11-1, 11-2... registration machine (input processing device), 12, 12-1, 12-2, 12-3, 12-4... accounting machine (payment device), 13... server, 14... network, 15... product master file, 21... store clerk, 22... customer, 31, 51... processor, 32, 52... main memory, 33, 53... auxiliary storage device, 34, 54... clock, 35, 55... communication unit, 36... keyboard, 37, 57... scanner, 38, 58... touch panel, 39... customer display, 40, 59... printer, 41, 62... system transmission path, 56... change machine interface, 60... reader / writer, 61... patrol lamp, 71, 72, 73... connection status table, 81... accounting machine status flag, 82... accounting machine status table.

Claims

1. an input processing device that creates payment information necessary for settling a transaction with a customer based on the input data; three or more payment devices that execute a payment process for the transaction based on the payment information; Equipped with A transaction processing system in which a transfer priority of the payment information is set for each of the three or more payment devices, The input processing device includes: a transmitting means for transmitting the payment information to a destination payment device set as a destination among the three or more payment devices; A status confirmation means for confirming the status of the destination payment device; a change means for changing a destination of the payment information to the other payment device when a notification of a change of destination is received from the other payment device other than the destination payment device; Equipped with The three or more payment devices, A confirmation notification means for notifying the input processing device of a status confirmation of the destination payment device; a change notification means for notifying the input processing device of a change in destination when a status confirmation result of the destination payment device, which is responded to by the input processing device in response to the notification of the status confirmation, satisfies a condition for changing the destination of the payment information; A transaction processing system comprising:

2. the status confirmation means is means for acquiring information relating to a status of the destination payment device from the destination payment device, The transaction processing system described in claim 1, wherein the change notification means notifies the input processing device of a change in destination when the transfer priority of the destination payment device included in the status confirmation result is higher than the transfer priority of the own device and when the input processing device responds as the status confirmation result of the destination payment device that it was unable to obtain information related to the status from the destination payment device.

3. The transaction processing system of claim 2, wherein the change notification means notifies the input processing device of a change of destination when the transfer priority of the destination payment device included in the status confirmation result is higher than the transfer priority of the own device, and when the input processing device responds with information regarding the status acquired from the destination payment device as the status confirmation result of the destination payment device, and when the information regarding the status satisfies a destination change condition.

4. A transaction processing system as described in any one of claims 1 to 3, wherein the change notification means notifies the input processing device of a change in destination when the transfer priority of the destination payment device included in the status confirmation result is lower than the transfer priority of the own device.

5. The input processing device includes: The method further includes storing a transfer order of the payment device set as the destination payment device among the three or more payment devices, 5. A transaction processing system according to claim 2, further comprising: a notification of information stored in said storage means together with the status confirmation result of said destination settlement device.

6. The three or more payment devices, The notification means periodically notifies the user of the status confirmation; The input processing device includes: performing a status confirmation by the status confirmation means in response to the notification of the status confirmation, and responding with a result of the status confirmation to the settlement device that issued the notification; A transaction processing system according to any one of claims 1 to 5.

7. A payment device in a transaction processing system comprising: an input processing device which creates payment information necessary for settlement of a transaction with a customer based on input data; and three or more payment devices which execute settlement processing of the transaction based on the payment information, wherein a transfer priority of the payment information is set for each of the three or more payment devices, A confirmation notification means for notifying the input processing device of a status confirmation of the destination settlement device set as the destination; a change notification means for notifying the input processing device of a change in destination when a status confirmation result of the destination payment device, which is responded to by the input processing device in response to the notification of the status confirmation, satisfies a condition for changing the destination of the payment information; A payment device comprising:

8. An input processing device constituting a transaction processing system and three or more payment devices that execute a transaction settlement process based on settlement information required for settlement of a transaction with a customer, A creating means for creating the payment information based on input data; a transmitting means for transmitting the payment information to a destination payment device set as a destination among the three or more payment devices; A status confirmation means for confirming the status of the destination payment device; a change means for changing a destination of the payment information to the other payment device when a notification of a change of destination is received from the other payment device other than the destination payment device; An input processing device comprising:

9. a computer of a payment device in a transaction processing system, the computer comprising: an input processing device which creates payment information necessary for a transaction with a customer based on input data; and three or more payment devices which execute a payment process for the transaction based on the payment information, the three or more payment devices being set with a transfer priority of the payment information; A confirmation notification means for notifying the input processing device of a status confirmation of the destination settlement device set as the destination; and a change notification means for notifying the input processing device of a change in destination when a status confirmation result of the destination payment device, which is responded to by the input processing device in response to the notification of the status confirmation, satisfies a condition for changing the destination of the payment information; A program to function as a

10. A transaction processing system includes three or more payment devices that execute transaction settlement processing based on settlement information required for settlement of transactions with customers, and an input processing device computer that constitutes the transaction processing system. A creating means for creating the payment information based on input data; a transmission means for transmitting the payment information to a destination payment device set as a destination among the three or more payment devices; A status confirmation means for confirming the status of the destination payment device; and a change means for changing a destination of the payment information to the other payment device when a notification of a change of destination is received from the other payment device other than the destination payment device; A program to function as a

Images