JP7342987B2 - Systems, methods and programs - Google Patents

Description

The present disclosure relates to a system and the like.

2. Description of the Related Art In accounting systems in stores and the like, a configuration is known in which a registration device is provided separately from a payment device for customers to make payment. For example, a POS (Point Of Sales) system described in Patent Document 1 includes a registration device in which a store clerk registers products, and a plurality of payment devices for customers to make their own payment.

Patent No. 5850100

For example, if change is left behind at a checkout device, neither the customer who is supposed to receive the change nor the clerk may notice that the change has been left out. When the POS system described in Patent Document 1 does not require the intervention of a store clerk to pay for products, there is a low possibility that the store clerk will notice that he or she has forgotten to take change. The same thing can be said about cards and receipts other than change.

One exemplary object of the present disclosure is to provide a technique for supporting measures against forgetting to take change or the like after payment in a system including a registration device and a payment device.

A system according to an aspect of the present disclosure includes a registration device that registers a product to be purchased by a customer based on an operation by a store clerk, and a settlement device that performs payment processing based on the operation of the customer, the settlement device , a product detection means for detecting a product; the registration device has a determination device for determining an available payment device; Make the device an unavailable payment device.

A method according to an aspect of the present disclosure is a system method having a registration device that registers a product to be purchased by a customer based on an operation by a store clerk, and a settlement device that performs payment processing based on the operation of the customer. Then, the payment device detects the product, the registration device determines an available payment device, and sets the payment device from which the product is detected as an unavailable payment device.

A program according to an aspect of the present disclosure is a program for a system that includes a registration device that registers a product to be purchased by a customer based on an operation by a store clerk, and a settlement device that performs payment processing based on the operation of the customer. The computer of the payment device detects the product and executes processing, the computer of the registration device determines the payment device that can be used, and the payment device where the product is detected is used for payment that cannot be used. device and execute the process.

According to the present disclosure, in a system including a registration device and a payment device, it is possible to support measures against forgetting to take change or the like after payment.

FIG. 1 is a block diagram showing an example of the configuration of an accounting system. FIG. 2 is a sequence chart showing an example of the accounting method. FIG. 3 is a block diagram showing another example of the configuration of the accounting system. FIG. 4 is a block diagram showing an example of the configuration of the payment device. FIG. 5 is a block diagram showing an example of the configuration of the registration device. FIG. 6A is a diagram showing an example of a registration receipt. FIG. 6B is a diagram showing another example of a registration receipt. FIG. 7 is a functional block diagram showing an example of the main functional configuration of the payment device. FIG. 8 is a functional block diagram showing an example of the main functional configuration of the registration device. FIG. 9 is a flowchart illustrating an example of transmission processing. FIG. 10A is a diagram showing a first display example of the selection screen. FIG. 10B is a diagram showing a second display example of the selection screen. FIG. 10C is a diagram showing a third display example of the selection screen. FIG. 11 is a flowchart illustrating an example of payment processing. FIG. 12 is a flowchart illustrating an example of card payment processing. FIG. 13 is a diagram showing an example of a confirmation screen. FIG. 14 is a diagram showing an example of a notification screen. FIG. 15 is a flowchart showing another example of transmission processing. FIG. 16 is a block diagram showing yet another example of the configuration of the accounting system. FIG. 17A is a block diagram showing another example of the configuration of the registration device. FIG. 17B is a block diagram showing yet another example of the configuration of the registration device. FIG. 18 is a block diagram showing an example of the hardware configuration of a computer device.

[First embodiment]
FIG. 1 is a block diagram showing the configuration of an accounting system 100 according to one embodiment. The accounting system 100 includes one or more payment devices 110 and one or more registration devices 120. The number of payment devices 110 and registration devices 120 is not limited to a specific number. The payment device 110 and the registration device 120 are configured to be able to communicate by wire or wirelessly.

The accounting system 100 is an information processing system for paying the price of products. The products referred to herein may include both tangible goods and intangible services. The accounting system 100 is installed in a store (such as a retail store) that handles such products.

Furthermore, in the accounting system 100, the price of the product is paid with at least one of money and its equivalent. The monetary equivalents here include, for example, cash vouchers, gift certificates, electronic money, credit cards, debit cards, and the like. The price for the goods is paid using one or more payment instruments having such monetary value.

The payment device 110 is a device for performing payment processing based on a customer's operation. The payment device 110 includes at least a detection unit 111. On the other hand, the registration device 120 is a device for registering products to be purchased by a customer based on operations by a store clerk. Registration device 120 includes at least determination section 121 . Note that the payment device 110 and the registration device 120 may further include other components.

Settlement here refers to paying the price of the product. However, the customer may pay a portion of the price of the product at the registration device 120. In this case, the customer uses the payment device 110 to pay the remaining amount after deducting the already paid amount from the price of the product. For example, the customer may pay a portion of the price of the product using a cash voucher (which cannot be accepted by the payment device 110), and pay the remaining amount by money (which can be accepted by the payment device 110). Can be done. The payment process according to the present disclosure includes at least a payment process in which a customer pays for a product, and may further include other processes associated with this payment process (screen display, receipt issuance, etc.).

The detection unit 111 detects change to be refunded at the payment device 110. Change is money equivalent to the difference when the price of the product exceeds the customer's actual payment amount. The detection unit 111 detects change at a predetermined position where change is held, such as a change slot. In other words, the detection unit 111 can be said to detect whether change remains at such a predetermined position (that is, the presence or absence of change at a predetermined position).

The method for detecting change by the detection unit 111 is not particularly limited. For example, the detection unit 111 can detect change using a weight sensor or an infrared sensor. Alternatively, when a lid or a door is provided on the change opening, the detection unit 111 detects that change has been taken out by detecting the opening/closing of the lid or door instead of detecting the change itself. You can. Furthermore, the detection unit 111 may detect change by combining a plurality of detection methods.

The determining unit 121 determines available payment devices 110. The determining unit 121 can exclude a part of the payment device 110 included in the accounting system 100 from being used. The number of available payment devices 110 here is not limited to one, and may be two or more.

More specifically, the determining unit 121 determines an available payment device 110 based on the detection result by the detecting unit 111. If there is a payment device 110 in which change has been detected, the determination unit 121 excludes that payment device 110 from the usage target. That is, the determining unit 121 disables the payment device 110 in which change is detected from being used for payment. In other words, it can be said that the detection unit 111 determines the payment device 110 in which change is not detected as an available payment device.

Note that when there is only one settlement device 110 included in the accounting system 100, the determination unit 121 determines whether or not that settlement device 110 is considered usable. In this case, the determining unit 121 does not determine that the payment device 110 is usable until the payment device 110 no longer detects change. In this case, the customer cannot make payment using the payment device 110 until the clerk or another customer (who has completed payment first) takes out the change.

FIG. 2 is a sequence chart showing the accounting method of this embodiment. In step 210 , the payment device 110 detects change using the detection unit 111 and transmits information indicating the detection result to the registration device 120 . For example, this information indicates "1" when the change is detected by the detection unit 111, and "0" when the change is not detected by the detection unit 111. The presence or absence is information that can be identified. Note that if the accounting system 100 includes a plurality of payment devices 110, the process of step 210 is executed by each payment device 110.

The registration device 120 that has acquired the information indicating the change detection result determines the payment device 110 that can be used for payment in step 220. Specifically, the determining unit 121 determines the availability of the payment device 110 based on the information transmitted in step 210. Then, the determining unit 121 excludes the payment device 110 determined to be unusable from the usage target.

As described above, the accounting system 100 according to the present embodiment has a configuration in which an available payment device 110 is determined based on the detection result of change in the payment device 110. This configuration makes it possible to exclude the payment device 110 in which change has been detected, that is, in which change remains, from the usage target. Therefore, according to the accounting system 100, it is possible to support countermeasures against forgetting to take change by a clerk.

For example, a clerk using the accounting system 100 can prevent a customer who is about to make a payment from being guided to the payment device 110 where change remains. Alternatively, when a particular payment device 110 becomes unavailable, the store clerk can understand that change has not been taken out from that device, and can take measures such as taking out the change and temporarily storing it. Therefore, a store that uses the accounting system 100 can reduce the risk of change being illegally obtained by a person different from the customer who should originally receive the change, compared to a store that does not use the system.

[Second embodiment]
FIG. 3 is a block diagram showing the configuration of an accounting system 300 according to another embodiment. Accounting system 300 includes payment devices 310a, 310b, and 310c and registration device 320. The payment devices 310a, 310b, 310c and the registration device 320 can communicate via a wired or wireless network. The accounting system 300 is used by store staff and customers at a store.

The payment devices 310a, 310b, and 310c each have a common configuration. In the following, the payment devices 310a, 310b, and 310c are collectively referred to as the "payment device 310" unless it is necessary to distinguish between them. Further, for convenience of explanation, the payment device 310a is also referred to as the "number 1 cash register," the payment device 310b is also referred to as the "number 2 cash register," and the payment device 310c is also referred to as the "number 3 cash register." These are names (common names) for store staff and customers.

The number of settlement devices 310 and registration devices 320 included in accounting system 300 is not necessarily limited to the number illustrated in FIG. 3. The accounting system 300 may include two, four or more payment devices 310, and may include two or more registration devices 320.

In this embodiment, the accounting system 300 corresponds to an example of the accounting system 100 of the first embodiment. The payment device 310 corresponds to an example of the payment device 110 of the first embodiment. The registration device 320 corresponds to an example of the registration device 120 of the first embodiment.

FIG. 4 is a block diagram showing the configuration of the payment device 310. The payment device 310 includes a control section 410, a communication section 420, a display section 430, an input section 440, a scanning section 450, a receipt issuing section 460, a cash processing section 470, a card processing section 480, and a sensor section. 490. Note that the payment device 310 may further include other components (for example, a sign pole described in Patent Document 1).

The control section 410 controls the operation of each section of the payment device 310. The control unit 410 includes, for example, an arithmetic processing device such as a CPU (Central Processing Unit) and a memory. The control unit 410 can control the operation of each part of the payment device 310 by executing a program.

The communication unit 420 exchanges data with the registration device 320. The communication unit 420 includes, for example, a communication module that enables data transmission and reception using a predetermined communication method. However, communication by the communication unit 420 is not limited to a specific method.

Display unit 430 displays information. The display unit 430 includes, for example, a display panel using a display element such as a liquid crystal and a drive circuit thereof. The information displayed on the display section 430 is primarily information intended for notification to customers. However, the display unit 430 may display information to be notified to the store clerk as necessary, and may have multiple screens. Further, it is assumed that the display unit 430 is a touch screen display in this embodiment.

The input unit 440 receives input from a user (mainly a customer). In this embodiment, the input unit 440 accepts touch operations on the display unit 430 in addition to key operations on a keyboard, keypad, etc. However, the input unit 440 may be configured to accept only one of a key operation and a touch operation.

The scanning unit 450 optically reads code information. Scanning unit 450 includes, for example, a barcode reader. The scanning unit 450 reads code information printed on the receipt issued by the registration device 320. Note that the code information is, for example, a barcode or a two-dimensional code (also referred to as a two-dimensional barcode).

Receipt issuing unit 460 issues a receipt. The receipt issuing unit 460 includes, for example, a thermal printer that prints characters and the like on paper using heat. The receipt issued by the receipt issuing unit 460 is a receipt issued after the customer makes payment, and is a so-called receipt.

The cash processing unit 470 processes payments using cash (ie, money). The cash processing unit 470 accepts deposits and dispenses change as needed. More specifically, the cash processing unit 470 has a deposit port 471 and a withdrawal port 472. The deposit port 471 accepts banknotes and coins. The withdrawal port 472 dispenses at least one of banknotes and coins corresponding to change. Note that the withdrawal port 472 may be configured to also serve as the deposit port 471.

Card processing unit 480 processes payment by credit card. More specifically, the card processing unit 480 includes a card reader 481. Card reader 481 reads information from the customer's credit card inserted into the insertion slot. Card reader 481 may include a sensor that detects the presence or absence of a credit card. Note that the card processing unit 480 is configured to process payments using electronic money using a contactless storage medium such as FeliCa (registered trademark) instead of (or in addition to) a credit card. Good too.

The sensor unit 490 detects change present at the withdrawal port 472. The sensor unit 490 is, for example, a sensor that can distinguish between a state where a foreign object is present in the withdrawal port 472 and a state where there is no foreign object. The sensor unit 490 supplies data (hereinafter also referred to as “detection data”) according to the change detection result to the control unit 410. Here, the detection data is a flag that indicates "1" when change is detected, and indicates "0" when change is not detected. The sensor section 490 corresponds to an example of the detection section 111 of the first embodiment.

FIG. 5 is a block diagram showing the configuration of the registration device 320. Registration device 320 includes a control section 510, a communication section 520, a display section 530, an input section 540, a scanning section 550, and a receipt issuing section 560. Note that, like the payment device 310, the registration device 320 may further include other components.

The control section 510 controls the operation of each section of the registration device 320. The control unit 510 includes, for example, an arithmetic processing unit such as a CPU and a memory. The control unit 510 can control the operation of each unit of the registration device 320 by executing a program. The control unit 510 corresponds to an example of the determination unit 121 in the first embodiment.

The communication unit 520 exchanges data with the payment device 310. The communication unit 420 includes, for example, a communication module that enables data transmission and reception using a common communication method with the communication unit 420 of the payment device 310. Communication by the communication unit 520 is not limited to a specific method, similar to the communication by the communication unit 420.

Display unit 530 displays information. The display unit 530 includes, for example, a display panel using a display element such as a liquid crystal and a drive circuit thereof. The information displayed on the display section 530 is primarily information intended for notification to store staff. However, the display section 530 may display information to be notified to the customer as necessary, and may have a configuration that includes a display for store staff and a display for customers. Further, it is assumed that the display unit 530 is a touch screen display in this embodiment.

The input unit 540 receives input from a user (mainly a store clerk). In this embodiment, the input unit 540 accepts touch operations on the display unit 530 in addition to key operations on a keyboard, keypad, etc. However, the input unit 540 may be configured to accept only one of a key operation and a touch operation.

The scanning unit 550 optically reads code information. Scanning unit 550 includes, for example, a barcode reader. The scanning unit 550 reads barcodes attached to products. This barcode is, for example, a barcode based on one of the Universal Product Code, JAN (Japanese Article Number) code, and EAN (European Article Number) code.

Receipt issuing unit 560 issues a receipt. The receipt issuing unit 560 includes, for example, a thermal printer that prints characters and the like on paper using heat. The receipt issued by the receipt issuing unit 560 includes information regarding the payment device 310 used by the customer for payment.

The configuration of the accounting system 300 is as described above. When a customer purchases a product at a store, the customer needs to bring the product to a store clerk who operates the registration device 320 and have the product registered. The store clerk uses the registration device 320 to register the product for which payment is to be made.

The registration device 320 generates registration data in response to operations by a store clerk. The registration data includes information necessary for a customer to make a payment using the payment device 310. The registration data of this embodiment includes at least the amount to be paid to the payment device 310 by the customer (hereinafter also referred to as "settlement amount"). In addition to the payment amount, the registration data may include general information that can be written on a receipt, such as product name, product unit price, and number of products.

The settlement amount here is typically the total price of products purchased by the customer. However, in this embodiment, the customer can pay part of the price of the product in advance at the registration device 320. For example, the customer may pay a portion of the price of the item in advance with cash or a payment means other than a credit card, and pay the remaining amount at checkout device 310 (ie, with cash or credit card). In such a case, the settlement amount is the remaining amount after subtracting the advance payment amount from the total price of the product.

When registration of the product is completed, the registration device 320 transmits the registration data to one of the payment devices 310. Further, the registration device 320 issues a receipt when the registration of the product is completed. This receipt proves that the product to be paid for has been registered. In the following, this receipt will be referred to as a "registered receipt" to distinguish it from the receipt issued by the settlement device 310.

6A and 6B are diagrams showing examples of registration receipts. The registration receipt 610 shown in FIG. 6A includes code information 611. The code information 611 is information that can be read by the payment device 310. On the other hand, the registration receipt 620 shown in FIG. 6B includes a message 621 urging the customer who received the registration receipt 620 to go to the payment device 310a. Registration receipt 620 differs from registration receipt 610 in that it does not include information read by payment device 310.

The customer makes a payment at the payment device 310 to which the registration data regarding the customer's product is transmitted. The payment device 310 to which the registration data has been sent can be identified by the information printed on the registration receipt. Alternatively, the store clerk may verbally guide the user to the checkout device 310 to which the registration data has been transmitted, such as, for example, "Please proceed to checkout number 1." In such a case, the registration device 320 does not need to have the function of issuing a registration receipt.

That is, the registration device 320 may not include the receipt issuing unit 560 depending on the manner in which the store clerk guides the customer. Furthermore, if the registration device 320 does not have the receipt issuing section 560, the payment device 310 does not need to have the scanning section 450.

After receiving registration data from the registration device 320, the payment device 310 executes payment processing in response to a customer's operation (predetermined touch operation, scanning of a registration receipt, etc.). The payment process in this embodiment refers to a series of processes that occur along with payment. Specifically, the payment device 310 accepts deposits in excess of the payment amount described in the registration data, and withdraws change as necessary. Further, the payment device 310 issues a receipt when the payment is completed. These processes correspond to a part of the payment process of this embodiment.

Further, the payment device 310 transmits state data representing the state of its own device to the registration device 320. The status data is, for example, data for notifying the registration device 320 of a status such as "Paying", "Paying completed", "Suspended", or "Abnormality occurring". Here, "in the process of payment" refers to a state in which payment processing for any customer is being executed. Moreover, "settlement completed" refers to a state in which the most recent settlement process has been completed and the next settlement process can be executed. Furthermore, "inactive" refers to a state in which the payment device 310 is not operating, such as when the power is off. Furthermore, "an abnormality is occurring" refers to a state in which the payment device 310 is unable to continue payment processing due to a customer calling a store clerk, a malfunction of the payment device 310, or the like. The payment device 310 transmits status data to the registration device 320 at predetermined time intervals (every 10 seconds, every minute, etc.) or every time the status of its own device is updated.

Note that the state data of "Payment in progress" may be further subdivided according to the progress of the payment process, such as "Before payment," "Payment in progress," and "Receipt issuance in progress." Furthermore, when a plurality of customers are waiting for payment for one payment device 310, the status data of "Paying" may further include data indicating the number of people waiting for payment. Further, the “settled” status data further includes detection data indicating the change detection result by the sensor unit 490.

When transmitting the registration data, the registration device 320 selects one of the destinations based on the operation of the store clerk. At this time, the registration device 320 accepts the selection of any of the available payment devices 310. One of the characteristics of the registration device 320 is that the payment device 310 whose status data is “settled” and whose detection data is “1” is excluded from the available payment devices 310.

FIG. 7 is a functional block diagram showing the main functional configuration of the control unit 410 included in the payment device 310. The control unit 410 includes a transmission control unit 710 and a payment processing unit 720. The functions corresponding to the transmission control unit 710 and the payment processing unit 720 are realized, for example, by the control unit 410 executing a program.

Transmission control unit 710 controls transmission of status data. The transmission control unit 710 detects the status of the payment device 310 and supplies status data to the communication unit 420 at an appropriate timing. The communication unit 420 transmits the status data acquired from the control unit 410 to the registration device 320.

The payment processing unit 720 executes payment processing. The payment processing unit 720 receives the registration data transmitted by the registration device 320, and upon accepting the customer's operation, executes payment processing based on the registration data. The settlement processing section 720 cooperates with the cash processing section 470 and the card processing section 480 to execute settlement processing.

FIG. 8 is a functional block diagram showing the main functional configuration of the control unit 510 included in the registration device 320. Control section 510 includes a determination section 810, a selection section 820, and a transmission control section 830. The functions corresponding to the determining section 810, the selecting section 820, and the transmission controlling section 830 are realized, for example, by the controlling section 510 executing a program.

The determining unit 810 determines the payment device 310 that can be used for payment. The determining unit 810 determines a payment device 310 that can be used for payment based on the status data (and detection data included in the status data) transmitted by the payment device 310. The determining unit 810 corresponds to an example of the determining unit 121 of the first embodiment.

The selection unit 820 selects the payment device 310 used for payment. The selection unit 820 selects the payment device 310 actually used for payment from among the payment devices 310 determined by the determination unit 810. If there are a plurality of available payment devices 310, that is, a plurality of payment devices 310 determined by the determination unit 810, the selection unit 820 selects any one of the plurality of payment devices 310. In this embodiment, the selection unit 820 selects the payment device 310 based on the clerk's operation. The payment device 110 selected by the selection unit 820 becomes ready to accept payment by the customer.

The transmission control unit 830 controls transmission of registration data. The transmission control unit 830 supplies the communication unit 520 with registration data to be transmitted to the payment device 310 selected by the selection unit 820. The communication unit 520 transmits the registration data acquired from the control unit 510 to the payment device 310.

FIG. 9 is a flowchart showing the registration data transmission process executed by the registration device 320. In step 910, the control unit 510 obtains the status data transmitted from the payment device 310. The control unit 510 acquires the status data received by the communication unit 520 from the communication unit 520.

In step 920, the control unit 510 determines whether status data has been acquired from all of the payment devices 310 (payment devices 310a, 310b, and 310c). If there is a payment device 310 that has not acquired status data (step 920: NO), the control unit 510 repeats the processing of steps 910 and 920 until status data is acquired from all payment devices 310. When the control unit 510 acquires the status data from all the payment devices 310 (step 920: YES), the control unit 510 executes the process of step 930.

In step 930, the control unit 510 determines the payment device 310 that can be used for payment. The control unit 510 determines the payment device 310 that can be used for payment based on the status data. Specifically, the control unit 510 excludes the payment device 310 that is not in a usable state from the usage target. For example, in the case of the above example, the control unit 510 determines that the payment device 310 whose status data indicates "inactive" or "abnormality occurring" is not available.

Furthermore, the control unit 510 excludes the payment device 310 whose status data indicates "settlement completed" and whose detection data indicates "1" from the usage target. On the other hand, the control unit 510 does not need to exclude from the usage target the payment device 310 whose status data indicates "payment completed" and whose detection data indicates "0". That is, even if the payment device 310 is in a state where the next payment process can be executed, the control unit 510 excludes the payment device 310 from being used if change is detected.

In step 940, the control unit 510 controls the display unit 430 to display the payment devices 310 that can be used for payment. More specifically, the control unit 510 causes the display unit 430 to display a selection screen that accepts selection of any of the payment devices 310 that can be used for payment.

10A, FIG. 10B, and FIG. 10C are diagrams showing display examples of the selection screen displayed by the display unit 430. The selection screen 1010 shown in FIG. 10A is displayed when any of the payment devices 310a, 310b, and 310c can be used for payment. Here, buttons 1011, 1012, and 1013 are images representing buttons for selecting one of the payment devices 310a, 310b, and 310c. By touching any of the buttons 1011, 1012, and 1013, the clerk can select the payment device 310 to be used for payment.

On the other hand, the selection screen 1020 shown in FIG. 10B is displayed when the payment devices 310a and 310b are available for payment, and the payment device 310c is not available for payment. Here, the buttons 1021 and 1022 are displayed in the same display manner as the buttons 1011 and 1012 on the selection screen 1010, and have the same functions as these buttons.

On the other hand, button 1023 is displayed in a different display manner from buttons 1021 and 1022. Button 1023 indicates that the payment device 310c is not available for payment. Further, the button 1023 is configured not to accept selection by the user. Even if the clerk touches the button 1023, he cannot select the payment device 310c.

Further, a selection screen 1030 shown in FIG. 10C is another display example in the same case as the selection screen 1020. Selection screen 1030 includes buttons 1031 and 1032 that correspond to buttons 1021 and 1022, but does not include a button that corresponds to button 1023. That is, the selection screen 1030 differs from the selection screen 1020 in that only buttons corresponding to the payment devices 310 that can be used for payment are displayed.

Note that the buttons displayed on the selection screen may be displayed in a display mode according to the status data. For example, the control unit 510 may change the color of the button depending on whether the status data is "Payment in Progress" or "Payment Completed." Alternatively, the control unit 510 may display the number of people waiting in the button when the status data is "Paying".

The clerk selects the payment device 310 to guide the customer while referring to the information displayed on such a selection screen. In addition to the information displayed on the selection screen, the clerk can select a payment device 310 while considering other factors such as the distance from the registration device 320 to each payment device 310.

Note that the control unit 510 may re-execute steps 930 and 940 when the state of the payment device 310 changes during the process, in other words, when the state data changes. For example, in a case where detection data is transmitted from the payment device 310 that was excluded from the usage target because change was detected, the control unit 510 determines that the detection data indicates that change is no longer detected in the device. In such a case, it is possible to change the device to an available payment device. When the number of available payment devices 310 increases (or decreases), the control unit 510 may update the selection screen.

In step 950, the control unit 510 determines which button (ie, payment device 310) has been selected by the clerk on the selection screen displayed in this way. If the button is not selected (step 950: NO), the control unit 510 repeats this determination. When one of the selectable buttons is selected (step 950: YES), the control unit 510 executes the process of step 960.

In response to the clerk's operation (ie, selection), the control unit 510 transmits registration data via the communication unit 520 in step 960. Specifically, the control unit 510 transmits registration data to the payment device 310 corresponding to the button selected by the clerk. By receiving the registration data, the payment device 310 becomes ready to perform payment processing.

FIG. 11 is a flowchart showing the payment process executed by the payment device 310. In step 1110, the control unit 410 acquires the registration data transmitted by the registration device 320 via the communication unit 420. In step 1120, the control unit 410 determines whether there is any input by the customer. For example, the control unit 410 determines whether code information (see FIG. 6A) has been read by the scanning unit 450. Alternatively, the control unit 410 may determine whether a predetermined operation is accepted at the input unit 440.

In step 1130, control unit 410 accepts payment from the customer. Prior to this deposit, the control unit 410 may determine whether the deposit is in cash or by credit card. For example, the control unit 410 causes the display unit 430 to display a selection screen for selecting either cash or credit card as a payment method, and receives input from the customer.

In step 1140, the control unit 410 determines whether the deposit will be made by cash or credit card. Thereafter, the control unit 410 executes payment processing according to the payment method selected by the user. If the payment means is cash (step 1140: YES), the control unit 410 executes the processing from step 1150 onwards. On the other hand, if the payment means is a credit card (step 1140: NO), the control unit 410 executes the card payment process in step 1180.

In step 1150, cash processing unit 470 determines whether change is required. Specifically, the cash processing unit 470 determines whether change is necessary by comparing the payment amount specified by the registration data and the deposited amount in step 1130. The cash processing unit 470 determines that change is required when the deposited amount is greater than the settled amount.

If change is required (step 1150: YES), the cash processing unit 470 withdraws change corresponding to the difference between the deposited amount and the settled amount in step 1160. On the other hand, if change is not required (step 1150: NO), the cash processing unit 470 skips the process of step 1160. In step 1170, the receipt issuing unit 460 issues a receipt according to the payment means.

FIG. 12 is a flowchart showing the card payment process in step 1180. In step 1210, control section 410 causes display section 430 to display a screen (hereinafter also referred to as "insertion screen") prompting the customer to insert a credit card. When the credit card is inserted, the control unit 410 switches the screen displayed on the display unit 430 from the insertion screen to the confirmation screen in step 1220. The confirmation screen is a screen for confirming payment details.

FIG. 13 is a diagram showing an example of a confirmation screen. The confirmation screen 1300 displays the amount to be paid by credit card, the payment method (lump sum payment, installment payment, etc.), and the like. The confirmation screen 1300 also includes a confirm button 1310 and a cancel button 1320. If the customer agrees to the payment displayed on the confirmation screen 1300, the customer touches a confirm button 1310. Further, if the customer does not agree to payment by credit card, the customer touches the cancel button 1320.

In step 1230, control unit 410 determines whether to perform payment by credit card. For example, the control unit 410 determines whether the confirm button 1310 on the confirmation screen 1300 is selected. In this case, the control unit 410 repeats the determination in step 1230 until the confirm button 1310 is selected. When the confirm button 1310 is selected (step 1230: YES), the card processing unit 480 executes the determination in step 1240.

In step 1240, card processing unit 480 determines whether a credit card remains in card reader 481. For example, the card reader 481 uses a sensor provided around the insertion slot to determine whether the credit card remains inserted in the insertion slot. If the credit card remains (step 1240: YES), the card processing unit 480 causes the display unit 430 to display a notification screen notifying that the credit card has been forgotten in step 1250.

FIG. 14 is a diagram showing an example of a notification screen. Notification screen 1400 includes a message 1410 prompting the user to remove the credit card. Card processing unit 480 causes display unit 430 to continue displaying notification screen 1400 until the credit card is removed from card reader 481. By displaying the notification screen 1400 until the credit card is removed, it is possible to reduce the risk of the customer forgetting to take out the credit card. Note that the card processing unit 480 may also display the notification screen 1400 when the cancel button 1320 on the confirmation screen 1300 is selected.

When the credit card is removed (step 1240: NO), the card processing unit 480 executes payment processing in step 1260. The payment process is a process in which a credit card is authenticated and a transaction is established after authentication. The card processing unit 480 can perform payment processing using a common method for credit card payments.

In this example, the registration device 320 may exclude the payment device 310 from being used until the card payment process is completed. In this way, it is possible to make it impossible to use the payment device 310 from which a credit card is not removed until the credit card is removed.

Note that the card payment process is not limited to the example shown in FIG. 12. The payment device 310 may perform card payment processing in a more general manner that is well known. Further, the payment device 310 may be configured not to accept payment by credit card, but only to accept payment by cash.

As described above, the accounting system 300 according to the present embodiment determines the available settlement devices 310 based on the change detection result in the settlement device 310, and further selects the settlement device 310 to be used for settlement according to the operation of the clerk. It has a configuration that With this configuration, the accounting system 300 can achieve the same effects as the accounting system 100 of the first embodiment.

Further, according to the accounting system 300, when there are multiple payment devices 310 available, the clerk can guide the customer to the payment device 310 that is considered to be more appropriate. For example, the clerk can guide the customer to the payment device 310 with fewer people waiting or to the payment device 310 that is closer to the registration device 320.

[Modified example]
The present disclosure is not limited to the first and second embodiments described above. The present disclosure includes, for example, the variations described below. Further, the present disclosure may include forms in which the matters described in this specification are appropriately combined or substituted as necessary. For example, matters described using a particular embodiment may be applied to other embodiments to the extent that no contradiction occurs. Furthermore, the present disclosure is not limited to these, and may include embodiments in which modifications or applications that can be understood by those skilled in the art are applied.

(Modification 1)
The registration device 320 can also select the payment device 310 to be used for payment without an operation by a store clerk. For example, the registration device 320 may select the payment device 310 to be used for payment based on a predetermined rule.

FIG. 15 is a flowchart showing another example of the registration data transmission process. In this flowchart, the processing up to step 930 is common to the transmission processing illustrated in FIG. Therefore, a description of the processing up to step 930 will be omitted here.

In step 1510, if there are a plurality of payment devices 310 determined in step 930, the control unit 510 selects one payment device 310 that satisfies a predetermined condition from among the plurality of payment devices 310. For example, the control unit 510 selects the payment device 310 with the least number of people waiting. Alternatively, if the number of people waiting in the plurality of payment devices 310 is the same (however, one or more people), the control unit 510 selects the payment device 310 in which the payment process is progressing the most. For example, if the status data of the payment device 310a is “before payment” and the status data of the payment device 310b is “issuing receipt”, the control unit 510 selects the payment device 310b as the usage target.

In step 1520, the control unit 510 transmits the registration data to the payment device 310 selected in step 1510 via the communication unit 520. The specific process of transmitting the registration data is the same as step 960.

By operating in this way, the registration device 320 can automatically select the payment device 310 to be used for payment, ie, without requiring any operation by the clerk to select the payment device 310.

(Modification 2)
The registration device 320 can also supply registration data to the payment device 310 without communication. For example, the registration device 320 may issue a registration receipt on which code information in which registration data is embedded is printed (see FIG. 6A). In this case, the payment device 310 can recognize the registered data by reading the code information.

(Modification 3)
The system according to the present disclosure can also be used to prevent the loss of objects other than change. For example, by detecting receipts and products after payment, the system according to the present disclosure can reduce the risk of these items being illegally acquired by a third party. Further, the system according to the present disclosure may be configured to detect a card instead of (or in addition to) change, as exemplified below.

FIG. 16 is a block diagram showing the configuration of an accounting system 1600 according to the present disclosure. Accounting system 1600 is an information processing system for reducing the risk that a card left behind by a customer will be illegally acquired by a third party. The card here is, for example, a credit card, but it may also be another card used at the time of payment, such as a prepaid card, point card, or member's card. That is, the card here does not matter whether it is a means of paying a price or not.

Accounting system 1600 includes a settlement device 1610 and a registration device 1620. The payment device 1610 includes at least a detection unit 1611 and a payment processing unit 1612. Registration device 1620 includes at least a determining unit 1621. Note that the number of each of the payment devices 1610 and the registration devices 1620 may be plural.

The detection unit 1611 detects a card. The detection unit 1611 has a sensor that detects the presence or absence of a card, like the card reader 481 of the second embodiment, for example. For example, the detection unit 1611 detects a card inserted into the insertion slot. In other words, the detection unit 1611 detects that the card remains inserted into the insertion slot.

The settlement processing unit 1612 executes settlement processing. The settlement processing unit 1612 may settle the price of the product using a card detected by the detection unit 1611, but may also settle the price using other payment means such as cash. The payment process executed by the payment processing unit 1612 may or may not be the same as the payment process described in the second embodiment.

The payment processing unit 1612 executes payment processing when the card is no longer detected by the detection unit 1611. Alternatively, the payment processing unit 1612 executes at least part of the processing included in the payment processing after the detection unit 1611 no longer detects the card. In other words, the payment process executed by the payment processing unit 1612 is not completed until the detection unit 1611 no longer detects the card. The payment processing unit 1612 may execute control such as the card payment processing in the second embodiment (see FIG. 12), in which the payment processing is not executed until the card is removed.

The determining unit 1621 determines available payment devices 1610. The determining unit 1621 assumes that the payment device 1610 for which payment processing has been completed by the payment processing unit 1612 can be used. For example, the determining unit 1621 may use data similar to the status data of the second embodiment to determine whether the payment process has been completed in the payment device 1610.

(Modification 4)
The system according to the present disclosure may include configurations other than the registration device and the payment device. For example, the system according to the present disclosure may include a configuration equivalent to a store computer in a POS system. In this case, some or all of the components of the registration device 120 or the registration device 320 described above may be included in the store computer.

(Modification 5)
17A and 17B are block diagrams showing other configuration examples of the registration device according to the present disclosure. Registration device 1710 shown in FIG. 17A includes a determining section 1711 and a selecting section 1712. Registration device 1720 shown in FIG. 17B includes an acquisition section 1721 and a determination section 1722. The registration device 120 described in the first embodiment or the registration device 320 described in the second embodiment can be replaced with the registration device 1710 or 1720. Further, the registration device according to the present disclosure may have a configuration in which the registration devices 1710 and 1720 are combined.

The determining unit 1711 determines available payment devices. For example, the determining unit 1711 determines that a payment device in which change is not detected can be used, and excludes a payment device in which change is detected from the usage target. The selection unit 1712 selects one of the payment devices determined by the determination unit 1711. The selection unit 1712 may select one of the payment devices based on a predetermined rule, or may accept an operation from a store clerk and select one of the payment devices based on the operation.

The acquisition unit 1721 acquires information indicating the change detection result in the payment device. This information is, for example, detection data in the second embodiment. The determining unit 1722 determines an available payment device based on the information acquired by the acquiring unit 1721. Specifically, the determining unit 1722 assumes that a payment device in which change is not detected can be used.

(Modification 6)
The specific hardware configurations of the registration device, payment device, and system according to the present disclosure include various variations and are not limited to specific configurations. For example, the registration device according to the present disclosure may be realized using software, or may be configured to share various processes using multiple pieces of hardware.

FIG. 18 is a block diagram illustrating an example of the hardware configuration of a computer device 1800 that implements the registration device or payment device according to the present disclosure. The computer device 1800 includes a CPU (Central Processing Unit) 1801, a ROM (Read Only Memory) 1802, a RAM (Random Access Memory) 1803, a storage device 1804, a drive device 1805, a communication interface 1806, and an input/output interface. 1807. The registration device or payment device according to the present disclosure can be realized by the configuration (or a part thereof) shown in FIG. 18.

The CPU 1801 executes a program 1808 using the RAM 1803. Program 1808 may be stored in ROM 1802. Further, the program 1808 may be recorded on a recording medium 1809 such as a memory card and read by the drive device 1805, or may be transmitted from an external device via the network 1810. Communication interface 1806 exchanges data with external devices via network 1810. The input/output interface 1807 exchanges data with peripheral devices (input devices, display devices, etc.). The drive device 1805, the communication interface 1806, and the input/output interface 1807 can function as components for acquiring or outputting data.

Note that the components of the registration device or payment device according to the present disclosure may be configured by a single circuit (such as a processor), or may be configured by a combination of multiple circuits. The circuit referred to herein may be either dedicated or general purpose. For example, a part of the registration device or payment device according to the present disclosure may be realized by a dedicated processor, and the other part may be realized by a general-purpose processor.

The configuration described as a single device in the embodiments described above may be distributed and provided in multiple devices. For example, the registration device 120 or the registration device 320 may be realized by cooperation of a plurality of computer devices using cloud computing technology or the like.

[Additional notes]
Some or all of the embodiments of the present disclosure may be described as in the following supplementary notes, but are not limited thereto.
(Additional note 1)
It has a registration device for registering products to be purchased by a customer based on the operations of a store clerk, and a payment device for performing payment processing based on the operations of the customer,
The payment device has a detection means for detecting change,
The registration device includes a determination device that determines, as an available payment device, a payment device whose change is not detected by the detection device.
(Additional note 2)
The determining means is configured to exclude a payment device whose change has been detected by the detection device from available payment devices, and then, when change is no longer detected by the detection device, select a payment device that can use the payment device. The system described in Appendix 1.
(Additional note 3)
The system according to appendix 1 or 2, wherein the registration device further includes a selection device that selects one of the payment devices determined by the determination device according to a user's operation.
(Additional note 4)
The system according to Appendix 1 or 2, wherein the registration device further includes a selection device that selects one of the payment devices determined by the determination device based on a predetermined rule.
(Appendix 5)
a plurality of payment devices each having a detection means for detecting change;
A system comprising: a registration device having a selection means for selecting, as a usage target, a payment device whose change is not detected by the detection device from among the plurality of payment devices.
(Appendix 6)
The system according to any one of Supplementary Notes 3 to 5, wherein the registration device further includes a transmission control unit that controls transmission of information used in the payment processing to the payment device selected by the selection unit.
(Appendix 7)
an acquisition means for acquiring information indicating a detection result of change in the payment device;
A registration device comprising: determining means for determining available payment devices based on the information acquired by the acquisition device, and determining means for making available payment devices for which change is not detected.
(Appendix 8)
The determining means is configured to exclude a payment device whose change has been detected by the detection device from available payment devices, and then, when change is no longer detected by the detection device, select a payment device that can use the payment device. The registration device described in Appendix 7.
(Appendix 9)
Detects change at the payment device,
A method of determining a payment device in which change is not detected as a usable payment device.
(Appendix 10)
The method according to appendix 9, wherein, after excluding the payment device in which the change has been detected from the available payment devices, if the change is no longer detected, the payment device is set as the available payment device.
(Appendix 11)
to the computer,
a first process of acquiring information indicating a detection result of change in the payment device;
and a second process for determining, based on the acquired information, the payment device in which the change is not detected as a usable payment device.
(Appendix 12)
The second process includes, after excluding the payment device in which the change has been detected from the available payment devices, when the change is no longer detected, the payment device is set as a usable payment device. Includes the program described in Appendix 11.
(Appendix 13)
It has a registration device for registering products to be purchased by a customer based on the operations of a store clerk, and a payment device for performing payment processing based on the operations of the customer,
The payment device is
a detection means for detecting the card;
and a payment processing means that executes at least a part of the payment processing when the card is no longer detected by the detection means,
The registration device includes:
A system comprising: a determining unit that, when the payment process is completed by the payment processing unit, sets the payment device on which the payment process has been completed as an available payment device.

100, 300, 1600 Accounting system 110, 310, 310a, 310b, 310c, 1610 Settlement device 111 Detection section 120, 320, 1620, 1710, 1720 Registration device 121, 810, 1621, 1711, 1722 Determination section 820, 1712 Selection section

Claims (6)

a registration device that registers products to be purchased by a customer based on operations by a store clerk;
and a payment device that performs payment processing based on the customer's operations,
The payment device is
It has a product detection means for detecting the product,
The registration device includes:
determining means for determining an available payment device based on status data representing the state of the payment device received from the payment device ;
When the state data represents a state in which the most recent payment process has been completed, the state data further includes detection data by the product detection means,
The determining means may be a payment device that can use a payment device in which the status data indicates that the payment has been completed, and the detection data included in the status data indicates that the product is not detected. , a payment device in which the state data represents a state in which payment has been completed, and the detection data included in the state data represents a state in which the product is detected; and the state data represents a state in which payment processing cannot be continued. a payment device and an unavailable payment device;
system. The registration device further includes a selection device that selects one of the payment devices made available by the determination device in response to an operation by the store clerk.
The system of claim 1. The registration device further includes selection means for selecting one of the determined payment devices based on a predetermined rule.
The system of claim 1. The payment device further includes card detection means for detecting a card,
The determining means determines the payment device whose card is detected by the card detection device as an unavailable payment device;
A system according to any one of claims 1 to 3. a registration device that registers products to be purchased by a customer based on operations by a store clerk;
A payment device that performs payment processing based on the customer's operations;
A method for a system having:
The payment device is
Detects the product,
The registration device,
determining an available payment device based on status data representing the state of the payment device received from the payment device ;
When the state data represents a state in which the most recent payment process has been completed, the state data further includes detection data regarding the detection of the product by the payment device,
The registration device,
An available payment device is a payment device in which the status data indicates that the payment has been completed, and the detection data included in the status data indicates that the product is not detected; a payment device that represents a state in which payment has been completed, and in which the detection data included in the state data represents a state in which the product is being detected; and a payment device in which the state data represents a state in which payment processing cannot be continued. make the payment device unusable;
Method. a registration device that registers products to be purchased by a customer based on operations by a store clerk;
A payment device that performs payment processing based on the customer's operations, the program for a system comprising:
The computer for the payment device,
detect the product,
execute the process,
the computer for the registration device;
determining an available payment device based on status data representing the state of the payment device received from the payment device ;
execute the process,
When the state data represents a state in which the most recent payment process has been completed, the state data further includes detection data regarding the detection of the product by the payment device,
In the determination by the computer for the registration device, the payment device is configured such that the status data represents a state in which payment has been completed, and the detection data included in the state data represents a state in which the product is not detected. A payment device that can be used, the state data representing a state in which the payment has been completed, and the detection data included in the state data representing a state in which the product is being detected; A payment device that represents a state where it is impossible to continue, and a payment device that is unavailable .
program .

Images