JP2024067470A - Transaction processing system, payment device, and payment program - Google Patents

Abstract

[Problem] To prevent a decrease in processing efficiency in a transaction processing system using a sharing method in which operations are shared between store clerks and customers. [Solution] An input processing device creates payment information for a transaction based on input data, and transmits the payment information to a specified one of multiple payment devices. When the payment device that has received the payment information is in a state in which it can execute the payment process, it executes the payment process based on the payment information received by the receiving means. When the payment device is in a state in which it cannot execute the payment process, the payment device searches for information indicating the connection status of multiple payment devices to the network, and selects one of the other payment devices that are connected to the network. The payment device transfers the payment information to the selected other payment device. [Selected Figure] Figure 4

Description

Embodiments of the present invention relate to a transaction processing system, a payment device of the system, and a payment program for causing a computer to function as a payment device.

In recent years, a transaction processing system for mass retailers has become known that shares operations between store clerks and customers. This type of transaction processing system separates an input processing device that accepts data input for the products to be bought and sold in each transaction from a payment device that executes the payment process for the transaction based on the product data input by the input processing device. The system is then arranged so that the store clerk operates the input processing device and the customer operates the payment device.

In a sharing transaction processing system, the product data is input by a store clerk, so the time required for data input is shorter than in a self-service transaction processing system in which the customer performs all operations themselves. On the other hand, because the customer operates the payment device, it is expected that customers who are unfamiliar with the operation will have difficulty making payments. Therefore, a sharing transaction processing system generally has one input processing device and, for example, three or more payment devices. The transfer order of payment information is preset for the three or more payment devices.

The input processing device transmits the information necessary for the 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 settlement 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 transfers (sends) the information necessary for the settlement of the transaction to the payment device (second payment device) that is second in the transfer order. The second payment device processes the settlement 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, it transfers the information necessary for the settlement of the transaction to the payment device (third payment device) that is third in the transfer order. The third payment device processes the settlement of the transaction based on the information received from the second payment device. In this way, the conventional transaction processing system using the shared method efficiently operates three or more payment devices, making it possible to settle many transactions in a short period of time.

However, for example, if the second payment device is powered off and is unable to receive the information necessary to settle the transaction, the information necessary to settle the transaction will not be transferred from the second payment device to the third payment device. As a result, not only the second payment device but also payment devices lower in the transfer order than the second payment device will be unable to process the settlement of the transaction, resulting in reduced processing efficiency.

JP 2013-242839 A

The problem that the embodiment of the present invention aims to solve is to prevent a decline in processing efficiency in a transaction processing system that uses a shared system in which operations are shared between store clerks and customers.

In one embodiment, the transaction processing system includes an input processing device and a plurality of payment devices connected via a network. The input processing device includes a creation means and a transmission means. The creation means creates payment information related to the transaction based on the input data. The transmission means transmits the payment information via the network to a predetermined payment device among the plurality of payment devices. The payment device includes a reception means, an execution means, a selection means, and a transfer means. The reception means receives the payment information via the network. When the payment device is in a state where it can execute the payment process, the execution means executes the payment process based on the payment information received by the reception means. When the payment device is in a state where it cannot execute the payment process, the selection means searches for information indicating the connection status of the plurality of payment devices to the network, and selects one of the other payment devices that are connected to the network. The transfer means transfers the payment information to the other payment device selected by the selection means.

FIG. 1 is a schematic diagram showing a schematic configuration of a transaction processing system according to an embodiment. FIG. 2 is a block diagram showing the main circuit configuration of an input processing device that constitutes the transaction processing system. FIG. 3 is a schematic diagram showing the data structure of a data table held by the input processing device. FIG. 4 is a block diagram showing the main circuit configuration of a settlement device constituting the transaction processing system. FIG. 5 is a schematic diagram showing the data structure of a data table held by the settlement device. FIG. 6 is a flowchart showing the main steps of the first information processing executed by the processor of the input processing device in accordance with the registration program. FIG. 7 is a flowchart showing a procedure of a third information processing executed by the processor of the payment device in accordance with the payment program. FIG. 8 is a flowchart showing a fourth information processing procedure executed by the processor of the payment device in accordance with the payment program. FIG. 9 is a flowchart showing the procedure of the second information processing executed by the processor of the input processing device in accordance with the registration program. FIG. 10 is a diagram illustrating the operation of the transaction processing system when the first settlement device set as the master is in a state in which settlement processing is possible. FIG. 11 is a diagram illustrating the operation of the transaction processing system when payment processing is not possible in the first payment device. FIG. 12 is a diagram illustrating the operation of the transaction processing system when the second payment device cannot receive the payment information transferred from the first payment device. FIG. 13 is a diagram illustrating the operation of the transaction processing system when payment information is retransmitted from the input processing device. FIG. 14 is a flowchart showing a procedure of a third information processing executed by the processor of the payment device in accordance with the payment program in the second embodiment. FIG. 15 is a flowchart showing the main steps of a first information processing operation executed by the processor of the input processing device in accordance with a registration program in the second embodiment.

Below, we will use the drawings to explain an embodiment that prevents a decline in processing efficiency in a transaction processing system that uses a sharing method in which operations are shared between store clerks and customers.

[First embodiment]
[Description of the configuration of the transaction processing system]
First, the configuration of a 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.

Figure 1 is a schematic diagram showing the general configuration of a transaction processing system 100. The transaction processing system 100 includes an input processing device 11, a payment device 12, a server 13, and a network 14 that connects these. There are no particular limitations on the type of network 14, but a wired or wireless LAN (local area network) is generally used.

The input processing device 11 is a device configured to accept data input for each transaction of the products to be bought and sold in that transaction. The payment device 12 is a device configured to perform payment processing for the transaction based on the product data input by the input processing device 11. The input processing device 11 is operated by a store clerk 21 who plays a role called a checker. The payment device 12 is operated by a consumer who purchases products in the store, a so-called customer 22. In FIG. 1, the input processing device 11 is attached to a work table 23. The work table 23 has a rectangular top. A passage for customers 22, a so-called checkout lane, is formed by arranging multiple work tables 23 so that the longitudinal directions of the tops are approximately parallel.

The input processing device 11 and the payment device 12 are arranged for each checkout lane in the store. For each checkout lane, one input processing device 11 and multiple payment devices 12 are arranged. Various data signals are exchanged between the input processing device 11 and the payment device 12 arranged in the same checkout lane via the network 14. The data signals may be exchanged via the server 13 or may be exchanged without going through the server 13.

Figure 1 shows an example in which one input processing device 11 and three payment devices 12 (12-1, 12-2, 12-3) are arranged in one checkout lane. Although not shown, one input processing device 11 and two or more payment devices 12 are arranged in other checkout lanes as well. All three payment devices 12 (12-1, 12-2, 12-3) execute payment processing for transactions processed by the input processing device 11 arranged in the same checkout lane. At least one of the three payment devices 12 (12-1, 12-2, 12-3) may execute payment processing for transactions processed by the input processing device 11 arranged in an adjacent checkout lane.

Of the three payment devices 12 (12-1, 12-2, 12-3), one is set as the parent device, and the other two are set as child devices. In this embodiment, it is assumed that payment device 12-1 is set as the parent device, and payment devices 12-2 and 12-3 are set as child devices. Note that child payment devices 12-2 and 12-3 have the function of monitoring the status of parent payment device 12-1, and declaring themselves to be the parent device when payment device 12-1 goes down. In response to this declaration, the input processing device 11 sets one of child payment devices 12-2 and 12-3 as the parent device.

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 connected to an external device of the server 13.

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

A product code is a unique code assigned to each product to identify it. Typically, each product is affixed with a barcode or two-dimensional code that represents the product code. Alternatively, an RFID (Radio Frequency Identification) tag that stores the product code may be attached. The input processing device 11 can input the product code of a product being bought and sold in a transaction by reading the barcode, two-dimensional code, or RFID tag attached to the product with a reading device.

The product name and unit price are the name of the product identified by the product code and the price per item. The attributes are, for example, information about the tax on the product. Information about taxes includes tax rates, tax types (tax-exclusive, tax-included, tax-exempt), etc.

Figure 2 is a block diagram showing the main circuit configuration of the input processing device 11. The input processing device 11 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.

The input processing device 11 constitutes a computer by connecting the processor 31 to the main memory 32, the auxiliary storage device 33, the clock 34, and the communication unit 35 via a system transmission path 41. The input processing device 11 then 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 path 41.

The processor 31 corresponds to the central part of the computer. The processor 31 controls each part to realize various functions of the input processing device 11 according to an operating system or an application program. The processor 31 is, for example, a CPU (Central Processing Unit).

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 application programs in the nonvolatile memory area. The main memory 32 may also store data required for the processor 31 to execute processes for controlling each part in a 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).

The auxiliary storage device 33 corresponds to the auxiliary storage portion of the computer. For example, the auxiliary storage device 33 may be an Electric Erasable Programmable Read-Only Memory (EEPROM), a Hard Disk Drive (HDD), or a Solid State Drive (SSD). 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 application programs described above.

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. The communication unit 35 is an interface for data communication between the server 13 and the multiple payment devices 12 connected via the network 14. The keyboard 36 is an input device on which various keys necessary for inputting data related to the products purchased by the customer, i.e., the purchased products, are arranged. The scanner 37 is an input device that reads and inputs code symbols such as barcodes and two-dimensional codes. The touch panel 38 is a device that combines an input device and a display device. The touch panel 38 displays information to the store clerk who is the operator of the input processing device 11, and accepts operation input by the store clerk. The customer display 39 displays information to the customer 22 whose purchased product data is registered in the input processing device 11. The printer 40 issues receipts by printing various character strings or images on receipt paper.

As the hardware for such an input processing device 11, for example, an existing POS terminal can be used. Note that the devices connected to the input processing device 11 are not limited to the keyboard 36, scanner 37, touch panel 38, customer display 39, and printer 40. Devices required for the application of the input processing device 11 may be added, or some devices may be omitted.

In the input processing device 11 configured as above, the processor 31 has the functions of a creation means 311, a transmission means 312, and a confirmation means 313. The creation means 311 has a function of creating payment information related to a transaction based on data input via an input device such as a keyboard 36, a scanner 37, or a touch panel 38.

The transmission means 312 is a function that transmits payment information via the network 14 to the payment device 12-1 set as the parent device among the multiple payment devices 12 (12-1, 12-2, 12-3). The payment information includes items such as a transaction number, transaction date and time, terminal ID, product sales data, total points, 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 made. The terminal ID is identification information set in the input processing device 11 that processed the transaction. A unique terminal ID is set in advance in each input processing device 11. Incidentally, a unique terminal ID is also set in each payment device 12. The product sales data consists of items such as the product code, product name, unit price, sales points, sales amount, and attributes of the product purchased by the customer 22. The payment information includes product sales data for all products purchased by the customer 22 in the transaction. The total points is the sum of the sales points of the product sales data in one transaction. The total amount is the sum of the sales amounts of the product sales data for one transaction.

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.

The confirmation means 313 is a function for confirming the operating status of multiple payment devices 12 (121, 12-2, 12-3) arranged in the same checkout lane as the input processing device 11. The processor 31 uses the data table 321 to confirm the operating status of each payment device 12 (121, 12-2, 12-3).

Figure 3 is a schematic diagram showing the data structure of data table 321. Data table 321 is provided in the volatile memory area of main memory 32. As shown in the figure, data table 321 has a data structure that stores a parent device flag F and a connection count N in association with each payment device ID of multiple payment devices 12 (121, 12-2, 12-3).

The parent device flag F is 1-bit data indicating whether the payment device 12 identified by the payment device ID is a parent device or not. In this embodiment, the parent device flag F indicating that it is a parent device is set to "1", and the parent device flag F indicating that it is a child device other than the parent device is set to "0". Incidentally, FIG. 3 shows a case in which the first payment device 12-1 with a payment device ID of "121" is the parent device, and the second payment device 12-2 with a payment device ID of "122" and the third payment device 12-3 with a payment device ID of "123" are all child devices.

The number of connections N is a counter that is incremented each time the input processing device 11 confirms that it is connected to a payment device 12 identified by the payment device ID. In this embodiment, the number of connections N of the first payment device 12-1 is Na, the number of connections N of the second payment device 12-2 is Nb, and the number of connections N of the third payment device 12-3 is Nc.

The functions of the creation means 311 and the transmission means 312 are realized by a first information processing executed by the processor 31 according to the registered program. The function of the confirmation means 313 is realized by a second information processing executed by the processor 31 according to the registered program. The first information processing and the second information processing will be described later.

The registered program is a type of application program stored in the main memory 32 or the auxiliary storage device 33. There are no particular limitations on the method for installing the registered program in the main memory 32 or the auxiliary storage device 33. The registered program can be installed in the main memory 32 or the auxiliary storage device 33 by recording it on a removable recording medium, or by distributing it by communication via the network 14. The recording medium can 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.

The program that causes the computer to realize the functions of the confirmation means 313 may be separate from the program that causes the computer to realize the functions of the creation means 311 and the transmission means 312.

Figure 4 is a block diagram showing the main circuit configuration of the payment device 12. In this embodiment, the payment devices 12-1, 12-2, and 12-3 have the same configuration. Therefore, in Figure 4, the payment devices 12-1, 12-2, and 12-3 will not be distinguished from each other and will be described as payment device 12.

The payment device 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 patrol lamp 61, and a system transmission path 62. The system transmission path 62 includes an address bus, a data bus, a control signal line, and the like. The system transmission path 62 connects the processor 51 to each of the other parts directly or via a signal input/output circuit, and transmits data signals exchanged between them.

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

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

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 application programs in the nonvolatile memory area. The main memory 52 may also 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.

The auxiliary storage device 53 corresponds to the auxiliary storage portion of the computer. For example, the auxiliary storage device 53 can be an EEPROM, HDD, or SSD. 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 application programs described above.

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. The communication unit 55 communicates data with the server 13 or the input processing device 11 connected via the network 14. The change machine interface 56 constitutes an interface with an automatic change machine (not shown). The change machine interface 56 inputs amount data of coins inserted into the automatic change machine from the automatic change machine. The change machine interface 56 outputs change data from the settlement device 12 to the automatic change machine. Having input the change data, the automatic change machine automatically pays out coins equivalent to the change data as change.

The scanner 57 is an input device for reading code symbols such as barcodes and two-dimensional codes. 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 device 12, and accepts operational input from the customer 22. The printer 59 issues receipts by printing various characters or images on receipt paper.

The reader/writer 60 has the function of reading data recorded on a medium such as a card or a smartphone, and the 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.

The patrol lamp 61 has light-emitting elements of two colors, for example, red and blue. The patrol lamp 61 is provided at the top of a pole that is erected in the vicinity of the payment device 12 in correspondence with the payment device 12, and lights up or flashes, for example, in red or blue, depending on the state of the corresponding payment device 12.

As the hardware for such a payment device 12, for example, an existing self-service POS terminal, a so-called self-checkout register, can be used. The devices connected to the payment device 12 are not limited to the scanner 57, touch panel 58, printer 59, reader/writer 60, and patrol lamp 61. Devices required for the purpose of the payment device 12 may be added, or some devices may be omitted.

In the payment device 12 configured in this manner, the processor 51 has the functions of a receiving means 511, an executing means 512, a selecting means 513, a transferring means 514, a changing means 515, a notifying means 516, and a restoring means 517.

The receiving means 511 is a function that receives payment information transmitted from the input processing device 11 via the network 14 using the communication unit 55. The executing means 512 is a function that executes payment processing based on the payment information received by the receiving means 511 when the payment device 12 equipped with the processor 51 is in a state in which it can execute payment processing. In the following, the payment device 12 equipped with the processor 51 is referred to as the payment device 12, and other payment devices 12 are referred to as other payment devices.

The selection means 513 is a function that searches for information indicating the connection status of other payment devices 12 to the network 14 when the payment device 12 is in a state where it cannot execute the payment process, and selects one of the other payment devices 12 that are connected to the network 14. The processor 51 uses the data table 521 to select another payment device 12 that is connected to the network 14.

Figure 5 is a schematic diagram showing the data structure of data table 521. Data table 521 is provided in the volatile memory area of main memory 52. As shown in the figure, data table 521 has a data structure that stores a transfer order R and a status S in association with each payment device ID of multiple payment devices 12 (12-1, 12-2, 12-3).

The transfer order R is the priority order when transferring payment information between multiple payment devices 12 (12-1, 12-2, 12-3). In this embodiment, the transfer order R of the first payment device 12-1 with a payment device ID of "121" is set to 1st, the transfer order R of the second payment device 12-2 with a payment device ID of "122" is set to 2nd, and the transfer order R of the third payment device 12-3 with a payment device ID of "123" is set to 3rd. Note that the payment device 12-1 with the transfer order R of 1st is not necessarily the parent device. As described above, the payment devices 12-2 to 12-3 set as child devices have the function of monitoring the status of the parent payment device 12-1 and declaring that they will become the parent device when the payment device 12-1 goes down. Therefore, the payment device 12-2 or the payment device 12-3 may become the parent device.

The status S is information indicating the connection state of the multiple payment devices 12 (12-1, 12-2, 12-3) to the network 14. There are three types of connection states: online state, offline state, and recovery state. The online state is a state in which the payment device 12 can receive data transmitted through the network 14. The offline state is a state in which the payment device 12 cannot receive data transmitted through the network 14. For example, a payment device 12 whose power is turned off is in the offline state. For example, a payment device 12 whose communication system has an abnormality is also in the offline state. The recovery state is a state in which the payment device 12 has recovered from the offline state to the online state. In this embodiment, the status S representing the online state is "0", the status S representing the offline state is "2", and the status S representing the recovery state is "1". The status S of the first payment device 12-1 is Sa, the status S of the second payment device 12-2 is Sb, and the status S of the third payment device 12-3 is Sc.

Returning to the explanation of FIG.
The transfer means 514 is a function of transferring (transmitting) the payment information to the other payment device 12 selected by the selection means 513. The change means 515 is a function of changing the status S, i.e., information indicating the connection state, for the other payment device 12 to which the transfer by the transfer means 514 has failed, from the value "0" indicating a state connected to the network 14 to the value "2" indicating a state disconnected from the network 14. The notification means 516 is a function of notifying the input processing device 11 of the transfer failure, when the transfer by the transfer means 514 has failed. The recovery means 517 is a function of changing the status S, i.e., information indicating the connection state, for the other payment device 12, from the information value "2" indicating a state disconnected from the network 14 to the information value "1" indicating a restored state, when the other payment device 12 disconnected from the network 14 is connected to the network 14.

The functions of the receiving means 511, the executing means 512, the selecting means 513, the transferring means 514, the changing means 515 and the notifying means 516 are realized by a third information processing executed by the processor 51 according to the payment program. The function of the recovery means 517 is realized by a fourth information processing executed by the processor 51 according to the payment program. The third information processing and the fourth information processing will be described later.

The payment program is a type of application program stored in the main memory 52 or the auxiliary storage device 53. There are no particular limitations on the method for installing the payment program in the main memory 52 or the auxiliary storage device 53. The payment program can be installed in the main memory 52 or the auxiliary storage device 53 by recording it on a removable recording medium, or by distributing the payment program by communication via the network 14. The recording medium can 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.

The program that causes the computer to realize the functions of the recovery means 517 may be separate from the program that causes the computer to realize the functions of the receiving means 511, the executing means 512, the selecting means 513, the forwarding means 514, the changing means 515, and the notifying means 516.

[Description of Information Processing]
Next, the contents and procedures of the main information processing of the input processing device 11 and the settlement device 12 constituting the transaction processing system 100 will be explained using the flowcharts of Figures 6 to 9. Note that the contents and procedures of the information processing explained below are merely examples. The contents and procedures can be changed as appropriate as long as the same operational effects can be achieved.

Figure 6 is a flow chart showing the main steps of the first information processing executed by the processor 31 of the input processing device 11 in accordance with the registration program. The customer 22 places the products he or she wishes to purchase from those displayed in the sales area into a shopping basket or the like, and heads to the checkout lane. When the customer 22 reaches the checkout lane, the store clerk 21, who acts as a checker, declares the start of registration to the input processing device 11. In response to this operation, the processor 31 starts the first information processing.

First, the processor 31 displays a registration screen on the touch panel 38 in ACT 1. The registration screen is a screen that, for example, has a details area and a total area, as well as a subtotal button and the like. The details area is an area for displaying the product name, quantity, unit price, and amount in list format in sequential numerical order. The total area is an area for displaying the total quantity (points) and total amount (yen) displayed in the details area. The subtotal button is an operator that the store clerk 21 touches to instruct the output of a subtotal for the products purchased by the customer 22.

After controlling the display of the registration screen, the processor 31 waits for data relating to the product to be input in ACT 2. Many products are affixed with a barcode indicating the product code, which is the product's identification information. The store clerk 21 operates the scanner 37 to read the barcode attached 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 input processing device 11. On the other hand, some products, such as fresh foods, may not have a barcode attached. If the purchased product does not have a barcode attached, the store clerk 21 touches a product button corresponding to the purchased product from the group of 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 input processing device 11.

When the product code is input, the processor 31 proceeds from ACT 2 to ACT 3. The processor 31 executes product sales data processing in ACT 3. 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 writes the product sales data, including items such as the product code, product name, unit price, sales quantity, sales amount, attributes, etc., into the transaction memory. The transaction memory is part of the volatile memory area in the main memory 32.

After completing the product sales data processing, the processor 31 checks whether the subtotal button has been pressed in ACT 4. The store clerk performs operations in sequence 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.

If the subtotal button is not pressed and the product code of the next purchased item is entered, the processor 31 returns from ACT 4 to ACT 2 and then proceeds to ACT 3. That is, the processor 31 executes product sales data processing based on the product code of the purchased item. As a result, the product sales data of the purchased item is stored sequentially in the transaction memory.

When the subtotal button is input, the processor 31 proceeds from ACT 4 to ACT 5. The processor 31 displays the subtotal screen in ACT 5. The subtotal screen is a screen on which a total area is arranged, and a checkout button and the like are also arranged. The total area is the same as the total area on the registration screen. The checkout button is an operator that the store clerk 21 touches to instruct the customer 22 to move on to checkout. After checking the subtotal screen, the store clerk 21 touches the checkout button.

After controlling the display of the sub-menu screen, processor 31 waits for the checkout button to be pressed in ACT 6. When the checkout button is pressed, processor 31 proceeds from ACT 6 to ACT 7. Processor 31 creates payment information in ACT 7. That is, processor 31 creates the payment information required to settle the transaction based on the product sales data and total number and total amount data for each purchased item stored in the transaction memory, and transaction specific data such as the transaction number, transaction date and time, and the terminal ID of the input processing device 11.

When the processor 31 has finished creating the payment information, it proceeds to ACT 8. The processor 31 selects the payment device 12 that has been set as the parent device in ACT 8. That is, the processor 31 refers to the data table 321 and selects the payment device 12 identified by the payment device ID in which the parent device flag F is set to "1". In the following, the explanation will be continued assuming that the data table 321 is in the state shown in FIG. 3, that is, the first payment device 12-1 with the payment device ID of "121" is set as the parent device.

If the first payment device 12-1 set as the parent device is selected, the processor 31 proceeds to ACT 9. In ACT 9, the processor 31 controls the communication unit 35 to transmit payment information to the first payment device 12-1 as the destination. With this control, the payment information is transmitted to the network 14 with the first payment device 12-1 as the destination.

After completing transmission of the payment information, the processor 31 checks whether or not a response command indicating that payment is not possible has been received in ACT 10. If a response command indicating that payment is not possible has not been received, the processor 31 proceeds from ACT 10 to ACT 11. The processor 31 checks whether or not a response command indicating that payment is possible has been received in ACT 11. If a response command indicating that payment is possible has not been received, the processor 31 returns from ACT 11 to ACT 10. In this way, after completing transmission of the payment information, the processor 31 waits for a response command indicating that payment is not possible or that payment is possible in ACT 10 and ACT 11. The response command indicating that payment is not possible is returned when payment processing is not possible in the payment device 12 connected to the network 14. The response command indicating that payment is possible is returned when payment processing is possible in the payment device 12.

If a response command indicating that payment is not possible is received during the standby state of ACT 10 and ACT 11, the processor 31 proceeds from ACT 10 to ACT 12. The processor 31 notifies the store clerk that payment is not possible in ACT 12. For example, the processor 31 notifies the store clerk by displaying a screen on the touch panel 38 to notify the store clerk that payment is not possible. This screen has an operator that instructs resending. The store clerk touches the operator that instructs resending.

After notifying that payment is not possible, the processor 31 proceeds to ACT 13. The processor 31 waits for an instruction to resend in ACT 13. When the processor 31 detects that an instruction to resend has been given by a touch operation of the operator, the processor 31 returns from ACT 13 to ACT 9. The processor 31 again performs control to send payment information to the first payment device 12-1 set in the parent device. The processor 31 then waits for a response command indicating that payment is not possible or that payment is possible.

If the processor 31 receives a response command indicating that payment is possible during the standby state of ACT10 and ACT11, the processor 31 proceeds from ACT11 to ACT14. The processor 31 notifies the payment device 12 that will be the payment destination in ACT14. For example, if the payment device 12 that transmitted the response command indicating that payment is possible is the first payment device 12-1, the processor 31 notifies the store clerk by displaying information on the touch panel 38 notifying that the payment destination is the first payment device 12-1. The store clerk who receives this notification instructs the customer 22 to make payment at the first payment device 12-1. The notification of the payment destination may be displayed on the customer display 39. Alternatively, it may be displayed on both the touch panel 38 and the customer display 39. When the processing of ACT14 is completed, the processor 31 ends the first information processing.

Here, the processor 31 realizes the function of the creation means 311 by the processing of ACT 7. The processor 31 realizes the function of the transmission means 312 by the processing of ACT 8 and ACT 9.

Figure 7 is a flow chart showing the procedure of the third information processing executed by the processor 51 of the payment device 12 according to the payment program. The processor 51 waits for payment information in ACT 21. When the processor 51 receives payment information by the communication unit 55, which is sent from the input processing device 11 or from another payment device 12 with a higher transfer order, the processor 51 proceeds from ACT 21 to ACT 22. In ACT 22, the processor 51 checks whether the payment device 12 is capable of executing the payment process. For example, if the payment process of the previous customer has not been completed, the payment device 12 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 payment device 12 cannot execute the payment process.

If the payment device 12 is capable of executing the payment process, the processor 51 proceeds from ACT 22 to ACT 23. In ACT 23, the processor 51 controls the communication unit 55 to send a payment possible notification command to the input processing device 11. Through this control, the payment device 12 sends the payment possible notification command to the input processing device 11 via the network 14.

The processor 51 executes the payment process as ACT 24. Specifically, the processor 51 sets the screen of the touch panel 58 to 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. The customer 22 who moves to the location of the payment device 12 instructed by the store clerk 21 touches the button corresponding to the desired payment method. That is, a customer 22 who wishes to pay by cash touches the cash button, a customer 22 who wishes to pay by credit card touches the credit button, and a customer 22 who wishes to pay by electronic money touches the electronic money button.

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 the settlement process corresponding to that payment method. For example, when cash is selected as the payment method, processor 51 executes the 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, if approved, determines the total amount as the credit settlement amount. 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.

When the payment process for each payment method is thus completed, the processor 51 controls the printer 59 in ACT 25 to issue a transaction receipt. The transaction receipt prints payment information, i.e., the transaction number, transaction date and time, terminal ID, product sales data, total points, total amount, etc. When the processing of ACT 25 is completed, the processor 51 ends the third information processing.

On the other hand, if the payment device 12 is unable to execute the payment process, the processor 51 proceeds from ACT 22 to ACT 26. In ACT 26, the processor 51 refers to the data table 521 to obtain the transfer order R of the payment device 12.

The processor 51 adds "1" to the transfer order R in ACT 27. Then, the processor 51 refers to the data table 521 and selects another payment device 12 whose transfer order is set to "R+1". The processor 51 checks whether the other payment device 12 whose transfer order is set to "R+1" can be selected in ACT 28. Hereinafter, the other payment device 12 whose transfer order is set to "R+1" is represented as payment device 12(R+1), and the other payment device 12 whose transfer order is set to "R+2" is represented as payment device 12(R+2). If the payment device 12(R+1) cannot be selected, the processor 51 skips the processes in ACT 29 to ACT 34 and proceeds to ACT 35. The processor 51 controls the communication unit 55 to transmit a payment failure notification command to the input processing device 11 in ACT 35. By this control, the payment device 12 transmits a payment possible notification command to the input processing device 11 through the network 14.

If the payment device 12 (R+1) is selectable, the processor 51 proceeds from ACT28 to ACT29. In ACT29, the processor 51 checks the status S of the payment device 12 (R+1). If the status S is "0", i.e., the payment device 12 (R+1) is online, or if the status S is "1", i.e., the payment device 12 (R+1) is restored, the processor 51 proceeds from ACT29 to ACT30. In ACT30, the processor 51 controls the communication unit 55 to transfer the payment information to the payment device 12 (R+1). With this control, the payment information is transmitted from the payment device 12 to the payment device 12 (R+1) one step below in the transfer order, via the network 14.

On the other hand, if the status S of the payment device 12 (R+1) is "2", the processor 51 returns from ACT 29 to ACT 27. The processor 51 executes the process from ACT 27 onwards in the same manner as described above. Therefore, when the payment device 12 (R+2) whose transfer order is set to "R+2" cannot be selected by referring to the data table 521, the processor 51 controls the communication unit 55 to transmit a payment impossible notification command to the input processing device 11. On the other hand, when the payment device 12 (R+2) whose transfer order is set to "R+2" can be selected and the status S for the payment device 12 (R+2) is "0" or "1", the processor 51 controls the communication unit 55 to transfer the payment information to the payment device 12 (R+2) whose transfer order is two steps below in ACT 30. That is, the payment device 12 skips the payment device 12 (R+1) whose transfer order is one step below and transfers the payment information to the payment device 12 (R+2) whose transfer order is two steps below.

In this way, when the payment device 12 is unable to execute the payment process, the processor 51 transfers the payment information to the payment device 12 (R+1) or the payment device 12 (R+2) which is lower in the transfer order than the payment device 12. Here, when the payment device 12 (R+1) or the payment device 12 (R+2) which transferred the payment information is online or in a recovered state, the transmission of the payment information does not usually result in an error. On the other hand, when it is offline, the transmission of the payment information results in an error.

The processor 51 that transmitted the payment information checks whether or not a transmission error occurred in ACT 31. If no transmission error occurred, the processor 51 proceeds from ACT 31 to ACT 32. The processor 51 checks the status S for the payment device 12 (R+1) or the payment device 12 (R+2) that transmitted the payment information in ACT 32. If the status S is "0", the processor 51 ends the third information processing.

On the other hand, if the status S is "1", the processor 51 proceeds from ACT 32 to ACT 33. In ACT 33, the processor 51 changes the status S from "1" to "0". With this, the processor 51 ends the third information processing.

On the other hand, if an error occurs in the transmission of the payment information, the processor 51 proceeds from ACT 31 to ACT 34. In ACT 34, the processor 51 sets the status S for the payment device 12 (R+1) or the payment device 12 (R+2), which is the destination of the payment information, to "2". Next, the processor 51 proceeds to ACT 35 and controls the communication unit 55 to transmit a payment failure notification command to the input processing device 11. With this control, the payment device 12 transmits the payment failure notification command to the input processing device 11 via the network 14. Having controlled the transmission of the payment failure notification command, the processor 51 ends the third information processing.

Here, the processor 51 realizes the function of the receiving means 511 by the processing in ACT 21. The processor 51 realizes the function of the executing means 522 by the processing in ACT 24. The processor 51 realizes the function of the selecting means 523 by the processing in ACT 26 to ACT 29. The processor 51 realizes the function of the forwarding means 524 by the processing in ACT 30. The processor 51 realizes the function of the changing means 525 by the processing in ACT 34. The processor 51 realizes the function of the notifying means 526 by the processing in ACT 35.

Figure 8 is a flow chart showing the procedure of the fourth information processing executed by the processor 51 of the payment device 12 in accordance with the payment program. Also, Figure 9 is a flow chart showing the procedure of the second information processing executed by the processor 31 of the input processing device 11 in accordance with the registration program. Since the fourth information processing and the second information processing are linked, the two processes are described here in parallel.

The processor 51 of the payment device 12 in which the payment program is running executes the fourth information processing at a preset cycle. First, the processor 51 controls the communication unit 55 to send a confirmation start command to the input processing device 11 as ACT 41 in FIG. 8. This control causes the confirmation start command to be sent from the payment device 12 to the input processing device 11 via the network 14.

Meanwhile, the processor 31 of the input processing device 11 in which the registration program is running waits for a confirmation start command as ACT 61 in FIG. 9. When the processor 31 receives a confirmation start command from any of the payment devices 12, the processor 31 proceeds from ACT 61 to ACT 62. The processor 31 acquires the payment device ID of the payment device 12 that sent the confirmation start command as ACT 62. The processor 31 counts up the number of connections N stored in association with the payment device ID in the data table 321 by "1" as ACT 63. Then, the processor 31 controls the transmission of a confirmation response command to the payment device 12 that sent the confirmation start command as ACT 64. With this control, the confirmation response command is transmitted to the network 14 with the payment device 12 that sent the confirmation start command as the transmission destination. The confirmation response command includes the data in the data table 321, that is, the number of connections Na, Nb, and Nc for each payment device ID. The processor 31 that controlled the transmission of the confirmation response command ends the second information processing.

Returning to the explanation of FIG.
The processor 51 of the payment device 12, which controlled the transmission of the confirmation start command, waits for an acknowledgement command in ACT 42. When the processor 51 receives the acknowledgement command from the input processing device 11, the processor 51 proceeds from ACT 42 to ACT 43. In ACT 43, the processor 51 obtains data of the data table 321 held by the input processing device 11 from the acknowledgement command.

The processor 51 searches the data table 521 held by the payment device 12 in ACT 44. Then, the processor 51 checks whether there is a payment device ID with a status S of "2" indicating an offline state in ACT 45. If there is no payment device ID with a status S of "2" indicating an offline state in ACT 45, the processor 51 skips the processes in ACT 45 to ACT 49 and proceeds to ACT 50. The processor 51 stores the data of the data table 321 acquired from the confirmation response command in ACT 50. The storage destination of the data table 321 may be the main memory 52 or the auxiliary storage device 53. After storing the data table 321, the processor 51 ends this fourth information processing.

On the other hand, if there is a payment device ID with a status S of "2" indicating an offline state, the processor 51 proceeds from ACT 45 to ACT 46. In ACT 46, the processor 51 searches the data table 321 stored in the previous fourth information processing to detect the number of connections Nx (Nx = Na, Nb, or Nc) associated with the payment device ID. In ACT 47, the processor 51 searches the data table 321 acquired from the confirmation response command to detect the number of connections Ny (Ny = Na, Nb, or Nc) associated with the payment device ID. Then, in ACT 48, the processor 51 determines whether the number of connections Ny has increased more than the number of connections Nx.

If the number of connections Ny has not increased more than the number of connections Nx, the processor 51 skips the process in ACT 49 and proceeds to ACT 50. In ACT 50, the processor 51 stores the data in the data table 321 acquired from the confirmation response command, and ends the current fourth information process.

In contrast, if the number of connections Ny is greater than the number of connections Nx, the processor 51 proceeds from ACT 48 to ACT 49. The processor 51 changes the status S stored in the data table 521 in association with the payment device ID with the increased number of connections from "2" to "1". The processor 51 then proceeds to ACT 50. The processor 51 stores the data in the data table 321 acquired from the confirmation response command in ACT 50, and ends the current fourth information processing.

As described with reference to FIG. 9, the number of connections N (Na, Nb, Nc) increases each time a confirmation start command is received from the corresponding payment device 12. In other words, the number of connections N of a payment device 12 that is online increases, but the number of connections N of a payment device 12 that is offline does not increase. The processor 51 of the payment device 12 periodically monitors the number of connections N of other payment devices 12 whose status S is "2", that is, offline, by the fourth information processing. If the number of connections N increases, the other payment device 12 that was offline has recovered, so the status S is changed to "1". Here, the processor 51 realizes the function of recovery means 517 by the processing of ACT41 to ACT50. The processor 31 of the input processing device 11 also realizes the function of confirmation means 313 by the processing of ACT61 to ACT64 of FIG. 9.

[Operation of the Transaction Processing System]
Fig. 10 is an explanatory diagram of the operation of the transaction processing system 100 when the first payment device 12-1 set as the parent device is in a state where payment processing is possible. The data table 521 of each payment device 12 (12-1, 12-2, 12-3) stores the values shown in Fig. 10. That is, the transfer order of the first payment device 12-1 is first, the transfer order of the second payment device 12-2 is second, and the transfer order of the third payment device 12-3 is third. In addition, the first payment device 12-1, the second payment device 12-2, and the third payment device 12-3 are in an online state.

In this state, when payment information is sent from the input processing device 11 to the first payment device 12-1, a payment possible notification command is sent from the first payment device 12-1 to the input processing device 11. Then, the payment process is executed in the first payment device 12-1.

Figure 11 is a diagram explaining the operation of the transaction processing system 100 when, for example, the payment process of the previous customer has not yet been completed in the first payment device 12-1 and payment processing is not possible. Note that the data table 521 held by each payment device 12 (12-1, 12-2, 12-3) has the same values as those shown in Figure 10.

In this state, when payment information is sent from the input processing device 11 to the first payment device 12-1, the payment information is transferred from the first payment device 12-1 to the second payment device 12-2, which is second in the transfer order. If the second payment device 12-2 is now in a state where it can carry out payment processing, it sends a payment possible notification command to the input processing device 11. Then, the payment processing is carried out in the second payment device 12-2.

In contrast, if the second payment device 12-2 is also unable to process the payment, the payment information is transferred from the second payment device 12-2 to the third payment device 12-3, which is third in the transfer order. If the third payment device 12-3 is now able to process the payment, it sends a payment possible notification command to the input processing device 11. The payment process is then carried out in the third payment device 12-3.

If the third payment device 12-3 is also unable to process the payment, it sends a payment impossible notification command to the input processing device 11. As a result, the input processing device 11 is notified that payment is impossible, and the store clerk instructs resending. At that point, if the first payment device 12-1 is, for example, in a state where it is able to process the payment, the first payment device 12-1 sends a payment possible notification command to the input processing device 11. Then, the first payment device 12-1 executes the payment process.

Figure 12 is a diagram illustrating the operation of the transaction processing system 100 when payment information is transferred from the first payment device 12-1 to the second payment device 12-2, but the second payment device 12-2 cannot receive the payment information because it is offline. If a transmission error occurs when the payment information is transferred to the second payment device 12-2, the status S for the second payment device 12-2 in the first payment device 12-1 is changed from "0" to "2". In addition, a payment failure notification command is sent from the first payment device 12-1 to the input processing device 11. As a result, the input processing device 11 is notified that payment is not possible, and the store clerk instructs resending.

Figure 13 is an explanatory diagram of the operation of the transaction processing system 100 when payment information is resent from the input processing device 11. In the first payment device 12-1 that receives the payment information, the status S for the second payment device 12-2, which is second in the transfer order, is "2", so the first payment device 12-1 does not transmit the payment information to the second payment device 12-2. The first payment device 12-1 skips the second payment device 12-2 and transfers the payment information to the third payment device 12-3, which is third in the transfer order. If the third payment device 12-3 is now in a state where it can perform payment processing, a payment possible notification command is sent from the third payment device 12-3 to the input processing device 11. Then, the third payment device 12-3 executes the payment processing.

In this way, in transaction processing system 100, even if payment device 12-2, which is one step below payment device 12-1 in the transfer order, is offline, payment device 12-1 can transfer payment information to payment device 12-3, which is further down in the transfer order. This eliminates the problem that not only payment device 12-2, which is offline, but also payment device 12-3, which is lower in the transfer order, cannot process transaction settlement, resulting in reduced processing efficiency. As a result, the processing efficiency of payment processing can be improved.

Second Embodiment
In the first embodiment, in ACT 35 of the third information processing executed by the payment device 12, the command sent by the processor 51 to the input processing device 11 is a payment failure notification command. In the second embodiment, as shown in Fig. 14, this command is an error notification command. The error notification command is a command for notifying the input processing device 11 that a communication error has occurred in another payment device 12 that is lower in the transfer order than the payment device 12. The error notification command includes the payment device ID of the payment device 12 that has gone offline due to the communication error.

After sending the error notification command, the processor 51 returns to ACT 27 from ACT 35. That is, the processor 51 adds another "1" to the transfer priority "R+1" selected in the previous processing of ACT 27. The processor 51 then refers to the data table 521 and selects another payment device 12 (R+2) whose transfer priority is set to "R+2". The processor 51 checks whether the payment device 12 (R+2) can be selected. If the payment device 12 (R+2) cannot be selected, the processor 51 controls the communication unit 55 to send a payment impossible notification command to the input processing device 11.

On the other hand, if the payment device 12(R+2) is selectable, the processor 51 checks the status S of the payment device 12(R+2). If the status S is "0", i.e., the payment device 12(R+2) is online, or if the status S is "1", i.e., the payment device 12(R+2) is restored, the processor 51 controls the communication unit 55 to transfer the payment information to the payment device 12(R+2). With this control, the payment information is sent from the payment device 12 to the payment device 12(R+2), which is two places below in the transfer order, via the network 14.

On the other hand, in the second embodiment, the input processing device 11 differs from the first embodiment in a part of the processing from ACT 9 onwards of the first information processing executed by the processor 31. That is, in the first embodiment, as described with reference to FIG. 7, the processor 31 waits for a response command indicating payment is not possible or payment is possible in ACT 10 and ACT 11. In the second embodiment, as shown in FIG. 15, in a state where a response command indicating payment is not possible or payment is possible is waited for, the processor 31 checks whether an error notification command has been received in ACT 71. If an error notification command has been received, the processor 31 proceeds from ACT 71 to ACT 72. The processor 31 notifies the processor 31 that the payment device 12 identified by the payment device ID included in the error notification command is offline in ACT 72. The processor 31 then waits for a response command indicating payment is not possible or payment is possible.

Even in the second embodiment with such a configuration, if the payment device 12 that is unable to execute the payment process is offline, the payment device 12 (R+1) that is one step below in the transfer order can skip that payment device 12 (R+1) and transfer the payment information to the payment device 12 (R+2) that is two steps below in the transfer order. Furthermore, even if the store clerk who is the operator of the input processing device 11 does not instruct retransmission, the payment device 12 transfers the payment information to the payment device 12 (R+2) that is two steps below in the transfer order. Therefore, the processing efficiency can be improved compared to the first embodiment in which a retransmission instruction is awaited. In addition, the store clerk can easily identify the payment device 12 that has gone offline by the information notified by the input processing device 11, which has the advantage of being able to quickly perform recovery work for that payment device 12.

[Other embodiments]
In the above embodiment, an example has been given of a case in which each payment device 12 stores the data table 521 in the main memory 52. In another embodiment, the server 13 may store the data table 521, and each payment device 12 may share this data table 521.

In the above embodiment, a transaction processing system 100 is illustrated in which three payment devices 12 (12-1, 12-2, 12-3) are connected to one input processing device 11. The number of payment devices 12 is not limited to three. The number of payment devices 12 may be four or more.

In the above embodiment, one input processing device 11 and three payment devices 12 (12-1, 12-2, 12-3) form one group. In this regard, it is not necessary to form a group. For example, multiple input processing devices and multiple payment devices are placed in different locations. A transfer order of payment information is set in advance for the multiple payment devices. In addition, one of the multiple payment devices is a parent device and the rest are child devices. The multiple input processing devices transmit payment information to the parent device. When the multiple payment devices are in a state where they can execute payment processing, they execute payment processing based on the payment information. When the payment device is in a state where they cannot execute payment processing, they transfer the payment information to another payment device that is lower in the transfer order. At this time, if the other payment devices are offline, the payment information is transferred to another payment device that is further lower. Even if such a configuration is adopted, the effect of improving efficiency can be achieved in the same way as in the above embodiment.

Although several other embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be implemented in various other forms, and various omissions, substitutions, and modifications can be made without departing from the 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 as set forth in the claims.

11...input processing device, 12 (12-1, 12-2, 12-3)...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, 311...creation means, 312...transmission means, 313...confirmation means, 321, 521...data table, 511...reception means, 512...execution means, 513...selection means, 514...transfer means, 515...change means, 516...notification means, 517...recovery means.

Claims (6)

The input processing device and a plurality of payment devices are connected via a network,
The input processing device includes:
A creating means for creating payment information relating to a transaction based on the input data;
a transmission means for transmitting the payment information to a predetermined one of the plurality of payment devices via the network;
Equipped with
The payment device,
A receiving means for receiving the payment information via the network;
an execution means for executing a payment process based on the payment information received by the receiving means when the payment device is in a state capable of executing a payment process;
a selection means for searching for information indicating a connection state of the plurality of payment devices to the network when the payment device is in a state where it cannot execute a payment process, and selecting one of the other payment devices that are in a state where they are connected to the network;
a transfer means for transferring the payment information to the other payment device selected by the selection means;
A transaction processing system comprising: The payment device,
a change means for changing, when the transfer means fails to transfer the payment information, information indicating the connection state of the other payment device to which the transfer has failed from information indicating a state connected to the network to information indicating a state disconnected from the other payment device;
2. The transaction processing system of claim 1, further comprising: The payment device,
a notification means for notifying said input processing device when said transfer means has failed to transfer said payment information;
3. The transaction processing system of claim 2, further comprising: A transfer priority of the payment information is set for the plurality of payment devices,
4. A transaction processing system according to claim 1, wherein the selection means selects, from among the other connected settlement devices, a settlement device that is lower in the transfer priority order than the settlement device in question and has the highest transfer priority. A payment device of a transaction processing system, comprising an input processing device and a plurality of payment devices connected via a network, the input processing device including a creation means for creating payment information relating to a transaction based on input data, and a transmission means for transmitting the payment information via the network to a predetermined one of the plurality of payment devices,
A receiving means for receiving the payment information via the network;
an execution means for executing a payment process based on the payment information received by the receiving means when the payment device is in a state capable of executing a payment process;
a selection means for searching for information indicating a connection state of the plurality of payment devices to the network when the payment device is in a state where it cannot execute a payment process, and selecting one of the other payment devices that are in a state where they are connected to the network;
a transfer means for transferring the payment information to the other payment device selected by the selection means;
A payment device comprising: A computer in a payment device of a transaction processing system, comprising an input processing device and a plurality of payment devices connected via a network, the input processing device including a creation means for creating payment information relating to a transaction based on input data, and a transmission means for transmitting the payment information via the network to a predetermined one of the plurality of payment devices,
A receiving means for receiving the payment information via the network;
an execution means for executing a payment process based on the payment information received by the receiving means when the payment device is in a state capable of executing a payment process;
a selection means for searching for information indicating a connection state of the plurality of payment devices to the network when the payment device is in a state where it cannot execute a payment process, and selecting one of the other payment devices that are in a state where they are connected to the network; and
a transfer means for transferring the payment information to the other payment device selected by the selection means;
Payment program to function as.