Sales data processor and program

Abstract

To provide a sales data processor and a program that can improve the identification of transactions in which unapproved code settlement brands are used.SOLUTION: An article registration device according to the embodiment includes: first acquisition means for acquiring data for settlement from a code symbol for code settlement; processing means for transmitting the data acquired by the first acquisition means to an external server providing a settlement proxy service for the code settlement, and receiving from the external server a settlement result including a code settlement brand used in the code settlement; and output means for outputting that the code settlement has been performed with an unapproved code settlement brand when the code settlement brand included in the settlement result does not match a pre-set approved code settlement brand.SELECTED DRAWING: Figure 11

Description

[Technical field]

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

[0002] Conventionally, in stores selling products, payment processing is performed using sales data processing devices such as POS terminals. In recent years, code payment, which is an electronic payment method using code symbols such as two-dimensional codes, has become widespread, and sales data processing devices compatible with code payment also exist. For example, a sales data processing device has been proposed that transmits data read from a code symbol for code payment displayed on a customer's smartphone together with the payment amount to an external server that provides a payment agency service, thereby requesting the external server to perform code payment of the payment amount.

[0003] There are many code payment brands (hereinafter simply referred to as brands) that provide code payment services, but some stores only approve the use of some brands. Customers who use such stores are required to present the code symbol of an approved brand when making a payment, but they may present the code symbol of an unapproved brand due to operational errors or other reasons. In this case, if data read from the code symbol of the unapproved brand is sent to an external server and the external server supports code payments for unapproved brands, code payment may be made even though the store is not approved of the brand.

[0004] In such cases, from the perspective of customer convenience, stores may complete the transaction as normal without canceling the transaction even if the brand is not approved, if the payment result on the external server indicates that the payment has been completed (successful). However, the store will need to perform additional post-processing, such as paying fees, for unapproved brands for which code payments have been made.

[0005] However, as mentioned above, in the case of operation that allows code payments of unapproved brands, the sales data processing device treats the code payment results of unapproved brands in the same way as the code payment results of approved brands, making it difficult for store clerks to recognize which transactions used unapproved brands. Therefore, when performing post-processing on the store side, it is not easy to extract transactions in which unapproved brands were used, and further improvements are desired from the viewpoint of processing efficiency. Summary of the Invention [Problem to be solved by the invention]

[0006] The problem to be solved by the present invention is to provide a sales data processing device and program capable of improving the identifiability of transactions in which an unauthorized code payment brand is used. [Means for solving the problem]

[0007] The sales data processing device of the embodiment comprises a first acquisition means for acquiring payment data from a code symbol related to code payment, a processing means for transmitting the data acquired by the first acquisition means to an external server providing a payment agency service for the code payment and receiving a payment result including the code payment brand used in the code payment from the external server, and an output means for outputting that the code payment was made with an unapproved code payment brand if the code payment brand included in the payment result does not match a previously set approved code payment brand. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram illustrating an example of a sales data processing system according to an embodiment. [Diagram 2] FIG. 2 is a diagram illustrating an example of a hardware configuration of the POS terminal according to the embodiment. [Diagram 3] FIG. 3 is a diagram illustrating an example of a data configuration of approved brand information according to the embodiment. [Figure 4]FIG. 4 is a diagram illustrating an example of a hardware configuration of a store server according to the embodiment. [Diagram 5] FIG. 5 is a diagram illustrating an example of a hardware configuration of a customer terminal according to the embodiment. [Figure 6] FIG. 6 is a diagram illustrating an example of a functional configuration of the POS terminal, the store server, and the customer terminal according to the embodiment. [Figure 7] FIG. 7 is a diagram showing an example of a screen displayed on the display unit of the POS terminal according to the embodiment. [Figure 8] FIG. 8 is a diagram illustrating an example of a store copy receipt according to the embodiment. [Figure 9] FIG. 9 is a diagram illustrating an example of a store copy receipt according to the embodiment. [Figure 10] FIG. 10 is a sequence diagram illustrating an example of a flow of processes executed in the sales data processing system according to the embodiment. [Figure 11] FIG. 11 is a flowchart illustrating an example of sales data processing performed by the POS terminal of the embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. In the embodiment described below, a POS terminal used in a store that sells products will be described as an example. Note that the present invention is not limited to the embodiment described below. For example, the object of sale is not limited to tangible products, but may be intangible services, etc.

[0010] 1 is a diagram illustrating an example of a sales data processing system according to an embodiment. The sales data processing system 1 includes a POS (Point of Sales) terminal 10, a store server 20, a customer terminal 30, and a code payment server 40.

[0011] The POS terminal 10 and the store server 20 are communicatively connected via a network Na such as a local area network (LAN) provided in the store. The POS terminal 10 and the code payment server 40 are communicatively connected via a network Nb such as the Internet or a dedicated line.

[0012] The POS terminal 10 is an example of a sales data processing device. One or more POS terminals 10 are installed, for example, in the checkout area of ​​a store. The POS terminal 10 reads a code symbol, such as a barcode or a two-dimensional code, attached to a product and obtains a product code that can identify the product. The product code is an example of product identification information, such as a JAN code.

[0013] The POS terminal 10 executes a registration process for a product purchased by a customer based on the product code of the product. The registration process refers to a process of reading the product name, price, etc. of the product corresponding to the product code based on the product code from the product master 142 described later and storing them in the RAM 13, etc.

[0014] In addition, the POS terminal 10 starts the payment process for the products registered in the registration process in response to a closing operation such as an operation to instruct the end of the registration process or an operation to instruct the start of payment. The payment process is a process in which the total amount of the products to be purchased by the customer is calculated based on the product information registered in the registration process, and this total amount is settled with the amount to be paid by the customer. Here, the payment method of the amount to be paid is not limited to cash, and may be other payment methods such as a credit card. In addition, the POS terminal 10 of this embodiment is capable of making payments by code payment by linking with the code payment server 40.

[0015] In addition, the POS terminal 10 issues a receipt for the customer on which product information of the processed products and payment information (total amount, payment amount, change amount, etc.) are printed, as well as a receipt for the store to keep, from the printer 18 described below.

[0016] The POS terminal 10 also transmits product information and transaction information (collectively referred to as transaction data) for the products for which payment has been processed to the store server 20. The timing of transmitting the transaction data from the POS terminal 10 to the store server 20 is not particularly important; for example, the data may be transmitted when the payment process is completed, or the data for one day may be transmitted collectively when the store is closed.

[0017] The store server 20 is installed, for example, in the back yard of a store. The store server 20 stores a product master in which the product name, price, product image, etc. of each product sold in the store are associated with the product code of the product. The store server 20 also provides the product master to each of the POS terminals 10. For example, the store server 20 transmits the product master to each of the POS terminals 10, causing the POS terminals 10 to store the product master locally. For example, the store server 20 also stores the product master in a state that can be referenced by each of the POS terminals 10.

[0018] The store server 20 also collects transaction data received from the POS terminal 10. The store server 20 also manages the sales of products at the store based on the collected transaction data, and extracts transaction data for each code payment brand (hereinafter, simply referred to as brand) of the code payment.

[0019] The customer terminal 30 is a terminal device used by a customer who visits a store. In this embodiment, the customer terminal 30 is a mobile terminal such as a smartphone owned by the customer. In addition, it is assumed that an application for using a code payment service (hereinafter also referred to as a code payment app) is pre-installed in the customer terminal 30. When making a code payment, the customer operating the customer terminal 30 starts up the code payment app, displays a code symbol for code payment (hereinafter also referred to as a payment code symbol), and then has the POS terminal 10 read the payment code symbol. Note that the brand of the code payment app installed in the customer terminal 30 is not limited to one, and may be multiple brands.

[0020] The code payment server 40 is a server device that provides payment agency services for multiple brands. The code payment server 40 cooperates with the POS terminal 10 to realize payment processing using code payment.

[0021] As described above, in the sales data processing system 1 of this embodiment, by having the POS terminal 10 read the payment code symbol presented on the customer terminal 30, it is possible to pay for the product by code payment.

[0022] Next, configurations of the POS terminal 10, the store server 20, and the customer terminal 30 among the devices included in the above-mentioned sales data processing system 1 will be described.

[0023] Fig. 2 is a diagram showing an example of a hardware configuration of the POS terminal 10. As shown in Fig. 2, the POS terminal 10 includes a CPU (Central Processing Unit) 11, a ROM (Read Only Memory) 12, a RAM (Random Access Memory) 13, a memory unit 14, etc.

[0024] The CPU 11 is an example of a processor, and controls the overall operation of the POS terminal 10. The ROM 12 stores various programs that the CPU 11 can execute. The RAM 13 is a work area for temporarily storing programs and various data. For example, the RAM 13 stores product codes and product information of registered products.

[0025] The memory unit 14 is composed of a non-volatile memory such as a hard disk drive (HDD) or a flash memory that retains stored information even when the power is turned off. The memory unit 14 stores various programs that the CPU 11 can execute, setting information, and the like. For example, the memory unit 14 stores a control program 141 that the CPU 11 can execute, a product master 142, and the like. The product master 142 stores product information of a product corresponding to a product code in association with the product code of each product sold in the store. The product information includes, for example, the product name, the price (unit price), and the like.

[0026] The memory unit 14 also stores approved brand information 143 that indicates the code payment brands that are approved for use in the store. In other words, brands other than the brands stored in the approved brand information 143 are brands that the store has not approved. Note that approved brands can also be said to be brands of the code payment service company that has entered into a service contract with the store.

[0027] Fig. 3 is a diagram showing an example of the data configuration of the approved brand information 143. As shown in Fig. 3, the approved brand information 143 registers information capable of identifying each approved brand, such as the name of the brand (brand name) and the ID of the brand (brand ID) (hereinafter also referred to as brand information). Fig. 3 shows an example in which brands with the brand names "Brand A" and "Brand B" are registered. Note that the number of brands registered in the approved brand information 143 is not particularly limited.

[0028] 2, the CPU 11, ROM 12, RAM 13, and memory unit 14 are connected to one another via a bus or the like. Here, the CPU 11, ROM 12, and RAM 13 constitute a control unit 100 of the POS terminal 10. The control unit 100 realizes the functions of the POS terminal 10 by the CPU 11 operating in accordance with a control program 141 stored in the ROM 12 and memory unit 14 and loaded in the RAM 13.

[0029] The control unit 100 is also connected to an operation unit 15, a display unit 16, a code reader 17, a printer 18, and the like via a bus or the like.

[0030] The operation unit 15 has various operation keys that allow the operator to perform operation input. The operation unit 15 has a closing key as an example of an operation key. The closing key is an operation key that is operated when completing the product registration process and proceeding to the payment process. The display unit 16 is a display device such as a liquid crystal display. Under the control of the control unit 100, the display unit 16 displays, for example, product information (product name, price, etc.) of the product that has been registered and accounting information related to the payment process. The operation unit 15 may be a touch panel provided on the display unit 16.

[0031] The code reader 17 is a reading device capable of reading a code symbol. For example, the code reader 17 captures an image of the code symbol and reads it. The code reader 17 may also read a symbol using red light (for example, infrared light). The code reader 17 also reads a code symbol attached to a product or a payment code symbol displayed on the customer terminal 30. The printer 18 is a printing device such as a thermal printer. Under the control of the control unit 100, the printer 18 issues a receipt on which product information, payment information, etc. relating to the product for which payment has been processed are printed.

[0032] The control unit 100 is also connected to a communication unit 19 via a bus or the like. The communication unit 19 is a variety of communication interfaces for connecting to external devices. The communication unit 19 is communicatively connected to the store server 20 via a network Na. The communication unit 19 is also communicatively connected to the code payment server 40 and the like via a network Nb.

[0033] Next, a description will be given of the hardware configuration of the store server 20. Fig. 4 is a diagram showing an example of the hardware configuration of the store server 20. As shown in Fig. 4, the store server 20 includes a CPU 21, a ROM 22, a RAM 23, a memory unit 24, and the like.

[0034] The CPU 21 is an example of a processor, and controls the overall operation of the store server 20. The ROM 22 stores various programs that can be executed by the CPU 21. The RAM 23 is a work area for temporarily storing programs and various data.

[0035] The memory unit 24 is composed of a non-volatile memory such as a HDD or a flash memory that retains stored information even when the power is turned off. The memory unit 24 stores various programs and setting information that the CPU 21 can execute. For example, the memory unit 24 stores a control program 241 that the CPU 21 can execute. The memory unit 24 also stores a product master 242, a transaction history DB (database) 243 for storing and managing transaction data, and the like. The data structure of the product master 242 is the same as that of the product master 142. For example, the product master 242 is provided to each of the POS terminals 10, and the product master 242 is used as the product master 142 in each of the POS terminals 10.

[0036] The CPU 21, ROM 22, RAM 23, and memory unit 24 are connected to one another via a bus or the like. Here, the CPU 21, ROM 22, and RAM 23 constitute a control unit 200 of the store server 20. The control unit 200 realizes the functions of the store server 20 by the CPU 21 operating in accordance with a control program 241 stored in the ROM 22 and memory unit 24 and loaded into the RAM 23.

[0037] The control unit 200 is connected to a communication unit 25 via a bus or the like. The communication unit 25 is a variety of communication interfaces for connecting to external devices. The communication unit 25 is connected to the POS terminal 10 or the like via a network Na so as to be able to communicate with the POS terminal 10 or the like.

[0038] Next, a description will be given of the hardware configuration of the customer terminal 30. Fig. 5 is a diagram showing an example of the hardware configuration of the customer terminal 30. As shown in Fig. 5, the customer terminal 30 includes a CPU 31, a ROM 32, a RAM 33, a memory unit 34, and the like.

[0039] The CPU 31 is an example of a processor, and controls the overall operation of the customer terminal 30. The ROM 32 stores various programs that can be executed by the CPU 31. The RAM 33 is a work area for temporarily storing programs and various data.

[0040] The memory unit 34 is composed of a non-volatile memory such as a HDD or flash memory that retains stored information even when the power is turned off. The memory unit 34 stores various programs that the CPU 31 can execute, setting information, and the like. For example, the memory unit 34 stores a control program 341 that the CPU 31 can execute. The memory unit 34 also stores a payment application 342 for performing code payment, and the like. Note that the memory unit 34 stores (installs) a payment application 342 for each brand of code payment used by the operator individually.

[0041] The CPU 31, ROM 32, RAM 33, and memory unit 34 are connected to each other via a bus or the like. Here, the CPU 31, ROM 32, and RAM 33 constitute a control unit 300 of the customer terminal 30. The control unit 300 realizes the functions of the customer terminal 30 by the CPU 31 operating in accordance with a control program 341 stored in the ROM 32 and memory unit 34 and expanded in the RAM 33. The control unit 300 also realizes functions related to code payment, such as displaying a payment code symbol, by operating in accordance with a started payment application 342.

[0042] The control unit 300 is also connected to an operation unit 35, a display unit 36, and the like via a bus or the like. The operation unit 35 has various operation keys that allow an operator to perform operation input. The display unit 36 ​​is a display device such as a liquid crystal display. The display unit 36 ​​displays a payment code symbol and the like under the control of the control unit 100. The operation unit 35 may be a touch panel provided on the display unit 36.

[0043] The control unit 300 is also connected to a communication unit 37 via a bus or the like. The communication unit 37 is a variety of communication interfaces for connecting to external devices. The communication unit 37 is connected to be able to communicate with a server device of a service company that provides a code payment service, for example, via a network such as a public line (not shown).

[0044] Next, a description will be given of the functional configurations of the POS terminal 10, the store server 20, and the customer terminal 30. FIG.

[0045] First, a description will be given of the functional configuration of the customer terminal 30. As shown in FIG.

[0046] The functional configuration of the customer terminal 30 is a software configuration realized by the processor of the customer terminal 30 operating in accordance with the control program 341 (and the payment application 342) stored in the ROM 32 or the memory unit 34, but is not limited to this. For example, some or all of the functional configuration of the customer terminal 30 may be realized by hardware such as a dedicated circuit.

[0047] The code payment function unit 301 is a functional configuration realized by cooperation between the control program 341 and the payment application 342. The code payment function unit 301 executes various processes related to code payment. For example, the code payment function unit 301 displays a payment code symbol for code payment on the display unit 36 ​​in response to an operation by an operator. The payment code symbol holds payment data for making code payment. The payment data includes, for example, information capable of identifying an ID that the operator has contracted with a service provider of the brand of the payment application 342.

[0048] The code payment function unit 301 is realized for each brand of the activated payment application 342, and displays a payment code symbol that holds the payment data corresponding to that brand. For example, the code payment function unit 301 realized by the payment application 342 with the brand name "Company A" displays a payment code symbol that holds the payment data for Company A. Also, for example, the code payment function unit 301 realized by the payment application 342 with the brand name "Company B" displays a payment code symbol that holds the payment data for Company B.

[0049] Next, a description will be given of the functional configuration of the POS terminal 10. The POS terminal 10 includes a read result acquisition unit 101, a registration processing unit 102, and a payment processing unit 103, as shown in FIG.

[0050] The functional configuration of the POS terminal 10 is a software configuration realized by the processor of the POS terminal 10 operating in accordance with the control program 141 stored in the ROM 12 or the memory unit 14, but is not limited to this. For example, a part or all of the functional configuration of the POS terminal 10 may be realized by hardware such as a dedicated circuit.

[0051] The reading result acquisition unit 101 is an example of a first acquisition means and a second acquisition means. The reading result acquisition unit 101 acquires the reading result read from the code symbol by the code reader 17. For example, the reading result acquisition unit 101 acquires the reading result of the code symbol attached to the product, that is, the product code. Also, for example, the reading result acquisition unit 101 acquires the reading result of the payment code symbol displayed on the customer terminal 30, that is, the payment data.

[0052] The registration processing unit 102 is an example of a registration means. The registration processing unit 102 executes a registration process of the product purchased by the customer based on the product code acquired by the read result acquisition unit 101. Specifically, the registration processing unit 102 reads out product information of the product corresponding to the product code acquired by the read result acquisition unit 101 from the product master 142. Then, the registration processing unit 102 stores (registers) the read product information in the RAM 13 or the like in association with the product code and the number of points of the product. In addition, the registration processing unit 102 causes the display unit 16 to display the product name, price, number of points, etc. of each product registered in the registration process in the order of registration.

[0053] The payment processing unit 103 is an example of a processing means and an output means. The payment processing unit 103 executes a payment process for the products registered in the registration process in response to a closing operation by an operator.

[0054] For example, when the payment processing unit 103 receives a closing operation via the operation unit 15, it causes the display unit 16 to display a screen on which a payment method, such as cash payment or code payment, can be selected. When cash payment is selected, the payment processing unit 103 executes a payment process in which the total amount of the products registered in the registration process is settled with the payment amount deposited via a deposit device (not shown). The payment processing unit 103 then issues a receipt for the customer and a copy for the store.

[0055] Here, a customer receipt is a receipt given to a customer who purchases a product, and is printed with, for example, the store name, the date and time of the transaction, the item (product name) of the purchased product, the unit price, the amount paid, etc. A store copy receipt is a document for keeping a record of the transaction, and is also called a journal. The contents of a store copy receipt may be the same as a customer copy receipt, or it may be a copy of the customer copy with some information extracted from the contents of the customer copy receipt. For example, a store copy receipt may have the date and time of the transaction and the total price of the products (amount paid) printed on it. Hereinafter, when there is no distinction between customer and store copy receipts, they will simply be referred to as receipts.

[0056] Furthermore, when code payment is selected, the payment processing unit 103 waits until payment data is acquired in cooperation with the reading result acquisition unit 101. When the reading result acquisition unit 101 acquires the payment data, the payment processing unit 103 transmits the payment data together with the total amount of the products, which is the payment amount, to the code payment server 40, thereby requesting the code payment server 40 to make code payment for the payment amount based on the payment data.

[0057] Then, when the payment processing unit 103 receives a notice of completion of payment (hereinafter also referred to as a payment completion notice) from the code payment server 40, it determines that the code payment for the total amount has been completed, and issues a receipt for the customer and a copy for the store. The payment completion notice includes, for example, the payment amount paid by code payment (i.e. the total amount of the goods), as well as brand information indicating the brand of code payment used. If the code payment server 40 notifies the payment processing unit 103 that the code payment has failed, the payment processing unit 103 displays a message or the like notifying the failure of the code payment on the display unit 16. If the code payment server 40 notifies the payment processing unit 103 that the code payment has failed, the payment processing unit 103 may also prompt the customer to select another payment method by displaying the payment method selection screen again.

[0058] When the payment processing is completed, the payment processing unit 103 generates transaction data indicating the details of the transaction and stores (records) it in the memory unit 14. The transaction data stored in the memory unit 14 is transmitted to the store server 20 at a predetermined timing under the control of the payment processing unit 103 or the control unit 100.

[0059] Generally, the brands of code payments that can be used at the store are displayed in the checkout area where the POS terminal 10 is installed. In this case, a customer who wishes to make a code payment checks the displayed brand and launches the corresponding payment application installed in his / her customer terminal 30 to make the code payment.

[0060] However, when multiple brands of payment applications are installed in the customer terminal 30, a payment application of a brand not approved by the store may be launched due to an operational error or other reasons, resulting in the presentation of a payment code symbol. In this case, if a store clerk inadvertently reads payment data from the presented payment code symbol at the POS terminal 10, the payment data will be transmitted to the code payment server 40. Furthermore, if the code payment server 40 supports code payment for the brand of the payment data transmitted from the POS terminal 10, code payment will be performed even if the brand is not approved by the store.

[0061] In such cases, from the perspective of customer convenience, if the payment result of the code payment server 40 indicates that the payment has been completed, the payment is handled in the same way as normal payment processing, even if the brand is unapproved. However, since the store will need to perform additional post-processing, such as paying a fee, for the unapproved brand for which the code payment was made later, it is desirable to be able to identify which transactions used unapproved brands.

[0062] Therefore, in this embodiment, when the payment processing unit 103 receives a payment completion notification from the code payment server 40, it compares the brand information contained in the payment completion notification with the brand information registered in the approved brand information 143 to determine whether the brand used for the code payment corresponds to one of the approved brands.

[0063] If the brand information included in the payment completion notice matches any of the brand information registered in approved brand information 143, approved brand information 143 determines that an approved brand was used for the code payment. In this case, payment processing unit 103 executes the specified payment process to issue various receipts and record transaction data.

[0064] On the other hand, if the brand information included in the payment completion notice does not match any of the brand information registered in the approved brand information 143, the approved brand information 143 determines that an unapproved brand was used for the code payment.

[0065] In this case, the payment processing unit 103 notifies the operator of the POS terminal 10 by displaying a notification screen on the display unit 16 to notify that an unapproved brand has been used for the code payment. The payment processing unit 103 also issues a receipt for the store copy with information that identifies that an unapproved brand has been used for the code payment added to it. Furthermore, the payment processing unit 103 records the transaction data it generates with information that identifies that an unapproved brand has been used for the code payment added to it.

[0066] Here, a notification screen displayed when an unapproved brand is used for code payment will be described with reference to Fig. 7. Fig. 7 is a diagram showing an example of a screen displayed on the display unit 16 of the POS terminal 10.

[0067] When the payment processing unit 103 determines that an unauthorized brand has been used for code payment, it causes the display unit 16 to display, for example, a notification screen G shown in Fig. 7. Specifically, the payment processing unit 103 causes the notification screen G to display a message Ga notifying the user that an unauthorized brand has been used and urging the user to contact the service company. The payment processing unit 103 also causes the notification screen G to display the payment amount (total amount of merchandise) Gb that has been paid by code payment.

[0068] This allows the operator of the POS terminal 10 to easily know that an unauthorized brand was used for code payment and the amount paid for this code payment by looking at the notification screen G. Therefore, the POS terminal 10 can improve the identifiability of transactions in which payments are made using unauthorized brands.

[0069] Next, an example of a store receipt issued when code payment is made will be described with reference to FIG. 8 and FIG.

[0070] Fig. 8 is a diagram showing an example of a store copy receipt, which is a diagram showing an example of a store copy receipt issued when code payment is made with an approved brand. Also, Fig. 9 is a diagram showing an example of a store copy receipt, which is a diagram showing an example of a store copy receipt issued when code payment is made with an unapproved brand.

[0071] As shown in Figures 8 and 9, the store receipt R has a first area Ra in which store information, a logo mark, etc. are printed, and a second area Rb in which the date and time of the transaction and a transaction number that identifies the transaction are printed.

[0072] The store copy receipt R also has a third area Rc where the transaction details are printed. The third area Rc includes a title area Pa where the receipt title is printed, a receipt type area Pb where information indicating that it is a store copy receipt is printed, a payment date and time area Pc where the date and time the transaction was performed is printed, and a transaction amount area Pd where the payment amount (transaction amount) paid in the transaction is printed.

[0073] Here, the title area Pa is printed with the payment method used in the transaction and information indicating that it is a sales slip related to the sale of a product. For example, if code payment is made with the approved brand "Brand A", the title area Pa is printed with information "Brand A" indicating the brand name of the code payment used as the payment method (see FIG. 8). Such a brand name can be read out from the brand information identified by, for example, matching the payment completion notice with the approved brand information 143.

[0074] On the other hand, when code payment is made with an unapproved brand, the brand name of the code payment used as the payment method is printed in the form of "XXXXXXXXXXXX" or the like in the title area Pa, as shown in Fig. 9. In this way, when an unapproved brand is used, the payment processing unit 103 replaces the brand name with a predetermined character string (hereinafter also referred to as a flag character string) and prints it. This allows a staff member or other person performing post-processing to easily determine whether or not the code payment for the transaction was made with an approved brand by checking the brand name displayed in the title area Pa.

[0075] The output format of the store copy receipt R is not limited to the above example. For example, when a code payment is made with an unapproved brand, the payment processing unit 103 may print some or all of the brand information (brand name, brand ID) included in the payment completion notice in the title area Pa. However, even in this case, it is preferable for the payment processing unit 103 to add a flag character string such as "X" to the beginning of the brand information so that it can be easily identified as an approved brand.

[0076] In the above example, the title area Pa is used to output information that can identify whether the code payment brand is approved or not, but the output destination is not limited to this. For example, the brand name of the code payment used in the transaction or information indicating an unapproved brand may be printed at the beginning of the receipt type area Pb. Also, the brand name of the code payment used in the transaction or information indicating an unapproved brand may be printed in a location other than the third area Rc.

[0077] The information included in the store copy receipt R is not limited to the above example. For example, the store copy receipt R may include information such as a terminal ID that can identify the POS terminal 10 where the payment process was performed, or a store clerk ID that can identify the store clerk who operated the POS terminal 10.

[0078] The payment processing unit 103 may also use a method similar to that of the store receipt R described above when adding information to the transaction data that identifies that an unapproved brand has been used for code payment. Specifically, when an unapproved brand has been used for code payment, the payment processing unit 103 inputs a predetermined flag string into the input field for the brand name included in the transaction data, making it identifiable as an approved brand. For example, when an unapproved brand has been used for code payment, the payment processing unit 103 inputs part or all of the brand information included in the payment completion notice together with the flag string into the input field for the brand name included in the transaction data, making it identifiable as an approved brand.

[0079] The customer receipt also includes an area displaying information similar to the first area Ra, second area Rb, and third area Rc described above, but information that identifies that an unauthorized brand was used for code payment may or may not be printed. In the former case, for example, the brand name of each brand registered in the approved brand information 143 may be added as a usable code payment brand in addition to (or instead of) printing the information that identifies the unauthorized brand. This allows the payment processing unit 103 to make the customer aware of the brands that can be used at its store, thereby alerting the customer to the possibility of using an unauthorized brand in subsequent transactions.

[0080] Next, a description will be given of the functional configuration of the store server 20. The store server 20 includes a transaction data collection unit 201 and a transaction data analysis unit 202, as shown in FIG.

[0081] The functional configuration of the store server 20 is a software configuration realized by the processor of the store server 20 operating in accordance with the control program 241 stored in the ROM 22 or the memory unit 24, but is not limited to this. For example, some or all of the functional configuration of the store server 20 may be realized by hardware such as a dedicated circuit.

[0082] The transaction data collection unit 201 acquires (collects) transaction data from each POS terminal 10 and stores it in the transaction history DB 243. For example, the transaction data collection unit 201 acquires transaction data transmitted from each POS terminal 10 and stores it in the transaction history DB 243. Also, for example, the transaction data collection unit 201 acquires the transaction data transmitted from the POS terminal 10 by requesting the transaction data from each POS terminal 10, and stores it in the transaction history DB 243.

[0083] The transaction data analysis unit 202 analyzes the transaction data stored in the transaction history DB 243 and outputs the analysis results to a file or the like. For example, the transaction data analysis unit 202 calculates the total sales amount for one day by adding up the payment amounts (transaction amounts) included in the transaction data for one day (e.g., the previous day) registered in the transaction history DB 243. Also, for example, the transaction data analysis unit 202 calculates the total sales amount for each settlement method by adding up the payment amounts (transaction amounts) included in the transaction data for one day (e.g., the previous day) registered in the transaction history DB 243 for each settlement method.

[0084] Also, for example, the transaction data analysis unit 202 extracts transaction data of transactions in which an unauthorized brand was used based on the code payment information included in the transaction data. For example, the transaction data analysis unit 202 extracts transaction data in which a predetermined flag string indicating an unauthorized brand has been entered in the brand name input field from the transaction history DB 243. Also, for example, the transaction data analysis unit 202 extracts transaction data in which a flag string has been entered in the brand name input field, and then classifies and extracts the transaction data for each unauthorized brand based on the brand information entered in the input field.

[0085] In this way, the transaction data generated by the POS terminal 10 includes information that can identify unauthorized brands, making it easy to extract transaction data in which code payments were made using unauthorized brands. Therefore, the sales data processing system 1 can efficiently perform post-processing such as payment of fees for unauthorized brands used in code payments.

[0086] Next, a description will be given of the flow of processing executed by the sales data processing system 1. Fig. 10 is a sequence diagram showing an example of the flow of processing executed by the sales data processing system 1. Note that this processing shows an example of processing when code payment is performed.

[0087] First, in the POS terminal 10, when the code reader 17 reads a product code from a code symbol attached to a product purchased by a customer, the read result acquisition unit 101 acquires the read product code (step S11). Next, the registration processing unit 102 executes a registration process based on the product code acquired in step S11 (step S12).

[0088] In addition, the POS terminal 10 executes the above-mentioned steps S11 and S12 every time a product code is read. In addition, when the POS terminal 10 accepts a closing operation via the operation unit 15 (step S13), the payment processing unit 103 causes the display unit 16 to display a screen on which a payment method can be selected (hereinafter, a payment method selection screen) (step S14).

[0089] Here, when code payment is selected from the payment method selection screen (step S15), the payment processing unit 103 cooperates with the reading result acquisition unit 101 and waits until payment data is input.

[0090] On the other hand, when the control unit 300 of the customer terminal 30 is instructed by the customer to start the payment application 342, the control unit 300 starts the instructed payment application 342, thereby realizing the code payment function unit 301 (step S16). Next, the code payment function unit 301 displays the payment code symbol on the display unit 36 ​​in response to the customer's operation (step S17).

[0091] When the payment code symbol displayed on the customer terminal 30 is held over the code reader 17 of the POS terminal 10, the code reader 17 reads the payment data from the payment code symbol. Next, the read result acquisition unit 101 acquires the payment data read by the code reader 17 (step S18).

[0092] The payment processing unit 103 transmits the payment data acquired in step S18 together with the total price of the products (payment amount) to the code payment server 40, thereby requesting code payment from the code payment server 40 (step S19).

[0093] When the code payment server 40 receives the payment data and the payment amount from the POS terminal 10, it executes the code payment for the payment amount based on the payment data (step S20). Then, the code payment server 40 transmits a payment completion notice including the brand information of the brand used for the code payment to the requesting POS terminal 10 (step S21).

[0094] When the payment processing unit 103 of the POS terminal 10 receives a payment completion notification from the code payment server 40, it compares the blend information included in the payment completion notification with the brand information registered in the approved brand information 143 to determine whether the code payment has been made with an approved brand.

[0095] If it is determined that code payment was made with an approved brand, the payment processing unit 103 issues a receipt including the blend name, etc. used in the code payment (step S31).Then, the payment processing unit 103 generates transaction data including the blend name, etc. used in the code payment, and records it in the memory unit 14, the store server 20, etc. (step S32).

[0096] On the other hand, if it is determined that the code payment was made with an unauthorized brand, the payment processing unit 103 causes the display unit 16 to display information informing the user that the code payment was made with an unauthorized brand (step S41). Next, the payment processing unit 103 issues a receipt including a flag string or the like indicating that the code payment was made with an unauthorized blend (step S42). The payment processing unit 103 then generates transaction data including the flag string or the like and records it in the memory unit 14, the store server 20, or the like (step S43).

[0097] Next, the sales data processing performed by the POS terminal 10 will be described with reference to Fig. 11. Here, Fig. 11 is a flow chart showing an example of the sales data processing performed by the POS terminal 10. Note that this processing corresponds to the processing from step S13 onwards among the processing performed by the POS terminal 10 in Fig. 10.

[0098] When the payment processing unit 103 determines that the closing operation has been received via the operation unit 15 (step S51), it displays a payment method selection screen on the display unit 16 (step S52) and waits until a payment method is selected.

[0099] Here, if a payment method other than code payment, such as cash payment, is selected (step S53; No), the payment processing unit 103 executes the payment process using the selected payment method (step S54) and proceeds to step S60.

[0100] Also, if code payment is selected (step S53; Yes), the payment processing unit 103 waits until the payment data is read (step S55; No). When the payment data is read by the code reader 17 (step S55; Yes), the read result acquisition unit 101 acquires the payment data (step S56).

[0101] Next, the payment processing unit 103 requests the code payment server 40 to perform code payment by transmitting the payment data acquired in step S49 together with the payment amount to the code payment server 40 (step S57). Next, the payment processing unit 103 waits until it receives a payment completion notification from the code payment server 40 (step S58; No).

[0102] When the payment processing unit 103 receives a payment completion notification (step S58; Yes), it compares the brand information included in the payment completion notification with the brand information registered in the approved brand information 143 to determine whether the code payment was made with an approved brand (step S59).

[0103] Here, if it is determined that code payment has been made with an approved brand (step S59; Yes), the payment processing unit 103 proceeds to step S60. In step S60, the payment processing unit 103 issues a receipt including the payment method used, etc. (step S60). For example, if the payment method used is cash payment, the payment processing unit 103 issues a receipt indicating that the payment was made in cash, the amount deposited, the amount of change, etc. If the payment method used is code payment, the payment processing unit 103 issues a receipt indicating the brand name, etc. identified by the comparison in step S59.

[0104] Furthermore, when the payment processing unit 103 generates transaction data including the used payment method and the like, it records the transaction data in the memory unit 14, the store server 20, etc. (step S61), and ends this process.

[0105] On the other hand, if it is determined that the code payment was made with an unapproved brand (step S59; No), the payment processing unit 103 causes the display unit 16 to display a notification screen informing the user that the code payment was made with an unapproved brand (step S62). Next, the payment processing unit 103 issues a receipt including a predetermined flag character string or the like indicating that the code payment was made with an unapproved blend (step S63). Then, when the payment processing unit 103 generates transaction data including the predetermined flag information or the like, it records the transaction data in the memory unit 14, the store server 20, or the like (step S64), and ends this process.

[0106] As described above, the POS terminal 10 acquires payment data from the payment code symbol, transmits the acquired payment data to the code payment server 40, and requests the code payment server 40 to execute the code payment, and receives a payment result notice including the brand used in the code payment from the code payment server 40. If the brand of the code payment included in the payment result notice does not match the brand registered in the approved brand information 143, the POS terminal 10 outputs that the code payment was made with an unapproved brand.

[0107] As a result, when an unauthorized brand is used in code payment, the POS terminal 10 can notify or record the fact that code payment was made with an unauthorized brand by display output, print output, or data output. Therefore, the POS terminal 10 can improve the identifiability of transactions in which unauthorized brands are used.

[0108] The above-described embodiment can be modified as appropriate by changing a part of the configuration or function of each of the above-described devices. Therefore, some modified examples of the above-described embodiment will be described below as other embodiments. Note that the following mainly describes the differences from the above-described embodiment, and a detailed description of the common points with the contents already described will be omitted. The modified examples described below may be implemented individually or in appropriate combination.

[0109] (Variation 1) In the above embodiment, the POS terminal 10 has been described as a device operated by a store employee such as a sales clerk, but the present invention is not limited to this, and the POS terminal 10 may be a self-service type that is operated by a customer himself / herself.

[0110] In addition, in the case of a self-service POS terminal 10, the payment processing unit 103 may perform control so as not to display the notification message that is displayed on the display unit 16 when an unapproved brand is used for code payment.

[0111] In the above embodiment, the registration process and the payment process are performed by the POS terminal 10, but the present invention is not limited to this, and the registration process and the payment process may be performed by different devices. In this case, the POS terminal 10 that performs the payment process (also called the registration device) can notify the operator and record the receipt and transaction data when a code payment is made with an unapproved brand by performing the same process as in the above embodiment, specifically, the process after the closing operation.

[0112] The programs executed by each device in the above-described embodiments (and modified examples) are provided in a state where they are pre-installed in a ROM, a storage unit, etc. The programs executed by each device in the above-described embodiments may be provided by being recorded in a computer-readable recording medium such as a CD-ROM, a flexible disk (FD), a CD-R, or a digital versatile disk (DVD) in the form of an installable or executable file.

[0113] Furthermore, the programs executed by each device of the above-described embodiments may be stored on a computer connected to a network such as the Internet and provided by being downloaded via the network. Also, the programs executed by each device of the above-described embodiments may be provided or distributed via a network such as the Internet.

[0114] Although the embodiment of the present invention has been described above, this embodiment is presented as an example and is not intended to limit the scope of the invention. These new embodiments and their modifications can be implemented in various other forms, and various omissions, substitutions, changes, and combinations can be made without departing from the gist of the invention. These embodiments and their modifications are included in the scope and gist of the invention, and are included in the scope of the invention and its equivalents described in the claims. [Explanation of symbols]

[0115] 1. Sales data processing system 10. POS terminals 20 Store Server 30 Customer terminal 40 Code payment server 101 Reading result acquisition unit 102 Registration processing unit 103 Payment processing unit 201 Transaction Data Collection Department 202 Transaction Data Analysis Department 301 Code payment function department [Prior art documents] [Patent documents]

[0116] [Patent Document 1] JP 2021-174103 A

Claims

1. A first acquisition means for acquiring data for payment from a code symbol related to code payment; A processing means for transmitting the data acquired by the first acquisition means to an external server that provides a payment agency service for the code payment, and receiving a payment result including the code payment brand used in the code payment from the external server; an output means for outputting, when the code payment brand included in the payment result does not match a previously set approved code payment brand, that the code payment has been made with an unapproved code payment brand; A sales data processing device comprising:

2. The sales data processing device according to claim 1 , wherein the output means prints out information indicating that code payment has been made with an unauthorized code payment brand.

3. The sales data processing device according to claim 1 or 2, wherein the output means prints out information indicating an approved code payment brand when code payment is made with an approved code payment brand, and prints out a predetermined character string when code payment is made with an unapproved code payment brand.

4. The sales data processing device according to claim 1 , wherein the output means displays and outputs a screen notifying that code payment has been made with an unapproved code payment brand.

5. A second acquisition means for acquiring product identification information capable of identifying the product from a code symbol attached to the product; a registration means for registering a product corresponding to the product identification information as a purchase target; Further comprising: The processing means transmits the total price of the products registered by the registration means to the external server together with the data acquired by the first acquisition means, thereby requesting the external server to make a code payment for the total price. The sales data processing device according to claim 1 .

6. A computer of the sales data processing device, A first acquisition means for acquiring data for payment from a code symbol related to code payment; A processing means for transmitting the data acquired by the first acquisition means to an external server that provides a payment agency service for the code payment, and receiving a payment result including the code payment brand used in the code payment from the external server; an output means for outputting, when the code payment brand included in the payment result does not match a previously set approved code payment brand, that the code payment has been made with an unapproved code payment brand; A program to make it function as such.

Images