Pay-at-the-table system and pay-at-the table method
The tabletop payment system uses a mobile terminal to lock shoe lockers and link them to ordering terminals, addressing the issue of unpaid eating by ensuring payment completion before locker unlocking, facilitating self-service transactions.
Patent Information
- Application Number
- JP2024013901
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2024-02-01
- Publication Date
- 2025-08-14
AI Technical Summary
Existing tabletop payment systems struggle to prevent customers from eating and drinking without completing payment, as staff cannot easily verify payment completion.
A tabletop payment system using a mobile terminal to lock shoe lockers, linked to an ordering terminal, which manages reservation and payment information, allowing customers to order and pay directly, ensuring shoe lockers are unlocked only upon completion of payment.
Prevents customers from eating and drinking without paying by ensuring shoe lockers are locked until payment is finalized, enabling self-service transactions and reducing staff oversight.
Smart Images

Figure 2025119180000001_ABST
Abstract
Description
[Technical Field]
[0001] The present disclosure relates to a table payment system and a table payment method. [Background technology]
[0002] Tabletop payment, where everything from ordering to payment can be done at the table, is becoming more common. With tabletop payment, after payment is made, a payment completion screen is displayed on the ordering terminal at the table. However, it is difficult for staff and others around to determine whether the customer has completed the payment, which can lead to customers eating and drinking without paying.
[0003] Patent document 1 describes a restaurant POS system that is characterized by having an electronic lock that opens and closes the lock on a shoe cabinet, and a control means that manages the unlocking information of this electronic lock in association with the restaurant's payment information, and instructs the electronic lock to unlock based on the payment information. [Prior art documents] [Patent documents]
[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2003-006749 Summary of the Invention [Problem to be solved by the invention]
[0005] The system disclosed in Patent Document 1 is equipped with a shoe locker that includes an RFID tag reader with an RFID tag slot and an electronic lock that opens and closes the lock. The lock is activated when the RFID tag is removed from the slot, and is unlocked when an RFID tag that has been used for payment at the restaurant is inserted into the slot. At the time of POS payment, the waiter must rewrite the unlocking permission information on the RFID tag. In other words, table payments without the involvement of a seating capacity are not supported.
[0006] The present disclosure aims to prevent eating and drinking without paying at the table by allowing shoe lockers to be locked using a mobile terminal and linking the shoe lockers to ordering terminals. [Means for solving the problem]
[0007] A tabletop payment system according to one aspect of the present disclosure includes: A tabletop payment system for making table payments for one or more customers comprises: a mobile terminal carried by each customer; an ordering terminal installed at a table in the store; a plurality of shoe lockers installed in the store that can be locked by operating the mobile terminal; and a management server that manages order information, the usage status of each shoe locker, and payment information. The mobile terminal acquires a reception number by registering the number of customers, the table used by the customer, and the shoe locker for each customer. After a sensor recognizes that the shoe locker door is closed, the customer operates the mobile terminal to lock the shoe locker. The ordering terminal uses the acquired reception number to display an order screen, allows the customer to order products on the order screen, and then performs payment processing. The shoe locker is unlocked when the customer completes payment.
[0008] A table settlement method according to one aspect of the present disclosure includes: A table payment method for when one or more customers visit a restaurant in a table payment system comprising a mobile terminal carried by each customer, an ordering terminal installed at a table in the restaurant, a plurality of shoe lockers installed in the restaurant that can be locked by operating the mobile terminal, and a management server that manages order information, the usage status of each shoe locker, and payment information, in which the mobile terminal registers the number of customers, the table used by the customer, and the shoe locker for each customer, thereby obtaining a reception number, and after a sensor recognizes that the shoe locker door has been closed, the customer operates the mobile terminal to lock the shoe locker, and the ordering terminal displays an order screen using the obtained reception number and orders products on the order screen, after which payment is processed and the shoe locker is unlocked upon completion of payment by the customer. [Effects of the Invention]
[0009] According to the present disclosure, it is possible to provide a table payment system that allows shoe lockers to be locked using a mobile terminal and links the shoe lockers to an ordering terminal, thereby preventing eating and drinking without paying when paying at the table. [Brief explanation of the drawings]
[0010] [Figure 1] FIG. 1 is a diagram illustrating an example configuration of a table-top payment system according to the present disclosure. [Figure 2] FIG. 1 is a diagram illustrating an example of the configuration of an order terminal according to the present disclosure. [Figure 3] 1A and 1B are diagrams illustrating an example of the configuration of a shoebox according to the present disclosure. [Figure 4] 10 is a flowchart illustrating a reception process according to the present disclosure. [Figure 5] 10 is a flowchart illustrating a process for linking a smartphone and an ordering terminal according to the present disclosure. [Figure 6] 1 is a flowchart illustrating accounting processing according to the present disclosure. [Figure 7] 10 is a flowchart illustrating a member addition process according to the present disclosure. [Figure 8] 10 is a flowchart illustrating mid-payment processing according to the present disclosure. [Figure 9] FIG. 1 is a diagram illustrating a method for ordering products in a group according to the present disclosure. [Figure 10] FIG. 10 is a diagram illustrating a method for registering a database according to the present disclosure. [Figure 11] FIG. 10 is a diagram illustrating how to register a database when adding a member according to the present disclosure. [Figure 12] FIG. 10 is a diagram illustrating how to register a database at the time of individual interim checkout according to the present disclosure. DETAILED DESCRIPTION OF THE INVENTION
[0011] First, an overview of the present disclosure will be described. The tabletop payment system is used for table payments for one or more customers. Each customer carries a mobile terminal. An ordering terminal is installed at a table in the store. Multiple shoe lockers are installed in the store (for example, near the entrance) and can be locked by operating the mobile terminal. The management server is configured to manage registration information, the usage status of each shoe locker, order information, and payment information. The mobile terminal, ordering terminal, multiple shoe lockers, and management server can be communicatively connected via a wired or wireless network.
[0012] In a table payment system, a mobile terminal can obtain a receipt number by registering the number of customers, the tables used by the customers, and the shoe lockers for each customer.
[0013] When a customer visits the store, their shoes are placed in the appropriate shoe locker, and after the sensor detects that the shoe locker door is closed, the customer can lock the shoe locker by operating their mobile device.
[0014] The ordering terminal uses the acquired reception number to display an order screen, allows the customer to place an order for the product on the order screen, and then performs payment processing. In some embodiments, the ordering terminal can use code payment. That is, the ordering terminal displays a reception identification code associated with the acquired reception number, and when the reception identification code is read by the customer's mobile terminal, the ordering terminal displays an order screen and allows the customer to place an order for the product on the order screen. The ordering terminal then displays a transaction identification code associated with the product order, and when the transaction identification code is read by the mobile terminal, the payment processing can be performed. In other embodiments, the order screen sets a payment percentage for each customer, and the amount of the ordered product is calculated for each customer according to each customer's payment percentage, linked to each customer's shoe locker number.
[0015] The shoe locker is designed to unlock when the customer completes payment. Therefore, the customer can remove their shoes from the shoe locker after completing payment, preventing eating and drinking without paying. Since customers can handle everything from reception to payment themselves, an unmanned store can be operated.
[0016] In some embodiments, if there is a member of the group who leaves early, the mobile terminal of the member who leaves early performs payment processing through the order terminal, and the shoe locker associated with the member who leaves early is configured to be unlocked upon completion of payment by the member.
[0017] In another embodiment, when a person who arrives midway through a group joins the group, the person's mobile device acquires the reception number and password, and the shoe locker information can be added to the group based on the reception number and password. The shoe locker can be locked by the person who arrives midway through the group operating the mobile device.
[0018] With the table payment system, each customer can use their mobile device (and its app) to pay and add members mid-way through their meal.
[0019] Hereinafter, specific embodiments to which the present invention is applied will be described in detail with reference to the drawings. However, the present invention is not limited to the following embodiments. In addition, the following description and drawings have been simplified as appropriate for clarity of explanation.
[0020] An example of the configuration of the tabletop payment system 1 will be described below with reference to FIG. FIG. 1 is a diagram illustrating an example of the configuration of a system 1 for preventing eating and drinking without paying. The restaurant provides a management server 50, a shoe locker 60, and an ordering terminal 20, and the customer carries a smartphone 10. The management server 50, the shoe locker 60, the ordering terminal 20, and the smartphone 10 are communicatively connected via a wired or wireless network. The ordering terminal 20 may be, for example, a tablet terminal with a touch panel. The smartphone 10 is an example of a mobile terminal, and is a smartphone with a camera. However, the smartphone 10 is not limited to this and may be any mobile terminal with a camera that a user can carry. A customer app for the system for preventing eating and drinking without paying 1 is installed on the smartphone 10. A store app for the system for preventing eating and drinking without paying 1 is installed on the ordering terminal 20. The system for preventing eating and drinking without paying 1 when paying at a table is assumed to be usable without registering the app. If the app requires registration of personal information such as name, address, and phone number, the customer, who is the individual user of the app, can be easily identified in the system, thereby preventing eating and drinking without paying.
[0021] The management server 50, the opening and closing control device for the shoebox 60, the order terminal 20, and the smartphone 10 have the function of executing various controls based on various programs stored in the memory unit, and are realized by a central processing unit (CPU), a read-only memory (ROM), a random access memory (RAM), an input / output port (I / O), etc.
[0022] Communication is performed between the smartphone 10 and the management server 50 to register reception information, register shoebox information, display status, etc. A reception number (or an identification code associated therewith) is used between the smartphone 10 and the ordering terminal 20 to link the smartphone 10 and the ordering terminal 20. Communication is performed between the ordering terminal 20 and the management server 50 to confirm whether the reception barcode and payment completion have been carried out normally. The management server 50 and the shoebox 60 are used to check the current availability of the shoebox and save the usage status (for example, unlocked or locked status).
[0023] FIG. 2 is a diagram illustrating an example of the configuration of an order terminal according to the present disclosure. The order terminal 20 includes a control unit 21, a storage unit 22, a communication unit 23, a display unit 24, an input unit 25, and a code reading unit 26.
[0024] The control unit 21 may be a processor that reads and executes software (computer programs) from memory to perform processing of the order terminal 20, etc., which will be described using flowcharts or sequences in the embodiments. The processor may be, for example, a CPU (Central Processing Unit), GPU (Graphic Processing Unit), DSP (Digital Signal Processor), MPU (Micro Processing Unit), FPU (Floating point number Processing Unit), PPU (Physics Processing Unit), TPU (Tensor Processing Unit), quantum processor, microcontroller, or a combination of these.
[0025] The storage unit 22 may be a memory, and may be configured by a combination of volatile and non-volatile memory. The memory may include storage located remotely from the processor. In this case, the processor may access the memory via an I / O interface, which may be the input unit 25.
[0026] 2, the storage unit 22 is used to store a group of software modules. The processor reads and executes these software modules from the storage unit 22, thereby performing processing of the order terminal 20 and the like described in the embodiment.
[0027] The communication unit 23 may be a network interface used to communicate with other network node devices constituting the communication system. The network interface may be used to perform wireless communication. For example, the network interface may be used to perform wireless LAN communication defined in the IEEE 802.11 series or mobile communication defined in 3GPP (3rd Generation Partnership Project). Alternatively, the network interface may include a network interface card (NIC) conforming to the IEEE 802.3 series.
[0028] Each of the processors included in the order terminal 20 executes one or more programs including a group of instructions for causing a computer to execute an algorithm that will be explained with reference to the drawings.
[0029] The display unit 24 displays the order details, total amount, code, etc. The display unit 24 can be various display means such as an LCD (liquid crystal display) or an LED (light emitting diode).
[0030] The input unit 25 may be an I / O interface. The code reading unit 26 reads a code displayed on a smartphone or the like.
[0031] FIG. 3 is a diagram illustrating an example of the configuration of a shoebox according to the present disclosure. The shoebox 60 includes a control unit 61, a storage unit 62, a communication unit 63, a sensor unit 64, a clock unit 65, and a door opening / closing control unit 66.
[0032] The control unit 61 may be a processor that reads and executes software (computer programs) from memory to perform processing of the order terminal 20, etc., which will be described using flowcharts or sequences in the embodiments. The processor may be, for example, a CPU (Central Processing Unit), GPU (Graphic Processing Unit), DSP (Digital Signal Processor), MPU (Micro Processing Unit), FPU (Floating point number Processing Unit), PPU (Physics Processing Unit), TPU (Tensor Processing Unit), quantum processor, microcontroller, or a combination of these.
[0033] The storage unit 62 may be a memory, and may be configured by a combination of volatile and non-volatile memory. The memory may include storage located remotely from the processor. In this case, the processor may access the memory via an I / O interface (not shown).
[0034] 3, the storage unit 62 is used to store software modules. The processor reads and executes these software modules from the storage unit 22 to perform the processing of the shoebox 60 described in the embodiment.
[0035] The communication unit 63 may be a network interface used to communicate with other network node devices constituting the communication system. The network interface may be used to perform wireless communication. For example, the network interface may be used to perform wireless LAN communication defined in the IEEE 802.11 series or mobile communication defined in 3GPP (registered trademark) (3rd Generation Partnership Project). Alternatively, the network interface may include, for example, a network interface card (NIC) conforming to the IEEE 802.3 series.
[0036] Each of the processors in shoebox 60 executes one or more programs containing instructions for causing the computer to perform algorithms that will be described with reference to the figures.
[0037] The sensor 64 includes a weight sensor or a door open / close sensor. The weight sensor may be installed inside the shoebox and used to determine whether the shoebox is present or not. The door open / close sensor may be used to determine whether the door is open or closed. The door open / close sensor may include, for example, a detector provided on one side edge of the door and a detector unit provided on the housing of the shoebox for detecting the detector. The detector unit may be configured to detect the detector (e.g., magnetic force from a magnet) only when the door is closed.
[0038] The clock unit 65 can measure time. The door opening / closing control unit 66 can accept control instructions from a smartphone or a management server and lock / unlock the door. The door opening / closing control unit 66 may automatically lock the door when a predetermined time has passed after the weight sensor detects that shoes have been placed in the shoebox and the door sensor detects that the door has been closed.
[0039] FIG. 4 is a flowchart illustrating the reception process. After entering the store, a customer uses an app on the smartphone 10 to specify the number of users in the group (i.e., the number of shoe lockers), the type of seating (e.g., counter, table, etc.), etc., to perform a reception process (A1). The smartphone 10 then transmits reception information specifying the number of users (i.e., the number of shoe lockers), the type of seating, etc., to the management server 50 (A2). In response to receiving the reception information, the management server 50 registers the reception information and issues a reception number (A3). The management server 50 then notifies the smartphone 10 of the issued reception number (A4). Note that when multiple customers visit the store, the reception information may be transmitted from one smartphone of one customer to the management server 50, and after the issued reception number is received by that smartphone, the reception number may be forwarded to other smartphones of other customers. In this case, as will be described later, the other customers may select shoe lockers and lock them from their respective smartphones.
[0040] The smartphone 10 displays the reception number and the current availability of the shoe locker (A5). The smartphone 10 communicates with the management server 50 (A6), and the management server 50 checks the status of the shoe locker 60 (A7, A8, A9). The smartphone 10 displays the status of the shoe locker 60 checked via the management server 50 in a selectable manner (A10, A101, A11). That is, the customer can display available shoe lockers in the smartphone 10 app and select the shoe locker location or shoe locker number. The smartphone 10 transmits the shoe locker information selected by the customer to the management server 50 (A12). The management server 50 stores the selected shoe locker (shoe locker location or shoe locker ID) in the database as in-use and issues a command to unlock the selected shoe locker (A13). Specifically, the management server 50 instructs the opening / closing control device (not shown) of the shoebox 60 to unlock the selected shoebox (for example, the shoebox location, number, or shoebox ID), and the opening / closing control device controls to open the lock of the shoebox 60 (A14). Note that if the shoebox door is open from the beginning, opening control by the management server 50 is not necessary. The customer then puts shoes into the shoebox 50 specified by the app on the smartphone 10 and closes the door of the shoebox 50. The opening / closing control device of the shoebox 50 recognizes, using a weight sensor, that shoes have been stored in the shoebox 50, or, using an opening / closing sensor, that the shoebox door has been opened once and that the shoebox 50 door has been closed (A15). In another example, the opening / closing control device of the shoebox 50 may simply recognize, using a closing sensor, that the shoebox 50 door has been closed. The opening / closing control device of the shoebox 50 notifies the management server 50 that the shoebox 50 door has been closed (A16). The management server 50 displays a lock button on the app on the smartphone 10, and then the user presses the lock button displayed on the app (A161, A17). The smartphone 10 sends a lock instruction to the opening / closing control device of the shoebox 50 via the management server 50 (A18, A19, A20). The opening / closing control device of the shoebox 50 locks the corresponding shoebox 60 (A21). The opening / closing control device of the shoebox 50 notifies the management server 50 that locking has been completed (A22). The management server 50 saves the completion of locking of the corresponding shoebox in the database (A23). In this way, in this system, shoeboxes can be locked individually and easily using a smartphone.
[0041] Figure 5 is a flowchart explaining the process of linking a smartphone with an ordering terminal. The customer causes the ordering terminal 20 to display a screen for reading the reception number's identification code (e.g., a barcode, QR code (registered trademark), etc.) (B1). The customer causes the smartphone 10 to display the reception number's identification code (B3). The ordering terminal 20 reads the reception number's identification code displayed on the smartphone 10 using the ordering terminal 20's camera or code reader (B2, B4). The ordering terminal 20 confirms with the management server 50 whether the received identification code information is a legitimate code, and then saves the reception number data (B5, B6). The management server 50 confirms whether the reception number received from the ordering terminal 20 is legitimate, and confirms whether the shoe locker 60 is locked (B7). Once the confirmation process by the management server 50 is complete, the ordering terminal 20 displays the order screen (B9).
[0042] In this way, this system can prevent customers from eating and drinking without paying by confirming that their shoes are stored in the shoe locker and that the shoe locker is locked before placing an order.
[0043] FIG. 6 is a flowchart illustrating the accounting process. When the user presses the checkout button (e.g., displayed on a touch panel) on the ordering terminal 20, a checkout identification code (e.g., a barcode or QR code (registered trademark)) for payment is generated and displayed on the screen (C1). The generated barcode may have an expiration date. The user opens a screen for code payment on the smartphone 10 and completes the payment by scanning the checkout identification code of the ordering terminal 20 (C2, C3). The smartphone 10 sends a payment completion notification to the ordering terminal 20 (C4), and the ordering terminal 20 displays a payment completion screen (C5). In response to the completion of payment on the ordering terminal 20, the management server 50 saves the status of payment completion in the database (C6, C7). The management server 50 then instructs the opening and closing control device to unlock the shoe locker (C7, C8). In response, the opening and closing control device unlocks the corresponding shoe locker 60 (C9). This allows the customer to remove their shoes from the shoe locker 60 after completing the payment. Various sensors inside the shoebox confirm that there is nothing inside the shoebox (i.e., shoes have been removed) (C10). After receiving a signal from the shoebox 60, the management server 50 changes the status of the shoebox that was in use from in use to empty, and saves this in the database (C11, 12).
[0044] FIG. 7 is a flowchart illustrating the member addition process. A customer currently in the store uses an app on smartphone 10 to register the number of customers to be added as group members (D1). In response to the registration using the app on smartphone 10, management server 50 issues passwords to smartphone 10 for the number of registered customers (D3, D4). The passwords may have an expiration date. Using smartphone 10, the customer shares the reception number and password with each additional smartphone of the other members to be added (for example, smartphones 10a, 10b, 10c, etc.) (D5, D6).
[0045] The shared member enters the reception number and password using the app on his / her smartphone 10a (D7). The management server 50 registers the additional member of the group in the database (D8, D9). When the additional member visits the store, the app on the additional smartphone 10a requests information on available shoe lockers (D11). The additional smartphone 10a communicates with the management server 50 and obtains the usage status of the shoe locker from the server 50's database (D12, D13). The management server 50 communicates with the opening / closing control device of the shoe locker 60 and checks the usage status of the shoe locker 50 (for example, locked or unlocked, whether shoes are present) (D14, D15, D16). By obtaining the usage status of the shoe locker 50 from the management server 50, the additional smartphone 10a displays available shoe lockers for selection (D161, D17). The additional member uses the app on the additional smartphone 10a to select the shoe locker he / she wants to use from the available shoe lockers (D17). Upon receiving shoebox selection information from the additional smartphone 10a, the management server 50 changes the selected shoebox 60 to an in-use status and saves the shoebox (e.g., shoebox location, number, shoebox ID) in the database (D171, D18). The management server 50 then instructs the opening / closing control device to unlock the shoebox (D18, D19). Note that if the shoebox door is open from the beginning, opening control by the management server 50 is not required. After the additional member places their shoes in the unlocked shoebox 60, various sensors in the shoebox 60 recognize that the shoebox door is closed (D20, D21). Upon recognizing that the shoebox door is closed, the management server 50 displays a lock button in the app on the additional smartphone 10a of the additional member (D211, D22). The user presses the lock button in the app on the additional smartphone 10a (D22). In response to this, the management server 50 controls the opening / closing control device of the shoebox 60 to lock the shoebox (D23, D231, D24). Upon receiving the locking status of the shoebox from the shoebox 60, the management server 50 stores the fact that the shoebox has been locked in the database (D25, D26).
[0046] In this way, with this system, customers can register additional members using an app on their smartphones, and then use the additional members' smartphones to lock the shoe lockers.
[0047] FIG. 8 is a flowchart illustrating the mid-transaction transaction process. When the customer presses the checkout button (for example, displayed on a touch panel) on the ordering terminal 20 and selects the shoebox of the member making the payment, a checkout identification code for payment is generated and displayed on the screen (E1). The person making the payment opens a screen for code payment on the smartphone 10b, and the camera on the smartphone 10b reads the checkout identification code displayed on the ordering terminal 20, completing the payment (E2, E3). For example, the smartphone 10b can communicate with an external payment management server to settle the bill. Another payment method is to display the bill on the screen, have the customer press the checkout button, and then have the camera on the ordering terminal 20 read the payment code generated by the smartphone's payment app to complete the payment.
[0048] The order terminal 20 receives notification from the external payment management server that the bill has been paid, and once the payment is complete, a payment completion screen is displayed, and the customer transmits the shoe locker number of the person who has left the checkout (E4, E5). When the management server 50 receives the shoe locker selection number of the person who has left the checkout from the order terminal 20, it uses the receipt number and shoe locker number as keys to change the payment status to complete and instructs the shoe locker to be unlocked (E7).
[0049] Upon receiving the unlock command, the opening / closing control device unlocks the shoe locker 60 (E9). After the customer who has finished paying removes their shoes from the shoe locker, various sensors confirm that there is nothing inside the shoe locker (E9). The management server 50 changes the status of the shoe locker that was in use from in use to empty (E10, E11).
[0050] In this way, a person who is paying midway through the transaction can use their smartphone to split the bill and complete the transaction.
[0051] Figure 9 is a diagram explaining how to order items in a group. Each time one of the customers orders an item, they can specify who will eat how much by specifying the corresponding shoebox. It is possible to select one shoebox to be linked to an item, but it is also possible to select two or more. Also, if two or more people are sharing one dish, by inputting the portion of the dish each customer will eat on the ordering terminal 20, the amount to be paid can be calculated in detail according to that portion. By linking all dishes to each shoebox corresponding to the customer, it is also possible to calculate the amount to be paid for each individual dish. Also, if there are two or more dishes for one customer (shoebox), the amount to be paid is added up in the database. The amount of the dishes is calculated on the ordering terminal 20.
[0052] FIG. 9 shows an example of the screen of an ordering terminal when ordering food. For example, let us consider the case where one salad (1,000 yen) is to be shared among three customers. In the ordering terminal 20, the customers input 50% for No. 3 (shoebox number), 20% for No. 8 (shoebox number), and 30% for No. 10 (shoebox number). Based on these percentages, the order price of the salad (1,000 yen) is calculated and the price is calculated as 500 yen for No. 3, 200 yen for No. 8, and 300 yen for No. 10. Each amount is saved in the database. For the other dishes, the percentage is similarly input for each customer (shoebox number), and the price for each dish is calculated based on the percentage. Finally, the total price is calculated.
[0053] In this way, the total amount can be calculated for each customer (shoe locker), so each customer can complete the payment individually, remove their shoes from their shoe locker, and leave the store, as explained in Figure 8.
[0054] 10, 11, and 12 are diagrams for explaining how to register the databases. These databases can be stored in the management server.
[0055] Figure 10 shows an example of the database at the time of entry. Specifically, Figure 10 shows the database after a group of five people enters the store, checks in using one smartphone at table number (No. 16), selects five shoe lockers, and places their shoes in them, but before ordering any products. The status of each shoe locker is shown as "locked" because each person's shoes are stored in the locker and locked. Payment types include bulk payment and individual payment, but "individual payment" is selected in Figure 10. Bulk payment is when one customer in the group pays the bill for everyone. Individual payment is also called split payment, and each customer pays their own amount. Note that once bulk payment is complete, the shoe lockers for all customers in the group can be unlocked.
[0056] Figure 11 shows an example of the database when a member is added. Specifically, Figure 11 shows the database when a group of five people enters the store, checks in using one smartphone, selects five shoe lockers, and then one new customer is added during the process. The newly added customer enters the "reception number" on their smartphone and selects shoe locker (No. 6). The newly added customer puts their shoes in the corresponding shoe locker and locks it, so the shoe locker status is shown as "locked," but because they have not yet ordered any products, the amount remains blank.
[0057] Figure 12 shows an example of a database after individual payments. Specifically, Figure 12 shows the database when a group of five people enters a restaurant, checks in using one smartphone, selects five shoe lockers and places their shoes in them, then one new person joins while they are eating, after which another person pays and leaves the restaurant. After the first person completes their payment, they use their own smartphone to individually complete the payment using their payment identification code, put on their own shoes, and leave the restaurant, so the corresponding payment status for shoe locker (No. 4) is shown as "Completed," and the shoe locker status is shown as "Open." Note that the other customers remain in the restaurant, so their payment status is shown as "Not yet," and the shoe locker status is shown as "Locked."
[0058] Although the present disclosure has been described above with reference to the embodiments, the present disclosure is not limited to the above-described embodiments. Various modifications that can be understood by those skilled in the art can be made to the configuration and details of the present disclosure within the scope of the present disclosure. Furthermore, each embodiment can be combined with other embodiments as appropriate.
[0059] Each drawing is merely an example for describing one or more embodiments. Each drawing may relate not only to one particular embodiment, but also to one or more other embodiments. As will be understood by those skilled in the art, various features or steps described with reference to any one drawing can be combined with features or steps shown in one or more other drawings to create, for example, an embodiment not explicitly shown or described. Not all features or steps shown in any one drawing are necessary to describe an exemplary embodiment, and some features or steps may be omitted. The order of steps described in any drawing may be changed as appropriate.
[0060] In the above examples, the program includes instructions (or software code) that, when loaded into a computer, cause the computer to perform one or more functions described in the embodiments. The program may be stored on a non-transitory computer-readable medium or a tangible storage medium. By way of example and not limitation, computer-readable medium or tangible storage medium includes random-access memory (RAM), read-only memory (ROM), flash memory, solid-state drive (SSD) or other memory technology, CD-ROM, digital versatile disc (DVD), Blu-ray® disc or other optical disk storage, magnetic cassette, magnetic tape, magnetic disk storage or other magnetic storage device. The program may also be transmitted on a transitory computer-readable medium or communication medium. By way of example and not limitation, transitory computer-readable medium or communication medium includes electrical, optical, acoustic, or other forms of propagated signals.
[0061] A part or all of the above-described embodiments can be described as, but not limited to, the following supplementary notes. (Appendix 1) A table payment system for making table payments for one or more customers, A mobile terminal carried by each customer; An order terminal installed on the table in the store, a plurality of shoe lockers provided in the store and lockable by operating the mobile terminal; a management server that manages order information, the usage status of each shoebox, and payment information; Equipped with the mobile terminal acquires a reception number by registering the number of customers, the tables used by the customers, and the shoeboxes for each customer; After the sensor recognizes that the door of the shoe locker is closed, the customer operates the mobile terminal to lock the shoe locker; The order terminal displays an order screen using the acquired receipt number, orders products on the order screen, and then performs payment processing. The table-top payment system is configured so that the shoebox is unlocked upon completion of payment by the customer. (Appendix 2) The table payment system described in Appendix 1 is configured such that, if a customer leaves the store early among a group of multiple customers, the mobile terminal of the customer who leaves the store early processes the payment through the ordering terminal, and the shoe locker linked to the customer who leaves the store early is unlocked upon completion of the payment by the customer. (Appendix 3) The table payment system described in Appendix 1 is configured such that, when a latecomer is added midway through a transaction, the latecomer's mobile terminal acquires the reception number and password, adds the shoe locker information of the latecomer based on the reception number and password, and locks the shoe locker by operating the mobile terminal of the latecomer. (Appendix 4) On the order screen, set the payment percentage for each customer, The table payment system described in Appendix 1 or 2, wherein the amount of the ordered items is calculated for each customer according to the payment proportion of each customer, linked to each customer's shoebox number. (Appendix 5) The table-top payment system described in Appendix 1, wherein the mobile terminal displays available shoe lockers for selection. (Appendix 6) The table payment system described in Appendix 1, wherein the ordering terminal displays an order screen by reading a reception identification code associated with the acquired reception number displayed on the mobile terminal, and the customer orders products on the order screen. (Appendix 7) The table payment system described in Appendix 6, wherein the ordering terminal displays a transaction identification code associated with the product order, and performs payment processing when the transaction identification code is read by the mobile terminal. (Appendix 8) The table-top payment system described in Appendix 1 further includes a database including the reception number, the number of customers, the table number, the payment type including lump-sum payment and individual payment, the shoebox number of each customer, the order amount associated with the shoebox number, the payment status associated with the shoebox number, and the shoebox status associated with the shoebox number. (Appendix 9) A tabletop payment system including a mobile terminal carried by each customer, an ordering terminal installed at a table in the store, a plurality of shoe lockers installed in the store that can be locked by operating the mobile terminal, and a management server that manages order information, the usage status of each shoe locker, and payment information, in which a tabletop payment method is used when one or more customers visit the store, comprising: registering the number of customers, the tables used by the customers, and the shoe lockers for each customer using the mobile terminal to obtain a reception number; After the sensor recognizes that the door of the shoe locker is closed, the customer operates the mobile terminal to lock the shoe locker; Using the order terminal, an order screen is displayed using the acquired reception number, an order for the product is placed on the order screen, and then payment processing is performed; This is a table payment method in which the shoebox is unlocked upon completion of payment by the customer.
[0062] Some or all of the elements (e.g., configurations and functions) described in Supplementary Notes 2 to 8 that are dependent on Supplementary Note 1 may also be dependent on Supplementary Note 9 in the same dependency relationship as Supplementary Notes 2 to 8. Some or all of the elements described in any Supplementary Note may be applied to various hardware, software, recording means for recording software, systems, and methods. [Explanation of symbols]
[0063] 1. System to prevent eating and drinking without paying 10 Smartphone 10a, 10b additional smartphone 20 Ordering terminal 50 Management Server 60 shoe box
Claims
1. A table payment system for making table payments for one or more customers, A mobile terminal carried by each customer; An order terminal installed on the table in the store, a plurality of shoe lockers provided in the store and lockable by operating the mobile terminal; a management server that manages order information, the usage status of each shoebox, and payment information; Equipped with the mobile terminal acquires a reception number by registering the number of customers, the tables used by the customers, and the shoeboxes for each customer; After the sensor recognizes that the door of the shoe locker is closed, the customer operates the mobile terminal to lock the shoe locker; The order terminal displays an order screen using the acquired receipt number, orders products on the order screen, and then performs payment processing. The table-top payment system is configured so that the shoebox is unlocked upon completion of payment by the customer.
2. 2. The table payment system of claim 1, wherein, when a customer leaves a group of multiple customers, the mobile terminal of the customer performs payment processing through the ordering terminal, and the shoe locker associated with the customer is unlocked upon completion of payment by the customer.
3. 2. The table-top payment system according to claim 1, wherein when a late-arrival customer is added midway through a transaction, the mobile terminal of the late-arrival customer acquires the reception number and password, adds shoe locker information for the late-arrival customer based on the reception number and password, and locks the shoe locker by operating the mobile terminal of the late-arrival customer.
4. On the order screen, set the payment percentage for each customer, 3. The table-top payment system according to claim 1, wherein the price of the ordered items is calculated for each customer according to the payment rate of each customer, linked to each customer's shoebox number.
5. The table-top payment system according to claim 1 , wherein the mobile terminal displays available shoe lockers so that the user can select them.
6. 2. The table-top payment system according to claim 1, wherein the ordering terminal displays an order screen by reading a reception identification code associated with the acquired reception number displayed on the mobile terminal, and the customer orders products on the order screen.
7. 7. The table-top payment system according to claim 6, wherein the order terminal displays a transaction identification code associated with the product order, and performs payment processing when the transaction identification code is read by the mobile terminal.
8. 2. The table-top payment system of claim 1, further comprising a database including the reception number, the number of customers, the table number, a payment type including lump-sum payment and individual payment, the shoebox number of each customer, the order amount associated with the shoebox number, the payment status associated with the shoebox number, and the shoebox status associated with the shoebox number.
9. A tabletop payment system including a mobile terminal carried by each customer, an ordering terminal installed at a table in the store, a plurality of shoe lockers installed in the store that can be locked by operating the mobile terminal, and a management server that manages order information, the usage status of each shoe locker, and payment information, in which a tabletop payment method is used when one or more customers visit the store, comprising: registering the number of customers, the tables used by the customers, and the shoe lockers for each customer using the mobile terminal to obtain a reception number; After the sensor recognizes that the door of the shoe locker is closed, the customer operates the mobile terminal to lock the shoe locker; Using the order terminal, an order screen is displayed using the acquired reception number, an order for the product is placed on the order screen, and then payment processing is performed; This is a table payment method in which the shoebox is unlocked upon completion of payment by the customer.
Citation Information
Patent Citations
Restaurant pos system
JP2003006749A