Sales data processing device and program
The sales data processing device improves transaction management by identifying unauthorized code payment brands, ensuring efficient post-processing and reducing operational complexities through enhanced transaction identification.
Patent Information
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2023-07-24
- Publication Date
- 2026-03-13
AI Technical Summary
Existing sales data processing systems fail to distinguish between authorized and unauthorized code payment brands, leading to difficulties in identifying and managing transactions with unapproved brands, which complicates post-processing and reduces operational efficiency.
A sales data processing device that includes a first acquisition means to read payment data from a code symbol, a processing means to transmit data to an external server for payment processing, and an output means to identify and notify if the payment brand is unauthorized, ensuring appropriate transaction management.
Enhances the identifiability of transactions using unauthorized code payment brands, facilitating efficient post-processing and reducing operational complexities by clearly distinguishing between authorized and unauthorized transactions.
Smart Images

Figure 0007829524000001 
Figure 0007829524000002 
Figure 0007829524000003
Abstract
Description
Technical Field
[0001] Embodiments of the present invention relate to a sales data processing apparatus and a program.
Background Art
[0002] Conventionally, in stores that sell goods, settlement processing has been performed using a sales data processing apparatus such as a POS terminal. In recent years, code settlement, which is an electronic payment method using a code symbol such as a two-dimensional code, has become widely popular, and there are also sales data processing apparatuses that support code settlement. For example, there has been proposed a sales data processing apparatus that requests a code settlement of a payment amount from an external server by transmitting data read from a code symbol for code settlement displayed on a customer's smartphone to the external server that provides a settlement agency service together with the payment amount.
[0003] By the way, there are a large number of code settlement brands that provide code settlement services (hereinafter, also simply referred to as brands), but there are stores that approve the use of only some brands depending on the store. Customers who use such stores will present the code symbol of the approved brand at the time of settlement, but there are cases where they may present the code symbol of an unapproved brand due to reasons such as a misoperation. In this case, if the data read from the code symbol of the unapproved brand is transmitted to the external server and the external server supports the code settlement of the unapproved brand, the code settlement may be performed on the store side regardless of the unapproved brand.
[0004] In such a case, from the perspective of customer convenience, in the store, when the settlement result of the external server indicates settlement completion (settlement success), even if it is an unapproved brand, the store does not cancel the transaction and usually finishes the transaction as normal. Note that the store side needs to perform additional post-processing such as paying a fee later for the unapproved brand for which the code settlement has been performed.
[0005] However, as mentioned above, in operations that allow QR code payments of unapproved brands, the sales data processing system treats the results of QR code payments of unapproved brands the same as those of approved brands. Therefore, it is difficult for store employees to recognize which transactions used unapproved brands. Consequently, stores cannot easily extract transactions in which unapproved brands were used during post-processing, and further improvements are desired from the perspective of processing efficiency. [Overview of the Initiative] [Problems that the invention aims to solve]
[0006] The problem that this invention aims to solve is to provide a sales data processing device and program that can improve the identifiability of transactions using unauthorized code payment brands. [Means for solving the problem]
[0007] The sales data processing device of this embodiment includes: 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 that provides a payment processing service for the code payment, and receiving the payment result, including the code payment brand used in the code payment, from the external server; and an output means for outputting that a code payment was made with an unauthorized code payment brand if the code payment brand included in the payment result does not match a pre-set approved code payment brand. [Brief explanation of the drawing]
[0008] [Figure 1] Figure 1 shows an example of a sales data processing system according to an embodiment. [Figure 2] Figure 2 shows an example of the hardware configuration of a POS terminal according to the present invention. [Figure 3] Figure 3 shows an example of the data structure of approved brand information according to the embodiment. [Figure 4]Figure 4 shows an example of the hardware configuration of a store server according to the embodiment. [Figure 5] Figure 5 shows an example of the hardware configuration of a customer terminal according to the embodiment. [Figure 6] Figure 6 shows an example of the functional configuration of a POS terminal, store server, and customer terminal according to an embodiment. [Figure 7] Figure 7 shows an example of a screen displayed on the display unit of a POS terminal according to the embodiment. [Figure 8] Figure 8 shows an example of a store receipt according to the embodiment. [Figure 9] Figure 9 shows an example of a store receipt according to the embodiment. [Figure 10] Figure 10 is a sequence diagram showing an example of the processing flow performed in the sales data processing system of the embodiment. [Figure 11] Figure 11 is a flowchart showing an example of sales data processing performed by the POS terminal of the embodiment. [Modes for carrying out the invention]
[0009] Embodiments of the present invention will be described below with reference to the drawings. The embodiments described below will use a POS terminal used in a store that sells goods as an example. However, the present invention is not limited to the embodiments described below. For example, the items for sale are not limited to tangible goods, but may also be intangible services, etc.
[0010] Figure 1 shows 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 connected via a network Na, such as a LAN (Local Area Network), located within the store. Furthermore, the POS terminal 10 and the code payment server 40 are connected via a network Nb, such as the internet or a dedicated line.
[0012] 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. POS terminal 10 reads code symbols such as barcodes and QR codes attached to products and obtains a product code that can identify the product. A product code is an example of product identification information, such as a JAN code.
[0013] The POS terminal 10 performs a registration process for the products purchased by the customer based on the product code of the products. The registration process involves reading the product name, price, etc. of the product corresponding to the product code from the product master 142 (described later) and storing it in RAM 13, etc.
[0014] Furthermore, the POS terminal 10 initiates the payment processing for the registered products in response to closing operations such as an operation to instruct the end of the registration process or an operation to instruct the start of payment. The payment processing involves calculating the total amount of the products the customer will purchase based on the product information registered in the registration process, and settling that total amount with the customer's payment amount. Here, the payment method is not limited to cash; it may also be other payment methods such as credit cards. In addition, the POS terminal 10 of this embodiment can perform payments via code payment by coordinating with the code payment server 40.
[0015] Furthermore, the POS terminal 10 prints a customer receipt containing product information and payment information (total amount, payment amount, change amount, etc.) for the processed items, as well as a store copy receipt, from the printer 18 described later.
[0016] In addition, the POS terminal 10 transmits product information and accounting information of the products for which settlement processing has been performed (collectively also referred to as transaction data) to the store server 20. Note that the timing of transmitting transaction data from the POS terminal 10 to the store server 20 is not particularly limited. For example, it may be performed at the timing when the settlement processing is completed, or it may be transmitted in a batch at the end of the day when the store closes.
[0017] The store server 20 is installed, for example, in the backyard of the 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. In addition, the store server 20 provides the product master to each of the POS terminals 10. For example, the store server 20 stores the product master locally in the POS terminal 10 by transmitting the product master to each of the POS terminals 10. Also, for example, the store server 20 stores the product master in a state where it can be referred to from each of the POS terminals 10.
[0018] In addition, the store server 20 collects the transaction data received from the POS terminal 10. Also, the store server 20 manages the sales of products in the store based on the collected transaction data, or extracts transaction data for each code settlement brand (hereinafter also simply referred to as a brand) of code settlement.
[0019] The customer terminal 30 is a terminal device used by a customer who visits the store. In the present 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 the code settlement service (hereinafter also referred to as a code settlement app) is pre-installed in the customer terminal 30. When performing code settlement, the customer operating the customer terminal 30 starts the code settlement app, displays a code symbol for code settlement (hereinafter also referred to as a settlement code symbol), and then causes the POS terminal 10 to read the settlement code symbol. Note that the brand of the code settlement app installed in the customer terminal 30 is not limited to one, and may be multiple brands.
[0020] The code settlement server 40 is a server device that provides settlement agency services for multiple types of brands. The code settlement server 40 collaborates with the POS terminal 10 to realize settlement processing using code settlement.
[0021] As described above, in the sales data processing system 1 of the present embodiment, by having the POS terminal 10 read the settlement code symbol presented to the customer terminal 30, it is possible to pay for the price of the goods by code settlement.
[0022] Next, among the devices included in the sales data processing system 1 described above, the configurations of the POS terminal 10, the store server 20, and the customer terminal 30 will be described.
[0023] FIG. 2 is a diagram showing an example of the 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, and the like.
[0024] The CPU 11 is an example of a processor and comprehensively controls the operation of the POS terminal 10. The ROM 12 stores various programs that can be executed by the CPU 11. The RAM 13 is a work area for temporarily storing programs and various data. For example, the RAM 13 stores the product code and product information of the registered products.
[0025] The memory unit 14 is composed of a non-volatile memory such as an HDD (Hard Disc Drive) or a flash memory that retains the stored information even when the power is turned off. The memory unit 14 stores various programs and setting information that can be executed by the CPU 11. For example, the memory unit 14 stores a control program 141 that can be executed by the CPU 11, a product master 142, and the like. The product master 142 stores product information corresponding to the product code in association with the product code of each product sold in the store. The product information includes, for example, the product name, price (unit price), and the like.
[0026] Furthermore, the memory unit 14 stores approved brand information 143, which indicates the brands of code payment services approved for use in the store. In other words, any brands other than those stored in the approved brand information 143 are brands not approved by the store. Approved brands can also be described as the brands of the code payment service companies with which the store has a service agreement.
[0027] Figure 3 shows an example of the data structure of the approved brand information 143. As shown in Figure 3, the approved brand information 143 registers information that can identify each approved brand, such as the brand name and brand ID (hereinafter also referred to as brand information). Figure 3 shows an example in which brands named "Brand A" and "Brand B" are registered. There is no particular limit to the number of brands registered in the approved brand information 143.
[0028] Returning to Figure 2, the CPU 11, ROM 12, RAM 13, and memory unit 14 are connected to each other via a bus or the like. Here, the CPU 11, ROM 12, and RAM 13 constitute the control unit 100 of the POS terminal 10. The control unit 100 realizes the functions of the POS terminal 10 by operating according to the control program 141 stored in the ROM 12 and memory unit 14 and loaded into the RAM 13.
[0029] Furthermore, the control unit 100 is connected to the operation unit 15, display unit 16, code reader 17, printer 18, etc., via a bus or the like.
[0030] The operation unit 15 has various operation keys for the operator to input operations. 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 the product registration process is completed and the process proceeds 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 registered product and accounting information related to the payment process. The operation unit 15 may also be a touch panel provided on the display unit 16.
[0031] The code reader 17 is a reading device capable of reading code symbols. The code reader 17 reads code symbols, for example, by capturing an image of them. Alternatively, the code reader 17 may read symbols using red light (for example, infrared light). The code reader 17 also reads code symbols attached to products and payment code symbols displayed on the customer terminal 30. The printer 18 is a printing device, for example, a thermal printer. Under the control of the control unit 100, the printer 18 issues a receipt that prints product information and payment information related to the products that have been processed for payment.
[0032] Furthermore, the control unit 100 is connected to the 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 connected to the store server 20 via network Na, enabling communication. The communication unit 19 is also connected to the code payment server 40, etc., via network Nb, enabling communication.
[0033] Next, the hardware configuration of the store server 20 will be described. Figure 4 is a diagram showing an example of the hardware configuration of the store server 20. As shown in Figure 4, the store server 20 includes a CPU 21, ROM 22, RAM 23, memory unit 24, etc.
[0034] The CPU 21 is an example of a processor that comprehensively controls the operation of the store server 20. The ROM 22 stores various programs that the CPU 21 can execute. The RAM 23 is a work area for temporarily storing programs and various data.
[0035] The memory unit 24 is composed of non-volatile memory such as an HDD or 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 and a transaction history DB (database) 243 for storing and managing transaction data. The data structure of the product master 242 is the same as that of the product master 142. For example, by providing the product master 242 to each POS terminal 10, the product master 242 is used as the product master 142 in each POS terminal 10.
[0036] The CPU 21, ROM 22, RAM 23, and memory unit 24 are connected to each other via a bus or the like. Here, the CPU 21, ROM 22, and RAM 23 constitute the control unit 200 of the store server 20. The control unit 200 realizes the functions of the store server 20 by having the CPU 21 operate according to the control program 241 stored in the ROM 22 and memory unit 24 and loaded into the RAM 23.
[0037] Furthermore, the control unit 200 is connected to the 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 and the like via the network Na, enabling communication.
[0038] Next, the hardware configuration of the customer terminal 30 will be described. Figure 5 is a diagram showing an example of the hardware configuration of the customer terminal 30. As shown in Figure 5, the customer terminal 30 includes a CPU 31, ROM 32, RAM 33, memory unit 34, etc.
[0039] The CPU 31 is an example of a processor that comprehensively controls the operation of the customer terminal 30. The ROM 32 stores various programs that the CPU 31 can execute. The RAM 33 is a work area for temporarily storing programs and various data.
[0040] The memory unit 34 is composed of non-volatile memory such as an HDD or flash memory that retains stored information even when the power is turned off. The memory unit 34 stores various programs and setting information that the CPU 31 can execute. 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 payments. In addition, the memory unit 34 is configured to store (install) a separate payment application 342 for each code payment brand used by the operator.
[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 the control unit 300 of the customer terminal 30. The control unit 300 realizes the functions of the customer terminal 30 by operating according to the control program 341 stored in the ROM 32 and memory unit 34 and loaded into the RAM 33. Furthermore, the control unit 300 realizes functions related to code payment, such as displaying a payment code symbol, by operating according to the launched payment application 342.
[0042] Furthermore, the control unit 300 is connected to the operation unit 35, display unit 36, etc., via a bus or the like. The operation unit 35 has various operation keys for the operator to input operations. The display unit 36 is a display device such as a liquid crystal display. The display unit 36 displays a payment code symbol, etc., under the control of the control unit 100. The operation unit 35 may be a touch panel provided on the display unit 36.
[0043] Furthermore, the control unit 300 is connected to the 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 a server device of a service company that provides code payment services via a network such as a public telephone line (not shown), enabling communication between the two.
[0044] Next, the functional configuration of the POS terminal 10, store server 20, and customer terminal 30 described above will be explained. Figure 6 shows an example of the functional configuration of the POS terminal 10, store server 20, and customer terminal 30.
[0045] First, let's describe the functional configuration of the customer terminal 30. As shown in Figure 6, the customer terminal 30 is equipped with a code payment function unit 301 as part of its functional configuration.
[0046] The functional configuration of the customer terminal 30 is a software configuration realized by the customer terminal 30's processor operating according to a control program 341 (and payment application 342) stored in the ROM 32 or 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 dedicated circuits.
[0047] The code payment function unit 301 is a functional configuration realized through the cooperation of the control program 341 and the payment application 342. The code payment function unit 301 performs various processes related to code payments. For example, the code payment function unit 301 displays a payment code symbol for code payments on the display unit 36 in response to the operator's operation. The payment code symbol holds payment data for performing code payments. The payment data includes, for example, information that can identify the ID that the operator has contracted with the service provider of the brand of the payment application 342.
[0048] The code payment function unit 301 is implemented 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 implemented by the payment application 342 with the brand name "Company A" will display a payment code symbol that holds the payment data for Company A. Similarly, the code payment function unit 301 implemented by the payment application 342 with the brand name "Company B" will display a payment code symbol that holds the payment data for Company B.
[0049] Next, the functional configuration of the POS terminal 10 will be described. As shown in Figure 6, the POS terminal 10 includes a reading result acquisition unit 101, a registration processing unit 102, and a payment processing unit 103.
[0050] The functional configuration of the POS terminal 10 is a software configuration realized by the POS terminal 10's processor operating according to a control program 141 stored in the ROM 12 or memory unit 14, but is not limited to this. For example, some or all of the functional configuration of the POS terminal 10 may be realized by hardware such as dedicated circuits.
[0051] The reading result acquisition unit 101 is an example of the first acquisition means and the second acquisition means. The reading result acquisition unit 101 acquires the reading results read by the code reader 17 from the code symbol. For example, the reading result acquisition unit 101 acquires the reading result of the code symbol attached to the product, i.e., the product code. Alternatively, for example, the reading result acquisition unit 101 acquires the reading result of the payment code symbol displayed on the customer terminal 30, i.e., payment data.
[0052] The registration processing unit 102 is an example of a registration method. Based on the product code acquired by the reading result acquisition unit 101, the registration processing unit 102 performs the registration process for the products purchased by the customer. Specifically, the registration processing unit 102 reads the product information of the product corresponding to the product code acquired by the reading result acquisition unit 101 from the product master 142. The registration processing unit 102 then stores (registers) the read product information in RAM 13 or the like, associating it with the product code and quantity of that product. The registration processing unit 102 also displays the product name, price, quantity, etc. of each product registered in the registration process on the display unit 16 in the order in which they were registered.
[0053] The settlement processing unit 103 is an example of a processing means and output means. The settlement processing unit 103 executes the settlement process for the products registered in the registration process in response to the operator's closing operation.
[0054] For example, when the settlement processing unit 103 receives a closing operation via the operation unit 15, it displays a screen on the display unit 16 that allows the user to select a payment method, such as cash payment or code payment. If cash payment is selected, the settlement processing unit 103 executes a settlement process that settles the total amount of the registered products with the payment amount received via a deposit device (not shown). The settlement processing unit 103 then issues receipts for both the customer and the store.
[0055] Here, a customer receipt is a receipt given to a customer who has purchased goods, and it prints information such as the store name, the date and time of the transaction, the items purchased (product names), the unit price, and the payment amount. A store copy receipt is a document used to keep a record of transactions and is also called a journal. The contents of the store copy receipt may be the same as the customer receipt, or it may be a collection of information extracted from the customer receipt. For example, a store copy receipt may print the date and time of the transaction and the total amount of goods purchased (payment amount). Hereafter, when customer and store copy receipts are not distinguished, they will simply be referred to as receipts.
[0056] Furthermore, when code payment is selected, the payment processing unit 103 works in cooperation with the reading result acquisition unit 101 to wait until payment data is acquired. Once the reading result acquisition unit 101 acquires the payment data, the payment processing unit 103 transmits that payment data, along with the total amount of the goods to be paid, to the code payment server 40, thereby requesting the code payment server 40 to perform a code payment for the amount to be paid based on the payment data.
[0057] When the payment processing unit 103 receives a payment completion notification (hereinafter also referred to as the payment completion notification) from the code payment server 40, it determines that the code payment for the total amount has been completed and issues receipts for the customer and the store. The payment completion notification 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 that the code payment has failed, the payment processing unit 103 will display a message indicating the code payment failure on the display unit 16. If the code payment server 40 notifies 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] The settlement processing unit 103 generates transaction data showing the details of the transaction once the settlement process is complete 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 settlement processing unit 103 or the control unit 100.
[0059] Incidentally, in the checkout area where the POS terminal 10 is set up, it is common to display the brands of code payment that can be used at the store. In this case, customers who wish to use code payment will check the displayed brand and perform the code payment by launching the corresponding payment application installed on their customer terminal 30.
[0060] However, if the customer terminal 30 has payment applications from multiple brands installed, a payment application from a brand not authorized by the store may be launched due to a mistake or other reason, and a payment code symbol may be displayed. In this case, if the store clerk inadvertently reads the payment data from the displayed payment code symbol at the POS terminal 10, that payment data will be sent to the code payment server 40. Furthermore, if the code payment server 40 supports code payment for the brand of payment data sent from the POS terminal 10, a code payment will be processed even though the brand is not authorized by the store.
[0061] In such cases, from the perspective of customer convenience, if the payment result from the code payment server 40 indicates that the payment has been completed, even if the brand is not authorized, it is treated the same as a normal payment process. However, since the store will later need to perform additional post-processing, such as paying fees, for unauthorized brands that were used in code payments, it is desirable to be able to identify which transactions used unauthorized brands.
[0062] Therefore, when the payment processing unit 103 of this embodiment 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 notification matches any of the brand information registered in the approved brand information 143, the approved brand information 143 determines that an approved brand was used for the code payment. In this case, the payment processing unit 103 executes the prescribed payment processing, issuing various receipts and recording transaction data.
[0064] On the other hand, if the brand information included in the payment completion notification does not match any of the brand information registered in the approved brand information 143, the approved brand information 143 will determine that an unauthorized 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 indicating that an unauthorized brand was used for code payment. The payment processing unit 103 also issues a receipt for the store's records with information that identifies the unauthorized brand being used for code payment. Furthermore, the payment processing unit 103 records the generated transaction data with information that identifies the unauthorized brand being used for code payment.
[0066] Now, referring to Figure 7, we will explain the notification screen that is displayed when an unauthorized brand is used for code payment. Figure 7 is a diagram showing an example of a screen displayed on the display unit 16 of the POS terminal 10.
[0067] If the payment processing unit 103 determines that an unauthorized brand has been used for code payment, it displays a notification screen G, for example, as shown in Figure 7, on the display unit 16. Specifically, on the notification screen G, the payment processing unit 103 notifies that an unauthorized brand has been used and displays a message Ga prompting the user to contact the service provider. The payment processing unit 103 also displays the payment amount (total amount of goods) Gb that has been paid by code payment on the notification screen G.
[0068] This allows the operator of the POS terminal 10 to easily see, by looking at the notification screen G, that an unauthorized brand was used for code payment and the amount paid by this code payment. Therefore, the POS terminal 10 can improve the identifiability of transactions in which payments were made using an unauthorized brand.
[0069] Next, with reference to Figures 8 and 9, we will explain an example of a store copy receipt issued when a code payment is made.
[0070] Figure 8 shows an example of a store copy receipt, specifically an example of a store copy receipt issued when a code payment is made using an approved brand. Figure 9 also shows an example of a store copy receipt, specifically an example of a store copy receipt issued when a code payment is made using an unapproved brand.
[0071] As shown in Figures 8 and 9, the store copy receipt R has a first area Ra on which store information and logo marks are printed, and a second area Rb on which the date and time of the transaction and a transaction number that identifies the transaction are printed.
[0072] Furthermore, the store copy receipt R has a third area Rc on which the transaction details are printed. The third area Rc includes a title area Pa on which the receipt title is printed, a receipt type area Pb on which information indicating that it is a store copy receipt is printed, a settlement date and time area Pc on which the date and time the transaction took place is printed, and a transaction amount area Pd on which the payment amount (transaction amount) paid in the transaction is printed.
[0073] Here, the title area Pa prints the payment method used in the transaction and information indicating that it is a sales slip for the sale of goods. For example, if a code payment is made using the approved brand "Brand A", the title area Pa prints "Brand A", indicating the brand name of the code payment used as the payment method (see Figure 8). Such a brand name can be read from brand information identified by, for example, matching the payment completion notice with the approved brand information 143.
[0074] On the other hand, if a code payment is made using an unapproved brand, as shown in Figure 9, the brand name of the code payment used as the payment method will be printed in the title area Pa in the form of "XXXXXXXXXXXX" or similar. In this way, the payment processing unit 103 replaces the brand name with a predetermined string (hereinafter also referred to as the flag string) and prints it when an unapproved brand is used. This allows store staff or other personnel performing post-processing to easily determine whether the code payment for that transaction was made using 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, if 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 notification in the title area Pa. However, even in this case, it is preferable that the payment processing unit 103 adds a flag string such as "X" to the beginning of the brand information, for example, to make it easily identifiable as an approved brand.
[0076] Furthermore, in the above example, the title area Pa is used to output information that identifies whether or not the code payment brand is approved, but the output destination is not limited to this. For example, the beginning of the receipt type area Pb may be printed with information indicating the code payment brand name used in the transaction or an unapproved brand. Alternatively, information indicating the code payment brand name used in the transaction or an unapproved brand may be printed in a location other than the third area Rc.
[0077] Furthermore, the information included in the store copy receipt R is not limited to the examples above. For example, the store copy receipt R may include information such as a terminal ID that can identify the POS terminal 10 on which the payment was processed, or a store employee ID that can identify the store employee who operated the POS terminal 10.
[0078] Furthermore, the settlement processing unit 103 may also use the same method as described above for the store receipt R when adding information to the transaction data that identifies that an unauthorized brand was used for code payment. Specifically, when an unauthorized brand is used for code payment, the settlement processing unit 103 enters a predetermined flag string into the input field for the brand name included in the transaction data, making it identifiable as an approved brand. Alternatively, for example, when an unauthorized brand is used for code payment, the settlement processing unit 103 may enter part or all of the brand information included in the payment completion notice, along 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 will also include areas that display information similar to the first area Ra, the second area Rb, and the third area Rc described above. However, information that identifies an unauthorized brand being used for code payment may or may not be printed. In the former case, for example, the brand names of each brand registered in the approved brand information 143 may be added as usable code payment brands, along with (or instead of) the printing of information that identifies an unauthorized brand. This allows the payment processing unit 103 to make the customer aware of the brands that can be used at its store, and to warn them about the possibility of using an unauthorized brand in future transactions.
[0080] Next, the functional configuration of the store server 20 will be described. As shown in Figure 6, the store server 20 includes a transaction data collection unit 201 and a transaction data analysis unit 202.
[0081] The functional configuration of the store server 20 is a software configuration realized by the store server 20's processor operating according to a control program 241 stored in the ROM 22 and 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 dedicated circuits.
[0082] The transaction data collection unit 201 acquires (collects) transaction data from each of the POS terminals 10 and stores it in the transaction history DB 243. For example, the transaction data collection unit 201 acquires transaction data transmitted from each of the POS terminals 10 and stores it in the transaction history DB 243. Alternatively, for example, the transaction data collection unit 201 requests transaction data from each of the POS terminals 10, acquires the transaction data transmitted from the POS terminals 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 other format. For example, the transaction data analysis unit 202 calculates the total sales amount for a day by summing 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. Alternatively, the transaction data analysis unit 202 calculates the total sales amount for each settlement method by summing 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] Furthermore, for example, the transaction data analysis unit 202 extracts transaction data for transactions using unauthorized brands based on the code payment information included in the transaction data. For example, the transaction data analysis unit 202 extracts transaction data from the transaction history DB 243 in which a predetermined flag string indicating an unauthorized brand has been entered in the brand name input field. Furthermore, for example, after extracting transaction data in which a flag string has been entered in the brand name input field, the transaction data is further separated and extracted for each unauthorized brand based on the brand information entered in the input field.
[0085] Thus, the transaction data generated by the POS terminal 10 includes information that can identify unauthorized brands, making it easy to extract transaction data where code payments were made using unauthorized brands. Therefore, the sales data processing system 1 can efficiently perform post-processing, such as paying fees for unauthorized brands used in code payments.
[0086] Next, we will explain the processing flow performed by the sales data processing system 1. Figure 10 is a sequence diagram showing an example of the processing flow performed by the sales data processing system 1. Note that this example shows the processing when a code payment is made.
[0087] First, at the POS terminal 10, when the code reader 17 reads the product code from the code symbol attached to the product purchased by the customer, the reading result acquisition unit 101 acquires the read product code (step S11). Next, the registration processing unit 102 performs the registration process based on the product code acquired in step S11 (step S12).
[0088] Furthermore, the POS terminal 10 executes the processes described in steps S11 and S12 each time a product code is read. Also, when the POS terminal 10 receives a closing operation via the operation unit 15 (step S13), the payment processing unit 103 displays a screen on the display unit 16 that allows the user to select a payment method (hereinafter referred to as the payment method selection screen) (step S14).
[0089] If code payment is selected from the payment method selection screen (step S15), the payment processing unit 103 works in cooperation with the reading result acquisition unit 101 and waits until payment data is entered.
[0090] Meanwhile, when the control unit 300 of the customer terminal 30 is instructed by the customer to start the payment application 342, it starts the instructed payment application 342, thereby realizing the code payment function unit 301 (step S16). Subsequently, the code payment function unit 301 displays a 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 payment data from the payment code symbol. Next, the reading result acquisition unit 101 acquires the payment data read by the code reader 17 (step S18).
[0092] The payment processing unit 103 requests code payment from the code payment server 40 by sending the payment data acquired in step S18, along with the total amount of the goods (payment amount) (step S19).
[0093] When the code payment server 40 receives payment data and payment amount from the POS terminal 10, it executes a code payment for the payment amount based on the payment data (step S20). Then, the code payment server 40 sends a payment completion notification, including 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 or not a code payment was made with an approved brand.
[0095] If the payment processor determines that a code payment has been made using an approved brand, it issues a receipt containing the name of the blend used for the code payment (step S31). The payment processor then generates transaction data containing the name of the blend used for the code payment and records it in the memory unit 14 or the store server 20 (step S32).
[0096] On the other hand, if it is determined that a code payment has been made with an unauthorized brand, the payment processing unit 103 displays information on the display unit 16 indicating that a code payment has been made with an unauthorized brand (step S41). Next, the payment processing unit 103 issues a receipt containing a flag string indicating that a code payment has been made with an unauthorized blend (step S42). Then, the payment processing unit 103 generates transaction data containing the flag string and records it in the memory unit 14 or the store server 20, etc. (step S43).
[0097] Next, with reference to Figure 11, the sales data processing performed by the POS terminal 10 will be explained. Here, Figure 11 is a flowchart showing an example of sales data processing performed by the POS terminal 10. Note that this processing corresponds to the processing from step S13 onwards in the processing performed by the POS terminal 10 shown in Figure 10.
[0098] When the settlement processing unit 103 determines that it has received a closing operation via the operation unit 15 (step S51), it displays the payment method selection screen on the display unit 16 (step S52) and waits until a payment method is selected.
[0099] 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 processing using the selected payment method (step S54) and proceeds to step S60.
[0100] Furthermore, if code payment is selected (Step S53; Yes), the payment processing unit 103 waits until payment data is read (Step S55; No). When payment data is read by the code reader 17 (Step S55; Yes), the reading result acquisition unit 101 acquires the payment data (Step S56).
[0101] Next, the payment processing unit 103 requests code payment from the code payment server 40 by sending the payment data acquired in step S49 along with the payment amount (step S57). Then, 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 or not a code payment was made with an approved brand (step S59).
[0103] If it is determined that a code payment was made using 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 that includes the payment method used (step S60). For example, if the payment method used is cash, the payment processing unit 103 issues a receipt that indicates it is a cash payment, the amount deposited, the amount of change given, etc. If the payment method used is a code payment, the payment processing unit 103 issues a receipt that includes the brand name, etc., identified in the verification in step S59.
[0104] Furthermore, once the settlement processing unit 103 generates transaction data including the payment method used, it records the transaction data in the memory unit 14 or the store server 20 (step S61) and terminates this process.
[0105] On the other hand, if it is determined that a code payment was made with an unauthorized brand (step S59; No), the payment processing unit 103 displays a notification screen on the display unit 16 indicating that a code payment was made with an unauthorized brand (step S62). Next, the payment processing unit 103 issues a receipt containing a predetermined flag string, etc., indicating that a code payment was made with an unauthorized blend (step S63). Then, the payment processing unit 103 generates transaction data containing the predetermined flag information, etc., records the transaction data in the memory unit 14 or the store server 20, etc. (step S64), and terminates this process.
[0106] As described above, the POS terminal 10 obtains payment data from the payment code symbol and sends the obtained payment data to the code payment server 40, thereby requesting the code payment server 40 to execute the code payment. The POS terminal 10 then receives a payment result notification from the code payment server 40, which includes the brand used for the code payment. If the brand of the code payment included in the payment result notification 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 unauthorized brand.
[0107] As a result, the POS terminal 10 can notify or record, using display output, print output, or data output, that an unauthorized brand was used in a code payment. Therefore, the POS terminal 10 can improve the identifiability of transactions in which unauthorized brands are used.
[0108] The embodiments described above can also be modified and implemented as appropriate by changing some of the configurations or functions of each of the devices described above. Therefore, several modifications of the embodiments described above will be described below as other embodiments. In the following, we will mainly describe the differences from the embodiments described above, and will omit detailed explanations of points that are common with what has already been described. Furthermore, the modifications described below may be implemented individually or in combination as appropriate.
[0109] (Variation 1) In the above-described embodiment, the POS terminal 10 was explained as a device operated by store employees such as shop staff. However, the POS terminal 10 is not limited to this, and may be a self-service type operated by the customer themselves.
[0110] Furthermore, if the POS terminal 10 is a self-service type, the payment processing unit 103 may be controlled not to display the notification message that is displayed on the display unit 16 when an unauthorized brand is used for code payment.
[0111] Furthermore, although the above-described embodiment explains a configuration in which registration processing and payment processing are performed on the POS terminal 10, the configuration is not limited to this, and the registration processing and payment processing may be performed on different devices. In this case, the POS terminal 10 (also called the registration device) that performs payment processing can perform the same processing as in the above-described embodiment, specifically the processing after the closing operation has been performed, so that when code payment is made with an unauthorized brand, the operator is notified, and the transaction is recorded on the receipt and in the transaction data.
[0112] The programs executed in each of the above-described embodiments (and modifications) are provided pre-installed in ROM, storage units, etc. The programs executed in each of the above-described embodiments may also be provided as installable or executable files recorded on a computer-readable recording medium such as a CD-ROM, flexible disk (FD), CD-R, or DVD (Digital Versatile Disk).
[0113] Furthermore, the programs executed by each 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. Alternatively, the programs executed by each of the above-described embodiments may be provided or distributed via a network such as the Internet.
[0114] Although embodiments of the present invention have been described above, these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments and their variations can be implemented in a variety of other forms, and various omissions, substitutions, changes, and combinations can be made without departing from the spirit of the invention. These embodiments and their variations are included in the scope and spirit of the invention, as well as in the claims of the invention and its equivalents. [Explanation of Symbols]
[0115] 1. Sales data processing system 10 POS terminals 20 Store Servers 30 Customer terminals 40 Code Payment Servers 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] Japanese Patent Publication No. 2021-174103
Claims
1. A first acquisition means for obtaining payment data from a code symbol related to code payment, Processing means that transmits the data acquired by the first acquisition means to an external server that provides the payment processing service for the code payment, and receives the payment results, including the code payment brand used in the code payment, from the external server. If the code payment brand included in the settlement result does not match a pre-configured approved code payment brand, an output means outputs that a code payment was made with an unapproved code payment brand. A sales data processing device equipped with the following features.
2. The sales data processing device according to claim 1, wherein the output means prints and outputs information indicating that a code payment was made using an unauthorized code payment brand.
3. The sales data processing device according to claim 1 or 2, wherein the output means prints information indicating the code payment brand when a code payment is made with an approved code payment brand, and prints a predetermined string of characters when a 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 indicating that a code payment has been made using an unauthorized code payment brand.
5. A second acquisition means for acquiring product identification information that can identify the product from a code symbol attached to the product, A registration means for registering a product corresponding to the aforementioned product identification information as a purchase target, Furthermore, The processing means transmits the total amount of the products registered by the registration means, along with the data acquired by the first acquisition means, to the external server, thereby requesting the external server to process a code payment for the total amount. The sales data processing device according to claim 1.
6. The computer for the sales data processing unit, A first acquisition means for obtaining payment data from a code symbol related to code payment, Processing means that transmits the data acquired by the first acquisition means to an external server that provides the payment processing service for the code payment, and receives the payment results, including the code payment brand used in the code payment, from the external server. If the code payment brand included in the settlement result does not match a pre-configured approved code payment brand, an output means outputs that a code payment was made with an unapproved code payment brand. A program to make it work.
Citation Information
Patent Citations
Information processing device and control program thereof
JP2021174103A