Data processing device and program

Abstract

To support a sound transaction.SOLUTION: A data processing device comprises first acquisition means, second acquisition means, settlement means, and processing control means. The first acquisition means acquires information about a customer by reading a code displayed on a medium with an optical system. The second acquisition means acquires the information about the customer by reading the code in a system different from that of the optical system. The settlement means performs settlement. The processing control means allows processing based on the information about the customer acquired by the second acquisition means; and the processing control means limits the processing based on the information about the customer acquired by the first acquisition means.SELECTED DRAWING: Figure 8

Description

[Technical field]

[0001] The present invention relates to a data processing device and a program. [Background technology]

[0002] Cash registers have traditionally been used in restaurants, convenience stores, and other types of stores. In recent years, self-service registers, which allow customers to register products and settle payments, have become widespread (see, for example, Patent Document 1). In various types of stores, cash registers are capable of reading personal information of customers to carry out transactions. For example, personal information would be employee ID information identifying employees in a store for employees, such as a staff cafeteria, or membership information identifying member customers in a regular store for general customers. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2020-205023 A Summary of the Invention [Problem to be solved by the invention]

[0004] However, in the conventional technology, there was a risk that a third party could obtain personal information of another person and conduct an illegal transaction that would cause a disadvantage to that person. For example, a fraudulent transaction would involve generating a barcode that encodes the personal information of another person and having the barcode read by a cash register, thereby using the personal information. Therefore, there was a problem in that sound transactions were not always conducted in the conventional technology.

[0005] The present invention has been made in view of the above circumstances, and has an object to provide a technique capable of supporting sound transactions. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems, one embodiment of the data processing device of the present invention is a data processing device characterized by comprising: a first acquisition means for acquiring customer information by optically reading a code displayed on a medium, a second acquisition means for acquiring customer information by reading the code by a method different from the optical method, a payment means for making a payment, and a processing control means for allowing processing based on the customer information acquired by the second acquisition means and restricting the processing based on the customer information acquired by the first acquisition means.

[0007] In order to solve the above-mentioned problems, another aspect of the present invention is a program that causes a computer to function as a data processing device, a first acquisition means for acquiring customer information by optically reading a code displayed on a medium, a second acquisition means for acquiring customer information by reading the code by a method different from the optical method, a payment means for making payment, and a processing control means for allowing processing based on the customer information acquired by the second acquisition means and restricting the processing based on the customer information acquired by the first acquisition means. [Brief description of the drawings]

[0008] [Figure 1] 1 is an explanatory diagram showing a network configuration of a sales data processing system St according to a first embodiment of the present invention. [Diagram 2] 2 is an explanatory diagram showing an example of installation of a registration settlement device 20. FIG. [Diagram 3] A block diagram showing an example of the hardware configuration of the registration settlement device 20. [Figure 4] FIG. 13 is a diagram showing an example of screen transitions from the start of registration to the start of settlement in full self-service mode. [Diagram 5] FIG. 13 is a diagram showing an example of screen transitions from the start of registration to the start of settlement in full self-service mode. [Figure 6] FIG. 13 is a diagram showing an example of screen transitions from the start of registration to the start of settlement in full self-service mode. [Figure 7A] 13 is a diagram showing an example of transaction management information stored in transaction management DB2. FIG. [Figure 7B] A block diagram showing an example of the functional configuration of a registration settlement device 20 according to this embodiment. [Figure 8] An example of the screen transition when an employee ID barcode is read will be described. [Figure 9] 13 is a flowchart showing an example of sales data processing performed by the registration settlement device 20. [Figure 10] 13 is a flowchart showing an example of sales data processing performed by the registration and settlement device 20 according to the first modification. [Figure 11] 13 is a flowchart showing an example of sales data processing performed by the registration and settlement device 20 according to the second modification. [Figure 12] 13 is a flowchart showing an example of sales data processing performed by the registration and settlement device 20 according to the second modification. [Figure 13] FIG. 13 is a diagram showing an example of an employee ID card presentation reminder screen relating to Modification 3. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] (Embodiment 1) (Network configuration of sales data processing system St) FIG. 1 is an explanatory diagram showing a network configuration of a sales data processing system St according to a first embodiment of the present invention. The sales data processing system St is introduced in stores for employees, such as a shop or a staff cafeteria within a business establishment. A business establishment is, for example, a facility where many employees are employed. Specifically, business establishments are, for example, offices, factories, hospitals, schools, government offices, accommodation facilities, airports, fishing ports, etc. Employees are customers at stores for employees, and specifically include employees (staff) and employers (officers) of the business establishment.

[0010] A store for employees may be a store operated by the business establishment, or may be a store outsourced by the business operator. A store may also be an unmanned store with no store staff (clerks) on-site. In the case of a cafeteria, the products sold at a store for employees are food and drink provided to customers, and in the case of a convenience store, they include regular products such as lunch boxes and drinks, as well as equipment provided to employees. Equipment is items used at the business establishment, and includes items worn by employees, such as work clothes, uniforms, shoes, hats, and belts. Equipment also includes office supplies. Office supplies include, for example, computer peripherals such as a mouse, writing implements such as ballpoint pens, and items surrounding copy machines such as copy paper and toner. In the following, employees are referred to as "employees."

[0011] Payments at stores include normal payments such as cash, credit card, and electronic money, as well as payments using employee ID cards (hereinafter referred to as "employee ID card payments"). Employee ID card payments are deducted from salary, i.e., are deferred payments. With employee ID card payments, for example, a specified discount (e.g., 30% off) is applied to the actual payment amount and then deducted from the salary. In addition, the sales data processing system St stores employee ID card information that identifies the employee in a transaction in association with transaction information. This enables post-payment settlement.

[0012] The sales data processing system St shown in Fig. 1 includes a transaction management server 1, a store controller 10, a transaction status management device 11, and a registration and settlement device 20. Each device is communicatively connected via a LAN 55. Each device is a computer device including a CPU (Central Processing Unit), a ROM (Read Only Memory), a RAM (Random Access Memory), a communication unit, etc.

[0013] The transaction management server 1 manages transactions for each employee. The transaction management server 1 is connected to the store controller 10 via a network. The transaction management server 1 communicates with the store controller 10, for example, and also communicates with the transaction status management device 11 and the registration settlement device 20 via the store controller 10. Note that the transaction management server 1 may communicate directly with the transaction status management device 11 and the registration settlement device 20 without going through the store controller 10.

[0014] The transaction management server 1 includes a transaction management DB (database) 2. The transaction management DB 2 stores transaction management information indicating transaction information for each employee. Details of the transaction management DB 2 will be described later with reference to FIG. 7A.

[0015] The store controller 10 stores various information necessary for transactions, such as a product master. A transaction includes product registration and settlement. The product master is a file that stores product information including product identification information (e.g., JAN (Japanese Article Number) code), product name, and sales price for each product. The product master includes product identification information, product name, unit price, etc. of products that require weighing (products to be weighed). In addition to the product master, the store controller 10 also stores various information such as inventory status, sales history, and deposit and withdrawal records.

[0016] The transaction status management device 11 is a device for a store clerk to monitor a customer who operates the registration and settlement device 20. Specifically, the transaction status management device 11 can display the status of the registration and settlement device 20 (operation mode, processing status, etc.) and control the registration and settlement device 20. A store clerk assigned to the transaction status management device 11 can monitor a customer who operates the registration and settlement device 20 via a monitor provided in the transaction status management device 11. Since users of a store for employees are limited to employees, the possibility of shoplifting or other fraudulent acts is lower than in a normal store. For this reason, a store clerk does not need to be assigned to the transaction status management device 11, and the sales data processing system St does not need to be provided with the transaction status management device 11.

[0017] The registration and settlement device 20 is an example of a data processing device. The registration and settlement device 20 is a cash register that accepts product registration and performs settlement. The registration and settlement device 20 operates in a full self-service mode among a plurality of operation modes. The plurality of operation modes include, for example, a full self-service mode, a store clerk registration mode, and a checkout only mode.

[0018] The full self-service mode is a mode in which the customer registers products on his / her own device (self-service registration) and settles the bill on his / her own device (self-service settlement). The store clerk registration mode is a mode in which a store clerk registers the product and the customer meets the store clerk to settle the payment (face-to-face settlement). The checkout-only mode is a mode for performing self-payment. In the checkout-only mode, self-payment is performed based on payment information generated by the registered payment device 20 in the store clerk registration mode. The registration and settlement device 20 may be a dedicated self-checkout register (a device dedicated to self-registration and self-settlement) in which the operation mode cannot be switched.

[0019] The sales data processing system St may include a clerk terminal carried by a clerk. The clerk terminal can display the status of the registered settlement device 20 (operation mode, processing status, etc.) and control the registered settlement device 20. The clerk terminal can also receive information from the registered settlement device 20 indicating that a clerk should be called. When the clerk terminal receives the information, it notifies the clerk that a call has been made from a customer.

[0020] (Example of configuration of the registration settlement device 20) Next, the configuration of the registration and settlement device 20 will be described with reference to FIG. 2 and FIG. FIG. 2 is an explanatory diagram showing an example of installation of the registration and settlement device 20. As shown in FIG. Fig. 3 is a block diagram showing an example of a hardware configuration of the registration and settlement device 20. In Fig. 2 and Fig. 3, the same parts are denoted by the same reference numerals.

[0021] An example of the configuration of registration and settlement device 20 shown in Fig. 3 will be described below with reference to Fig. 2. Registration and settlement device 20 includes a CPU 201, a ROM 202, a RAM 203, a hard disk 204, a customer display unit 205, a customer scanner unit 206, a card reader unit 208, a change dispenser 209, a store clerk display unit 210, a key operation unit 211, a store clerk scanner unit 212, a printer unit 213, an audio output unit 214, a communication unit 215, and a camera 216. These can communicate with each other via a bus.

[0022] The CPU 201 is a central processing unit, and controls the operation of the registered settlement device 20 by reading and executing various programs stored in the ROM 202. The various programs include a data processing program according to this embodiment. The ROM 202 is a read-only memory, and stores various types of information used by the CPU 201, including programs.

[0023] The RAM 203 is a readable and writable memory, and stores various information. For example, the RAM 203 stores information acquired from the outside (for example, a product master acquired from the store controller 10) and information generated during processing. This information includes, for example, registration information generated during product registration processing for registering products, and settlement information generated during settlement processing for settling the registered products (registered products).

[0024] Hard disk 204 stores various information. For example, hard disk 204 stores imaging results (e.g., video) captured by camera 216. Hard disk 204 may store various programs executed by CPU 201, instead of ROM 202. Also, instead of RAM 203, hard disk 204 may store information acquired from the outside and information generated in processing.

[0025] The customer-side display unit 205 is a touch display for customers. The customer-side display unit 205 displays various information to the customer and accepts various inputs from the customer. In the full self-service mode, the customer-side display unit 205 displays a preset key (a button for ordering a product) corresponding to a product, and accepts registration of the product by operating (pressing) the preset key.

[0026] The customer-side scanner unit 206 is a scanner unit for customers, and optically reads various codes (barcodes and two-dimensional codes). The customer-side scanner unit 206 can extract code information by irradiating light onto the code and acquiring the reflected light, thereby replacing the black and white parts of the code with digital signals. The various codes include product codes attached to the product menu or the product itself, and payment codes related to code payment. Furthermore, the various codes include codes printed on various media such as gift certificates (gift certificates and coupons), membership cards, and point cards. The customer-side scanner unit 206 may be a built-in type that is incorporated into the main body of the registered settlement device 20, or may be a separate type that is later attached to the main body of the registered settlement device 20.

[0027] The card reading unit 208 is a magnetic card reader and reads information from various cards. The various cards include magnetic employee ID cards and magnetic credit cards. The card reading unit 208 also includes a card payment unit. The card payment unit performs payment using various cards. The card payment unit includes employee ID payment using employee ID cards and credit card payment using credit cards. The card reading unit 208 also includes a reader / writer unit such as an RFID (Radio Frequency Identification) unit, and can read information from a contactless charging medium to perform payment (electronic money payment). The contactless charging medium is, for example, a transportation IC card or a mobile terminal device such as a smartphone.

[0028] The change machine 209 is a cash settlement mechanism, and has an input port for banknotes and coins, and an output port for banknotes and coins. The change machine 209 calculates the amount of money inserted into the input port, calculates the change amount, which is the difference between the input amount and the purchase amount, and outputs the change from the output port. The change machine 209 faces the customer side, and accepts various operations and cash insertion from the customer. The change machine 209 has a sensor that detects banknotes and coins inserted into the input port. The sensor detects that banknotes and coins have been inserted into the input port, detects the number of banknotes by denomination, and the like. The change machine 209 can also accept the insertion of cash to be charged to a charging medium.

[0029] The store clerk display unit 210 is a touch display for the store clerk. The store clerk display unit 210 displays various information to the store clerk and accepts various inputs from the store clerk. The store clerk display unit 210 displays preset keys corresponding to products. When a preset key is pressed, the store clerk display unit 210 accepts registration of the product corresponding to the preset key.

[0030] The registration and settlement device 20 performs processing based on the code information indicated by the code read by the customer side scanner unit 206 or the store clerk side scanner unit 212. The registration and settlement device 20 determines the type of the read code (payment code, product code, store clerk code, etc.) by checking the value of a flag or the like indicated by a specific digit in the code information, the number of digits read, etc. When the registration and settlement device 20 determines that the read code is a payment code, it performs payment processing based on that code. Furthermore, when the registration and settlement device 20 determines that the read code is a product code, it performs product registration processing. Furthermore, when the registration and settlement device 20 determines that the read code is a store clerk code, it performs login processing.

[0031] The key operation unit 211 has various keys (hardware keys, buttons). The key operation unit 211 accepts various inputs from a store clerk. The key operation unit 211 includes keys corresponding to merchandise. When a store clerk presses a key, the key operation unit 211 accepts registration of the merchandise corresponding to the key. The key operation unit 211 also includes a mode switching button, and accepts switching of the operation mode.

[0032] The store clerk scanner unit 212 is a scanner unit for store clerks, and optically reads various information. For example, the store clerk scanner unit 212 optically reads barcodes attached to products and store clerk codes attached to store clerk nametags. The store clerk scanner unit 212 can also read codes printed on coupons and various cards.

[0033] The printing unit 213 prints and outputs receipts. The audio output unit 214 outputs sounds. For example, the audio output unit 214 outputs audio guidance, warning sounds, etc. The audio guidance and warning sounds include, for example, sounds related to product registration operations and payment operations. The communication unit 215 is an interface for transmitting and receiving information to and from other devices (the store controller 10, the transaction status management device 11, and other registered settlement devices 20).

[0034] The camera 216 is attached to the upper right of the customer display unit 205 as seen from the customer side. The camera 216 continuously captures moving images or still images. A CCD (charge coupled device) camera or a CMOS (complementary metal oxide semiconductor) camera is used for the camera 216. The camera 216 captures various operations performed by the customer. The various operations are operations at the time of registration and settlement. For example, the camera 216 captures the inside (items) of a shopping basket and the operation status of the customer at the time of registration. The camera 216 also captures the operation status of the customer when settlement is performed. For example, the camera 216 captures bills and coins held by the customer, the change machine 209, hand movements, etc. Note that since the users of the store are employees, etc., it is difficult for fraud such as shoplifting to occur. For this reason, the registration and settlement device 20 does not need to be provided with the camera 216, and if there is a function to switch the camera 216 on and off, the camera 216 may be always turned off.

[0035] The sign pole 220 (see FIG. 2) is equipped with a light-emitting unit such as an LED (light emitting diode) and lights up in a predetermined color and in a predetermined lighting pattern. Depending on the lighting pattern, the sign pole 220 indicates that the registered settlement device 20 is in use or reports an abnormality. In addition, the sign pole 220 is provided at the very top of the registered settlement device 20, so that even store clerks who are not near the registered settlement device 20 can recognize the lighting pattern.

[0036] (Screen transitions in full self mode) Next, an example of a screen displayed on customer side display unit 205 in the full self-service mode will be described with reference to FIGS. 4 to 6 are diagrams showing an example of screen transitions from the start of registration to the start of settlement in the full self-service mode.

[0037] Fig. 4(A) shows a standby screen 410. The standby screen 410 is a screen displayed in a standby state. The standby screen 410 includes a registration start button 411. When the registration start button 411 is pressed, the screen transitions to an employee ID card payment confirmation screen 420 in Fig. 4(B).

[0038] FIG. 4(B) shows an employee ID card payment confirmation screen 420. The employee ID card payment confirmation screen 420 includes a notification 421, an employee ID card payment start button 422a, and a normal payment start button 422b. The notification 421 shows a notification indicating whether or not to perform employee ID card payment. The employee ID card payment start button 422a is a button that accepts the start of a transaction with employee ID card payment. When the employee ID card payment start button 422a is pressed, the screen transitions to an employee ID card insertion prompt screen 430 in FIG. 4(C). The normal payment start button 422b is a button that accepts the start of a transaction with a payment other than employee ID card payment (such as cash payment). When the normal payment start button 422b is pressed, the screen transitions to a product registration start screen 610 shown in FIG. 6(A).

[0039] FIG. 4(C) shows an employee ID card insertion prompt screen 430. The employee ID card insertion prompt screen 430 is a screen that prompts the insertion of the employee ID card into the card reading unit 208. The employee ID card is a magnetic card. Employee ID card information is stored in the employee ID card. When the registration settlement device 20 acquires employee ID card information from the magnetic employee ID card, the screen transitions to a product registration start screen 510 in FIG. 5(A). The registration settlement device 20 can also acquire employee ID card information by reading the employee ID card barcode with the customer side scanner unit 206. The employee ID card barcode is a code that represents the employee ID card information in a scannable manner. However, in this embodiment, the registration settlement device 20 restricts employee ID card settlement based on the employee ID card barcode. When the registration settlement device 20 acquires employee ID card information from the employee ID card barcode, the screen transitions to an error notification screen 810 in FIG. 8(A).

[0040] The employee ID card insertion prompt screen 430 includes a "Do not possess" button 431 for accepting that the user does not have an employee ID card. When the "Do not possess" button 431 is pressed, the screen transitions to a product registration start screen 610 shown in FIG.

[0041] 5A shows a product registration start screen 510. The product registration start screen 510 includes a guide notice 511, a product registration field 512, a total display field 513, and an employee ID field 514. The guide notification 511 includes a notification to have the customer-side scanner unit 206 read the product code, and a notification to prompt input from a preset key for a product without a barcode. The product registration field 512 is an area in which the name and price of a registered product are displayed. The total display field 513 is an area in which the total number of registered products and the total price are displayed. The employee ID field 514 is an area where employee ID information acquired from a magnetic employee ID card is displayed. When a product is registered on the product registration start screen 510, the screen transitions to a post-product registration screen 520 in FIG.

[0042] Fig. 5(B) shows a post-product registration screen 520. In addition to the various displays displayed on the product registration start screen 510, the post-product registration screen 520 includes a start checkout button 521. On the post-product registration screen 520, the product registration field 512 indicates that a fried chicken bento has been registered. When one or more products are registered, the start checkout button 521 is displayed on the customer side display unit 205. When the start checkout button 521 is pressed on the post-product registration screen 520, the screen transitions to a payment type confirmation screen 530 in Fig. 5(C).

[0043] FIG. 5(C) shows a payment type confirmation screen 530. The payment type confirmation screen 530 includes a confirmation button 531. The confirmation button 531 is a button for accepting employee ID card payment. When the confirmation button 531 is pressed, the employee ID card payment is made, and when the employee ID card payment is completed, a receipt is issued. The employee ID card information is printed on the receipt. Note that the payment type confirmation screen 530 may be omitted since it is merely a confirmation screen, i.e., it is not a screen for the customer to select. In other words, when the start settlement button 521 is pressed on the post-product registration screen 520, the employee ID card payment may be made directly and a receipt may be issued.

[0044] Fig. 6(A) shows a product registration start screen 610. The product registration start screen 610 differs from the product registration start screen 510 of Fig. 5(A) in that it does not include an employee ID column 514, but is otherwise similar.

[0045] Fig. 6(B) shows a post-product registration screen 620. The post-product registration screen 620 differs from the post-product registration screen 520 in Fig. 5(B) in that it does not include the employee ID column 514, but is otherwise similar. When the payment start button 521 is pressed on the post-product registration screen 620, the screen transitions to a payment type selection screen 630 in Fig. 6(C).

[0046] FIG. 6(C) shows a payment type selection screen 630. The payment type selection screen 630 includes selection buttons 631a and 631b. Selection button 631a is a button for accepting payment by cash. Selection button 631b is a button for accepting payment by credit card. The payment type selection buttons 631 may also include buttons for accepting payment by electronic money and code payment. When selection button 631a is pressed, payment by cash (cash payment) is made, and a receipt is issued when the cash payment is completed. When selection button 631b is pressed, payment by credit card (credit card payment) is made, and a receipt is issued when the credit card payment is completed. Employee ID information is not printed on the receipt.

[0047] (Regarding transaction management information) Fig. 7A is a diagram showing an example of transaction management information stored in transaction management DB2. In Fig. 7A, the transaction management information is information that associates employee ID card information, employee associated information, and transaction information. The employee ID card information includes the fields of "employee type," "department code," "employee number," and "check digit." "Employee type" is a number that identifies whether the employee is a full-time employee or a non-regular employee. The "department code" is a number assigned to each department. An "employee number" is a number assigned to each employee. The "check digit" is a check digit based on the employee type and employee number. The employee ID information is a sequence of numbers entered in each field, that is, information indicating a number of a predetermined number of digits.

[0048] The employee-related information includes the items "name" and "department name." "Name" indicates the employee's name. The "department name" indicates the name of the department to which the employee belongs.

[0049] The transaction information includes the following fields: "date and time," "payment amount," and "product name." "Date and time" indicates the date and time (including the hour and minute) when the transaction took place. "Payment Amount" refers to the total payment amount in a transaction. "Product name" indicates the name of the product to be traded.

[0050] The transaction management DB 2 is not limited to being provided in the transaction management server 1. The transaction management DB 2 may be provided in another device. The other device may be, for example, the store controller 10, the registration and settlement device 20, or an external device other than these.

[0051] (Regarding fraudulent transactions) Here, there is a risk that a third party may obtain another person's employee ID information and perform an illegal transaction in which the payment is made by the other person. Specifically, a third party may encode another person's employee ID information to generate an employee ID barcode, and have the customer-side scanner unit 206 read the employee ID barcode, thereby performing an illegal transaction in which the payment is made by the other person's employee ID. In this embodiment, therefore, such illegal transactions are prevented. The functional configuration of the registration settlement device 20 according to this embodiment will be described below with reference to FIG. 7B.

[0052] Fig. 7B is a block diagram showing an example of the functional configuration of the registration and settlement device 20 according to this embodiment. In Fig. 7B, the registration and settlement device 20 includes a first acquisition unit 701, a second acquisition unit 702, a settlement unit 703, and a settlement control unit 704. Each functional unit is realized by the CPU 201 of the registration and settlement device 20. That is, the CPU 201 of the registration and settlement device 20 executes a data processing program to realize the function of each functional unit.

[0053] (1st acquisition part 701) The first acquisition unit 701 acquires customer information. The customer information is, for example, employee ID information (FIG. 7A). The employee ID information is stored on an employee ID card. The employee ID information is information that includes a predetermined number of digits. For this reason, a third party can generate an employee ID barcode from the employee ID information, for example, by using a barcode creation site or a barcode creation app. The employee ID barcode is displayed on a medium as a one-dimensional code, but may also be displayed on a medium as a two-dimensional code. The medium is a paper medium or a display medium of an electronic device such as a smartphone. The employee ID barcode is not displayed on the employee ID card.

[0054] The employee ID barcode is optically read by the customer-side scanner unit 206. The customer-side scanner unit 206 reads employee ID information from the employee ID barcode. When the customer-side scanner unit 206 reads the employee ID information from the employee ID barcode, it outputs the read employee ID information to the first acquisition unit 701. The first acquisition unit 701 acquires the employee ID information output from the customer-side scanner unit 206.

[0055] (Second acquisition part 702) The second acquisition unit 702 acquires employee ID information in the same manner as the first acquisition unit 701. However, the employee ID information acquired by the second acquisition unit 702 is read using a method other than the optical method. The method other than the optical method is, for example, a magnetic method. Specifically, the card reading unit 208 reads the employee ID information from a magnetic employee ID card. After reading the employee ID information from the employee ID card, the card reading unit 208 outputs the read employee ID information to the second acquisition unit 702. The second acquisition unit 702 acquires the employee ID information output from the card reading unit 208.

[0056] The method of acquiring employee ID information by the second acquisition unit 702 is not limited to the magnetic method. For example, when the registration and settlement device 20 operates in a store clerk registration mode or a maintenance mode, the second acquisition unit 702 can also acquire employee ID information by a store clerk inputting a number of items.

[0057] (Settlement department 703) The payment unit 703 performs payment. The payment includes multiple payment types. The multiple payment types include, for example, employee ID card payment, cash payment, credit card payment, electronic money payment, code payment, etc. The payment unit 703 accepts one of the multiple payment types from the customer and performs the payment.

[0058] (Payment control unit 704) The payment control unit 704 is an example of a process control means. The payment control unit 704 allows employee ID card payment based on employee ID card information acquired by the second acquisition unit 702. In other words, the payment control unit 704 allows employee ID card payment based on employee ID card information read from an employee ID card by the card reading unit 208. On the other hand, the payment control unit 704 restricts employee ID card payment based on employee ID card information acquired by the first acquisition unit 701. In other words, the payment control unit 704 restricts employee ID card payment based on an employee ID card barcode read by the customer-side scanner unit 206. Note that restricting means not allowing (prohibiting).

[0059] This makes it possible to prevent employee ID settlement based on an employee ID barcode generated based on another person's employee ID information from being made using that employee ID barcode, thereby preventing fraudulent transactions that use the employee ID of another person as payment.

[0060] (About the fact that this fraud is specific to the Full Self Mode) In modes where a store clerk is involved, such as the store clerk registration mode and maintenance mode, such fraud is unlikely to occur due to the effectiveness of the store clerk's monitoring. On the other hand, in the full self-service mode, the effectiveness of the store clerk's monitoring is reduced, making such fraud more likely to occur. For this reason, the restriction on payments based on the employee ID barcode applies to the full self-service mode (situations where no store clerk is involved). In other words, the restriction applies to situations where employee ID information is obtained based on a reading operation by a customer. In this embodiment, both the first acquisition unit 701 and the second acquisition unit 702 apply to situations where employee ID information is obtained based on a reading operation by a customer.

[0061] In the case of magnetic cards, there may be cases where the magnetic portion cannot be read properly (hereinafter referred to as "magnetic read failure"). If a magnetic read failure occurs when a store clerk is present, it is possible for the clerk to enter the employee ID information by inputting the number of units. Inputting the number of units is the direct operation of inputting the employee ID information written on the employee ID card. The registration and settlement device 20 can accept the number of units input from the clerk and enter the employee ID information. Furthermore, when a store clerk is present, there is almost no concern that the above-mentioned fraud will occur.

[0062] On the other hand, in the full self-service mode, if the input of the number of pieces is accepted, there is a concern that the above-mentioned fraudulent behavior may occur. In view of such concerns and also from the viewpoint of the difficulty of operation for customers, the input of the number of pieces is not accepted in the full self-service mode. If, for example, an employee ID card payment based on the employee ID card barcode were made possible in the case of a magnetic reading failure in the full self-service mode, the above-mentioned fraudulent behavior may occur, as described above. For this reason, even if a magnetic reading failure occurs in the full self-service mode, the registration and settlement device 20 is configured to restrict the employee ID card payment based on the employee ID card barcode and the input of the number of pieces.

[0063] Note that restrictions based on the employee ID information obtained from the employee ID barcode may be only restrictions related to employee ID payment, and other controls may not be restricted. Other controls may be, for example, controls related to the use of coupons that can be commonly applied to all employees, or controls related to viewing purchase history. In other words, the registration and settlement device 20 may be able to execute controls other than employee ID payment (such as the use of coupons) by reading the employee ID barcode.

[0064] (About the screen transition when scanning the employee ID barcode) An example of the screen transition when an employee ID barcode is read will be described with reference to Fig. 8. When an employee ID barcode is read on the employee ID insertion prompt screen 430 shown in Fig. 4(C), the screen transitions to an error notification screen 810 shown in Fig. 8(A).

[0065] Fig. 8(A) shows an error notification screen 810. The error notification screen 810 displays a notification that reading of the employee ID barcode is prohibited. The error notification screen 810 includes a confirmation button 811. When the confirmation button 811 is pressed, the screen transitions to a confirmation screen 820 in Fig. 8(B).

[0066] Fig. 8(B) shows a confirmation screen 820. The confirmation screen 820 includes a confirmation button 821. When the confirmation button 821 is pressed, the screen returns to the employee ID card payment confirmation screen 420 of Fig. 4(B). Note that either the error notification screen 810 of Fig. 8(A) or the confirmation screen 820 of Fig. 8(B) may be omitted. In other words, when either the confirmation button 811, 821 is pressed, the screen may return to the employee ID card payment confirmation screen 420 of Fig. 4(B).

[0067] (Sales data processing performed by the registration settlement device 20) Fig. 9 is a flow chart showing an example of sales data processing performed by the registration settlement device 20. As shown in Fig. 9, the registration settlement device 20 judges whether or not a transaction is to be started by pressing the registration start button 411 on the standby screen 410 (Fig. 4(A)) (step S901). The registration settlement device 20 waits until a transaction is to be started (step S901: NO), and when a transaction is to be started (step S901: YES), it displays the employee ID card payment confirmation screen 420 (Fig. 4(B)) (step S902).

[0068] Then, it is determined whether employee ID card payment (employee ID card payment start button 422a in FIG. 4(B)) has been selected (step S903). If employee ID card payment has not been selected (step S903: NO), in other words, if normal payment start button 422b (FIG. 4(B)) has been pressed, the registration settlement device 20 proceeds to step S910. On the other hand, if employee ID card payment has been selected (step S903: YES), the registration settlement device 20 displays the employee ID card insertion prompt screen 430 (FIG. 4(C)) (step S904).

[0069] Then, the registration and settlement device 20 judges whether the employee ID information has been acquired (step S905). If the employee ID information has been acquired (step S905: YES), the registration and settlement device 20 proceeds to step S907. On the other hand, if the employee ID information has not been acquired (step S905: NO), the registration and settlement device 20 judges whether the "No employee ID" button 431 has been selected (step S906).

[0070] If the employee ID card is not possessed (the "does not possess" button 431) is selected (step S906: YES), the registration settlement apparatus 20 proceeds to step S910. On the other hand, if the employee ID card is not possessed (the "does not possess" button 431) is not selected (step S906: NO), the registration settlement apparatus 20 returns to step S905.

[0071] In step S907, the registration and settlement device 20 judges whether the employee ID information is acquired based on reading the employee ID barcode (step S907). If the employee ID information is acquired based on reading the employee ID barcode (step S907: YES), the registration and settlement device 20 displays the error notification screen 810 (FIG. 8(A)) and the confirmation screen (FIG. 8(B)) (step S908), and returns to step S902. The registration and settlement device 20 discards the acquired employee ID information without storing it.

[0072] On the other hand, if the acquisition of the employee ID information is not based on reading the employee ID barcode (step S907: NO), in other words, if the acquisition of the employee ID information is based on reading the magnetic employee ID card, the registration and settlement device 20 stores the employee ID information and turns on the employee ID settlement flag to perform employee ID settlement (step S909), and proceeds to step S910.

[0073] Then, the registration and settlement device 20 performs a product registration process (step S910). In the product registration process, the customer-side scanner unit 206 reads a product code, and the customer-side display unit 205 accepts an operation of a preset key (product registration button), whereby the product is registered, and the registered product is displayed on the customer-side display unit 205.

[0074] The registration settlement device 20 then determines whether settlement has started by pressing the settlement start button 521 (FIGS. 5(B) and 6(B)) (step S911). If settlement has not started (step S911: NO), the registration settlement device 20 returns to step S910. On the other hand, if settlement has started (step S911: YES), the registration settlement device 20 determines whether the employee ID settlement flag is ON (step S912).

[0075] If the employee ID payment flag is ON (step S912: YES), that is, if employee ID information has been obtained based on reading the employee ID information on the magnetic card, the registration settlement device 20 displays the payment type confirmation screen 530 (FIG. 5(C)) (step S913). Then, the registration settlement device 20 accepts pressing of the confirmation button 531 and performs settlement processing using employee ID payment (step S914). When the settlement processing is completed, the registration settlement device 20 turns the employee ID payment flag OFF (step S915) and ends the series of processes.

[0076] In step S912, if the employee ID settlement flag is OFF (step S912: NO), that is, if it is normal settlement, the registration settlement device 20 displays the payment type selection screen 630 (FIG. 6(C)) (step S916). Then, the registration settlement device 20 accepts the pressing of the selection buttons 631a, 631b, and performs settlement processing by the payment type (normal settlement) indicated by the accepted button (step S917), and ends the series of processes.

[0077] As described above, the registration and settlement device 20 according to this embodiment allows employee ID card payments based on reading a magnetic card, and restricts employee ID card payments based on reading an employee ID card barcode. This makes it possible to prevent employee ID card payments based on another person's employee ID card barcode from being made, even if that person obtains another person's employee ID card information and generates an employee ID card barcode. This makes it possible to prevent fraudulent transactions using another person's employee ID card information. Therefore, this embodiment makes it possible to support sound transactions.

[0078] In this embodiment, the first acquisition unit 701 and the second acquisition unit 702 acquire employee ID information based on the customer's reading operation. This makes it possible to effectively prevent fraudulent acts that are likely to occur in the full self-service mode, since the customer-side scanner unit 206 and the card reading unit 208 are used by the customer in the full self-service mode.

[0079] Furthermore, in this embodiment, the second acquisition unit 702 acquires employee ID information read by a magnetic method. This makes it possible to permit employee ID settlement based on employee ID information read from a magnetic employee ID card. It is not easy to forge a magnetic employee ID card from employee ID information. In other words, it is not easy to forge a magnetic employee ID card and commit the above-mentioned fraud. Therefore, by permitting employee ID settlement based on a magnetic employee ID card, it is possible to improve the deterrent effect against the above-mentioned fraud.

[0080] In this embodiment, the employee ID card payment is a deferred payment. This makes it possible to effectively prevent fraud in deferred payment, which is particularly likely to occur in deferred payment, since victims cannot immediately notice that fraud has occurred in deferred payment.

[0081] (Modification of the embodiment) Next, modified examples of the embodiment will be described. In the following modified examples, the contents described in the above-mentioned embodiment will be omitted as appropriate. In addition, the following modified examples and the above-mentioned embodiment can be combined with each other.

[0082] (Variation 1) First, a description will be given of Modification 1. In the above-described embodiment, an example has been described in which the selection of employee ID card payment is accepted first, and then product registration is performed. In Modification 1, an example will be described in which product registration is performed first, and then the selection of employee ID card payment (selection of payment type) is accepted.

[0083] Fig. 10 is a flowchart showing an example of sales data processing performed by the registration settlement device 20 according to the first modified example. As shown in Fig. 10, the registration settlement device 20 judges whether or not a transaction is to be started by pressing the registration start button 411 on the standby screen 410 (Fig. 4(A)) (step S1001). The registration settlement device 20 waits until a transaction is to be started (step S1001: NO), and when a transaction is to be started (step S1001: YES), it performs a product registration process (step S1002).

[0084] The registration settlement device 20 then determines whether settlement has started by pressing the settlement start button 521 (FIG. 6(B)) (step S1003). If settlement has not started (step S1003: NO), the registration settlement device 20 returns to step S1002. On the other hand, if settlement has started (step S1003: YES), the registration settlement device 20 displays a payment type selection screen (step S1004). This payment type selection screen is a screen that accepts the selection of, for example, either employee ID card payment or normal payment (cash payment or credit card payment).

[0085] The registration settlement device 20 judges whether or not employee ID card payment has been selected on the payment type confirmation screen (step S1005). If employee ID card payment has not been selected (step S1005: NO), that is, if normal payment (cash payment or credit card payment) has been selected, the registration settlement device 20 performs settlement processing according to the accepted payment type (normal payment) (step S1006), and ends the series of processes.

[0086] On the other hand, if employee ID card payment is selected in step S1005 (step S1005: YES), the registration and settlement apparatus 20 displays the employee ID card insertion prompt screen 430 (FIG. 4(C)) (step S1007).

[0087] Then, the registration and settlement device 20 judges whether the employee ID information has been acquired (step S1008). If the employee ID information has not been acquired (step S1008: NO), the registration and settlement device 20 judges whether the employee ID not possessed button 431 has been selected (step S1009).

[0088] If the employee ID card is not possessed (the "does not possess" button 431) is selected (step S1009: YES), the registration settlement device 20 returns to step S1004. On the other hand, if the employee ID card is not possessed (the "does not possess" button 431) is not selected (step S1009: NO), the registration settlement device 20 returns to step S1008.

[0089] In step S1008, if the employee ID information is acquired (step S1008: YES), the registration settlement device 20 judges whether the acquisition of the employee ID information is based on reading the employee ID barcode (step S1010). If the acquisition of the employee ID information is based on reading the employee ID barcode (step S1010: YES), the registration settlement device 20 displays the error notification screen 810 (FIG. 8(A)) and the confirmation screen (FIG. 8(B)) (step S1011), and returns to step S1004. Note that the registration settlement device 20 discards the acquired employee ID information without storing it.

[0090] On the other hand, in step S1010, if the acquisition of the employee ID information is not based on reading the employee ID barcode (step S1010: NO), in other words, if the acquisition of the employee ID information is based on reading the magnetic employee ID card, the registration and settlement device 20 stores the employee ID information and performs settlement processing using employee ID payment (step S1012), and ends the series of processes.

[0091] Even if product registration is performed first and then employee ID card payment selection is accepted as in variant 1, it is possible to permit employee ID card payment based on reading the magnetic employee ID card and restrict employee ID card payment based on reading the employee ID barcode. This makes it possible to prevent employee ID card payment based on the employee ID barcode from being made even if another person's employee ID information is obtained and an employee ID barcode is generated. This makes it possible to prevent fraudulent transactions using another person's employee ID information. Thus, variant 1 makes it possible to support sound transactions.

[0092] (Variation 2) Next, a description will be given of Modification 2. In the above-described embodiment, an example has been described in which employee ID information is acquired before product registration. In Modification 2, an example will be described in which employee ID information can be acquired during product registration.

[0093] (Functional configuration of the registration settlement device 20 according to the second modification) In the second modification, the customer side scanner unit 206 reads various codes when registering a product. The various codes include a product code attached to the product and an employee ID barcode. The customer side scanner unit 206 outputs information indicated by the read various codes to the first acquisition unit 701.

[0094] The product code is read by the customer-side scanner unit 206 using an optical method. The customer-side scanner unit 206 reads product information from the product code. After reading the product information from the product code, the customer-side scanner unit 206 outputs the read product information to the first acquisition unit 701. The first acquisition unit 701 acquires the product information output from the customer-side scanner unit 206. After acquiring the product information, the first acquisition unit 701 causes a registration unit (not shown) to register the product. In addition, in product registration, the first acquisition unit 701 can acquire employee ID information by having the employee ID barcode read by the customer-side scanner unit 206.

[0095] In the second modification, the card reading unit 208 can read employee ID information from a magnetic employee ID card during product registration. The card reading unit 208 outputs the employee ID information that it has read to the second acquisition unit 702. This allows the second acquisition unit 702 to acquire employee ID information in a magnetic format during product registration.

[0096] The payment control unit 704 allows payment based on the employee ID information acquired by the second acquisition unit 702 during product registration. On the other hand, the payment control unit 704 restricts payment based on the employee ID information acquired by the first acquisition unit 701 during product registration. Specifically, the payment control unit 704 discards the employee ID information acquired by the first acquisition unit 701 during product registration, and does not allow payment based on that employee ID information.

[0097] (An example of sales data processing performed by the registration settlement device 20 according to the second modification) 11 and 12 are flowcharts showing an example of sales data processing performed by the registration settlement device 20 according to the modified example 2. As shown in Fig. 11, the registration settlement device 20 judges whether or not a transaction is to be started by pressing the registration start button 411 on the standby screen 410 (Fig. 4(A)) (step S1101). The registration settlement device 20 waits until a transaction is to be started (step S1101: NO), and when a transaction is to be started (step S1101: YES), enables product registration processing.

[0098] Specifically, the registration settlement device 20 determines whether the product code attached to the product has been read by the customer side scanner unit 206 (step S1102). If the product code attached to the product cannot be read (step S1102: NO), the registration settlement device 20 proceeds to step S1104. On the other hand, if the product code attached to the product has been read (step S1102: YES), the registration settlement device 20 registers the product and displays the registered product on the customer side display unit 205 (post-product registration screen 620 in FIG. 6(B)) (step S1103).

[0099] Then, the registration and settlement device 20 judges whether or not the employee ID information is acquired during the execution of the product registration process (step S1104). If the employee ID information is not acquired (step S1104: NO), the registration and settlement device 20 proceeds to step S1108.

[0100] On the other hand, if the employee ID information has been acquired (step S1104: YES), the registration and settlement device 20 judges whether the acquisition of the employee ID information is based on reading the employee ID barcode (step S1105). If the acquisition of the employee ID information is based on reading the employee ID barcode (step S1105: YES), the registration and settlement device 20 displays the error notification screen 810 (FIG. 8(A)) and the confirmation screen (FIG. 8(B)) (step S1106), and returns to step S1102. The registration and settlement device 20 discards the acquired employee ID information without storing it.

[0101] On the other hand, if the employee ID information is not acquired based on reading the employee ID barcode (step S1105: NO), in other words, if the employee ID information is acquired based on reading the magnetic employee ID card, the registration and settlement device 20 stores the employee ID information (step S1107).

[0102] The registration settlement device 20 then determines whether or not settlement has started by pressing the settlement start button 521 (FIG. 6(B)) (step S1108). If settlement has not started (step S1108: NO), the registration settlement device 20 returns to step S1102. On the other hand, if settlement has started (step S1108: YES), the registration settlement device 20 displays a payment type selection screen (step S1201). This payment type selection screen is a screen that accepts the selection of, for example, either employee ID card payment or normal payment (cash payment or credit card payment).

[0103] The registration settlement device 20 judges whether or not employee ID card payment has been selected on the payment type selection screen (step S1202). If employee ID card payment has not been selected (step S1202: NO), that is, if normal payment (cash payment or credit card payment) has been selected, the registration settlement device 20 performs settlement processing according to the accepted payment type (normal payment) (step S1203), and ends the series of processes.

[0104] On the other hand, if employee ID card payment is selected in step S1202 (step S1202: YES), it is determined whether the employee ID card information acquired during the registration process is stored (step S1204). If the employee ID card information is stored (step S1204: YES), the registration and settlement device 20 performs settlement processing using the employee ID card payment (step S1205) and ends the series of processes.

[0105] On the other hand, in step S1204, if the employee ID information is not stored (step S1204: NO), the registration and settlement apparatus 20 displays the employee ID insertion prompt screen 430 (FIG. 4(C)) (step S1206).

[0106] Then, the registration and settlement device 20 judges whether the employee ID information has been acquired (step S1207). If the employee ID information has not been acquired (step S1207: NO), the registration and settlement device 20 judges whether the employee ID not possessed button 431 has been selected (step S1208).

[0107] If the employee ID card is not possessed (the "does not possess" button 431) is selected (step S1208: YES), the registration settlement apparatus 20 returns to step S1201. On the other hand, if the employee ID card is not possessed (the "does not possess" button 431) is not selected (step S1208: NO), the registration settlement apparatus 20 returns to step S1207.

[0108] In step S1207, if the employee ID information is acquired (step S1207: YES), the registration and settlement device 20 judges whether the acquisition of the employee ID information is based on reading the employee ID barcode (step S1209). If the acquisition of the employee ID information is based on reading the employee ID barcode (step S1209: YES), the registration and settlement device 20 displays the error notification screen 810 (FIG. 8(A)) and the confirmation screen (FIG. 8(B)) (step S1210), and returns to step S1201. Note that the registration and settlement device 20 discards the acquired employee ID information without storing it.

[0109] In step S1209, if the acquisition of the employee ID information is not based on reading the employee ID barcode (step S1209: NO), in other words, if the acquisition of the employee ID information is based on reading the magnetic employee ID card, the registration and settlement device 20 performs settlement processing using employee ID payment (step S1205) and terminates the series of processes.

[0110] Note that there are cases where the processes of step S1201 (displaying a payment type confirmation screen) and step S1202 (determining whether employee ID card payment has been selected) may be omitted. Specifically, when settlement has started (step S1108: YES), it is determined whether the employee ID card information acquired during the registration process has been stored, and if the determination indicates YES, the processes of step S1201 and step S1202 may be omitted and the process may proceed directly to step S1205 (settlement process using employee ID card).

[0111] As in the second modification, since it is possible to obtain employee ID information based on a magnetic employee ID card during product registration, it is possible to obtain the employee ID information and perform employee ID payment without prompting the customer to insert the employee ID card. Even if employee ID information based on an employee ID barcode is obtained during product registration, the employee ID information is discarded, so payment based on the employee ID barcode can be restricted. This enables quick transactions while preventing employee ID payment based on the employee ID barcode from being performed even if another person's employee ID information is obtained and an employee ID barcode is generated. This makes it possible to prevent fraudulent transactions using another person's employee ID information. Therefore, according to the second modification, it is possible to support sound transactions.

[0112] (Variation 3) Next, a description will be given of Modification 3. In the above-described embodiment, an example has been described in which card reading unit 208 is a magnetic card reader. In Modification 3, instead of or in addition to such an example, an example will be described in which card reading unit 208 is a non-contact card reader.

[0113] In the third modification, the card reading unit 208 includes a reader / writer unit such as an RFID, and reads information from various cards in a non-contact manner. The various cards include a non-contact employee ID card (IC card) equipped with an RFID tag. The employee ID card stores employee ID information. The second acquiring unit 702 acquires the employee ID information read by the wireless tag method.

[0114] FIG. 13 is a diagram showing an example of an employee ID card presentation prompting screen according to the third modified example. In FIG. 13, the employee ID card presentation prompting screen 1300 is a screen displayed in place of or in addition to the employee ID card insertion prompting screen 430 (FIG. 4(C)). The employee ID card presentation prompting screen 1300 is a screen that prompts the user to hold the employee ID card over the non-contact card reading unit 208. When the registration settlement device 20 acquires employee ID card information from a non-contact employee ID card, the registration settlement device 20 transitions to the product registration start screen 510 shown in FIG. 5(A). When the customer side scanner unit 206 acquires employee ID card information by reading the employee ID card barcode, the registration settlement device 20 transitions to the error notification screen 810 shown in FIG. 8(A). When the not possessed button 431 is pressed, the registration settlement device 20 transitions to the product registration start screen 610 shown in FIG. 6(A).

[0115] Alternatively, either the magnetic employee ID card or the contactless employee ID card may be selectable. In this case, the registration and settlement device 20 displays the employee ID card insertion prompt screen 430 (FIG. 4(C)) when it receives the selection of the magnetic employee ID card from the customer, and displays the employee ID card presentation prompt screen 1300 when it receives the selection of the contactless employee ID card.

[0116] In the third modification, the second acquisition unit 702 acquires employee ID information read in a contactless manner. This makes it possible to permit employee ID settlement based on employee ID information read from a contactless employee ID card. It is not easy to forge a contactless employee ID card from the employee ID card information. In other words, it is not easy to forge a contactless employee ID card and commit the above-mentioned fraud. Therefore, by permitting employee ID settlement based on a contactless employee ID card, it is possible to improve the deterrent effect against the above-mentioned fraud.

[0117] (Variation 4) Next, Variation 4 will be described. In the above embodiment, an example (FIG. 6(C)) was described in which the selection of the payment type is accepted after product registration when payment is not made with an employee ID card. Instead of this example, Variation 4 will describe an example in which the selection of the payment type is accepted before product registration when payment is not made with an employee ID card.

[0118] Specifically, the payment type selection screen 630 in Fig. 6(C) may be displayed when the normal payment start button 422b is pressed on the employee ID card payment confirmation screen 420 in Fig. 4(B) or when the not possessed button 431 is pressed on the employee ID card insertion prompt screen 430 in Fig. 4(C). Then, when a payment type is selected on the payment type selection screen 630, the screen may transition to the product registration start screen 610 in Fig. 6(A).

[0119] (Variation 5) Next, Modification 5 will be described. In Modification 5, an example of further improving the security of employee ID card payments will be described. In Modification 5, authentication is required for employee ID card payments. Specifically, the registered settlement device 20 accepts authentication information from a customer in employee ID card payments. The authentication information is various input information such as a PIN number, biometric information (fingerprint information, etc.), and a temporary password. The temporary password may be transmitted to a terminal device (smartphone, etc.) registered in advance, for example. Authentication may also be performed when the transaction is a predetermined amount or more (for example, 10,000 yen or more). In other words, authentication may not be required for transactions less than the predetermined amount. Modification 5 can further improve the security of employee ID card payments.

[0120] (Variation 6) Next, Variation 6 will be described. In the above embodiment, an example in which the registration and settlement device 20 is a fully self-service cash register will be described. In Variation 6, an example in which the registration and settlement device 20 is a ticket vending machine will be described. The ticket vending machine does not include, for example, the clerk-side display unit 210 and the clerk-side scanner unit 212 of the configuration shown in FIG. 2. The ticket vending machine mainly registers products by pressing a product registration button such as a preset key. In addition, the customer-side scanner unit 206 is mainly used to read codes written on coupons, service vouchers, and the like.

[0121] For example, the ticket vending machine allows employee ID card payments based on reading a magnetic card, but restricts employee ID card payments based on reading an employee ID card barcode. This makes it possible to prevent fraudulent transactions using other people's employee ID card information, even at the ticket vending machine.

[0122] (Variation 7) Next, a description will be given of Modification 7. In the above-described embodiment, an example has been described in which the customer information acquired by the first acquisition unit 701 and the second acquisition unit 702 is used as employee ID information. In Modification 7, an example will be described in which the customer information is used as membership information.

[0123] The member information is stored on the member card. The member information is information that includes a predetermined number of digits. Therefore, a third party can generate a member barcode from the member information using, for example, a barcode creation site or a barcode creation app. The member barcode is displayed on a medium as a barcode or two-dimensional code. The medium can be a paper medium or a display medium of an electronic device such as a smartphone. Note that the member barcode (barcode) is not displayed on the member card.

[0124] The member barcode is optically read by customer-side scanner unit 206. Customer-side scanner unit 206 reads member information from the member barcode. When customer-side scanner unit 206 reads the member information from the member barcode, it outputs the read member information to first acquisition unit 701. First acquisition unit 701 acquires the member information output from customer-side scanner unit 206.

[0125] The second acquisition unit 702 acquires member information in the same manner as the first acquisition unit 701. However, the member information acquired by the second acquisition unit 702 is read by a method (magnetic or non-contact) different from the optical method. The card reading unit 208 reads the member information from, for example, a magnetic or non-contact member card. After reading the member information from the member card, the card reading unit 208 outputs the read member information to the second acquisition unit 702. The second acquisition unit 702 acquires the member information output from the card reading unit 208.

[0126] The settlement unit 703 performs settlement. The settlement is performed by applying a discount according to the number of points included in the member information. For example, points are returned at a rate of 1 yen per point.

[0127] The payment control unit 704 allows payment (payment with discount applied) based on the membership information acquired by the second acquisition unit 702. In other words, the payment control unit 704 allows a discount based on the membership information read from the membership card by the card reading unit 208. On the other hand, the payment control unit 704 restricts a discount based on the membership information acquired by the first acquisition unit 701. In other words, the payment control unit 704 restricts a discount based on the membership barcode read by the customer-side scanner unit 206.

[0128] This means that even if a membership barcode is generated by encoding someone else's membership information, it is not possible to apply a discount based on that membership barcode, thereby preventing fraudulent transactions such as applying someone else's points.

[0129] (Variation 8) Next, an eighth modified example will be described. In some stores for employees, products are prepared at an employee discount (employee-priced products). Products for employees are prepared in limited quantities for each employee, for example. Therefore, each employee can purchase products at the employee discount within the range of the prepared quantities.

[0130] Here, there is a risk that if a third party obtains another person's employee ID information, the third party may illegally purchase employee-priced products prepared for that person at an employee discount. Specifically, if a third party encodes another person's employee ID information to generate an employee ID barcode, and has the customer-side scanner unit 206 read the employee ID barcode, the third party may illegally purchase employee-priced products prepared for that person at an employee discount. Therefore, in the eighth modification, such illegal transactions are prevented.

[0131] In the above-described embodiment, the payment control unit 704 is an example of the process control means. In the eighth modification, the discount control unit is an example of the process control means. The discount control unit allows or restricts an employee discount. Specifically, the discount control unit allows an employee discount based on the employee ID information acquired by the second acquisition unit 702. In other words, the discount control unit allows an employee discount based on the employee ID information read from the employee ID card by the card reading unit 208. On the other hand, the discount control unit restricts an employee discount based on the employee ID information acquired by the first acquisition unit 701. In other words, the discount control unit restricts an employee discount based on the employee ID barcode read by the customer-side scanner unit 206.

[0132] This makes it possible to prevent an employee discount from being applied to an employee ID barcode generated based on someone else's employee ID information, thereby preventing fraudulent transactions using the employee ID of another person.

[0133] (Variation 9) Next, a modification 9 will be described. In the modification 9, an example will be described in which points are accumulated on an employee ID card (or a membership card) and the accumulated points can be used. Note that, although the following description will be given assuming that points are affixed to an employee ID card (employee ID information), the same applies to the case in which points are affixed to a membership card (membership information).

[0134] In the above-described embodiment, an example of the process control means is the payment control unit 704. In the ninth modification, an example of the process control means is the points control unit. The points control unit allows or restricts the accumulation and use of points.

[0135] (If you want to collect points) When points are accumulated, there is almost no benefit to the third party even if the third party commits fraud. For this reason, when points are accumulated, the point control unit allows points to be accumulated regardless of whether the employee ID information is acquired by the first acquisition unit 701 or the second acquisition unit 702. In other words, the discount control unit allows points to be accumulated based on the employee ID information read from the employee ID card by the card reading unit 208, and also allows points to be accumulated based on the employee ID barcode read by the customer-side scanner unit 206.

[0136] (When using points) When points are used, there is a risk that they may be used fraudulently by a third party. For this reason, when points are used, the point control unit allows the use of points based on the employee ID information acquired by the second acquisition unit 702. In other words, the discount control unit allows the use of points based on the employee ID information read from the employee ID card by the card reading unit 208. On the other hand, the discount control unit restricts the use of points based on the employee ID information acquired by the first acquisition unit 701. In other words, the discount control unit restricts the use of points based on the employee ID barcode read by the customer-side scanner unit 206.

[0137] This makes it possible to prevent points from being used based on an employee ID barcode generated based on someone else's employee ID information, thereby preventing fraudulent transactions that attempt to use someone else's points.

[0138] (Variation 10) Next, a description will be given of Modification 10. In Modification 10, since there is a risk of fraud occurring when an employee ID barcode is read, an example will be described in which a warning is issued when the employee ID barcode is read.

[0139] In the tenth modification, the sales data processing system St includes a warning unit. The warning unit issues a warning when processing is performed based on the employee ID information acquired by the first acquisition unit 701. The warning includes a display mode, a sound mode, and a light emission mode. The warning unit is provided, for example, in the transaction status management device 11, the registration and settlement device 20, or a clerk terminal (wearable terminal) carried by the clerk. For example, the warning unit provided in the registration and settlement device 20 issues a warning by causing the sound output unit 214 to output a warning sound and by causing the sign pole 220 to emit light in a predetermined lighting mode.

[0140] According to the tenth modification, a warning is issued when the employee ID barcode is read, making it possible to more effectively prevent fraudulent transactions.

[0141] The embodiments will be summarized below. [Name of invention] Data processing device and program [Technical Field] The present invention relates to a data processing device and a program. [Background technology] Cash registers have traditionally been used in restaurants, convenience stores, and other types of stores. In recent years, self-service registers, which allow customers to register products and settle payments, have become widespread (see, for example, Patent Document 1). In various types of stores, cash registers are capable of reading personal information of customers to carry out transactions. For example, personal information would be employee ID information identifying employees in a store for employees, such as a staff cafeteria, or membership information identifying member customers in a regular store for general customers. [Prior art document] [Patent documents] [Patent Document 1] JP 2020-205023 A [Summary of the Invention] [Problem to be solved by the invention] However, in the conventional technology, there was a risk that a third party could obtain personal information of another person and conduct an illegal transaction that would cause a disadvantage to that person. For example, a fraudulent transaction would involve generating a barcode that encodes the personal information of another person and having the barcode read by a cash register, thereby using the personal information. Therefore, there was a problem in that sound transactions were not always conducted in the conventional technology. The present invention has been made in view of the above circumstances, and has an object to provide a technique capable of supporting sound transactions. [Means for solving the problem]

[0142] (1) In order to solve the above-mentioned problems, a data processing device according to one embodiment of the present invention is a data processing device comprising: a first acquisition means for acquiring customer information by optically reading a code displayed on a medium; a second acquisition means for acquiring customer information by reading the code by a method different from the optical method; a payment means for making a payment; and a processing control means for allowing payment based on the customer information acquired by the second acquisition means and restricting processing based on the customer information acquired by the first acquisition means. According to the above configuration, even if another person's employee ID information is obtained and an employee ID barcode is generated, it is possible to prevent employee ID settlement based on the employee ID barcode. Therefore, it is possible to prevent fraudulent transactions using another person's employee ID information. Therefore, according to this embodiment, it is possible to support sound transactions.

[0143] (2) In the above configuration (1), the first acquisition means and the second acquisition means may acquire customer information based on a reading operation by the customer. According to the above configuration, in the full self-service mode, the customer-side scanner unit 206 and the card reading unit 208 are used by the customer, and therefore, although the above-mentioned fraud is likely to occur in the full self-service mode, the fraud can be effectively prevented.

[0144] (3) In the above configuration (1) or (2), the second acquisition means may acquire customer information read by a magnetic method. According to the above configuration, it is possible to permit employee ID settlement based on employee ID information read from a magnetic employee ID card. It is not easy to forge a magnetic employee ID card from the employee ID information. In other words, it is not easy to forge a magnetic employee ID card and commit the above-mentioned fraud. Therefore, by permitting employee ID settlement based on a magnetic employee ID card, it is possible to improve the deterrent effect against the above-mentioned fraud.

[0145] (4) In the above configuration (1) or (2), the second acquisition means may acquire customer information read by a wireless tag method. According to the above configuration, it is possible to permit employee ID settlement based on employee ID information read from a contactless employee ID card. It is not easy to forge a contactless employee ID card from the employee ID card information. In other words, it is not easy to forge a contactless employee ID card and commit the above-mentioned fraud. Therefore, by permitting employee ID settlement based on a contactless employee ID card, it is possible to improve the deterrent effect against the above-mentioned fraud.

[0146] (5) In the configuration of (1) or (2) above, the processing may be postpaid settlement. According to the above configuration, in a deferred payment system, the victim cannot immediately notice that the fraud has occurred, and therefore the fraud is particularly likely to occur in deferred payment, but the fraud in deferred payment can be effectively prevented.

[0147] (6) In the configuration of (1) or (2) above, the first acquisition means may be capable of acquiring product information by reading a product code attached to a product using the optical method, and may be capable of acquiring customer information by reading the code using the optical method when registering the product, and the second acquisition means may be capable of acquiring customer information by reading the code using the different method when registering the product. According to the above configuration, since it is possible to obtain employee ID information based on a magnetic employee ID card during product registration, it is possible to obtain the employee ID information and perform employee ID payment without prompting the customer to insert the employee ID card. Furthermore, even if employee ID information based on an employee ID barcode is obtained during product registration, the employee ID information is discarded, so payment based on the employee ID barcode can be restricted. This enables quick transactions while preventing employee ID payment based on the employee ID barcode from being performed even if another person's employee ID information is obtained and an employee ID barcode is generated. Therefore, it is possible to prevent fraudulent transactions using another person's employee ID information. Therefore, according to the second modification, it is possible to support sound transactions.

[0148] (7) In order to solve the above-mentioned problems, another aspect of the present invention is a program that causes a data processing device to function as a first acquisition means for acquiring customer information by optically reading a code displayed on a medium, a second acquisition means for acquiring customer information by reading the code by a method different from the optical method, a payment means for making a payment, and a processing control means for allowing payment based on the customer information acquired by the second acquisition means and restricting processing based on the customer information acquired by the first acquisition means. According to the above configuration, even if another person's employee ID information is obtained and an employee ID barcode is generated, it is possible to prevent employee ID settlement based on the employee ID barcode. Therefore, it is possible to prevent fraudulent transactions using another person's employee ID information. Therefore, according to this embodiment, it is possible to support sound transactions.

[0149] In addition, all or part of each function (input / output, memory, processing (including judgment, etc.)) of the registered settlement device 20 described above may be realized in a device other than the device described as the entity that executes the function.

[0150] For example, the store controller 10, the transaction management server 1, or a cloud server (not shown) may allow employee ID card payments based on reading a magnetic card and restrict processing based on reading an employee ID card barcode, instead of the registration and settlement device 20. Specifically, for example, another device may execute the processing (see FIG. 9) performed by the registration and settlement device 20, instead of the registration and settlement device 20.

[0151] In the above description, the registered settlement device 20 is described as having a first acquisition unit 701, a second acquisition unit 702, a settlement unit 703, and a settlement control unit 704. However, all or a part of these functional units may be provided in another computer device. For example, all or a part of these functional units may be provided in the transaction management server 1, the store controller 10, or a computer device other than these. Furthermore, the number of computer devices on which these functional units are provided is not limited to multiple, and may be one. For example, one computer device may have all of these functional units.

[0152] In relation to the above, the registration and settlement device 20 may function as a so-called thin client specialized in the input / output interface portion with respect to the control of employee ID card settlement. In other words, the registration and settlement device 20 may accept various inputs (operation by an operator, detection by a device such as a scanner), transmit the input information (operation information, scan information, etc.) to a cloud server, receive the processing results of the cloud server based on the input information (update screen information, device control information, etc.), and perform various outputs (display on a display unit, control of a device).

[0153] The program for implementing the sales data processing system St and the registration and settlement device 20 described above may be recorded in a computer-readable recording medium, and the program may be read into a computer system and executed. The term "computer system" as used herein includes hardware such as an OS and peripheral devices. The term "computer-readable recording medium" refers to a portable medium such as a USB (Universal Serial Bus) flash memory, an SSD (Solid State Drive), a flexible disk, an optical magnetic disk, a ROM, a CD-ROM, and a storage device such as a hard disk built into a computer system. The term "computer-readable recording medium" also refers to a storage device that holds a program for a certain period of time, such as a volatile memory (RAM) inside a computer system that becomes a server or a client when a program is transmitted via a network such as the Internet or a communication line such as a telephone line. The program may be transmitted from a computer system that stores the program in a storage device, etc., to another computer system via a transmission medium or by a transmission wave in the transmission medium. The "transmission medium" that transmits the program refers to a medium that has a function of transmitting information, such as a network (communication network) such as the Internet or a communication line (communication line) such as a telephone line. The program may be for implementing some of the functions described above, or may be a so-called differential file (differential program) that can implement the functions described above in combination with a program already recorded in the computer system. [Explanation of symbols]

[0154] St...sales data processing system, 1...transaction management server, 2...transaction management DB, 10...store controller, 11...transaction status management device, 20...registration and settlement device, 201...CPU, 202...ROM, 203...RAM, 204...hard disk, 205...customer side display unit, 206...customer side scanner unit, 208...card reading unit, 209...change machine, 213...printing unit, 214...audio output unit, 215...communication unit, 701...first acquisition unit, 702...second acquisition unit, 703...settlement unit, 704...settlement control unit

Claims

1. a first acquisition means for acquiring customer information by optically reading a code displayed on the medium; A second acquisition means for acquiring customer information by reading the customer information in a manner different from the optical method; A payment method for making a payment; a process control means for permitting a process based on the customer information acquired by the second acquisition means and restricting the process based on the customer information acquired by the first acquisition means; A data processing device comprising:

2. the first acquisition means and the second acquisition means acquire customer information based on a reading operation by the customer; 2. The data processing device according to claim 1.

3. The second acquisition means acquires customer information read by a magnetic method.

3. The data processing device according to claim 1, wherein the first and second inputs are connected to the first and second inputs.

4. The second acquisition means acquires customer information read by a wireless tag method.

3. The data processing device according to claim 1, wherein the first and second inputs are connected to the first and second inputs.

5. The process is a deferred payment process.

3. The data processing device according to claim 1, wherein the first and second inputs are connected to the first and second inputs.

6. the first acquisition means is capable of acquiring product information by reading a product code attached to a product using the optical method, and is also capable of acquiring customer information in registering the product by reading the code using the optical method; the second acquisition means is capable of acquiring customer information by being read in the different manner during product registration; 3. The data processing device according to claim 1, wherein the first and second inputs are connected to the first and second inputs.

7. A computer in the data processing device; a first acquisition means for acquiring customer information by optically reading a code displayed on the medium; A second acquisition means for acquiring customer information by reading the customer information in a manner different from the optical method; The payment method through which the payment is made; a process control means for permitting a process based on the customer information acquired by the second acquisition means and restricting the process based on the customer information acquired by the first acquisition means; A program characterized by causing the program to function as a

Images