Article sales data processor and program

Abstract

To provide an article sales data processor and a program that enable customers to check a payable amount of payment media without worrying about the eyes of others during article registration, and also enable the customers to cancel registered articles according to the payable amount.SOLUTION: An article sales data processor according to an embodiment includes payment method registration means and display means. The payment method registration means accepts registration of a payment method before registration of articles to be settled. The display means displays a payable amount confirmation operation unit which can accept a user's operation requesting the display of the payable amount corresponding to the payment method registered during the registration of the articles to be settled. The display means also displays an article cancellation declaration unit that enables the user to cancel the registered articles for settlement when the payable amount confirmation operation unit is operated by the user and when the payable amount of the user corresponding to the payment method is not sufficient for a payment amount for the purchase of the articles for settlement.SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] An embodiment of the present invention relates to a product sales data processing device and a program. [Background technology]

[0002] Conventionally, when a customer pays with various electronic money, prepaid cards, credit cards, etc. (hereinafter referred to as payment media) at a POS (Point Of Sale) terminal, after completing the registration of all products to be purchased, the customer must then have the POS terminal read the payment media when making the payment.

[0003] In such technology, if the available balance of the payment medium is insufficient for the total payment amount, the customer cannot check the available balance of the payment medium until the time of executing the payment. Therefore, especially in a POS register where a store clerk is present, the customer may feel embarrassed if the balance of the payment medium is insufficient, and even in a fully self-service POS register where no store clerk is present, the customer may feel that they are causing trouble to customers waiting behind them if the register is busy. In addition, even if the customer himself knows that the available balance of the payment medium is insufficient, since all the products to be purchased have already been registered, it is time-consuming to ask a store clerk to cancel the purchase of the products so that the total amount according to the balance of the payment medium is brought down. Summary of the Invention [Problem to be solved by the invention]

[0004] To provide a product sales data processing device and program that enables a customer to check the available payment amount of a payment medium without worrying about other people's eyes while registering a product, and enables the customer himself to cancel a registered product according to the available payment amount. [Means for solving the problem]

[0005] The product sales data processing device according to the embodiment includes a payment method registration means and a display means. The payment method registration means accepts the registration of a payment method before the registration of a product to be paid. The display means displays a payment available amount confirmation operation unit capable of accepting a user's operation to request the display of a payment available amount corresponding to the registered payment method during the registration of the product to be paid. In addition, when the payment available amount confirmation operation unit is operated by a user during the registration of the product to be paid and the payment available amount of the user corresponding to the payment method is insufficient for the payment amount for the purchase of the product to be paid, the display means displays a product cancellation declaration unit that enables an operation to cancel the registered product to be paid. Note that "product registration in progress" means that the product sales data processing device is in a state where it can read a code symbol attached to the product and store product information of the product. Therefore, "product registration in progress" includes a state where no product is registered but a product can be registered, and also includes a period from when one or more products are registered until the start of payment processing. [Brief description of the drawings]

[0006] [Figure 1] FIG. 1 is a diagram illustrating an example of a hardware configuration of a POS terminal according to an embodiment. [Diagram 2] FIG. 2 is a diagram illustrating an example of a functional configuration of the POS terminal according to the embodiment. [Diagram 3] FIG. 3 is a diagram illustrating an example of a payment medium registration screen according to the embodiment. [Figure 4] FIG. 4 is a diagram illustrating an example of a product details screen according to the embodiment. [Diagram 5] FIG. 5 is a diagram showing an example of a balance confirmation screen when the balance is sufficient according to the embodiment. [Figure 6] FIG. 6 is a diagram showing an example of a balance confirmation screen when the balance is insufficient according to the embodiment. [Figure 7] FIG. 7 is a diagram showing an example of a product details screen in the product cancellation mode according to the embodiment. [Figure 8]FIG. 8 is a diagram showing an example of a change / add / delete screen for payment media according to the embodiment. [Figure 9-1] FIG. 9-1 is a flowchart illustrating an example of a flow of a process executed by the POS terminal according to the embodiment. [Figure 9-2] FIG. 9-2 is a continuation of the flowchart of FIG. 9-1. [Figure 10] FIG. 10 is a diagram showing an example of a balance confirmation screen when the balance is sufficient according to the modified example. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0007] (Embodiment) Hereinafter, a product sales data processing device and a program according to an embodiment will be described with reference to the drawings. In the following embodiment, an example of a product sales data processing device introduced in a retail store (shop) such as a supermarket or a convenience store will be described, but the present invention is not limited to this embodiment.

[0008] FIG. 1 is a diagram showing an example of a hardware configuration of a POS (Point Of Sale) terminal 10 according to the present embodiment. The POS terminal 10 is an example of a product sales data processing device according to the present embodiment. The POS terminal 10 may be a manned register or an unmanned register. A manned register is a register where a store clerk is involved in the registration or payment of products purchased by a customer. For example, a normal POS register, a face-to-face POS register, and a semi-self-service register are examples of a manned register. A normal POS register is a register where a store clerk who faces a customer registers products and makes payments. A face-to-face POS register is a register where a store clerk who faces a customer registers products and the customer makes payments. A semi-self-service register is a register where a store clerk who faces a customer registers products using a registration machine, and the customer makes payments (settlements) using an accounting machine configured separately from the registration machine. An unmanned register is a register where a customer registers products to purchase and makes payments by himself. For example, a full self-service register is an example of an unmanned register.

[0009] In the following, the present embodiment will be described by taking as an example a case where the POS terminal 10 is a fully self-service register. Therefore, in the present embodiment, the user of the POS terminal 10 is a customer, but in the case of a manned register, the user may be a store clerk.

[0010] As shown in FIG. 1, the POS terminal 10 includes a central processing unit (CPU) 11, a read only memory (ROM) 12, and a random access memory (RAM) 13.

[0011] The CPU 11 is an example of a processor, and performs overall control of each unit of the POS terminal 10. The ROM 12 stores various programs. The RAM 13 is a workspace in which programs and various data are expanded.

[0012] The CPU 11, ROM 12, and RAM 13 are connected via a bus or the like to constitute a computer-configured control unit 100. In the control unit 100, the CPU 11 operates according to a program stored in the ROM 12 or the storage unit 18 and loaded into the RAM 13, thereby executing various types of processing.

[0013] The POS terminal 10 also includes a display unit 14, an operation unit 15, an imaging unit 16, a communication unit 17, a storage unit 18, and the like.

[0014] The display unit 14 is a display device such as an LCD (Liquid Crystal Display), etc. Under the control of the CPU 11, the display unit 14 displays various types of information.

[0015] The operation unit 15 is an input device capable of accepting user operations. In this embodiment, the operation unit 15 is a touch panel provided on the display unit 14. The operation unit 15 may also be a keyboard, a pointing device, or the like. The operation unit 15 outputs the operation content input via the input device to the CPU 11.

[0016] The imaging unit 16 is, for example, a digital camera having an imaging element such as a CCD (Charge Coupled Device) or a CMOS (Complementary Metal Oxide Semiconductor). In this embodiment, the imaging unit 16 is used for reading (imaging) code symbols such as barcodes and two-dimensional codes, or for object recognition, but is not limited to this. Object recognition is general object recognition that recognizes the type of product, etc. from an image of the product itself obtained by imaging the product. Furthermore, the imaging unit 16 may be a scanner specialized for reading code symbols.

[0017] The imaging unit 16 of this embodiment not only reads the code symbol attached to the product to be paid for, but also reads the code symbol for a payment service using the code symbol. For example, the imaging unit 16 reads the code symbol displayed by a payment application preinstalled in a mobile terminal carried by a customer. The POS terminal 10 may include an imaging unit 16 for reading the code symbol for the payment service in addition to the imaging unit 16 for reading the code symbol attached to the product to be paid for.

[0018] The communication unit 17 is a wired or wireless communication interface that can be connected to an in-store network or the like. The communication unit 17 communicates with external devices such as a store server via the network. For example, the communication unit 17 communicates with the store server via the network and acquires product information such as the product name, product code, and unit price from the store server. Also, for example, under the control of the control unit 100, the communication unit 17 communicates with a payment server of a credit card company, a payment server of a payment service company that provides a payment app, and a virtual currency payment app pre-implemented in a mobile terminal held by the customer, and inquires about the payment amount that the customer's credit card can pay.

[0019] The storage unit 18 is a non-volatile storage device that has a storage medium such as a hard disk drive (HDD) or a flash memory, and maintains the stored contents even when the power is cut off. The storage unit 18 stores a program 181 that can be executed by the CPU 11 and various setting information.

[0020] The magnetic card reader / writer (RW) 19 reads the prepaid balance stored in a magnetic prepaid card and writes the balance after a payment is made. The magnetic card reader / writer 19 may also have a function of reading magnetic credit cards.

[0021] An IC (Integrated Circuit) card reader / writer 20 reads and writes data from and to an IC card having an IC chip built in. The IC card is, for example, an IC chip type credit card.

[0022] The electronic money reader / writer 21 reads and writes prepaid electronic money registered in a card or a portable electronic device. The electronic money reader / writer 21 includes, for example, an NFC (Near Field Communication) antenna 211 and a data communication unit 212 configured with a control chip. The data communication unit 212 performs data communication by wireless communication with an electronic payment medium, that is, an IC card or a portable electronic device equipped with a non-contact IC chip, and reads and writes data from and to the IC chip. The electronic money in this embodiment is, for example, prepaid or precharged.

[0023] The change machine 22 accepts bills and coins (hereinafter collectively referred to as cash) paid by customers and dispenses change as necessary. The change machine 22 includes, for example, a bill insertion slot, a coin insertion slot, a bill ejection slot, and a coin ejection slot.

[0024] In addition, Figure 1 illustrates an example in which the POS terminal 10 is equipped with a magnetic card reader / writer 19, an IC card reader / writer 20, and an electronic money reader / writer 21, but the magnetic card reader / writer 19, the IC card reader / writer 20, and the electronic money reader / writer 21 may be externally connected to the POS terminal 10 via various interfaces.

[0025] Electronic money payment, credit card payment, code payment, prepaid payment, and virtual currency payment are examples of payment methods and payment media in this embodiment. Note that the term "payment method" may include cash payment. Also, when electronic money payment, credit card payment, code payment, prepaid payment, and virtual currency payment are distinguished from cash payment, they are called cashless payment. Note that the payment method, payment media, and cashless payment are not limited to the above examples, and known technologies can be adopted.

[0026] The hardware configuration of the POS terminal 10 is not limited to the example shown in Fig. 1, and the POS terminal 10 may further include other configurations. For example, the POS terminal 10 may include a reader for credit card touch payment, a printer for issuing a paper receipt showing the payment result, and a speaker capable of outputting sound. The POS terminal 10 does not have to support all of the above payment methods.

[0027] Next, the functional configuration of the POS terminal 10 will be described. FIG. 2 is a diagram showing an example of the functional configuration of the POS terminal 10 according to this embodiment. Specifically, FIG. 2 illustrates various functions realized by the program 181 installed in the POS terminal 10. The program 181 executed by the POS terminal 10 of this embodiment has a modular configuration including the display control unit 101, the payment media registration processing unit 102, the reception unit 103, the product registration processing unit 104, the balance inquiry unit 105, and the settlement processing unit 106 shown in FIG. 2. The CPU 11 reads out the program 181 from the storage unit 18 and loads the above-mentioned units (the display control unit 101, the payment media registration processing unit 102, the reception unit 103, the product registration processing unit 104, the balance inquiry unit 105, and the settlement processing unit 106) onto the RAM 13. As a result, the above-mentioned units are generated on the RAM 13. Note that the functions of the POS terminal 10 are not limited to those shown in FIG. 2.

[0028] The display control unit 101 controls the display unit 14 to display various screens. Specifically, the display control unit 101 in this embodiment displays a payment medium registration screen, a product details screen, a balance confirmation screen, and a payment medium change / add / delete screen on the display unit 14. The display control unit 101 is an example of a display means in this embodiment.

[0029] 3 is a diagram showing an example of a payment medium registration screen 30 according to the present embodiment. When a user starts an operation on the POS terminal 10, the display control unit 101 causes the display unit 14 to display the payment medium registration screen 30 before registering the product to be paid for.

[0030] The payment medium registration screen 30 includes, as an example, a message 310 asking the user whether or not to register a payment medium, a “Yes” button 311, and a “No” button 312.

[0031] The "Yes" button 311 is a button image that accepts a request from the user to register a payment medium. When the "Yes" button 311 is pressed by the user, the display control unit 101 causes the display unit 14 to display a message that provides guidance on how to register the payment medium, such as "Please hold the payment medium to be registered over the reader." Alternatively, the display control unit 101 may cause a pop-up display on the display unit 14 of a screen that allows the user to select the type of payment medium. A plurality of screens, such as the screen that provides guidance on how to register a payment medium, may be collectively referred to as the payment medium registration screen 30.

[0032] When the user operates to input the payment medium to be registered in response to the guidance, the payment medium registration processing unit 102 described below registers the input payment medium. In addition, when the user completes the registration of the payment medium, the display control unit 101 causes the display unit 14 to display a product details screen.

[0033] The "No" button 312 is a button image that accepts the user's request that registration of payment media is not necessary at this stage. When the "No" button 312 is pressed by the user, the display control unit 101 ends the display of the payment media registration screen 30 and causes the display unit 14 to display the product details screen.

[0034] 4 is a diagram showing an example of a product details screen 40 according to this embodiment. The display control unit 101 displays the product details screen 40 while the product to be paid for is being registered. Note that "registering a product" means that the POS terminal 10 is in a state where it can read the code symbol attached to the product with the imaging unit 16 and store the product information of the product in the storage unit 18. Therefore, "registering a product" includes a state where no product has been registered but a product can be registered, and also includes a period from when one or more products have been registered until the "Checkout" button 410 is pressed.

[0035] The product details screen 40 includes, for example, a detail display field 400 of the registered product to be paid for (hereinafter simply referred to as the detail display field 400), a "Check balance of payment medium" button 420, a "Change / add / delete payment medium" button 421, and a payment amount display field 423. In the case of a fully self-service register where the customer himself operates the POS terminal 10 as a user, the display control unit 101 may display a message 401 prompting the user to register the product and a "Checkout" button 410 on the display unit 14, as shown in FIG.

[0036] The details display section 400 is a screen area in which, for example, the product names, quantities, unit prices, and total prices for each product registered as items to be settled are displayed.

[0037] The "Check balance of payment media" button 420 is a button image capable of accepting a user's operation to request the display of the balance of the registered payment media. The balance of the payment media is an example of a payable amount corresponding to the payment method in this embodiment. As shown in FIG. 4, the "Check balance of payment media" button 420 is displayed on the product details screen 40 during the registration of the product to be paid. That is, the display control unit 101 in this embodiment displays the "Check balance of payment media" button 420 on the display unit 14, capable of accepting a user's operation to request the display of the payable amount corresponding to the registered payment method during the registration of the product to be paid. The "Check balance of payment media" button 420 is an example of a payable amount confirmation operation unit in this embodiment. In addition, the user's operation of pressing the "Check balance of payment media" button 420 is an example of a user's operation to request the display of the payable amount corresponding to the registered payment method.

[0038] The display control unit 101 displays the balance of the registered payment media when a user operation requesting to display the payable amount corresponding to the registered payment method is accepted by the acceptance unit 103 described below, that is, when the user presses the "Check balance of payment media" button 420. Specifically, when the user presses the "Check balance of payment media" button 420, the display control unit 101 causes the display unit 14 to display a balance confirmation screen described below.

[0039] The "Change / Add / Delete Payment Media" button 421 is a button image that can accept a user's operation to request adding, changing, or deleting a payment media. The display control unit 101 displays the "Change / Add / Delete Payment Media" button 421 on the product details screen 40 while the product to be paid for is being registered. When the user presses the "Change / Add / Delete Payment Media" button 421, the display control unit 101 displays a change / add / delete payment media screen, described below, as a pop-up on the product details screen 40. The "Change / Add / Delete Payment Media" button 421 may also be called a change / add / delete payment media declaration button.

[0040] The payment amount display field 423 is a screen area that displays the total amount that the customer needs to pay for the purchase of all products registered as items to be settled. This total amount is an example of the payment amount for the purchase of products to be settled in this embodiment. The total amount that the customer needs to pay for the purchase of all products to be settled is, for example, the total of the unit prices of the registered products to be settled, consumption tax, the price of the plastic bag to put the products in, etc. If there are any other expenses that the customer needs to pay for the purchase of the products, they may be included in this total amount.

[0041] The "Checkout" button 410 is a button image that can receive an operation by the user to request the start of payment. When the "Checkout" button 410 is pressed by the user, the payment processing unit 106, which will be described later, starts the payment process.

[0042] Note that the product details screen 40 in Figure 4 is an example of a fully self-service register, but in the case of a face-to-face manned register equipped with two display units 14 facing the store clerk and the customer, the display control unit 101 displays the product details screen 40 on the display unit 14 facing the customer, which includes a details display field 400, a "Check payment medium balance" button 420, a "Change / add / delete payment medium" button 421, and a payment amount display field 423.

[0043] When the user presses the "Check balance of payment medium" button 420, the display control unit 101 displays a balance check screen on the display unit 14. In this embodiment, the display control unit 101 changes the display content of the balance check screen depending on whether the balance of the registered payment medium is equal to or greater than the payment amount for purchasing the product to be settled.

[0044] First, a case will be described in which the balance of the registered payment medium is equal to or greater than the payment amount for the purchase of the product to be settled, that is, the balance of the registered payment medium is sufficient.

[0045] 5 is a diagram showing an example of a balance check screen 50 when the balance is sufficient according to this embodiment. As shown in FIG 5, the display control unit 101 displays the balance check screen 50 as a pop-up on the product details screen 40, for example.

[0046] When there is no insufficient balance, the balance confirmation screen 50 includes, for example, a display field 510 for the name of the registered payment media, a field 511 for displaying the balance of the registered payment media, a field 512 for displaying the payment amount, a field 513 for displaying the difference, a ``Back'' button 520, and a ``Close'' button 515.

[0047] The registered payment media name display field 510 is a screen area in which the names of payment media registered by the payment media registration processing unit 102 (described later) based on user operation are displayed.

[0048] The registered payment media balance display field 511 is a screen area in which the balance of the payment media registered by the payment media registration processing unit 102 described below is displayed based on the user's operation. The balance of the payment media displayed in the registered payment media balance display field 511 is an example of the payable amount corresponding to the registered payment method in this embodiment. Hereinafter, the registered payment media balance display field 511 is also simply referred to as the balance display field 511.

[0049] The balance of a payment medium is the amount that a customer can pay with that payment medium in the current settlement, i.e., the available payable amount. For example, if the registered payment medium is a prepaid or precharge type, the unused amount of the deposited or charged amount is displayed as the balance in the balance display field 511 of the registered payment medium. Also, if the registered payment medium is a credit card, the unused amount of the credit card's credit limit is displayed as the balance in the balance display field 511 of the registered payment medium.

[0050] The payment amount display field 512 is a screen area that displays the total amount that the customer must pay for the purchase of all products registered as items to be settled, i.e., the payment amount. The amount displayed in the payment amount display field 512 is the same as the amount displayed in the payment amount display field 423 on the product details screen 40.

[0051] The difference display field 513 is a screen area in which the difference between the balance of the payment medium displayed in the balance display field 511 and the payment amount displayed in the payment amount display field 512 is displayed.

[0052] If the user has not registered a payment medium, the registered payment medium name display field 510, the registered payment medium balance display field 511, and the difference display field 513 will be blank. Alternatively, if the user has not registered a payment medium, the display control unit 101 may not display the “Check payment medium balance” button 420 on the product details screen 40.

[0053] The "Back" button 520 is a button image that can accept a user operation to close the balance confirmation screen 50 and return the screen display to the product details screen 40. Note that the wording displayed on the button may be "Confirm" or "Confirm", etc., which indicates completion of the balance confirmation.

[0054] The "Close" button 515 is a button image that can accept a user operation to close the balance check screen 50. In Fig. 5, the balance check screen 50 is displayed as a pop-up on the product details screen 40, so when the balance check screen 50 is closed by the display control unit 101, the product details screen 40 is displayed. Note that only one of the "Back" button 520 and the "Close" button 515 may be displayed.

[0055] As shown in the product details screen 40 illustrated in FIG. 4, in this embodiment, the display control unit 101 does not display the balance of the registered payment media unless the "Check balance of payment media" button 420 is pressed. Then, when the "Check balance of payment media" button 420 is pressed by the user, the display control unit 101 displays the balance confirmation screen 50 as shown in FIG. 5. For this reason, the timing of displaying the balance of the payment media can be determined by the customer user. For example, if the customer user does not want the balance of the payment media to be seen by accompanying persons or other customers around, the customer user can press the "Check balance of payment media" button 420 when there is no one around to display the balance of the registered payment media.

[0056] Next, a case where the balance of the registered payment medium is less than the payment amount for the purchase of the product to be settled, that is, a case where the balance of the registered payment medium is insufficient, will be described.

[0057] FIG. 6 is a diagram showing an example of a balance confirmation screen 50 when the balance is insufficient according to this embodiment.

[0058] The balance confirmation screen 50 in the event of insufficient balance includes, for example, a display field 510 for the name of the registered payment medium, a field 511 for displaying the balance of the registered payment medium, a field 512 for displaying the payment amount, a field 513 for displaying the difference, a ``Back'' button 520, a ``Close'' button 515, a message 530 notifying that the balance of the registered payment medium is insufficient, a ``Cancel item'' button 540, and a ``Cash payment'' button 543.

[0059] The display field 510 for the name of the registered payment media, the display field 511 for the balance of the registered payment media, the payment amount display field 512, the difference display field 513, the ``Back'' button 520, and the ``Close'' button 515 are the same as when there is no insufficient balance as described in Figure 5.

[0060] The message 530 notifying that the registered payment medium has an insufficient balance is, for example, a statement such as "The payment medium has an insufficient balance." Note that the method of notifying that the registered payment medium has an insufficient balance is not limited to the message 530, and the display control unit 101 may highlight the difference display field 513.

[0061] The "Cancel Product" button 540 is a button image capable of accepting a user's operation to request a cancellation operation of a registered product that is the subject of payment. When the "Cancel Product" button 540 is pressed by a user, the product registration processing unit 104 described below enables the operation of canceling the registered product that is the subject of payment. Furthermore, when the "Cancel Product" button 540 is pressed by a user, the display control unit 101 closes the balance confirmation screen 50 and displays the product details screen 40 in a product cancellation possible mode. The "Cancel Product" button 540 is an example of a product cancellation declaration unit in this embodiment. The "Cancel Product" button 540 may be called a product cancellation declaration button.

[0062] The "Cash Payment" button 543 is a button image that can accept a user's operation to change the payment method to cash payment. When the "Cash Payment" button 543 is pressed by the user, the payment medium registration processing unit 102 described later deletes the registered payment medium and changes the payment method to cash payment. When the registered payment method is cashless payment and the available payment amount corresponding to the registered payment method is insufficient for the payment amount for the purchase of the product to be paid, the display control unit 101 displays the "Cash Payment" button 543. In this embodiment, as shown in FIG. 6, the display control unit 101 displays the "Cash Payment" button 543 on the balance confirmation screen 50 when the balance is insufficient.

[0063] When the "Cash Payment" button 543 is pressed, the payment medium registration processing unit 102 described below may not only change all payments to cash payments, but may also permit the remaining balance after cashless payment to be paid in cash. In other words, the "Cash Payment" button 543 allows the user to select whether to change the payment method to cash payment or to pay the remaining balance after cashless payment in cash. The "Cash Payment" button 543 is an example of a cash payment declaration section in this embodiment.

[0064] In addition, the display control unit 101 may display the “Change / Add / Delete Payment Medium” button 421 displayed on the product details screen 40 described in FIG. 4 on the balance confirmation screen 50 when the balance is insufficient, as shown in FIG. 6.

[0065] 5 and 6 is an example, and the display control unit 101 may display the balance check screen 50 in full screen on the display unit 14. The display control unit 101 may also display the display content of the balance check screen 50 in a blank area of ​​the product details screen 40.

[0066] Next, the product details screen 40 in the product cancellation mode will be described. When the user presses the "Cancel product" button 540 on the balance confirmation screen 50 in the case where the balance is insufficient as described in Fig. 6, the display control unit 101 closes the balance confirmation screen 50 and displays the product details screen 40 in the product cancellation mode.

[0067] FIG. 7 is a diagram showing an example of the product details screen 40 in the product cancellation mode according to the present embodiment.

[0068] The product details screen 40 in the product cancellation mode has various button images or an input field for the number of products that can be input by the user to cancel the product registered as the payment target, in addition to the normal display contents described in Fig. 4. In the example shown in Fig. 7, the product details screen 40 in the product cancellation mode includes a delete button 440 and a minus button 431 in addition to the normal display contents described in Fig. 4.

[0069] The delete button 440 is a button image that can accept a user operation to delete a product on an item-by-item basis.

[0070] The minus button 431 is a button image that can receive a user's operation to decrease the number of products by one.

[0071] In the example shown in Fig. 7, the user presses the minus button 431 once in the row of the product with the product name "Tomato" on the product details screen 40 shown in Fig. 4, decreasing the quantity from "2" to "1." When a user operation is input to cancel a product registered as a payment target, the display control unit 101 updates the total amount for each product in the details display field 400 and the payment amount in the payment amount display field 423 to match the item and quantity of the product after cancellation.

[0072] The delete button 440 and the minus button 431 are examples of means capable of accepting a user's operation to cancel a product registered as a payment target, and means for accepting a user's operation to cancel a product registered as a payment target are not limited to these. For example, the display control unit 101 may display an input field on the product details screen 40 in which the quantity of the product can be selected using a list box, or may display a numeric keypad on the product details screen 40 for inputting the number of the product quantity.

[0073] Next, the screen for changing, adding, and deleting payment media will be explained.

[0074] 8 is a diagram showing an example of the change / add / delete payment medium screen 60 according to this embodiment. When the user presses the “change / add / delete payment medium” button 421 on the product details screen 40, the display control unit 101 displays the change / add / delete payment medium screen 60 as a pop-up on the product details screen 40.

[0075] As shown in Figure 8, the change / add / delete payment media screen 60 includes, for example, a message 601 instructing the user how to input the payment media to be registered, a display field 610 for the name of a registered payment media, a display field 620 for the name of a newly registered payment media, a delete button 611 for the registered payment media, a confirmation button 621 for the newly registered payment media, a "Back" button 630, and a "Close" button 515.

[0076] The content of the message 601 instructing the user how to input the payment medium to be registered is, for example, "Please hold the payment medium to be added over the reader" as shown in FIG. 8, but is not limited to this.

[0077] The display field 610 for the names of registered payment media is a screen area in which the names of payment media already registered by the user are displayed. If a payment media has not yet been registered, the display control unit 101 does not display the display field 610 for the names of registered payment media.

[0078] The Delete Registered Payment Media button 611 is a button image that can accept a user operation to delete a registered payment media. When the Delete Registered Payment Media button 611 is pressed by a user, the payment media registration processing unit 102 described later deletes the registration of the payment media displayed in the display field 610 of the registered payment media name corresponding to the Delete Registered Payment Media button 611.

[0079] The display field 620 for the name of the newly registered payment medium is a screen area in which the name of the payment medium newly registered by the user is displayed after the change / add / delete payment medium screen 60 is displayed.

[0080] The confirmation button 621 for the newly registered payment medium is a button image that can accept a user operation to confirm the registration of the payment medium displayed in the display field 620 for the name of the newly registered payment medium.

[0081] If the user wishes to change the payment medium, the registered payment medium can be changed by deleting the registered payment medium and registering a new payment medium. The payment medium change / add / delete screen 60 may include a "Change" button that accepts the operation to change the payment medium. Only one payment medium may be registered, or multiple payment media may be registered.

[0082] The "Back" button 630 is a button image that can accept a user operation to close the change / add / delete payment medium screen 60 and return the screen display to the product details screen 40. The wording displayed on the button may be "End" or "Confirm", etc.

[0083] The "Close" button 640 is a button image that can accept a user's operation to close the change / add / delete payment medium screen 60. In Fig. 8, the change / add / delete payment medium screen 60 is displayed as a pop-up on the product details screen 40, so when the change / add / delete payment medium screen 60 is closed by the display control unit 101, the product details screen 40 is displayed. Note that only one of the "Back" button 630 and the "Close" button 640 may be displayed.

[0084] 8 is an example, and the display control unit 101 may display the change / add / delete payment medium screen 60 on the full screen of the display unit 14. The display control unit 101 may also display the display content of the change / add / delete payment medium screen 60 in a blank area of ​​the product details screen 40.

[0085] The display modes of the above-mentioned screens are merely examples, and the screen layouts and the like are not limited to those described above. Furthermore, the display control unit 101 may cause the display unit 14 to display various screens other than those described above.

[0086] Returning now to FIG. 2, the payment media registration processing unit 102 accepts the registration of a payment method before the registration of a product to be paid for. More specifically, the payment media registration processing unit 102 registers a payment media when the user operates to register the payment media in response to the guidance on the payment media registration screen 30 displayed before the registration of a product to be paid for. If the payment media to be registered is a prepaid or precharge card, etc., the payment media registration processing unit 102 obtains the balance of the payment media from the payment media when accepting the registration. Also, if the payment media to be registered is a credit card or a payment app whose balance is stored on the server side, the payment media registration processing unit 102 obtains access information from the payment media to inquire about the available payment amount from the credit card operating company or the payment app server when accepting the registration.

[0087] The payment media registration processing unit 102 stores the payment media to be registered and the balance or access information for inquiries in, for example, the storage unit 18. The payment media registration processing unit 102 is an example of a payment method registration means in this embodiment.

[0088] Furthermore, the payment media registration processing unit 102 can accept at least one of adding, changing, and deleting a payment method while registering a product to be paid for. In this embodiment, the payment media registration processing unit 102 can accept all of adding, changing, and deleting while registering a product to be paid for. More specifically, when the payment media change / add / delete screen 60 described in FIG. 8 is displayed while registering a product to be paid for, the payment media registration processing unit 102 adds, changes, and deletes a payment medium based on a user operation performed on the screen.

[0089] 6, when the user presses the "Cash payment" button 543 on the balance confirmation screen 50, the payment medium registration processing unit 102 deletes the registered payment medium and changes the payment method to cash payment. The payment medium registration processing unit 102 may not only change all payments to cash payments, but may also permit the balance paid by cashless payment to be paid in cash.

[0090] The reception unit 103 receives various operations of the user via the operation unit 15. In the present embodiment, the operation unit 15 is configured as a touch panel provided on the display unit 14, and therefore, when various button images displayed on the display unit 14 are pressed, the reception unit 103 receives the pressing operation.

[0091] The product registration processing unit 104 registers the product to be paid for. For example, the product registration processing unit 104 communicates with the store server via the communication unit 17 and the network, and acquires product information such as the product name, product code, and unit price corresponding to the code symbol read by the imaging unit 16 or the captured product image from the store server. The product registration processing unit 104 stores the acquired product information in the storage unit 18 as product information of the product to be paid for, together with the quantity of the product to be purchased.

[0092] Furthermore, when the user presses the "Cancel Product" button 540 on the balance confirmation screen 50 when the balance is insufficient, the product registration processing unit 104 enables the operation of canceling a registered product that is the subject of payment. When the user performs an operation to cancel a product on the product details screen 40 in the product cancellation mode, the product registration processing unit 104 deletes the product information of the product that is the subject of payment stored in the storage unit 18 or changes the quantity based on the operation.

[0093] When the "Check balance of payment medium" button 420 on the statement display field 400 is pressed, the balance inquiry unit 105 inquires about the balance of the registered payment medium. If the registered payment medium is a prepaid or precharge card, the balance inquiry unit 105 reads out the balance of the payment medium stored in the memory unit 18. If the registered payment medium is a credit card or a payment app whose balance is stored on the server side or on the customer's mobile terminal side, the balance inquiry unit 105 inquires about the available payment amount from the credit card operating company or the server or mobile terminal of the payment app.

[0094] The payment processing unit 106 pays for the products to be paid for based on the registered payment method. More specifically, the payment processing unit 106 executes a payment process to pay the total amount to be paid by the customer for the purchase of all the products registered as the products to be paid for by the registered payment medium. The payment processing unit 106 is an example of a payment processing means in this embodiment.

[0095] Next, the flow of processing executed by the POS terminal 10 configured as above will be described.

[0096] 9-1 and 9-2 are flowcharts showing an example of the flow of processing executed by the POS terminal 10 according to this embodiment. This flowchart is displayed, for example, when the user starts an operation on the POS terminal 10.

[0097] First, the display control unit 101 causes the display unit 14 to display the payment medium registration screen 30 (S1).

[0098] Then, when the user presses the "Yes" button 311 on the payment medium registration screen 30 to input the payment medium, the reception unit 103 receives the input operation of the payment medium by the user.

[0099] When the accepting unit 103 accepts an input operation of a payment medium by the user (S2 "Yes"), the payment medium registration processing unit 102 registers the input payment medium (S3).

[0100] Then, the display control unit 101 causes the display unit 14 to display the product details screen 40 (S4). At this point, the product to be paid for has not yet been registered, so the product is not yet displayed in the details display field 400 of the product details screen 40. After the product details screen 40 is displayed in S4, it becomes possible to register the product to be paid for. Therefore, in Figs. 9-1 and 9-2, the period from S4 to the execution of the payment process in S26 described below is called "registering the product to be paid for". As described above, the product details screen 40 includes a "check balance of payment media" button 420. The process of displaying the product details screen 40 in S4 is an example of a first display step in this embodiment.

[0101] Furthermore, if the user presses the "No" button 312 on the payment media registration screen 30, the user's input operation of the payment media is not accepted (S2 "No"). In this case, the display control unit 101 ends the display of the payment media registration screen 30, proceeds to S4 and displays the product details screen 40 on the display unit 14. Note that here, if the input operation of the payment media is not accepted in S2, the display control unit 101 does not display the "Check payment media balance" button 420 on the product details screen 40, or grays out the "Check payment media balance" button 420 so that it cannot be pressed.

[0102] Then, when an operation to register a product, such as reading a code symbol by the imaging unit 16, is accepted (S5 "Yes"), the product registration processing unit 104 registers the product to be paid for (S6). In this case, the display control unit 101 displays the product registered by the product registration processing unit 104 in the details display field 400 of the product details screen 40 (S7).

[0103] Moreover, if the operation to register the product is not accepted (S5 "No"), the display control unit 101 continues to display the product details screen 40.

[0104] In this embodiment, the POS terminal 10 is a fully self-service register, so the user performs the operation of registering the product. However, if the POS terminal 10 is a manned register, a store clerk performs the operation of registering the product.

[0105] Furthermore, when the "Check balance of payment media" button 420 on the product details screen 40 is pressed (S8 "Yes"), the balance inquiry unit 105 inquires about the balance of the registered payment media (S9).

[0106] If the balance of the registered payment medium is equal to or greater than the payment amount (S10 “No”), the display control unit 101 pops up a balance confirmation screen 50 without the “Cancel product” button 540 on the product details screen 40 as shown in FIG. 5 (S11).

[0107] The display control unit 101 continues to display the balance confirmation screen 50 without the “Cancel item” button 540 until the user presses the “Back” button 520 or the “Close” button 515 (S12 “No”).

[0108] If the user presses the "Back" button 520 or the "Close" button 515 on the balance confirmation screen 50 without the "Cancel Product" button 540 (S12 "Yes"), the display control unit 101 ends the display of the balance confirmation screen 50 and returns to the product details screen 40 (S13). Then, returning to S5, the product registration processing unit 104 waits for the acceptance of an operation to register a product.

[0109] Furthermore, if the balance of the registered payment medium is less than the payment amount (S10 “Yes”), the display control unit 101 pops up a balance confirmation screen 50 including a “Cancel item” button 540 on the item details screen 40 as shown in Fig. 6 (S14). The process of S14 is an example of the second display step in this embodiment.

[0110] Then, when the user presses the “Cancel Product” button 540 on the balance confirmation screen 50 (S15 “Yes”), the display control unit 101 closes the balance confirmation screen 50 and displays the product details screen 40 in the product cancellation mode (S16).

[0111] Then, when the reception unit 103 receives an operation to cancel the product by the user (S17 "Yes"), the product registration processing unit 104 deletes the product information of the product to be settled stored in the memory unit 18 based on the operation, or changes the quantity. In this case, the display control unit 101 updates the product details screen 40 in response to the user's operation to cancel the product (S18). When updating the product details screen 40, the display control unit 101 may continue to display the product cancellation mode of the product details screen 40, or may return to the normal mode, that is, the product details screen 40 that does not have a button image for canceling the product as shown in FIG. 4.

[0112] After that, the process returns to S5, and the product registration processing unit 104 may accept an operation to register another product. For example, the user may cancel the registration of a high-priced product in accordance with the balance of the payment medium already registered in S17, and then perform an operation to additionally register a low-priced product in S5.

[0113] Also, when the user's operation to cancel the product is not accepted in the product cancellation mode (S17 "No"), the process returns to S5, and the product registration processing unit 104 may accept an operation to register another product.

[0114] Furthermore, if the user does not press the “Cancel Product” button 540 on the balance confirmation screen 50 (S15 “No”), but presses the “Cash Payment” button 543 (S19 “Yes”), the payment medium registration processing unit 102 deletes the registration of the payment medium and changes the payment method to cash payment (S20).

[0115] Furthermore, if neither the “Cancel Product” button 540 nor the “Cash Payment” button 543 on the balance confirmation screen 50 is pressed (S19 “No”), but the “Back” button 520 or the “Close” button 515 is pressed (S12 “Yes”), the process proceeds to S13 described above.

[0116] Furthermore, if the “Check payment media balance” button 420 on the product details screen 40 is not pressed (S8 “No”), but the “Change / Add / Delete payment media” button 421 is pressed (S21 “Yes”), the display control unit 101 causes the change / add / delete payment media screen 60 to pop up on the product details screen 40 (S22).

[0117] Then, when the reception unit 103 receives an operation by the user to change, add, or delete a payment medium on the change / add / delete payment medium screen 60 (S23 "Yes"), the payment medium registration processing unit 102 executes the change, addition, or deletion of the payment medium according to the received operation (S24). Then, the process proceeds to S13, and the display control unit 101 ends the display of the change / add / delete payment medium screen 60 and returns to the product details screen 40.

[0118] Furthermore, if the reception unit 103 does not receive any of the operations of changing, adding, or deleting the payment medium by the user on the change / add / delete payment medium screen 60 (S23 "No") and the user presses the "Back" button 630 or the "Close" button 640 (S12 "Yes"), the display control unit 101 ends the display of the balance confirmation screen 50 and returns to the product details screen 40 (S13). Then, returning to S5, the product registration processing unit 104 waits for reception of an operation to register a product.

[0119] Furthermore, if the "Change / Add / Delete Payment Medium" button 421 is not pressed (S21 "No") and the "Checkout" button 410 is not pressed (S25 "No"), the process returns to S5.

[0120] Furthermore, if the "Checkout" button 410 on the product details screen 40 is pressed (S25 "Yes"), the payment processing unit 106 executes the payment process (S26). Here, the process of this flowchart ends.

[0121] In this way, the POS terminal 10 of the present embodiment accepts the registration of a payment medium before registering a product to be paid for, and displays a "Check balance of payment medium" button 420 that can accept a user's operation to request the display of the balance corresponding to the registered payment medium during the registration of the product to be paid for. If the "Check balance of payment medium" button 420 is operated by a user during the registration of a product to be paid for, and if the user's balance corresponding to the payment medium is insufficient to cover the payment amount for the purchase of the product to be paid for, a "Cancel product" button 540 is displayed that allows the operation of canceling the registered product to be paid for. With this configuration, the POS terminal 10 of the present embodiment allows a customer to check the balance of the payment medium without worrying about other people's eyes during product registration, and allows the customer to cancel the registered product according to the balance.

[0122] As a comparative example, if a user cannot check the balance of the payment medium until the start of the payment process, when the user tries to make a payment, the balance of the payment medium may be insufficient and the payment may not be made. In such a case, the user must prepare another payment medium or change to cash payment after the payment has been made in error, and the customer may feel embarrassed when the balance of the payment medium is insufficient in a POS register where a store clerk is present, or may feel that the customer waiting behind them is being inconvenienced when the register is busy, even in a full-self POS register where no store clerk is present. In addition, even if the customer himself knows that the payment amount of the payment medium is insufficient, since the registration of all the products to be purchased has already been completed, it may be necessary to ask a store clerk to cancel the purchase of the products so that the total amount according to the balance of the payment medium is included. In contrast, in the POS terminal 10 of this embodiment, the user can check the balance of the payment medium at any time without worrying about the eyes of others while registering the products to be paid, and the registered products can be canceled if the balance is insufficient, thereby reducing the occurrence of a situation in which the user is concerned about causing inconvenience to store clerks and other customers.

[0123] In addition, the POS terminal 10 of this embodiment can accept at least one of addition, change, and deletion of payment media during registration of the product to be paid for. Therefore, the POS terminal 10 of this embodiment allows the user to select a payment media according to the payment amount at that time during the registration of the product to be paid for. Therefore, the POS terminal 10 of this embodiment can reduce the user's trouble of trying multiple payment media to find one with a sufficient balance at the payment stage.

[0124] Furthermore, when the registered payment method is cashless payment and the available payment amount corresponding to the registered payment method is insufficient to cover the payment amount for the purchase of the product to be paid, the POS terminal 10 of this embodiment displays a "Cash Payment" button 543 that allows the user to select whether to change the payment method to cash payment or to pay the remaining amount paid by cashless payment in cash. Therefore, according to the POS terminal 10 of this embodiment, when the user's cashless payment means has an insufficient balance, the user can select to pay part or all of the payment amount in cash before starting payment. This can reduce the occurrence of a situation in which the user finds out that the cashless payment means has an insufficient balance at the payment stage and then hurriedly checks the amount of cash on hand.

[0125] Furthermore, the POS terminal 10 of this embodiment displays a product details screen 40 including details of the registered product to be paid for, and displays a "Check balance of payment media" button 420 that can accept a user's operation on the product details screen 40. Therefore, according to the POS terminal 10 of this embodiment, the user can check the balance of the payment media by pressing the "Check balance of payment media" button 420 at any time without worrying about other people's eyes while checking the details of the product being registered.

[0126] (Modification) In the above embodiment, the balance confirmation screen 50 is described as an example when one payment medium is registered, but the POS terminal 10 may also accept the registration of multiple payment media and enable payment by combining the respective balances.

[0127] For example, the payment medium registration processing unit 102 may accept the registration of multiple payment media before registering the product to be paid for. Then, the display control unit 101 displays the multiple registered payment media and their respective balances on the balance confirmation screen 50 in association with each other.

[0128] In this case, if the balance of each of the registered payment media is insufficient to cover the payment amount, the payment processing unit 106 makes the payment using a combination of two or more of the registered payment media.

[0129] Fig. 10 is a diagram showing an example of a balance confirmation screen 50 according to this modified example. As shown in Fig. 10, the display control unit 101 includes a display field 551 for the name of a first registered payment medium, a display field 561 for the balance of the first registered payment medium, a display field 552 for the name of a second registered payment medium, a display field 562 for the balance of the second registered payment medium, a total balance display field 570, a payment amount display field 512, a difference display field 513, a "Back" button 520, and a "Close" button 515.

[0130] Payment amount display field 512, difference display field 513, "Back" button 520, and "Close" button 515 are the same as those in the embodiment described in FIG.

[0131] The first registered payment medium name display field 551 is a screen area in which the name of one of the payment media registered by the payment medium registration processing unit 102 based on a user operation is displayed.

[0132] The first registered payment medium balance display field 561 is a screen area in which the balance of the payment medium displayed in the first registered payment medium name display field 551 is displayed.

[0133] The second registered payment media name display field 552 is a screen area that displays the names of payment media registered by the payment media registration processing unit 102 based on user operation, which are different from the names displayed in the first registered payment media name display field 551.

[0134] The second registered payment medium balance display field 562 is a screen area in which the balance of the payment medium displayed in the second registered payment medium name display field 552 is displayed.

[0135] The total balance display field 570 is a screen area that displays the sum of the balance displayed in the balance display field 561 of the first registered payment medium and the balance displayed in the balance display field 562 of the second registered payment medium.

[0136] 10 shows an example in which two types of payment media are registered, but it may be possible to register three or more types of payment media. The display control unit 101 displays a display field for the registered payment media names and a display field for the registered payment media balances on the balance confirmation screen 50 for the number of registered payment media.

[0137] The display order of registered payment media may be the order in which they were registered, or may be the order of priority set by the user. When the user sets the priority of registered payment media, the settlement processing unit 106 uses the balances of registered payment media in descending order of priority for payment.

[0138] Note that Figure 10 illustrates an example of the balance confirmation screen 50 when there is no insufficient balance, but if there is an insufficient balance, a message 530 notifying that the balance of the registered payment medium is insufficient, a "Cancel item" button 540, and a "Cash payment" button 543 will be displayed on the balance confirmation screen 50, similar to the embodiment described in Figure 6.

[0139] In addition, in the above-described embodiment, the payment media registration processing unit 102 is an example of a payment method registration means, but hardware devices such as the imaging unit 16, the IC card reader / writer 20, the magnetic card reader / writer 19, and the electronic money reader / writer 21 may also be examples of a payment method registration means.

[0140] Furthermore, in the above embodiment, the display control unit 101 is an example of a display unit, but the display unit 14 may be an example of a display unit.

[0141] The POS terminal 10 does not need to support all of the payment media described in the above-described embodiments, but only needs to support at least one type of cashless payment.

[0142] In addition, the POS terminal 10 may be a terminal dedicated to cashless payment that does not support cash payment. When this configuration is adopted, the POS terminal 10 does not include the change dispenser 22. When this configuration is adopted, the POS terminal 10 does not display the "Cash Payment" button 543.

[0143] In the above embodiment, the display control unit 101 displays the "Change / Add / Delete Payment Media" button 421 on the product details screen 40, but the display location of the "Change / Add / Delete Payment Media" button 421 is not limited to this. The display control unit 101 may display the "Change / Add / Delete Payment Media" button 421 on the balance confirmation screen 50.

[0144] Although some embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be implemented in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their modifications are included in the scope and spirit of the invention, and are included in the scope of the invention and its equivalents described in the claims. [Explanation of symbols]

[0145] 10. POS terminals 14 Display section 15 Control section 16 Imaging unit 17 Communications Department 18 Memory section 19 Magnetic card reader / writer 20 IC card reader / writer 21 Electronic money reader / writer 22 Change machine 30 Payment media registration screen 40 Product details screen 50 Balance confirmation screen 60 Payment medium change / add / delete screen 100 Control section 101 Display control unit 102 Payment media registration processing unit 103 Reception 104 Product registration processing unit 105 Balance inquiry section 106 Payment processing unit 181 Programs 400 Details of the registered item to be paid for 410 "Checkout" button 420 "Check balance of payment media" button 421 "Change / Add / Delete Payment Media" button 423 Payment amount display field 431 Minus button 440 Delete button 510 Display field for registered payment medium name 511 Balance display field for registered payment medium name 512 Payment amount display field 513 Difference display field 540 "Cancel item" button 543 "Cash payment" button 551 Display field for the first registered payment medium name 552 Second registered payment medium name display field 561 Balance display field for the first registered payment medium 562 Second registered payment medium balance display field 570 Balance total display field 610 Display field for the name of the registered payment medium 611 Delete registered payment medium button 620 Display field for the name of the newly registered payment medium [Prior art documents] [Patent documents]

[0146] [Patent Document 1] Patent Publication No. 2021-51427

Claims

1. a payment method registration means for accepting registration of a payment method prior to registration of a product to be paid for; a display means for displaying a payment available amount confirmation operation section capable of receiving a user's operation for requesting display of a payment available amount corresponding to the registered payment method during registration of the product to be paid for, the display means displays a product cancellation declaration section that enables an operation to cancel the registered product to be paid for, when the user operates the available payment confirmation operation section during registration of the product to be paid for and when the available payment amount of the user corresponding to the payment method is insufficient to cover the payment amount for the purchase of the product to be paid for. Product sales data processing device.

2. the payment method registration means is capable of accepting at least one of addition, change, and deletion of the payment method during registration of the product to be paid for; The product sales data processing device according to claim 1 .

3. When the registered payment method is a cashless payment and the payable amount corresponding to the registered payment method is insufficient to cover the payment amount for the purchase of the product to be paid for, the display means displays a cash payment declaration section that allows the user to select to change the payment method to cash payment or to pay the balance remaining after making the payment using the cashless payment method in cash. The product sales data processing device according to claim 1 .

4. The payment processing means further includes a payment processing means for paying for the product to be paid for based on the registered payment method, The payment method registration means accepts registration of a plurality of payment methods before the registration of the product to be paid for; the display means displays the registered plurality of payment methods in association with the respective available payment amounts; the payment processing means, when the payable amount of each of the plurality of payment methods is insufficient to cover the payment amount, performs payment using a combination of two or more of the plurality of registered payment methods; The product sales data processing device according to claim 1 .

5. The display means displays a product details screen including details of the registered product to be settled, the available payment confirmation operation unit is a button image displayed on the product details screen and capable of accepting an operation by the user; The product sales data processing device according to any one of claims 1 to 4.

6. On the computer, a payment method registration step for accepting registration of a payment method before registration of a product to be paid for; a first display step of displaying a payment available amount confirmation operation section capable of receiving a user's operation for requesting display of a payment available amount corresponding to the registered payment method during registration of the product to be paid for; a second display step of displaying a product cancellation declaration section that enables an operation to cancel the registered product to be paid for, when the user operates the payment available amount confirmation operation section during registration of the product to be paid for and when the payment available amount of the user corresponding to the payment method is insufficient to cover the payment amount for the purchase of the product to be paid for; A program for executing the above.

Images