JP7732485B2 - Payment system, method, and recording medium - Google Patents

Description

The present invention relates to a payment system, method, and recording medium for payment of goods.

One example of this type of system is a payment system in which the restaurant bill is settled by reading an ID tag attached to each dish (see, for example, Patent Document 1). Another known system is an identity authentication payment system in which a user charges a desired amount to a charging machine by linking it to their iris, and the iris is used to authenticate payment for purchased items (see, for example, Patent Document 2).

Patent No. 3910247 Japanese Patent Application Laid-Open No. 2004-227134

However, the personal authentication payment system of Patent Document 2 requires users to enter a password in addition to iris authentication, and is also required to touch the screen of the payment terminal to indicate consent to the payment. Since the payment cannot be completed without the user's payment operation, there are technical issues with the system, such as a lack of convenience and hygiene.

The objective of the present invention is to provide a payment system, method, and recording medium that realizes highly safe payment processing with improved convenience and hygiene.

One aspect of the payment system of the present invention comprises a product identification information acquisition means for acquiring product identification information of a product purchased by a user at a cafeteria, a user authentication means for authenticating the user using the user's face or iris, a product linking means for linking the authenticated user with the product identification information, and a payment means for making a payment for the authenticated user to purchase the product after the product identification information is no longer recognized by the product identification information acquisition means.

One aspect of the method of the present invention is a payment system having a product identification information acquisition means for acquiring product identification information of a product purchased by a user at a restaurant, and a user authentication means for authenticating the user using the user's face or iris. The method authenticates the user using the user's face or iris, links the authenticated user to the product identification information, and, after the product identification information is no longer recognized by the product identification information acquisition means, performs payment for the authenticated user to purchase the product.

One aspect of the recording medium of the present invention stores a computer program configured to cause a computer to function as: product identification information acquisition means for acquiring product identification information for products purchased by a user at a cafeteria; user authentication means for authenticating the user using the user's face or iris; product linking means for linking the authenticated user with the product identification information; and payment means for making payment for the authenticated user's purchase of the product after the product identification information is no longer recognized by the product identification information acquisition means.

According to one aspect of each of the above-described payment systems, methods, and recording media, it is possible to realize highly safe payment processing that is both convenient and hygienic.

1 is a diagram showing an example of the overall configuration for realizing a payment system according to the present invention. FIG. 2 is a diagram showing an example of a hardware configuration of a server according to the present invention. 10 is a flowchart showing an example of a payment routine executed by the payment system according to the present invention. FIG. 2 is a diagram showing an example of a top screen in the payment system according to the present invention. FIG. 10 is a diagram showing an example of a confirmation screen in the payment system according to the present invention. FIG. 10 is a diagram showing an example of an end screen in the payment system according to the present invention.

1. Overall Configuration First, an example of the overall configuration for realizing the payment system according to the present invention will be described with reference to FIG.

FIG. 1 shows an example of the overall configuration of a payment system according to the present invention when applied as a payment system for processing payments for products purchased at a restaurant 40. In the example shown in FIG. 1, a server 10, which can access a database 20, and a cash register 400 at the restaurant 40 are connected for data communication via a communications network (e.g., the Internet) 30. Products to be paid for include, for example, food and beverages purchased by a customer at the restaurant 40. The purchased food may be wrapped in paper, plastic film, or other wrapping paper, and may be served on plates, cups, or other tableware. The purchased beverage may be a canned or bottled beverage, and may be served on plates, cups, or other tableware. The customer places at least one product on a tray, goes to the cash register 400, and pays for the products. The cash register 400 may be a self-service cash register, eliminating the need for a cashier to operate the cash register. While FIG. 1 shows only one cash register 400, multiple cash registers 400 may be installed within the restaurant 40.

The cash register unit 400 may be provided with, for example, a cash register table 401, a product reader 402, a monitor 403, and a camera 404. The cash register table 401 is a table on which a user places products when paying for them. For example, a user may place a tray containing products on the cash register table 401. The product reader 402 is a device that has the function of capturing product identification information from products on the cash register table 401 (for example, products on a tray placed on the cash register table 401).

Product identification information may be, for example, information integrated with a product to identify each product. Product identification information may be provided, for example, on wrapping paper or tableware that is integrated with the product. Product identification information may be captured by product reader 402 using radio waves. For example, product identification information may be recorded on an RF tag that uses RFID (Radio Frequency Identifier) technology. In this case, product reader 402 may be an RFID reader that reads product identification information from an RF tag provided on tableware or the like on a tray.

Alternatively, for example, the product identification information may be a barcode or two-dimensional code attached to tableware or the like. In this case, the product reader 402 may be a camera or code reader capable of reading various codes. Furthermore, the product identification information may be the appearance of the product itself. In this case, the product reader 402 may be a product camera that captures an image of the product and generates image information indicating the product's appearance as product identification information.

For example, when a product (or a tray containing products) is placed within the capture area 401a on the register table 401, the product reader 402 can capture (i.e., read) the product identification information associated with that product. For example, when using communication technology such as RFID technology, the capture area 401a is the communication range of the product reader 402 (i.e., the range in which product identification information can be captured). If the product identification information is image information showing the appearance of the product, the capture area 401a is, for example, the imaging range of a product camera.

Monitor 403 displays various information and messages to be presented to the user. For example, as described below, the product name, unit price, and total payment amount of the product corresponding to the product identification information captured by product reader 402 may be displayed. Monitor 403 may also display various messages for confirmation or requests to the user. Monitor 403 may be, for example, a touch panel that accepts touch operations by the user on the screen. Input devices such as a mouse and keyboard that accept user operations may also be connected to monitor 403.

Camera 404 is an imaging device that captures an image of the face of a user at cash register 400 and generates a facial image for authentication. Camera 404 may, for example, be a sensor camera that detects and captures an image of a user at cash register 400. Camera 404 may, for example, be an AI camera that detects the user's facial features and generates a facial image for authentication. Camera 404 is preferably installed in a direction that the user's face is easily oriented toward (for example, the direction in which the user looks at monitor 403) so that the user's entire face can be easily captured. Camera 404 may also have a video function that captures the user's actions at cash register 400.

The cash register table 401, product reader 402, and monitor 403 of the cash register unit 400 may be components of an existing POS (Point of Sale) system. The camera 404 may be added on and incorporated into the POS system. Alternatively, if the camera 404 has communication capabilities, it may be provided independently of the POS system and connectable to the server 10.

Server 10 may be configured using a single physical server, or may be a single conceptual server configured using multiple physical servers. The hardware configuration of server 10 will be described later.

The server 10 and the accessible database 20 may be configured, for example, as a readable/writable non-volatile recording medium. The database 20 may store, for example, various information required for processing by the server 10. The various information held in the database 20 may be referenced by the server 10 as appropriate. The database 20 may store, for example, user registration information, which will be described later. The user registration information contains information about the user. The user registration information may include, for example, a facial image used for facial authentication, a payment method, contact information, etc. The database 20 may also store, for example, product information, which is information about the product corresponding to the product identification information. The product information may include, for example, the product name, unit price, and inventory quantity. In FIG. 1, the server 10 is connected to the database 20 without via the communication network 30, but the server 10 may also be connected to the database 20 via the communication network 30 so that it can be accessed.

2. Hardware Configuration of the Server The hardware configuration of the server 10 will be described with reference to Fig. 2. As shown in Fig. 2, the server 10 may include, for example, a storage device 11, a computing device 12, and a communication interface 13. The storage device 11, the computing device 12, and the communication interface 13 may be connected via a data bus 15 so as to enable data communication.

The storage device 11 is capable of storing desired data. For example, the storage device 11 may temporarily or long-term store a computer program executed by the processing device 12. The storage device 11 may also temporarily store data used by the processing device 12 while the processing device 12 is executing a computer program. The storage device 11 may include at least one of RAM (Random Access Memory), ROM (Read Only Memory), a hard disk device, a magneto-optical disk device, an SSD (Solid State Drive), and a disk array device. In other words, the storage device 11 may include a volatile recording medium and a non-volatile recording medium.

The arithmetic device 12 includes, for example, a CPU (Central Processing Unit). The arithmetic device 12 may be, for example, a computer unit including a CPU and storage media such as RAM and ROM that store various information required for the CPU's operation. The arithmetic device 12 loads computer programs. For example, the arithmetic device 12 may load a computer program stored in the storage device 11. For example, the arithmetic device 12 may load a computer program stored in a computer-readable non-volatile storage medium using a storage medium reading device (not shown). The arithmetic device 12 may obtain (i.e., download or load) a computer program from a device (not shown) located outside the server 10 via the communication interface 13. The arithmetic device 12 executes the loaded computer program. As a result, logical functional blocks for executing the operations to be performed by the server 10 are realized within the arithmetic device 12. In other words, the arithmetic device 12 can function as a controller for realizing logical functional blocks for executing the operations to be performed by the server 10.

Figure 2 shows an example of logical functional blocks implemented within the computing device 12 to realize the payment system according to the present invention. As shown in Figure 2, the computing device 12 includes a registration unit 12a, a product identification information acquisition unit 12b, a user authentication unit 12c, a product linking unit 12d, a payment unit 12e, a notification unit 12f, and an operation determination unit 12g. The operation of each unit 12a-12g will be described later.

The communication interface 13 is an interface that enables data communication between the server 10 and devices external to the server 10 (e.g., the database 20, the cash register 400 in the cafeteria 40, a user terminal, etc.). The communication interface 13 is configured, for example, to receive various types of information output from devices external to the server 10 and send it to the computing device 12. In this way, the communication interface 13 functions as an input device that inputs information from devices external to the server 10 to the server 10. The communication interface 13 is also configured, for example, to receive various types of control information related to devices external to the server 10 from the computing device 12 and output it to the external devices. In this way, the communication interface 13 functions as an output device that outputs information from the server 10 to devices external to the server 10.

3. Operation of Each Functional Block of the Server The operation of each of the units 12a to 12g as functional blocks realized within the arithmetic device 12 will be described.

The registration unit 12a, for example, associates a user's facial image as authentication registration information with the payment method used by the user when making a payment and registers them in the database 20. For example, the user may send their facial image and information indicating the desired payment method from their user terminal to the server 10. The user terminal may be, for example, a smartphone, tablet, personal computer, or other device that accepts user operations and has general camera and communication functions. The registered "facial image" may be, for example, an image of the user's face captured using any camera or the camera function of the user terminal. The registered "payment method" is the payment method used to pay for the product. The "payment method" may be any method of electronic payment, such as electronic payment based on a credit card or prepaid card, or electronic money payment based on points or virtual currency. The "payment method" may be set, for example, in response to the user's operation on the user terminal.

The user's facial image and desired payment method are transmitted to the server 10, for example, as registration request information. The registration unit 12a may, for example, store in the database 20 user registration information that links the facial image included in the registration request information with the payment method. The facial image in the user registration information may function as user identification information that identifies the user. When there is user identification information separate from the facial image, the registration unit 12a may, for example, store information that links the registration request information with the user identification information as user registration information in the database 20. Hereinafter, the facial image included in the user registration information will be referred to as the "registered facial image."

The registration request information may also include contact information for the user. The "notification destination" may be, for example, an email address, user identification number, or terminal identification number where the user can check notifications from the payment system on their user terminal. The registration unit 12a may associate the contact information included in the registration request information with a facial image and payment method and store it in the database 20 as user registration information.

For example, when the product identification information acquisition unit 12b recognizes product identification information captured by the product reader 402, it acquires the product identification information. The user authentication unit 12c acquires, for example, an authentication facial image generated by the camera 404 and performs user authentication. For example, the user authentication unit 12c references the user registration information in the database 20 and searches for a registered facial image that matches (or is deemed to match) the authentication facial image based on the feature quantities (e.g., size, shape, positional relationship, etc.) of multiple facial feature points (e.g., eyes, nose, ears, mouth, etc.). If a registered facial image that matches (or is deemed to match) the authentication facial image is found, the user authentication unit 12c determines that user authentication has been successful (i.e., the user has been authenticated); if the registered facial image is not found, it determines that user authentication has failed (i.e., the user has not been authenticated).

The product linking unit 12d, for example, links the product identification information acquired by the product identification information acquisition unit 12b to a user whose user authentication has been successful (i.e., an authenticated user). The product linking unit 12d may, for example, link the product identification information acquired by the product identification information acquisition unit 12b to a registered face image (or a face image for authentication) whose user authentication has been successful. When there is user identification information other than the registered face image, the product linking unit 12d may link the product identification information acquired by the product identification information acquisition unit 12b to the user identification information of the user whose user authentication has been successful.

For example, when the product identification information acquisition unit 12b no longer recognizes the product identification information, the payment unit 12e may assume that the product identification information for all products to be purchased has been acquired and perform the payment process. For example, the payment unit 12e may perform the payment process using the payment method registered in the user registration information for the authenticated user.

For example, if there is a possibility of duplicate payments in at least two consecutive payments, the notification unit 12f issues a notification to confirm the user's intention to purchase (i.e., purchase confirmation). For example, if the same user is authenticated in at least two consecutive payments and at least one identical item identification information is acquired by the item identification information acquisition unit 12b, the notification unit 12f issues a purchase confirmation notification to the corresponding user. That is, for example, the notification unit 12f issues a purchase confirmation to the user when consecutive payments are made for the same item to the same user. The notification unit 12f may notify the user of the payment details as purchase confirmation after the payment process by the payment unit 12e is completed. For example, the notification unit 12f may display the purchase confirmation on the monitor 403 of the cash register unit 400. For example, the notification unit 12f may send the purchase confirmation to the user's terminal so that it is displayed on the screen of the user's terminal.

The action determination unit 12g, for example, acquires information about the actions of the user at the cash register unit 400 and determines whether the actions satisfy predetermined conditions. The action information may be, for example, video information captured by the camera 404. Alternatively, a camera (not shown) different from the camera 404 may be provided in the cash register unit 400, and the action information may be video information captured by the camera (not shown). The action determination unit 12g determines that "the action satisfies the predetermined condition" when, for example, the action indicated by the action information is an action that prevents the product reader 402 from capturing product identification information. In other words, the action determination unit 12g determines that "the action satisfies the predetermined condition" when an action is performed that causes product identification information to leave the capture area 401a.

For example, as in this embodiment, if a tray containing products is placed in the take-in area 401a of the register table 401, when a user lifts the tray from the register table 401, the product identification information integrated with the products on the tray may fall out of the take-in area 401a. Therefore, the action determination unit 12g may determine, for example, that the action of a user lifting a tray containing products from the register table 401 "satisfies a predetermined condition."

Even if the product identification information is a code such as a barcode or two-dimensional code, the product identification information on the tray may fall out of capture area 401a when the user lifts the tray from register table 401. Even if the product identification information is an image of the product's exterior, the product on the tray may fall out of capture area 401a, which is the imageable range of the product camera, when the user lifts the tray from register table 401. A user action that causes the product identification information to fall out of capture area 401a may be, for example, a user sliding the tray from capture area 401a to a position adjacent to capture area 401a.

4. Processing Flow in the Payment System An example of the processing flow executed by the payment system implemented by the server 10 will be described using Figure 3 and Figures 4A to 4C. Figure 3 shows an example of a payment routine executed by the payment system. Figures 4A to 4C show examples of screens displayed on the monitor 403.

For example, the server 10 may display the top screen 50a shown in FIG. 4A on the monitor 403 as a standby screen for the payment system until processing of the payment routine is initiated. For example, as shown in FIG. 4A, the top screen 50a may display a message urging the user to place a tray on the register table 401. This prompts a user who comes to the register unit 400 with a tray to place the tray on the register table 401. For example, when the server 10 detects a user standing at the register unit 400 using the camera 404, it may use this as a trigger to start the payment routine.

For example, the server 10 may first perform user authentication processing (step S101). In the user authentication processing, the server 10 may, as described above, refer to the database 20 to search for a registered face image that matches (or is deemed to match) the authentication face image. If the user authentication is successful, the server 10 may, for example, proceed to product linking processing (step S102). If the user authentication is unsuccessful, the server 10 may, for example, display on the monitor 403 a message urging the user to look at the camera 404 to obtain the authentication face image again. If the user authentication is unsuccessful, the server 10 may, for example, display on the monitor 403 a message requesting the user to make payment after registering user registration information.

In the product linking process (step S102), the server 10 links the user with the product to be purchased. The server 10 recognizes and acquires the product identification information captured by the product reader 402, and links the acquired product identification information to, for example, the registered facial image of the authenticated user. The server 10 may also, for example, refer to the product information in the database 20 to acquire product information (e.g., product name, unit price, etc.) for the product corresponding to each acquired product identification information. For example, based on the acquired product information, the server 10 may display a product list for the products on the tray (i.e., the products to be purchased) including the product, unit price, total payment amount, etc., as shown on the confirmation screen 50b in Figure 4B. This allows the user to check the total payment amount and its details.

Next, the server 10 may determine whether the product identification information is no longer recognized (step S103). If the product identification information is recognized (step S103: No), the server 10 may return to step S102 and perform product linking processing for the acquired product identification information. The server 10 may perform the product linking processing (step S102) for the product identification information until the product identification information is no longer recognized. If the product identification information is no longer recognized (step S103: Yes), the server 10 may proceed to step S104, assuming that the product identification information of all products on the tray (i.e., the products to be purchased) has been acquired and linked to the user.

Here, for example, if the server 10 no longer recognizes the product identification information (step S103: Yes), it may confirm the number of products on the tray using a camera (not shown) capable of capturing images of the products on the tray and compare the number with the number of products in the product list displayed on the confirmation screen 50b. If the confirmed number of products differs from the number of products in the product list, the server 10 may, for example, display a message on the monitor 403 requesting the user to move the tray or the products so that the product identification information of the products on the tray can be correctly captured by the product reader 402. For example, if the product identification information is recorded on an RF tag, the product identification information may not be read by the product reader 402 due to interference from metal products or the like. Therefore, the server 10 may, for example, display a message requesting the user not to place any items other than products, such as metal products, on the tray. Alternatively/and, for example, the server 10 may display a message requesting the user to place the tray in the correct position (e.g., within the capture area 401a). For example, if the server 10 recognizes the product identification information after displaying the message, it may return to step S102. If the server 10 does not recognize the product identification information after displaying the message, it may, for example, notify the cashier manager that a problem has occurred in the cashier unit 400. Note that the above processing regarding the number of products may be controlled, for example, by a product number confirmation unit that the server 10 implements as a functional block in the computing device 12.

In step S104, the server 10 may determine whether a predetermined action has been performed by the user. The "predetermined action" is an action that has been predetermined as the "action that satisfies the predetermined condition" described above. The server 10 may, for example, acquire from the camera 404 action information for a predetermined period of time, including the time when it was determined that the product identification information was no longer recognized, and determine whether a "predetermined action" has been performed based on the action information. Specifically, the "predetermined action" may be, for example, the action of lifting a tray placed on the register table 401 from the register table 401, as described above. As shown in FIG. 4B, the server 10 may display a message on the confirmation screen 50b indicating that payment has been completed in response to the action of lifting the tray. This makes it possible to clearly confirm the user's intention to pay for the product list displayed on the confirmation screen 50b.

If the server 10 determines in step S104 that a predetermined operation has not been performed (step S104: No), it may, for example, perform payment confirmation (step S110). In the payment confirmation, the server 10 may, for example, confirm via the monitor 403 whether or not to pay for the product list displayed on the confirmation screen 50b. If the server 10 receives confirmation of the intention to pay (step S110: Yes), it may, for example, proceed to payment processing (step S105). On the other hand, if the server 10 does not receive confirmation of the intention to pay (for example, if the user wishes to make a correction) (step S110: No), the server 10 may, for example, proceed to correction processing (step S111). In the correction processing, the server 10 may, for example, allow the user to correct the product list to be paid for displayed on the confirmation screen 50b, and after the product list has been corrected, it may proceed to payment processing (step S105).

On the other hand, if the server 10 determines in step S104 that a predetermined action has been performed (step S104: Yes), it may proceed to payment processing (step S105). In the payment processing, the server 10 may, for example, perform payment processing for the purchased items using the payment method set in the user registration information corresponding to the user. When the payment processing is complete, the server 10 may, for example, display a closing screen 50c as shown in FIG. 4C on the monitor 403 to indicate that payment has been completed. In this way, in the payment system of the present disclosure, a user can complete payment for the items by simply placing a tray containing the items to be purchased on the register table 401 and then lifting the tray. This series of actions is natural for cafeteria users and does not burden them. The payment system of the present disclosure enables users to complete payment using only natural, effortless actions.

Following step S105, the server 10 may perform a notification process (step S106). In the notification process, the server 10 may, for example, notify the contact information (e.g., the user terminal) set in the user registration information corresponding to the user of the purchase confirmation. After notifying the purchase confirmation, the server 10 may terminate the payment routine. Note that the server 10 may enable a process that allows a user who has received the purchase confirmation to cancel the corresponding payment.

In step S106, the server 10 may, for example, determine whether two or more consecutive payments are likely to be duplicate payments. For example, the server 10 may determine that there is a possibility of a duplicate payment if the same user is authenticated and product identification information for the same product is obtained for two or more consecutive payments. If the server 10 determines that there is a possibility of a duplicate payment, it may notify a purchase confirmation regarding the duplicate payment. For example, the server 10 may notify the user terminal of the purchase confirmation. For example, if the user performs an operation on the user terminal to continue all payments related to the duplicate payment, the server 10 may terminate the payment routine. For example, if the user performs an operation to cancel at least one of the two or more payments related to the duplicate payment, the server 10 may perform processing to cancel the payment to be canceled. The server 10 may then terminate the payment routine.

Note that the server 10 may, for example, display a purchase confirmation on the monitor 403 when payment is completed. The server 10 may also enable processing similar to that when notifying the user terminal in response to a user operation on the monitor 403.

Step S101 is performed by the user authentication unit 12c. Step S102 is performed by the product identification information acquisition unit 12b and the product linking unit 12d. Step S104 is performed by the action determination unit 12g. Steps S103 and S105 are performed by the payment unit 12e. Step S106 is performed by the notification unit 12f.

If step S103 returns a positive judgment (step S103: Yes), the server 10 may skip step S104 and proceed to step S105. The server 10 may start processing the payment routine, for example, when the server 10 acquires product identification information. The server 10 may perform user authentication processing after acquiring all product identification information. Alternatively, the server 10 may acquire product identification information and perform user authentication processing in parallel.

Iris authentication may be adopted as a user authentication method in addition to or instead of facial authentication. In this case, a camera for iris authentication may be adopted as camera 404. The product identification information may be, for example, various code information integrated with a product tag that replaces the product, rather than information integrated with the product itself. In this case, payment is made by placing only the product tag corresponding to the product to be purchased on a tray, and after payment is completed, the actual product corresponding to the product tag on the tray is received.
The payment system of the present disclosure is not limited to payments at restaurants, but can be applied to any situation where a user pays for purchased items.

<Additional Notes>
A part or all of the above-described embodiments can be described as, but not limited to, the following supplementary notes.

(Appendix 1)
The payment system described in Appendix 1 is a payment system having a product identification information acquisition means for acquiring product identification information of a product purchased by a user at a cafeteria, a user authentication means for authenticating the user using the user's face or iris, a product linking means for linking the authenticated user with the product identification information, and a payment means for making a payment for the authenticated user to purchase the product after the product identification information is no longer recognized by the product identification information acquisition means.

According to the payment system described in Appendix 1, when purchasing items at a cafeteria, payment can be triggered by the fact that product identification information is no longer recognized by the product identification information acquisition means. That is, the payment system considers the state in which product identification information is no longer recognized as a state in which product identification information for all purchased items has been acquired, and is able to perform payment. In this way, the payment system can perform payment without the user having to perform any operation for payment. This eliminates the need for the time and effort of entering a password, etc., improving the convenience of payment processing. Therefore, the payment system can avoid users having to wait in line for payment and provide a smooth payment process. Furthermore, the payment system does not require the user to perform any operation using their fingers, etc., meaning that payment is completely touchless and improves hygiene. Furthermore, the payment system ensures a high level of security because payment is made to a user authenticated by facial recognition. In this way, the payment system can achieve comfortable, safe, and highly secure payments.

(Appendix 2)
The payment system described in Appendix 2 is the payment system described in Appendix 1, further having a notification means for notifying the user to confirm the purchase, and the notification means sends the notification when the same user is authenticated by the user authentication means and at least one piece of the same product identification information is acquired by the product identification information acquisition means in at least two consecutive payments.

According to the payment system described in Appendix 2, if the same user is authenticated and at least one identical item identification information is obtained in at least two consecutive payments, i.e., if the same user makes two or more consecutive payments for the same item (i.e., if there is a possibility of a duplicate payment), the system notifies the user to confirm the purchase. This allows the user to confirm whether the payment was unintentional and makes it possible to avoid unintentional payments.

(Appendix 3)
The payment system described in Supplementary Note 3 is the payment system described in Supplementary Note 2, in which the notification means sends the notification to a user terminal of the user.

The payment system described in Appendix 3 can directly notify a user's user terminal of purchase confirmation in the event of a possible duplicate payment. In particular, if the user terminal is a portable terminal, the notification can be sent to a user in any location. For example, it is possible to send the notification to a user who has left the payment area (e.g., the cash register) at a restaurant and taken to their seat. This allows the user to respond to the notification at their seat at their leisure. On the other hand, if the notification is sent to the cash register immediately after payment is completed, for example, there is a possibility of a long queue forming at the cash register in the restaurant while the user waits to respond. This payment system makes it possible to avoid such long queues.

(Appendix 4)
The payment system described in Appendix 4 is a payment system described in any one of Appendixes 1 to 3, further comprising an action determination means for acquiring action information indicating the user's action and determining whether the action satisfies a predetermined condition, and the payment means performs the payment if the action satisfies the predetermined condition.

According to the payment system described in Supplementary Note 4, payment is made when the product identification information is no longer recognized by the product identification information acquisition means and the user performs an action that satisfies a predetermined condition. For example, if the product identification information acquisition means fails to recognize the product identification information of all products to be purchased for some reason, it is possible to avoid making payment. It is desirable that the "action that satisfies a predetermined condition" be an action that does not impose a burden on the user.
In addition, the payment systems described in Supplementary Notes 1 to 4 may have a product quantity confirmation means for confirming whether the number of products purchased by the user is the same as the number of product identification information linked to the user.

(Appendix 5)
The payment system described in Appendix 5 is the payment system described in Appendix 4, in which the action determination means acquires the action information for a predetermined period including the point at which the product identification information acquisition means no longer recognizes the product identification information, and determines whether the action satisfies the predetermined condition.

In the payment system described in Appendix 5, a user action taken within a predetermined period of time, including the point at which the product identification information is no longer recognized by the product identification information acquisition means, can be considered an "action that satisfies a predetermined condition" in the payment system described in Appendix 4. It is desirable that the "action that satisfies a predetermined condition" be, for example, an action that causes the product identification information to no longer be recognized by the product identification information acquisition means. Such an "action that satisfies a predetermined condition" can function as a cross-check that the product identification information of all products purchased by the user has been acquired by the product identification information acquisition means.

(Appendix 6)
The payment system described in Appendix 6 is a payment system described in any one of Appendixes 1 to 5, further comprising a database and a registration means for linking authentication registration information regarding the user's face or iris used for the authentication with the payment method used by the user for the payment and registering the linked information in the database, wherein the product linking means links the authentication registration information of the authenticated user with the product identification information, and the payment means makes the payment using the payment method linked and registered to the authentication registration information.

According to the payment system described in Appendix 6, the payment system can refer to the facial information used for authentication and the payment method to be used by referencing the registered information in the database. Since the payment method to be used can be registered in advance, even people on overseas business trips can easily make payments using their desired payment method.

(Appendix 7)
The payment system described in Supplementary Note 7 is the payment system described in any one of Supplementary Notes 1 to 6, in which the product identification information is information integrated with the product.

According to the payment system described in Appendix 7, product identification information is integrated with the product, so the status of the product identification information can be considered as the status of the product.

(Appendix 8)
The method described in Appendix 8 is a method in a payment system having a product identification information acquisition means for acquiring product identification information of a product purchased by a user at a cafeteria, and a user authentication means for authenticating the user using the user's face or iris, wherein the user is authenticated using the user's face or iris, the authenticated user is linked to the product identification information, and after the product identification information is no longer recognized by the product identification information acquisition means, the authenticated user makes a payment to purchase the product.

By implementing the method described in Appendix 8 on a computer, it is possible to realize the payment system described in Appendix 1, i.e., a highly secure payment system with improved convenience and hygiene.

(Appendix 9)
The computer program described in Appendix 9 is a computer program configured to cause a computer to function as a product identification information acquisition means for acquiring product identification information of a product purchased by a user at a cafeteria, a user authentication means for authenticating the user using the user's face or iris, a product linking means for linking the authenticated user with the product identification information, and a payment means for making payment for the authenticated user to purchase the product after the product identification information is no longer recognized by the product identification information acquisition means.

By running the computer program described in Appendix 9 on a computer, the payment system described in Appendix 1 can be realized. In other words, a highly secure payment system with improved convenience and hygiene can be realized.

(Appendix 10)
The computer-readable recording medium described in Supplementary Note 10 is a recording medium on which the computer program described in Supplementary Note 9 is stored.

The present invention is not limited to the above-described embodiments, and may be modified as appropriate within the scope of the claims and the entire specification without departing from the spirit or concept of the invention. Payment systems, methods, and recording media incorporating such modifications are also included within the technical spirit of the present invention.

This application claims priority based on Japanese Patent Application No. 2020-217123, filed on December 25, 2020, the disclosure of which is incorporated herein in its entirety.

12a Registration unit (registration means)
12b Product identification information acquisition unit (product identification information acquisition means)
12c User authentication unit (user authentication means)
12d Product linking unit (product linking means)
12e Payment section (payment means)
12f Notification section (notification means)
12g Operation determination unit (operation determination means)
10 Server 20 Database 40 Cafeteria

Claims (11)

an acquisition unit that acquires facial information obtained by photographing a user;
an identification unit that identifies a payment method linked to the pre-registered face information by comparing the face information with pre-registered face information;
a product identification information acquisition unit that acquires product identification information of products on a tray placed on a cash register table;
a display unit that displays a total price of the products on the tray obtained based on unit price information of the products associated with the product identification information;
an action determination unit that acquires action information indicating the action of the user and determines whether the tray has been lifted by the action;
If it is determined that the tray has been lifted, the total amount is paid using the payment method;
a payment unit that, when it is determined that the tray cannot be lifted, displays a confirmation of whether or not to pay for the items on the tray;
A payment system having: a notification unit that notifies the user of a purchase confirmation;
The notification unit, in at least two consecutive payments,
The payment system according to claim 1 , wherein the notification is made when at least one piece of the same product identification information is acquired by the product identification information acquisition unit for the same user. The payment system described in claim 2, wherein the notification unit sends the notification to the user terminal of the user. The payment system described in any one of claims 1 to 3, wherein the movement determination unit acquires the movement information for a predetermined period of time including the point at which the product identification information acquisition means no longer recognizes the product identification information, and determines whether the tray has been lifted. A database,
a registration unit that associates registration information relating to the user's face information used in the matching with a payment method used by the user for the payment and registers the association information in the database;
The payment system according to claim 1 , wherein the identification unit identifies the payment method registered in association with the registration information of the user. The payment system described in any one of claims 1 to 5, wherein the product identification information is information integrated with the product. By at least one computer,
Acquires facial information from a photograph of the user,
Identifying a payment method linked to the pre-registered face information by matching the face information with pre-registered face information;
Acquire product identification information of the products on the tray placed on the cash register table,
displaying a total price of the products on the tray obtained based on unit price information of the products associated with the product identification information;
acquiring action information indicating an action of the user and determining whether the tray has been lifted by the action;
If it is determined that the tray has been lifted, the total amount is paid using the payment method;
If it is determined that the tray cannot be lifted, a message is displayed to confirm whether the customer wishes to pay for the items on the tray.
method. Computer,
an acquisition unit that acquires photographed face information of a user;
an identification unit that identifies a payment method linked to the pre-registered face information by comparing the face information with pre-registered face information;
a product identification information acquisition unit that acquires product identification information of products on a tray placed on a cash register table;
a display unit that displays the total price of the products on the tray obtained based on the unit price information of the products associated with the product identification information;
an action determination unit that acquires action information indicating an action of the user and determines whether the tray has been lifted by the action; and if it is determined that the tray has been lifted, that performs payment of the total amount using the payment method;
a payment unit that, when it is determined that the tray cannot be lifted, displays a confirmation of whether or not to pay for the items on the tray;
A computer program that functions as a an acquisition unit that acquires facial information obtained by photographing a user;
an identification unit that identifies user registration information linked to the pre-registered face information by comparing the face information with pre-registered face information;
a product identification information acquisition unit that acquires product identification information of products on a tray placed on a cash register table; and a display unit that displays a total price of the products on the tray obtained based on unit price information of the products associated with the product identification information.
an action determination unit that acquires action information indicating the action of the user and determines whether the tray has been lifted by the action;
If it is determined that the tray has been lifted, the total amount is paid based on the payment method included in the user registration information,
a payment unit that, when it is determined that the tray cannot be lifted, displays a confirmation of whether or not to pay for the items on the tray;
A payment system having: By at least one computer,
Acquires facial information from a photograph of the user,
Identifying user registration information linked to the pre-registered face information by matching the face information with pre-registered face information;
Acquire product identification information of the products on the tray placed on the cash register table,
displaying a total price of the products on the tray obtained based on unit price information of the products associated with the product identification information;
acquiring action information indicating an action of the user and determining whether the tray has been lifted by the action;
If it is determined that the tray has been lifted, the total amount is paid based on the payment method included in the user registration information,
When it is determined that the tray cannot be lifted, a display is displayed to confirm whether or not the customer wishes to pay for the items on the tray. Computer,
an acquisition unit that acquires photographed face information of a user;
an identification unit that identifies user registration information linked to the pre-registered face information by comparing the face information with pre-registered face information;
a product identification information acquisition unit that acquires product identification information of products on a tray placed on a cash register table;
a display unit that displays the total price of the products on the tray obtained based on the unit price information of the products associated with the product identification information;
an action determination unit that acquires action information indicating an action of the user and determines whether the tray has been lifted by the action; and if it is determined that the tray has been lifted, settles the total amount based on the settlement method included in the user registration information;
a payment unit that, when it is determined that the tray cannot be lifted, displays a confirmation of whether or not to pay for the items on the tray;
A computer program that functions as a