Electronic payment systems and electronic payment methods

Abstract

The challenge is to provide customers with printed receipts using a simple system that is linked to electronic payments. [Solution] Stickers 23A and 23B, each bearing identification information to identify the location, are placed in each location where a user can use the service. In the electronic payment system 1A, the usage status of each location is detected by the usage status detection device 24. Each slave unit 20 placed in each location requests payment or receipt issuance using its own identification information. The master unit 10A executes payment or receipt issuance in response to the request of each slave unit 20. The management server 50A executes payment upon matching the identification information of the stickers 23A and 23B obtained from the user terminal 40 with the identification information obtained from the slave units 20 via the master unit 10A.

Description

Technical Field

[0001] The present invention relates to, for example, an electronic payment system and an electronic payment method.

Background Art

[0002] In restaurants such as restaurants and cafes, various technologies have been introduced to improve customer convenience. Among them, the table payment system is a system in which customers use their smartphones or tablets to complete orders and payments at the table without contacting employees, and has attracted attention.

[0003] Patent Document 1, which is an example of an electronic payment system, discloses a cashless food order system in a restaurant (hereinafter referred to as the "conventional system").

[0004] In the restaurant where this conventional system is introduced, on all the tables where the customers who come to the store sit, a label printed with a QR code (registered trademark) as a two-dimensional code in which the store number information of the store, the unique table number information for all tables, and the system address information are recorded in advance is pasted. When a customer who comes to the store reads the QR code (registered trademark) printed on the label using the QR code (registered trademark) reading function of their own smartphone, the system placed on the cloud and the customer's smartphone are linked through the Internet, and thereafter, the customer can use their own smartphone to follow the procedures executed by the system to place food orders and perform payment processing for the ordered food without going through the store clerk.

Prior Art Documents

Patent Documents

[0005]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0006] As mentioned above, conventional electronic payment systems offer customers the convenience of completing payments on the spot, but they have the problem of not being able to obtain a paper receipt immediately after the payment process. For this reason, there is a need for a system that can provide customers with a printed receipt through a simple mechanism linked to electronic payments.

[0007] Recently, it has become common for restaurants to place tablets on tables and allow customers to pay at the table. However, this requires restaurants to provide tablets at every table, which means that as the scale of the electronic payment system grows, the burden of capital investment increases.

[0008] This invention was made in view of the above background, and aims to provide an electronic payment system and electronic payment method that can provide customers with printed receipts through a simple mechanism linked to electronic payment. [Means for solving the problem]

[0009] To solve the above-mentioned problems and achieve the above objectives, one embodiment of the present invention is an electronic payment system that performs payment using a user terminal, comprising: a component placed at each location where a user can use the system and having identification information added to identify the location; a detection device that detects the usage status of each location; a slave unit placed at each location and requesting payment or receipt issuance using identification information that identifies itself; a master unit that executes payment instructions or receipt issuance in response to the request of the slave unit; and a management server that performs payment upon matching the identification information of the component obtained from the user terminal with the identification information obtained from the slave unit via the master unit, wherein the master unit issues a receipt when payment is completed by the management server.

[0010] Another embodiment of the present invention is an electronic payment system that performs payment using a user terminal, The system comprises: a component placed in each user-accessible location and bearing identification information to identify that location; a detection device for detecting the usage status of each location; a sub-unit placed in each location and requesting receipt issuance using its own identification information; a master unit that issues receipts in response to requests from the sub-units; and a management server that performs a comparison between the identification information of the component obtained from the user terminal and the identification information obtained from the sub-units via the master unit. The management server performs a comparison between the identification information of the component obtained from the user terminal and the identification information obtained from the sub-units via the master unit, and the master unit issues a receipt when it receives a matching result from the management server.

[0011] Another embodiment of the present invention is an electronic payment method that performs payment using a detection device, slave units, master units, a management server, and a user terminal connected to a network, wherein a component with identification information that identifies the location is placed at each location where a user can use the service, the detection device detects the usage status of each location, the slave units placed at each location request payment or receipt issuance from the master unit using the identification information that identifies the slave unit, the management server performs payment upon matching the identification information of the component obtained from the user terminal with the identification information obtained from the slave units via the master unit, and the master unit issues a receipt after the management server has completed the payment.

[0012] Another embodiment of the present invention is an electronic payment method that performs payment using a user terminal, wherein a component with identification information that identifies the location is placed at each location where a user can use the service, a detection device detects the usage status of each location, a slave unit placed at each location requests payment or receipt issuance from a master unit using identification information that identifies the slave unit, a management server compares the identification information of the component obtained from the user terminal with the identification information obtained from the slave unit via the master unit, and the master unit issues a receipt when it receives a matching result from the management server. [Effects of the Invention]

[0013] According to the present invention, it is possible to provide a customer with a receipt as a printed matter in a simple mechanism linked to electronic payment. Note that the effects described here are not necessarily limited, and any of the effects described in the present disclosure may be applicable.

Brief Description of the Drawings

[0014] [Figure 1] It is a block diagram showing a configuration example of an electronic payment system in the present invention. [Figure 2] It is a flowchart for explaining an operation example of the electronic payment system shown in FIG. 1. [Figure 3A] It is an explanatory diagram showing an example of use when the present invention is applied to table payment. [Figure 3B] It is an explanatory diagram showing an example of receipt issuance when the present invention is applied to table payment. [Figure 4A] It is an explanatory diagram showing an example of use when the present invention is applied to in-vehicle payment. [Figure 4B] It is an explanatory diagram showing an example of receipt issuance when the present invention is applied to in-vehicle payment. [Figure 5] It is a block diagram showing a modified example of the electronic payment system shown in FIG. 1. [Figure 6] It is a block diagram showing another modified example of the electronic payment system shown in FIG. 1. [Figure 7] It is a diagram showing a configuration example of a table payment system of the present invention. [Figure 8] It is a diagram showing a hardware configuration example of a management server. [Figure 9A] It is a diagram for explaining child unit QR management information. [Figure 9B] It is a diagram for explaining a specific example of child unit QR management information. [Figure 9C] It is a diagram for explaining parent unit-child unit management information. [Figure 10A] It is a diagram showing a hardware configuration example of a parent unit. [Figure 10B] It is a diagram showing a hardware configuration example of a terminal with a display. [Figure 11A]It is a diagram showing an example of the hardware configuration of the slave device. [Figure 11B] It is a diagram showing the appearance of the slave device and the QR code. [Figure 12] It is a diagram showing an example of the hardware configuration of the user terminal. [Figure 13A] It is a sequence diagram for explaining the operation of the table settlement system. [Figure 13B] It is a sequence diagram for explaining the operation of the table settlement system. [Figure 14A] It is a sequence diagram for explaining the operation of the table settlement system. ? [Figure 14B] It is a sequence diagram for explaining the operation of the table settlement system. [Figure 14C] It is a sequence diagram for explaining the operation of the table settlement system. [Figure 15A] It is a sequence diagram for explaining the operation of the table settlement system. [Figure 15B] It is a sequence diagram for explaining the operation of the table settlement system. [Figure 16] It is a diagram for explaining the use case. [Figure 17] It is a diagram for explaining the operation of the changer when updating the slave device QR management information. [Figure 18] It is a diagram for explaining the use case. [Figure 19] It is a diagram for explaining the use case. [Figure 20] It is a diagram for explaining the use case. [Figure 21] It is a diagram for explaining the use case. [Figure 22] It is a diagram showing the appearance of the slave device and the QR code. [Figure 23A] It is a diagram showing another configuration example of the table settlement system of the present invention. [Figure 23B] It is a diagram for explaining the operation example of the table settlement system shown in Fig. 23A.

Embodiments for Carrying Out the Invention

[0015] The embodiments of the present invention will be described below with reference to the drawings. In all the drawings of the embodiments, the same or corresponding parts may be denoted by the same reference numerals. In the following description, various types of information may be described using expressions such as "table" and "record," but these types of information may be represented by data structures other than these. When describing identification information, the expression "ID" will be used, but other expressions are possible. In the following description, the device may be used as the subject when describing processing, but the subject of the processing may be the CPU or the like instead of the device. <Summary of the Invention and Examples of its Application> The outline of the present invention will be explained with reference to examples of its application using Figures 1 to 6. First, Figure 1 will be used to explain an example of the configuration of the electronic payment system in the present invention. In the following explanation, "user terminal" refers to a mobile device such as a smartphone or tablet owned by the user, and "receipt" refers to a printed document that includes the meaning of a receipt and proves that payment has been made for goods or services.

[0016] Figure 1 shows an electronic payment system 1A that performs payments using a user terminal. In Figure 1, a user terminal 40 is shown as a typical example of a user terminal, and a slave unit 20 is shown as a typical example of a slave unit. The electronic payment system 1A consists of, for example, a master unit 10A, slave units, a POS terminal 30A connected to a payment service provider server 60, a management server 50A, a printer 80, etc., and each is connected to the others via wired or wireless communication.

[0017] Each table in a restaurant or each parking space in a parking lot, which are locations accessible to users, corresponds to the placement locations R1, R2, R3, etc. for each slave unit 20. The number of slave units 20 is equal to the number of placement locations R1, R2, R3, etc. In addition, at each placement location R1, R2, R3, etc. accessible to users, components with QR codes visibly attached as identification information for that location, namely stickers 23A and 23B, are installed. Sticker 23A has a QR code for payment, and sticker 23B has a QR code for receipt issuance. The QR codes on these stickers 23A and 23B are read by the user terminal 40, and the management server 50A executes the payment and receipt issuance processes.

[0018] Here, regarding QR codes, the payment QR code on sticker 23A and the receipt issuance QR code on sticker 23B will be described as containing the same information, except for the difference in their intended use, such as payment or receipt issuance. However, the handling of these codes may differ depending on whether a browser or an application is used on the user terminal 40.

[0019] For example, if a browser is used on the user terminal 40, the receipt issuance QR code can simply contain only the URL (Uniform Resource Locator) information that executes the process for issuing the receipt on the management server. In this case, data verification becomes possible by having the payment QR code read again when issuing the receipt. In this case, that is, when a browser is used, the payment QR code will contain the URL information that executes the process for payment in the management server table described later.

[0020] Furthermore, when using an application that links with the management server on the user's terminal (assuming prior installation), it is possible to use only one type of QR code for payment, rather than separating them into payment and receipt types. In this case, there is no need to scan a QR code with a URL attached for receipt issuance, simplifying the process.

[0021] Of course, the processing between QR codes, payment, and receipt issuance, as described above, is a design matter and can be modified in various ways.

[0022] Each user-accessible location R1, R2, R3, etc., is equipped with a usage status detection device 24 to detect user activity, and the detection data acquired from each detection is transmitted to the master unit 10A. In the case of a restaurant table, the usage status detection device 24 becomes a human presence sensor. Human presence sensors include infrared, ultrasonic, image (camera), and touch types. In the case of a parking lot, the usage status detection device 24 becomes a vehicle detection sensor. Vehicle detection sensors include loop coil, ultrasonic, microwave, optical, far-infrared, image (camera), vibration power generation, and radar types.

[0023] Each user-accessible location R1, R2, R3, etc., is equipped with a slave unit 20 that uses its own identifying information to request payment or receipt issuance. The master unit 10A performs payment or receipt issuance in response to the request of each slave unit 20.

[0024] When the instruction unit 22 of each slave unit 20 is operated by the user, the master unit 10A sends detection data as a settlement request to the POS terminal 30A in response to the settlement request from the operated slave unit 20, and obtains the settlement amount from the POS terminal 30A. The master unit 10A then executes the settlement.

[0025] The management server 50A then performs a settlement on the master unit 10A by matching the identification information (sticker 23A) obtained from the user terminal 40 with the identification information obtained from the master unit 10A via a network (not shown). Here, the identification information obtained from the master unit 10A includes the master unit ID and the child unit ID along with the settlement request data. The master unit 10A also transmits the settlement amount along with the identification information.

[0026] Furthermore, after payment is completed, the master unit 10A, in the same manner as during payment, will print a receipt using the printer 80 based on the payment amount in response to a receipt issuance request from the operated slave unit 20 if the instruction unit 22 of each slave unit 20 is operated by the user. In this way, the master unit 10A controls receipt issuance when payment is completed. The management server 50A then, via a network not shown, checks and matches the identification information (sticker 23B) obtained from the user terminal 40 with the identification information obtained from the master unit 10A, and instructs the master unit 10A to issue a receipt. Here, the identification information obtained from the master unit 10A includes the master unit ID and slave unit ID along with the receipt issuance request data.

[0027] In the case of sticker 23A, a payment QR code is attached. Therefore, the identification information read from that payment QR code indicates the location ID (QRID) used by the user and the sub-unit ID that identifies the sub-unit 20 associated with that location, used for payment. In the case of sticker 23B, a receipt issuance QR code is attached.

[0028] The identification information read from the receipt-issuing QR code includes the location ID (QRID) used by the user and the device ID that identifies the device associated with that location, as information used for receipt issuance. Of course, the receipt-issuing QR code may also be used as the URL for accessing the management server 50A for receipt issuance.

[0029] In the case of table payment, the location is the table, and the information associated with it is the location ID and sub-unit ID associated with the table. In addition to the table number, this table may also have additional information to identify the location, such as an address. In the case of vehicle room payment, the location is the vehicle room, and the information associated with it is the location ID and sub-unit ID associated with the vehicle room. In addition to the vehicle room number, this vehicle room may also have additional information to identify the location, such as an address.

[0030] Figure 1 shows an example where the management server 50A is connected to an external payment service provider server 60 via a network. The payment service provider server 60 executes cashless payments in response to payment requests from the management server 50A.

[0031] Next, the configuration shown in Figure 1 will be explained in more detail. The user terminal 40 consists of an input / output unit 41, a control unit and a communication unit (not shown), etc. The input / output unit 41 includes, for example, a touch panel for text input, screen display, and various operations, as well as a camera function for reading subjects such as QR codes.

[0032] The user terminal 40 reads the QR code with the input / output unit 41 via the network and sends the acquired identification information as verification data to the management server 50A, and obtains the verification result (result notification) from the management server 50A.

[0033] Furthermore, in this invention, in addition to QR codes, NFC (Near Field Communication) tags can also be used for payment and receipt issuance. In this case, NFC tags are installed instead of stickers 23A and 23B. Therefore, the input / output unit 41 of the user terminal 40 is equipped with a communication function to read NFC tags.

[0034] The slave unit 20 consists of a control unit 21 that controls the entire system with components such as a CPU, ROM, and RAM, an instruction unit 22 that has buttons to detect user presses, and a communication unit (not shown). The instruction unit 22 sends a payment request and a receipt issuance request to the management server 50A as verification data, along with a slave unit ID that identifies the slave unit 20, in the order of payment and receipt issuance.

[0035] The master unit 10A consists of a control unit 11 that controls the entire system using components such as ROM and RAM, a payment and receipt processing unit 12A, a printing processing unit 13A, an input / output unit 15 that communicates with the user terminal 40, and a communication unit (not shown). The input / output unit 15 reads a QR code containing receipt information displayed on the screen of the user terminal 40, and the payment and receipt processing unit 12A instructs the printing processing unit 13A to issue a receipt based on that receipt information.

[0036] When the payment and receipt processing unit 12A receives payment request data and a child unit ID from each child unit 20, it sends the payment request, the payment amount already obtained from the POS terminal 30A, its own identifying master unit ID, and the child unit ID obtained from the child unit 20 to the management server 50A, and receives a result notification indicating whether the payment is approved or not. The payment and receipt processing unit 12A stores the result in the control unit 11: payment OK if the result notification indicates payment is approved, and payment NG if the result notification indicates payment is not approved.

[0037] Here, when the master unit 10A receives payment request data and a slave unit ID from the slave unit 20, it sends the payment request and detection data received from the usage status detection device 24 to the POS terminal 30A and obtains the payment amount.

[0038] In the case of a restaurant, the POS terminal 30A confirms the table usage of a customer based on the detection data, and then performs a settlement process based on the items of food ordered and eaten by that user and their prices. Of course, if there is a discrepancy in the data received from the master unit 10A, the settlement unit 31 cannot complete the settlement, and a settlement failure message is sent to the master unit 10A.

[0039] Here is an example of the table payment settlement process described above. A user who has come to a restaurant sits down at a table and then operates the user terminal 40 to display the menu screen and order food. At that time, the user terminal 40 accesses the management server 50A, for example, via a URL printed on the menu or by scanning a QR code, to receive the menu data and display it on the screen.

[0040] Here, the control unit 51 provides menu data in response to access from the user terminal 40, accepts orders (order information) in response to requests for dishes displayed based on that menu data, associates the orders with the tables used by the user, and stores and manages settlement information based on the order information in memory. In this way, the control unit 51 accepts the user's orders each time until payment, and transmits the settlement information (information such as dishes and amounts) to the POS terminal 30A at the time of payment. The control unit 51 may also transmit settlement information to the POS terminal 30A each time it receives order information, even before payment.

[0041] In the case of a parking lot, the POS terminal 30A calculates the parking time of vehicles using the parking space based on the detection data, and then performs payment processing based on that parking time. Of course, if there is a discrepancy in the data received from the master unit 10A, payment cannot be made by the payment unit 31, and payment NG is returned to the master unit 10A. Of course, the above payment processing may also be handled by the control unit 51.

[0042] Furthermore, when the payment and receipt processing unit 12A of the master unit 10A receives the receipt issuance request data and the slave unit ID from the slave unit 30 after the payment is completed, it sends the receipt issuance request, the master unit ID that identifies itself, and the slave unit ID obtained from the slave unit 20 to the management server 50A and receives a result notification indicating whether or not the receipt can be issued. If the result notification indicates that the receipt can be issued, the payment and receipt processing unit 12A stores the result as "receipt issuance OK" in the control unit 11, and if the result notification indicates that the receipt cannot be issued, it stores the result as "receipt issuance NG".

[0043] If a receipt can be issued, the payment and receipt processing unit 12A instructs the printing processing unit 13A to print a receipt including the payment amount to the printer 80. The printing processing unit 13A then uses the printer 80 to print the receipt, and receipt T1 is printed out from the printer 80.

[0044] The management server 50A is composed of a control unit 51 that controls the entire system using components such as ROM and RAM, a verification unit 52, and a settlement determination unit 53, and is connected to user terminals 40 and master unit 10A via a network for communication.

[0045] Figure 1 illustrates a scenario where one master unit 10A is installed in a restaurant or parking lot. If the restaurant or parking lot has multiple locations, multiple master units 10A are connected to the management server 50A via the network.

[0046] The matching unit 52 compares the matching data consisting of the child terminal ID and the payment location ID received from the user terminal 40 with the matching data consisting of the payment request, the master unit ID and the child terminal ID received from the master unit 10A, and outputs the matching result to the subsequent payment determination unit 53.

[0047] The matching unit 52, although specific examples will be described later, stores a table in advance that separates the correspondence between the sub-unit ID, placement location ID, etc., for payment purposes and receipt issuance purposes. This allows the two sets of matching data to be compared and verified.

[0048] The settlement determination unit 53, in accordance with the verification result of the verification unit 52, notifies the settlement and receipt processing unit 12A and the user terminal 40 of the result notification, including information that the payment is possible, if the verification matches and the settlement determination of the settlement service provider server 60 has made the payment. On the other hand, if the verification does not match or the settlement service provider server 60 has made the payment impossible, the settlement determination unit 53 notifies the settlement and receipt processing unit 12A and the user terminal 40 of the result notification, including information that the payment is impossible. At this point, the settlement and receipt processing unit 12A reports the result notification to the slave unit 20.

[0049] The same procedure is followed for receipt issuance. The matching unit 52 compares the matching data consisting of the slave terminal ID and the location ID for receipt issuance received from the user terminal 40 with the matching data consisting of the payment request, the master unit ID and the slave terminal ID received from the master unit 10A, and outputs the matching result to the subsequent payment determination unit 53.

[0050] The settlement determination unit 53, in accordance with the verification result of the verification unit 52, notifies the settlement and receipt processing unit 12A and the user terminal 40 with a receipt issuance instruction in the result notification if the verification matches, while notifying the settlement and receipt processing unit 12A and the user terminal 40 with a receipt issuance instruction in the result notification if the verification does not match. The settlement and receipt processing unit 12A then reports the result notification to the slave unit 20.

[0051] Next, the operation will be explained using Figures 2, 3A, 3B, 4A, and 4B. Figure 2 shows an example of the operation of the electronic payment system shown in Figure 1, Figures 3A and 3B show an example of use when the present invention is applied to table payment, and Figures 4A and 4B show an example of use when the present invention is applied to in-car payment.

[0052] First, when the usage detection device 24 detects that a user has started using the device at one of the installation locations R1, R2, R3, etc. (step S21), the usage detection device 24 transmits detection data to the master unit 10A, and the master unit 10A recognizes that the user has started using the device (step S22).

[0053] In the case of table payment, as shown in Figure 3A, the usage detection device 24 detects when user BDY is seated. In this case, the payment and receipt processing unit 12A of the master unit 10A recognizes the start of table use and understands the usage status until payment is completed.

[0054] In this table payment process, the control unit 51 of the management server 50A transmits menu data for menu selection to the user terminal 40, and the user receives the order information through the order operation (step S50) on the user terminal 40. In this way, the menu provision process is executed (step S30). The management server 50A receives the order information from the user terminal 40 each time and manages the order information in association with the table number used by the user. Therefore, in order to enable the user terminal 40 to identify the table, code information such as a barcode or QR code that identifies the table in association with the dishes on the menu may be printed.

[0055] In the control unit 51, the order information managed in the menu provision process is transmitted to the POS terminal 30A as settlement information, with the table number associated with the dish and its price (step S31). The POS terminal 30A receives the settlement information and stores it in its memory (step S41).

[0056] Furthermore, in the case of parking space payment (time-based billing), as shown in Figure 4A, the vehicle CR is detected entering the parking space by the usage detection device 24. In this case, the payment and receipt processing unit 12A of the master unit 10A recognizes the start of parking use and starts recording the usage status (step S22). In this case of parking use, the payment and receipt processing unit 12A may calculate the parking time from the start and end times of use at the time of payment, or the POS terminal 30A may be configured to calculate the parking time.

[0057] Of course, even in the case of parking space payment, it is conceivable that the control unit 51 would take in the data necessary for settlement and transmit it to the POS terminal 30A. In this case, the control unit 51 would calculate settlement information from the time the vehicle entered the parking space, the elapsed parking time, and the time the vehicle exits the parking space, either directly or indirectly from the master unit 10A, based on the detection data from the usage status detection device 24, and transmit this information to the POS terminal 30A.

[0058] In this embodiment, the control unit 51 may be responsible for processing by the management server 50A.

[0059] Next, we will explain the rest of the table payment process. In the slave unit 20, as shown in Figure 3A, when a button operation is detected by the user BDY's hand HND in the instruction unit 22 (step S11), the instruction unit 22 transmits payment request data and the slave unit ID to the master unit 10A (step S12). In response to this payment request, the payment and receipt processing unit 12A of the master unit 10A first transmits the detection data along with the settlement request data to the POS terminal 30A (step S23). Accordingly, the settlement processing is started by the settlement unit 31 in the POS terminal 30A, and as a result, the payment amount is determined. The data of that payment amount is transmitted to the payment and receipt processing unit 12A (step S42).

[0060] The payment and receipt processing unit 12A transmits to the management server 50A, along with the payment amount data received from the POS terminal 30A, payment request data, its own master unit ID, and verification data consisting of the slave unit ID of the slave unit 20 that made the payment request (step S24).

[0061] The management server 50A enters a waiting state to receive verification data and settlement amounts from the master unit 10A, as well as verification data from the user terminal 40 (step S32).

[0062] As shown in Figure 3A, when the QR code on the sticker 23A is read by the input / output unit 41 on the user terminal 40 (step S51), identification information (sticker ID) including the child device ID and placement location ID is obtained from the QR code as verification data. Then, the user terminal 40 transmits this verification data to the management server 50A via the network (step S52).

[0063] In this way, the matching unit 52 of the management server 50A performs data matching using matching data from the master unit 10A and matching data from the user terminal 40. If the payment determination unit 53 obtains a matching result from the matching unit 52, it retrieves the payment amount data from the matching unit 52 and requests payment from the payment service provider server 60 based on that payment amount data.

[0064] In this way, if the payment determination unit 53 receives notification of successful payment from the payment service provider server 60, it sends the payment success determination result to the user terminal 40 and the payment and receipt processing unit 12A (step S33). Of course, if the matching unit 52 determines that there is a mismatch or if it receives notification of payment failure from the payment service provider server 60, it sends a result notification indicating payment failure to the user terminal 40 and the master unit 10A (step S33).

[0065] Further details regarding the payment process will be discussed later, but the following processing takes place between the management server 50A and the payment service provider server 60. The management server 50A requests authorization from the payment service provider server 60. When authorization is performed, the management server 50A sends the necessary authorization information, including information received from the user terminal 700 (such as information identifying the user), along with the request.

[0066] Returning to the explanation of the process, the payment and receipt processing unit 12A of the master unit 10A receives a payment result notification from the payment determination unit 53 of the management server 50A. If the result notification indicates a successful payment (YES route in step S25), a payment completion notification indicating a successful payment is sent to the slave unit 20 (step S26). If the result notification indicates a failed payment (NO route in step S25), the payment and receipt processing unit 12A, although not shown in the diagram, sends a payment completion result indicating a failed payment to the slave unit 20, and this process ends.

[0067] When the sub-unit 20 receives a payment completion notification indicating successful payment, it executes a termination process related to the payment (step S13), and for example, it accepts button operations for receipt issuance (operation of the instruction unit 22) for a certain period of time (step S14). If no button operations are performed within the specified period of time, this process ends.

[0068] In this case, if payment is made at the table, the staff member will either use the sub-unit 20 when clearing the table, or use a terminal (for example, a smartphone) that the staff member is carrying to perform the initialization process on the management server 50A and the control unit 51.

[0069] Furthermore, if a button operation is detected within a certain period of time (step S14), the receipt issuance operation will start in conjunction with the payment. At that time, a receipt issuance request is sent to the master unit 10A (step S15).

[0070] Specifically, as shown in Figure 3A, when the slave unit 20 detects a button operation (operation of the instruction unit 22) by the user BDY's hand HND (step S14), a receipt issuance request and the slave unit ID are sent to the master unit 10A (step S15). In response to the receipt issuance request, the master unit 10A sends the receipt issuance request, its own master unit ID, and the slave unit ID of the slave unit 20 that made the receipt issuance request as verification data to the management server 50A (step S27).

[0071] When the management server 50A receives verification data from the master unit 10A, the verification data on the user terminal 40 enters a waiting state (step S34). On the user terminal 40, as shown in Figure 3A, when the QR code on the sticker 23B is read by the input / output unit 41 (step S56), identification information (sticker ID) including the slave unit ID and placement location ID is obtained from the QR code and transmitted to the management server 50A via the network (step S57).

[0072] Here, since it is up to the user whether or not to request a receipt, after the user terminal 40 receives the result of successful payment from the management server 50A (step S53), a receipt printing operation screen is displayed on the screen (step S54). In the input / output unit 41, when the button BTN displayed on the screen shown in Figure 3B is tapped (step S55), a QR code is read as shown in Figure 3A as a receipt issuance request from the user.

[0073] In this way, the verification unit 52 of the management server 50A performs data verification between the verification data from the master unit 10A and the verification data from the user terminal 40, and the settlement determination unit 53 sends a notification to the master unit 10A and the user terminal 40 that permits receipt issuance if the verification matches (step S35). Of course, if the verification does not match, a notification that does not permit receipt issuance is sent to the slave unit 20 as well, and although not shown in the diagram, the process ends (step S35).

[0074] In table payment, if a receipt issuance permission notification is sent in step S35, the management server 50A, which already holds settlement information for completed payments, generates receipt information necessary for printing a receipt, such as the store name, receipt issuance time, ordered dishes and prices, in data format or QR code format and sends it to the user terminal 40 (step S36).

[0075] When the user terminal 40 requests receipt issuance, receipt information in data format or QR code format received from the management server 50A is transmitted to the master unit 10A, and a receipt issuance command is issued (step S58).

[0076] In the payment and receipt processing unit 12A of the master unit 10A, if a notification authorizing receipt issuance is received from the management server 50A and a receipt issuance instruction is received from the user terminal 40, the printer 80 will issue a receipt (print receipt) via the printing processing unit 13A (step S28), and a receipt issuance completion notification will be sent to the slave unit 20 and the user terminal 40 (step S29). If there is a mismatch in the verification, the process will terminate, so a detailed explanation of that will be omitted.

[0077] When the user terminal 40 receives notification of success or failure in receipt issuance, a message to that effect is displayed, and the process ends (step S59).

[0078] If the printer 80 is installed near the store entrance or cash register, the user can receive a receipt T11 issued from the printer 80, as shown in Figure 3B.

[0079] In this manner, table payment and receipt issuance are performed at restaurants. The same process is carried out for parking space payment and receipt issuance, so a detailed explanation will be omitted. In the case of parking space payment, as shown in Figure 4A, for example, a pole PL is installed in the parking space (location R1) where the vehicle CR is parked, and a sub-unit 20 with stickers 23A and 23B attached is mounted on it.

[0080] When a user requests payment, the QR code on sticker 23A is read, and when a receipt is requested, sticker 23B is read. In addition, the entry of a vehicle into the parking space (location R1) is detected by the usage status detection device 24, which is a sensor.

[0081] Therefore, in the case of time-based billing for parking space payments, when the usage detection device 24 detects the entry (start of use) of a vehicle at a designated location R1, R2, R3, etc. (step S21), detection data is transmitted from the usage detection device 24 to the master unit 10A, and the master unit 10A recognizes the start of use and begins measuring the time. Then, when payment is requested from the slave unit 20 to the master unit 10A by button operation, the time measurement ends and the usage time from the start to the end of use is calculated (step S22). In obtaining the payment amount in step S23, the master unit 10A transmits the usage time to the POS terminal 30A as the basis for settlement.

[0082] As shown in Figures 4A and 4B, receipt issuance is performed by tapping button BTN on the user terminal 40 and pressing a button on the instruction unit 22 of the slave unit 20. For example, as shown in Figure 4B, if a printer 80 is provided in the vending machine VDR, the user can receive a receipt T12 at the location of the vending machine VDR.

[0083] Next, we will explain modified examples using Figures 5 and 6. The overall configuration is the same as in Figure 1, so we will omit the illustration and explanation, and instead, we will explain the different configurations and functions using different numerals.

[0084] As shown in Figure 5, the electronic payment system 1B may be configured such that the payment and receipt processing unit 12B of the master unit 10B and the settlement unit 71 of the vending machine 70 are connected in a communicative manner, and the vending machine 70 issues a receipt T2 from the printer 80 with the payment amount. Of course, the electronic payment system 1B may also handle the payment process. Of course, conversely, a printer may be placed on the vending machine 70, and the electronic payment system 1B may issue receipts to that printer. Alternatively, the electronic payment system 1B described above may be attached to the vending machine 70 itself to issue receipts.

[0085] Furthermore, as shown in Figure 6, the electronic payment system 1C may be configured to include a printing unit 14 equivalent to a printer within the master unit 10C itself, and issue a receipt T3.

[0086] In this way, electronic payment can be provided to users at the location where they use it (such as a restaurant table or a parking space), and furthermore, it is possible to provide a printed receipt through a simple mechanism linked to the electronic payment on that user terminal.

[0087] In particular, in stores, there is no need to place an electronic payment tablet at each table, so the cost of capital investment in introducing an electronic payment system is low. This is because, since tablets for the electronic payment system are not required, the scale of the equipment does not increase in proportion to the number of tables, and the burden in terms of system maintenance is also reduced.

[0088] Furthermore, in the above explanation, two types of QR codes were used: a payment sticker ID and a receipt issuance sticker ID. This allows for processing by scanning each QR code once during payment and once during receipt issuance. Of course, even if the receipt issuance sticker ID QR code is used as the URL for receipt issuance, the payment sticker ID only needs to be scanned again when issuing the receipt, so there is no operational burden and the process is simple. In particular, when using a URL, there is no need for users to install a special application on their terminal, making it possible to achieve payment and receipt issuance with a simple configuration and no burden on the user.

[0089] Furthermore, regarding the usage detection device 24, in the case of table payment, if a sensor is not placed at each table, and user seating is detected by image processing using at least one camera, the equipment required to implement the electronic payment system will have fewer parts and be less expensive. Of course, the same applies to parking lots; if cameras can be used to individually detect vehicles entering each parking space, the equipment required to implement the electronic payment system will be fewer and less expensive.

[0090] Furthermore, in the example described above, stickers with QR codes were placed in locations used by users to facilitate electronic payment and receipt printing. However, as already mentioned, NFC tags using the near-field communication standard could be used as an alternative. In this case, too, the same benefits can be obtained through similar functionality as an electronic payment system. In this case, a smartphone equipped with an NFC reader would read the NFC tag.

[0091] Furthermore, by linking with purchasing devices such as vending machines, it becomes possible to settle payments for other services as well. This allows a single electronic payment system to handle electronic payments for different services offered on the premises, thus reducing the capital investment required for individual businesses.

[0092] Furthermore, regarding the interaction between the user terminal and the management server, the user terminal was previously configured to access a URL using a browser and execute the process. However, the present invention is not limited to this, and an application may be pre-installed on the user terminal to authenticate the user with the management server and execute the same process.

[0093] Furthermore, while two types of QR codes were used—one for payment sticker IDs and one for receipt issuance sticker IDs—similar operation and functionality can be achieved by using only one sticker ID to read the QR code. In this case, the system could use flag management to determine whether it is a payment step or a receipt issuance step, or it could have the user download an app to their terminal, which would then determine whether the QR code is being read as a payment sticker ID or a receipt issuance sticker ID and execute the appropriate process.

[0094] Furthermore, while the electronic payment system 1A in Figure 1 has a separate configuration for the management server 50A and the POS terminal 30A, the present invention is not limited to this configuration. The management server 50A may also be equipped with a POS processing unit that has the same functions as the POS terminal 30A. In this case, the processing of the POS terminal 30A shown in Figure 2 will be handled by the management server 50A.

[0095] Next, using Figures 7 to 23B, we will explain an application example using a table payment system as an example. Note that individual payments and receipt issuance at the installation location are also possible in places such as parking lots, bicycle parking areas, laundromats, and co-working spaces, and these fall within the scope of application of the present invention. In this case, the mechanism is the same as that of the table payment system described below, so individual explanations will be omitted. Furthermore, the explanation of POS terminals will be omitted in the following description. In addition, the following description will show an example where the user terminal performs payment and receipt issuance via a browser, so the QR codes for payment and receipt issuance will be attached to the payment sticker and receipt issuance sticker, respectively. <First Embodiment> A table payment system according to the first embodiment of the present invention will now be described. Figure 7 is a diagram showing an example configuration of the table payment system according to the first embodiment of the present invention. Hereinafter, as an example, three tables will be used, so there will be a total of three sub-units corresponding to each table, and a total of three payment stickers and three receipt-issuing stickers corresponding to each table. The payment stickers and receipt-issuing stickers will be attached to the corresponding sub-units, attached to the corresponding tables, or installed on plates.

[0096] As shown in Figure 7, the table payment system includes a management server 100, a master unit 200, a terminal with a display 300, slave units 400a, 400b, 400c, payment stickers 500a, 500b, 500c, receipt issuing stickers 501a, 501b, 501c, a payment service provider server 600, and a user terminal 700. Although not shown in the figure, the table payment system may also include a terminal for the administrator who manages the table payment system.

[0097] In this example, a table payment system is installed in store A, which is operated by restaurant operator X. Store A is equipped with a master unit 200, a terminal with a display 300, slave units 400a, 400b, 400c, payment stickers 500a (identification information QRID11Y), 500b (identification information QRID12Y), 500c (identification information QRID13Y), receipt issuing stickers 501a (identification information QRID11P), 501b (identification information QRID12P), 501c (identification information QRID13P), table A800A, table B800B, and table C800C.

[0098] Table A800A is equipped with a sub-unit 400a, a payment sticker 500a, and a receipt issuing sticker 501a; Table B800B is equipped with a sub-unit 400b, a payment sticker 500b, and a receipt issuing sticker 501b; and Table C800C is equipped with a sub-unit 400c, a payment sticker 500c, and a receipt issuing sticker 501c.

[0099] In addition, sub-units 400a, 400b, and 400c may be referred to as "sub-unit 400" when there is no need to distinguish between them. Payment stickers 500a, 500b, and 500c may be referred to as "QR500" when there is no need to distinguish between them. Receipt issuing stickers 501a, 501b, and 501c may be referred to as "QR501" when there is no need to distinguish between them. Tables A800A, B800B, and C800C may be referred to as "table 800" when there is no need to distinguish between them.

[0100] Furthermore, in the following, including in the diagrams and explanations, the QRID11Y of the payment sticker 500a and the QRID11P of the receipt issuing sticker 501a may be collectively referred to as QR11, the QRID12Y of the payment sticker 500b and the QRID12P of the receipt issuing sticker 501b may be collectively referred to as QR12, and the QRID13Y of the payment sticker 500c and the QRID13P of the receipt issuing sticker 501c may be collectively referred to as QR13.

[0101] The management server 100, the master unit 200, the payment service provider server 600, and the user terminal 700 are connected to each other via the network NW1, enabling communication between them. The master unit 200 and the multiple slave units 400a to 400c are connected to each other via low-power wireless communication using low-power wireless technology (such as PAN (Personal Area Network) or LPWA (Low Power Wide Area)). Note that, if the management server 100 is only to support table payment and receipt issuance at a single store, it may be connected via the network NW1 as shown in Figure 7, or it may be an integrated structure with the master unit 200 without using the network NW1. Even in this integrated structure, the master unit 200 is connected to the payment service provider server 600 via the network NW1.

[0102] Figure 8 shows an example of the hardware configuration of the management server 100. As shown in Figure 8, the management server 100 includes a non-volatile storage device 110 that can read and write data, a memory 120 (e.g., RAM), a CPU 130, an input / output interface 140, and a network interface 150. The CPU 130, storage device 110, memory 120, input / output interface 140, and network interface 150 are connected via a bus 160.

[0103] A device including a CPU 130, a storage device 110, memory 120, an input / output interface 140, a network interface 150, and a bus 160 may be referred to as an "information processing device." An information processing device may be a combination of multiple information processing devices or a virtual information processing device built on the cloud. The CPU 130 may be referred to as an "arithmetic unit."

[0104] The storage device 110 holds (stores) the program 111 and the database 112. The CPU 130 loads the program 111 stored in the storage device 110 into the memory 120. The CPU 130 then executes the program 111 loaded into the memory 120 to realize the various functions of the management server 100.

[0105] Database 112 includes child device QR management information 112a, master-child device management information 112b, and menu information 112c. Child device QR management information 112a and / or master-child device management information 112b may be referred to as "management information".

[0106] Figure 9A is a diagram illustrating the child device QR management information 112a. As shown in Figure 9A, the child device QR management information 112a includes child device ID 112a1, QRID 112a2 (QRIDs for the payment sticker and receipt issuance sticker), and related information 112a3 as columns for storing information (values). In the child device QR management information 112a, information corresponding to each column regarding the child device 400 and the QRIDs (QR11, QR12, QR13) used in conjunction with the child device 400 is associated with each other and stored as row-level information (records).

[0107] Specifically, the slave unit ID 112a1 stores the slave unit ID (slave unit identification information) for identifying slave unit 400. The QRID 112a2 stores the QRID (QR identification information) for identifying QR500 and QR501, respectively. The related information 112a3 stores related information. Related information is information related to slave units 400 and QR500 and QR501 that are associated with the slave unit ID and QRID, and is at least one of the following: table identification information, store identification information, and restaurant operator identification information.

[0108] The information (records) at the row level is sometimes referred to as "correspondence information." Correspondence information associates the identification information (slave unit ID, QRID) of each slave unit 400 and QR500 installed together on the table with store identification information indicating the store where the slave units 400 and QR500 and QR501 are installed, and restaurant business identification information indicating the restaurant business operator that manages the store where the slave units 400 and QR500 and QR501 are installed.

[0109] Figure 9B is a diagram illustrating a specific example of the slave QR management information 112a. The slave QR management information 112a in Figure 9B includes related information 112a3, which includes a table 112a4, a store 112a5, and a restaurant operator 112a6. Table 112a4 stores table identification information for identifying table 800. Store 112a5 stores store identification information for identifying a store. Restaurant operator 112a6 stores restaurant operator identification information for identifying a restaurant operator.

[0110] In the example shown in Figure 9B, each record has only one sub-unit ID and one QR ID set for payment and receipt issuance associated with the related information (table identification information, store identification information, and restaurant operator identification information). However, multiple sub-unit IDs and multiple QR IDs may be associated.

[0111] Figure 9C is a diagram illustrating the master-slave management information 112b. As shown in Figure 9C, the master-slave management information 112b includes master ID information 112b1, slave ID information 112b2, slave ID information 112b3, and slave ID information 112b4 as columns for storing information (values). The master-slave management information 112b stores information corresponding to each column regarding the master unit 200 and the multiple slave units 400 that perform low-power wireless communication with the master unit 200, with the information being associated with each other and stored as row-level information (records).

[0112] Specifically, the master unit ID information 112b1 stores master unit identification information (master unit ID "100") for identifying master unit 200. The slave unit ID information 112b2 stores identification information (slave unit ID "1") for identifying the first slave unit 400a. The slave unit ID information 112b3 stores identification information (slave unit ID "2") for identifying the second slave unit 400b. The slave unit ID information 112b4 stores identification information (slave unit ID "3") for identifying the third slave unit 400c.

[0113] Menu information 112c contains information about the menu items offered as part of the food and beverage services provided at the store.

[0114] Referring again to Figure 8, as mentioned above, the program 111 executed by the CPU 130 is loaded into memory 120, and data used by the CPU 130 when executing program 111 is temporarily stored there.

[0115] The input / output interface 140 is an interface for connecting operating devices such as a keyboard and mouse, as well as a display. The network interface 150 is an interface for connecting the management server 100 to the network NW1.

[0116] Figure 10A shows an example of the hardware configuration of the master unit 200. As shown in Figure 10A, the master unit 200 has a CPU 210, memory 220, storage device 230, first communication unit 240, second communication unit 250, and third communication unit 260. The CPU 210, memory 220 (e.g., RAM), storage device 230, first communication unit 240, and second communication unit 250 are connected via a bus.

[0117] The CPU 210 loads the program stored in the storage device 230 into the memory 220. The CPU 210 executes various processes by running the program loaded into the memory 220. The storage device 230 is a non-volatile storage device that can be read from and written to. The storage device 230 stores (retains and holds) programs for controlling the master unit 200. The storage device 230 also stores slave unit management information 231. The slave unit management information 231 stores information necessary for communication with the slave unit 400. The storage device 230 also stores a master unit ID for identifying the master unit 200.

[0118] The first communication unit 240 is a communication interface used for communication with the slave unit 400. The second communication unit 250 is a communication interface used for communication with the external management server 100 via the network NW1. The second communication unit 250 is connected to the management server 100 via the network NW1. The third communication unit 260 is an interface for connecting to the terminal 300 with a display.

[0119] Figure 10B shows an example of the hardware configuration of a terminal with a display 300. As shown in Figure 10B, the terminal with a display 300 includes a CPU 310, memory 320, storage device 330, display 340, and communication unit 350.

[0120] The CPU 310 loads the program stored in the storage device 330 into the memory 320. The CPU 310 performs various processes by executing the program loaded into the memory 320. The storage device 330 stores programs for controlling the terminal 300 with a display, etc. The display 340 is a display device capable of displaying images. The communication unit 350 is a communication interface used for communication with the master unit 200.

[0121] Figure 11A shows an example of the hardware configuration of the slave unit 400. As shown in Figure 11A, the slave unit 400 includes a CPU 410, a memory 420, a storage device 430, a first communication unit 440, a button 450, a voice guidance unit 460, a buzzer 470, a light-emitting unit 480, and a battery device 490.

[0122] The CPU 410 loads the program stored in the storage device 430 into the memory 420. The CPU 410 executes various processes by running the program loaded into the memory 420. The storage device 430 stores programs for controlling the slave unit 400, etc. The storage device 430 is a non-volatile storage device that can be read from and written to. The storage device 430 stores (remembers, holds) programs, etc. The storage device 430 also stores master unit information 431. The master unit information 431 stores information necessary for communication with the master unit 200. The storage device 430 also stores a slave unit ID for identifying the slave unit 400.

[0123] The first communication unit 440 is a communication interface used for communication with the master unit 200. The button 450 is an operating device operated by the customer. The voice guidance unit 460 is a device that generates voice. The buzzer 470 is a device that generates a buzzer sound. The light-emitting unit 480 is a device that emits light (for example, an LED). The battery device 490 is a device for supplying power to the slave unit 400.

[0124] Figure 11B shows the appearance of the slave units 400a and QR500a, 501a as a representative example of a table. As shown in Figure 11B, the slave units 400a and QR500a, 501a are installed on the table 800a as a single unit. As will be described in detail in the second embodiment, the slave units 400a and QR500a, 501a may also be installed on the table 800a as separate units (see Figure 22).

[0125] QR500 is an information storage medium that stores information and allows that information to be read by a specific device (e.g., a user terminal 700). QR500 is an information storage medium on which a code, such as a two-dimensional code like a QR code (registered trademark), is printed on paper or similar material. QR500 stores information necessary for executing electronic payments, such as the location (URL) of the management server 100 and the payment service provider server 600 on the network NW1, and the QR500's identification information (QRID), as well as information necessary to identify the table 800 where the customer is located. Note that other information storage media, such as NFC tags capable of storing information, may be used instead of a QR code (registered trademark) for QR500. The QR500's identification information (QRID) and the NFC tag's identification information are sometimes referred to as "information storage medium identification information." QR501 is similar to QR500 except for its use in issuing receipts.

[0126] The payment service provider server 600 provides electronic payment services. The payment service provider server 600 can be configured with the same hardware configuration as the management server 100 shown in Figure 8.

[0127] Figure 12 shows an example of the hardware configuration of a user terminal 700. As shown in Figure 12, the user terminal 700 includes a CPU 710, a memory 720, a storage device 730, various sensors 740, a touch panel 750, a communication unit 760, an NFC communication unit 770, and an imaging unit 780. The CPU 710, memory 720, storage device 730, various sensors 740, touch panel 750, communication unit 760, NFC communication unit 770, and imaging unit 780 are connected via a bus. An example of a user terminal 700 is a smartphone.

[0128] The CPU 710 controls the operation of the user terminal 700. The CPU 710 loads programs stored in the storage device 730 into memory 720. The CPU 710 executes various processes by running the programs loaded into memory 720. The storage device 730 is a non-volatile storage device that can read and write data. The storage device 730 stores (retains) programs for controlling the user terminal 700 and applications for using electronic payment services.

[0129] The various sensors 740 include position sensors, geomagnetic sensors, distance sensors, acceleration sensors, and gyroscopes. These sensors enable the detection of the user terminal 700's position, orientation, direction of movement, motion, tilt, etc. The user terminal 700 may also be equipped with other sensors, such as illuminance sensors and proximity sensors.

[0130] The touch panel 750 is a display device that can display images and also functions as an input device.

[0131] The communication unit 760 is a communication interface that can be connected to the network NW1. Under the control of the CPU 710, the communication unit 760 communicates with external devices connected to the network NW1. For example, the communication unit 760 communicates with external devices such as the management server 100 and the payment service provider server 600.

[0132] The NFC communication unit 770 performs NFC communication when in close proximity to a compatible reader / writer. The NFC communication unit 770 is equipped with an encoding circuit, a decoding circuit, an antenna, and the like.

[0133] The NFC communication unit 770 reads information from the NFC tag via NFC communication.

[0134] The communication unit 760 may also include other communication units, such as a Bluetooth® communication unit or an infrared communication unit.

[0135] The imaging unit 780 is an imaging device equipped with an image sensor such as a CCD (Charge Coupled Device) or CMOS (Complementary MOS). For example, the imaging unit 680 is used to capture images of two-dimensional codes. In this case, the user terminal 700 reads information from the image of the two-dimensional code contained in the captured image.

[0136] Referring again to Figure 7, in a restaurant (store A) to which the table payment system according to the first embodiment is applied, a master unit 200 and a set of slave units 400 and QR codes 500 and 501 are installed. The set of slave units 400 and QR codes 500 and 501 is installed at each table 800. The management server 100 holds slave unit QR management information 112a which includes multiple records (correspondence information) in which the slave unit ID and QR ID are associated with related information.

[0137] In the table payment system, the sub-units 400 and QR codes 500 and 501 are installed at any location (tables A800A to C800C in the example in Figure 7), and table identification information indicating the installation location (table 800) is associated with the sub-units 400 and QR codes 500 and 501 in the sub-unit QR management information 112a. In the table payment system, customers can order food and beverages and make payments for food and beverage services at the location (table 800) where the sub-units 400 and QR codes are installed, without any contact with employees.

[0138] The detailed operation of the table payment system will be described later with reference to Figures 13A to 15B, but in the table payment system, the management server 100 identifies the table 800 (place where orders are placed and food and beverage services are received) where the customer is seated (the place where orders are placed and food and beverage services are received) based on the slave unit ID sent from the slave unit 400, the QR ID sent from the user terminal 700, and the slave unit QR management information 112a, and notifies the employee. The employee recognizes the table 800 where the customer to whom food and beverage services are to be provided is seated.

[0139] In the table payment system, the management server 100 sends the menu (menu information 112c) to the user terminal 700. By selecting from the menu displayed on the user terminal 700, the customer can order food and beverage services (dishes, drinks, etc.) from the menu.

[0140] In the table payment system, when a customer makes a payment, the management server 100 identifies the table 800 that the customer paid for based on the slave device ID sent from the slave device 400, the QR ID sent from the user terminal 700, and the slave device QR management information 112a, and notifies the staff that the table 800 has been paid for. Since the staff can recognize whether the table 800 where the customer received food and beverage service has been paid for or not, there is no need to confirm with the customer whether or not the payment has been made when the customer leaves the table.

[0141] In this way, the table payment system allows customers at a restaurant (store A) to order and pay at table 800 without any contact with employees. <Operation> Figure 13A is a sequence diagram illustrating the operation of the table payment system when a customer enters store A and sits down at table A800A. Figure 13A further illustrates the operation of the table payment system when, after the customer sits down at table A800A, the management server 100 identifies the table A800A where the customer is seated and makes it possible to place an order. The appropriate operation for placing an order is the operation of the sub-unit 400 (button operation) and the reading of the QR code 500 by the user terminal.

[0142] S501: Button 450 on handset 400 is operated by the customer.

[0143] S502: When button 450 is pressed, the sub-unit 400 transmits the sub-unit ID (sub-unit ID: 1) to the master unit 200.

[0144] S503: When the master unit 200 receives the slave unit ID (Slave Unit ID: 1) from the slave unit 400, it sends the slave unit ID to the management server 100.

[0145] S504: The user terminal 700 obtains the QRID (QRID:11Y) by reading it from the payment sticker 500a.

[0146] S505: When user terminal 700 obtains a QRID (QRID:11Y), it sends the QRID (QRID:11Y) to management server 100.

[0147] S506: When the management server 100 receives the child device ID (child device ID: 1) and QR ID (QR ID: 11Y), it refers to the child device QR management information 112a to identify the table identification information corresponding to the child device ID (child device ID: 1) and QR ID (QR ID: 11Y). In this example, the table identification information that indicates table A800A corresponding to child device ID: 1 and QR ID: 11Y is identified.

[0148] S507: When the management server 100 identifies the table identification information, it sends the identified table identification information (table A) and menu (menu information 112c) to the user terminal 700.

[0149] S508: The management server 100 transmits the identified table identification information (table A) and the child unit ID:1 received in S503 to the master unit 200.

[0150] S509: When the master unit 200 receives the identified table identification information (Table A) and the slave unit ID (Slave unit ID: 1), it sends a voice guidance command to the slave unit 400 indicated by the slave unit ID (Slave unit ID: 1).

[0151] S510: When the sub-unit 400 receives a voice guidance command, it provides voice guidance via the voice guidance unit 460. An example of voice guidance is, "Thank you for visiting. Please begin placing your order." The sub-unit 400 may also generate a buzzer sound using the buzzer 470 or illuminate the light-emitting unit 480, either in conjunction with or instead of voice guidance. In this case, the command may be referred to as a "guidance command."

[0152] S511: The master unit 200 transmits the identified table identification information (table A) to the terminal 300 with a display.

[0153] S512: When the terminal 300 with a display receives the identified table identification information (table A), it displays information on the display 340 indicating that a customer is seated at the identified table identification information (table A). By checking the display 340, the employee can recognize that the customer is seated at table 800 (table A800A).

[0154] Figure 13B is a sequence diagram illustrating the operation of the table payment system when a customer enters store A and sits down at table A800A. Figure 13B also illustrates the operation of the table payment system when the customer does not perform the appropriate steps to place an order after sitting down at table A800A.

[0155] Steps S501 through S503 are the same as those described in Figure 13B.

[0156] S513: Management server 100 has only received the child device ID (child device ID: 1), therefore it determines that the table cannot be identified.

[0157] S514: The management server 100 sends the warning and the child device ID (child device ID: 1) received in S513 to the master unit 200.

[0158] S515: When the master unit 200 receives a warning and a slave unit ID (Slave unit ID: 1) from the management server 100, it sends a voice guidance command to the slave unit 400 indicated by the slave unit ID (Slave unit ID: 1).

[0159] S516: When the sub-unit 400 receives a voice guidance command, it provides voice guidance via the voice guidance unit 460. An example of voice guidance is, "Thank you for visiting. Please scan the QR code on the table." The sub-unit 400 may also generate a buzzer sound using the buzzer 470 or illuminate the light-emitting unit 480, either in conjunction with or instead of voice guidance.

[0160] S517: The master unit 200 sends a warning to the terminal 300 with a display.

[0161] S515: When the terminal 300 with a display receives a warning from the master unit 200, it displays information on the display 340 indicating that the customer is not performing the correct operation. By checking the display 340, employees can recognize that the customer is not performing the correct operation.

[0162] Figures 14A and 14B are sequence diagrams illustrating the operation of the table payment system when a customer makes a payment for food and beverage services received at table A800A. Figures 14A and 14B illustrate the operation of the table payment system when the payment is completed by the customer performing the appropriate actions for payment at table 800A. The appropriate actions for payment include operating the sub-unit 400 (button operation) and reading the QR code 500 with the user terminal 700.

[0163] S521: Button 450 on handset 400 is operated by the customer.

[0164] S522: When button 450 is pressed, the sub-unit 400 sends the sub-unit ID (sub-unit ID: 1) and payment request to the master unit 200 (master unit ID: 100).

[0165] S523: When the master unit 200 receives the slave unit ID (Slave Unit ID: 1) and payment request, it sends the slave unit ID (Slave Unit ID: 1), master unit ID (Master Unit ID: 200), and payment request to the management server 100.

[0166] S524: The user terminal 700 obtains the QRID (QRID:11Y) by reading it from the payment sticker 500a.

[0167] S525: When user terminal 700 obtains a QRID (QRID:11Y), it sends the QRID (QRID:11Y) to management server 100.

[0168] S526: When the management server 100 receives the child device ID (child device ID: 1) and QR ID (QR ID: 11Y), it refers to the child device QR management information 112a to identify the table identification information (table A) corresponding to the child device ID (child device ID: 1) and QR ID (QR ID: 11Y), as well as the store identification information (A) and restaurant business identification information (X).

[0169] S527: The management server 100 requests authorization from the payment service provider server 600. Authorization is the process of determining whether electronic payment is permitted for a purchaser (user). Authorization is sometimes referred to as "authorization." When authorization is performed, the management server 100 sends the necessary information for authorization (such as the store identification information and restaurant business identification information identified in S527) and the necessary information for authorization received from the user terminal 700 (such as information identifying the user) along with the request.

[0170] S528: When the payment service provider server 600 receives an authorization request and the information necessary for authorization from the management server 100, it performs the authorization and sends the authorization result (information indicating whether electronic payment is possible or impossible) to the management server 100.

[0171] S529: When the management server 100 receives the authorization result, it sends the table identification information (table A), the authorization result, and the child device ID (child device ID: 1) to the master device 200.

[0172] S530: When the master unit 200 receives the table identification information (table A), authorization result, and slave unit ID (slave unit ID: 1), it completes the service settlement (payment of the fee for the service).

[0173] S531: When the master unit 200 completes the payment for the product, it sends a payment completion message (information indicating payment completion) to the slave unit 400, which is indicated by the slave unit ID (Slave unit ID: 1).

[0174] S532: The sub-unit 400 provides voice guidance via the voice guidance unit 460. An example of voice guidance is, "Payment has been completed." The sub-unit 400 may also generate a buzzer sound via the buzzer 470 or illuminate the light-emitting unit 480, either in conjunction with or instead of voice guidance.

[0175] S533: The master unit 200 transmits table identification information (Table A) and payment completion information (information indicating payment completion) to the terminal 300 with a display.

[0176] S534: When the terminal with display 300 receives table identification information (table A) and payment completion information (information indicating payment completion) from the master unit 200, it displays information on the display 340 indicating that table A800A, indicated by the table identification information, has been paid for. By checking the display 340, employees can recognize that payment for the food and beverage services provided to the customer at table A800A has been completed.

[0177] Now, we will insert an explanation of receipt issuance. Figure 14C is a sequence diagram illustrating the operation of the table payment system when issuing receipts. Since we have already explained the overview of the operation using Figure 2, we will briefly explain it below. Note that the operations shown by dotted lines in Figure 14C are modified examples.

[0178] On the user terminal 700, the receipt issuance QR code 501 is read, and verification data to be sent to the management server 100 for receipt issuance is confirmed (step S1600). On the slave unit 400, when a button operation requesting receipt issuance by the user is detected (step S1601), a slave unit ID to identify the slave unit that made the receipt issuance request and the button operation is sent to the master unit 200 (step S1601).

[0179] In the master unit 200, in accordance with the receipt issuance request received from the slave unit 400, the received slave unit ID, its own master unit ID, and the receipt issuance request are sent to the management server 100 (step S1603). The management server 100 then refers to the data already stored and performs data verification of the issuance conditions for receipt issuance, confirming that the receipt issuance request is from a registered master unit and slave unit (step S1604).

[0180] If the result of step S1604 is a match, the management server 100 determines whether to grant permission to issue a receipt based on the sticker ID information received in step S1600 (step S1607).

[0181] If the management server 100 also obtains a result of a successful match, it generates and issues information regarding the receipt (receipt data or QR code data) for outputting the settlement result, i.e., the details (issuance of a receipt), to the master unit 200 (step S1608). The management server 100 sends the result to the master unit 200 according to whether it was a success or failure (step S1609).

[0182] Furthermore, if successful, the management server 100 sends the aforementioned receipt data or QR code data to the user terminal 700 as a result notification, in order to have the master unit 200 issue a receipt (step S1612). The master unit 200 notifies the slave unit 400 of the result received from the management server 100 (step S1610), and the slave unit 400 performs a notification (termination operation) in response to the result notification (step S1611).

[0183] When the user terminal 700 decides to proceed with receipt issuance, the receipt data received from the management server 100 is transmitted to the master unit 200 via communication, or a QR code displayed on the user terminal 700's display screen is read by the master unit 200 (step S1613). Once the master unit 200 receives the data necessary for receipt issuance, it instructs the printer 301 to issue the receipt (step S1614). The printer 3401 then prints the receipt according to the receipt issuance instruction (step S1616).

[0184] In this way, when the receipt issuance is complete on the master unit 200, the management server 100 is notified of the completion of printing (step S1615), and the master unit 200 itself performs a notification (step S1617).

[0185] Here, we will also touch upon variations. In the above explanation, the payment sticker and the receipt issuance sticker are paired and can be read at the user's location, i.e., on the table. Furthermore, the information read from each sticker alone is sufficient for verifying and deciding whether to proceed with payment and receipt issuance. Alternatively, the receipt issuance sticker contains only the information to instruct receipt issuance, and in both cases, the information from the payment sticker is used for payment and receipt issuance. In other words, the difference between payment and receipt issuance lies in the fact that when issuing a receipt, the information from both the receipt issuance sticker and the payment sticker is used.

[0186] Specifically, in Figure 14C, the user terminal 700 reads the receipt issuance QR code 501, and the sticker ID obtained from reading it is data that instructs receipt issuance. Therefore, the user terminal 700 further reads the sticker ID, including the master unit ID and slave unit ID, from the payment QR code 500 (step S1605), and the sticker ID obtained from reading the receipt issuance QR code 501 and the sticker ID obtained from reading the payment QR code 500 are sent to the management server 100 as verification data (step S1606).

[0187] On the management server, step 100 determines that the request is for receipt issuance based on the sticker ID of the receipt issuance QR code 501, and further determines whether or not to issue a receipt based on the sticker ID of the payment QR code 500 (step S1607).

[0188] Furthermore, regarding communication between the user terminal 700 and the master unit 200, the master unit 200 may either optically read the QR code or transmit and receive it via short-range wireless communication (NFC tag, etc.), and this technology can be implemented using publicly known technologies.

[0189] Next, using Figures 15A and 15B, we will explain the operation of the table payment system when payment becomes impossible due to the customer not performing the appropriate steps to make a payment at table 800. Figures 15A and 15B are sequence diagrams illustrating the operation of the table payment system when a customer makes a payment for food and beverage services received at table A800A.

[0190] Steps S521 through S523 are the same as those described in Figure 14A.

[0191] S610: The management server 100 has only received the child device ID (child device ID: 1) and has not received the QR ID. Therefore, it cannot refer to the child device QR management information 112a to identify the table identification information, store identification information, and restaurant identification information corresponding to the child device ID (child device ID: 1) and QR ID. In this case, the management server 100 does not send an authorization request to the payment service provider server 600 and the payment is not possible.

[0192] S611: The management server 100 sends a warning and the child device ID (child device ID: 1) received by S611 to the master unit 200.

[0193] S612: When the master unit 200 receives a warning and a slave unit ID (Slave unit ID: 1) from the management server 100, it commands the slave unit 400 indicated by the slave unit ID (Slave unit ID: 1) to send a voice guidance.

[0194] S613: When the sub-unit 400 receives a voice guidance command from the master unit 200, it provides voice guidance. An example of voice guidance is, "Payment could not be processed. Please try the payment operation again." In addition, the sub-unit 400 may generate a buzzer sound using the buzzer 470 or illuminate the light-emitting unit 480 along with or instead of providing voice guidance.

[0195] S614: The master unit 200 sends a warning to the terminal 300 with a display.

[0196] S615: When the terminal 300 with a display receives a warning from the master unit 200, it displays information on the display 340 indicating that table A800A cannot be settled.

[0197] As described above, the table payment system according to the first embodiment allows the association between the QR ID and the child device ID and the related information of the child device QR management information 112a held by the management server 100 to be changed. This allows restaurants to reuse sets of child devices 400 and QR 500, 501 at tables 800 within the store simply by changing the related information (table identification information) associated with the QR ID and child device ID, making it easy to adapt to changes in the table layout of the store and the substitution of child devices 400 and QR 500, 501. Furthermore, restaurants can easily adapt to changes in the number of child devices 400 and QR 500, 501 installed at tables 800.

[0198] Furthermore, even if the restaurant operator changes, the restaurant can easily adapt to a change in the restaurant operator by simply changing the related information (restaurant operator identification information) associated with the 400 and QR500 / 501 sets. This allows the 400 and QR500 / 501 sets to be reused by another restaurant operator.

[0199] Furthermore, even if a restaurant uses the 400 and QR500 / 501 units at a different location, they can easily reuse the 400 and QR500 / 501 sets at other locations simply by changing the associated information (store ID) linked to the 400 and QR500 sets. This makes it easy to adapt to changes in the locations where the 400 and QR500 / 501 units are used.

[0200] The following explains these effects using Use Cases 1 through 5 as examples. <Use Case 1> In store A, the layout of table 800 may be changed. For example, suppose the layout of table 800 shown in Figure 7 is changed to the layout of table 800 shown in Figure 16. In the layout of table 800 shown in Figure 16, tables A800A and B800B from Figure 7 are combined into a new table A800A1, and a set of sub-unit 400a and payment sticker 500a, and a set of sub-unit 400b and payment sticker 500b are installed on this new table A800A1. In other words, the set of sub-unit 400b and payment sticker 500b that was installed on table B800B in Figure 7 is reused on the new table A800A1.

[0201] In this case, the user who made the change updates the slave device QR management information 112a held by the management server 100 by inputting instructions to the management server 100 from the user's terminal (for example, an administrator terminal (not shown)), as shown in the flowchart of Figure 17.

[0202] Step 1205: The user making changes logs into the management server 100 via their terminal (for example, an administrator terminal (not shown)) connected to the management server 100 via network NW1.

[0203] Step 1210: The user making the change inputs a selection instruction for the child device QR management information 112a to be changed to the management server 100 via their terminal.

[0204] Step 1215: The user making the change inputs an editing instruction for the child device QR management information 112a to be changed to the management server 100 via the user's terminal (not shown). In this example, as shown in Figure 18, the management server 100 edits the child device QR management information 112a in accordance with the editing instruction to change the table identification information corresponding to the child device ID:2 before the change from "B" to "A".

[0205] Step 1220: The user making the changes inputs an instruction to the management server 100 to save the edited child device QR management information 112a via the user's terminal (not shown). The management server 100, in accordance with the instruction, saves the modified child device QR management information 112a to the management server 100's storage device 110 (updating the child device QR management information 112a before the change to the modified child device QR management information 112a).

[0206] Step 1225: The person making the changes logs out of the management server 100 via their terminal (not shown).

[0207] In this way, when a restaurant changes the layout of table 800 from the layout shown in Figure 7 to the layout shown in Figure 16, the management server 100 can simply update the slave device QR management information 112a according to the instructions entered from the user's terminal, and the set of slave device 400b, payment sticker 500c, and receipt issuing sticker 501c that was installed on table B800B can be reused on the new table A800A1. This allows restaurants to easily adapt to changes in table layouts. <Use Case 2> The restaurant operator managing store A may change. For example, suppose the restaurant operator managing store A changes from restaurant operator X, as shown in Figure 7, to restaurant operator Y. In this case, as shown in the flowchart in Figure 17, the management server 100 updates the child device QR management information 112a according to the instructions entered from the terminal of the person making the change. In use case 2, in step 1215, the management server 100 edits the restaurant operator to change from "X" to "Y", as shown in Figure 19.

[0208] In this way, when a restaurant operator changes from restaurant operator X to restaurant operator Y as shown in Figure 7, the management server 100 can simply update the slave device QR management information 112a according to the instructions entered from the terminal of the operator who made the change, and the multiple sets of slave devices 400 and QR500 that were installed on tables A800A to C800C can be reused by the new restaurant operator Y. This makes it easy for restaurants to respond to changes in their operator. <Use Case 3> The store where the set of sub-unit 400 and QR50 is used may change. For example, suppose the store where the set of sub-unit 400 and QR50 is used changes from store A to store B, as shown in Figure 7. In this case, as shown in the flowchart in Figure 17, the management server 100 updates the sub-unit QR management information 112a according to the instructions entered from the terminal of the person making the change. In use case 3, in step 1215, the management server 100 edits the store to change from "A" to "B", as shown in Figure 20.

[0209] In this way, when a restaurant changes the location where multiple sets of sub-units 400 and QR500,501 are used, from store A to store B, the management server 100 can simply update the sub-unit QR management information 112a according to the instructions entered from the terminal of the person making the change, and the multiple sets of sub-units 400 and QR500,501 that were used at store A can be reused at the new store B. This makes it easy for restaurants to respond to changes in the location where sets of sub-units 400 and QR500,501 are used. <Use Case 4> There are cases where the child units 400 and QR500,501 become unavailable. For example, suppose that in table A800A shown in Figure 7, at least one of the child units 400 and QR500,501 becomes unavailable. In this case, suppose there is a customer who has reserved table A800A, and table B800B is not scheduled to be used, so the use of table A800A must be prioritized. In this case, the person making the change installs the child unit 400 and QR500,501 set from table B800B into table A800A. As shown in the flowchart in Figure 17, the management server 100 updates the child unit QR management information 112a according to the instructions entered from the terminal of the person making the change. In use case 4, in step 1215, the management server 100 edits the table identification information corresponding to the child unit ID:2 before the change from "B" to "A", as shown in Figure 18.

[0210] In this way, if at least one of the sub-units 400 and QR500 becomes unusable, the restaurant can easily make a change by substituting it with another sub-unit 400 and QR500 or 501, simply by updating the sub-unit QR management information 112a. <Use Case 5> In some cases, two sets of child devices 400 and QR500,501 may be placed in a single table 800. For example, suppose two sets of child devices 400 and QR500,501 are placed in table A800A as shown in Figure 7 by adding one set of child devices 400 and QR500,501. In this case, as shown in the flowchart in Figure 17, the management server 100 updates the child device QR management information 112a according to the instructions entered from the user's terminal. In use case 5, in step 1215, the management server 100 edits to add a record that includes child device ID:4, QRID:14, table:A, store:A, and restaurant operator:X, as shown in Figure 21.

[0211] In this way, if a restaurant installs two sub-units (400 and QR500 / 501) on a single table (800), the person making the change can easily handle it by simply updating the sub-unit QR management information (112a). <Benefits of implementing the system> The table settlement system according to the first embodiment has the advantage of significantly reducing the lead time for system implementation compared to conventional technologies that require the placement of QR codes on tables to embed specific table identification information, as described below. This effect will be explained below using Use Case 6 as an example. <Use Case 6> In the table payment system according to the first embodiment, multiple sets of sub-units 400 and QR 500 can be prepared in advance for provision to restaurant operators. For example, when the table payment system is introduced to restaurant operator X's store A, the restaurant operator X is provided with the required number of sets of sub-units 400 and QR 500 and 501 from the multiple sets of sub-units 400 and QR 500 and 501 prepared in advance. The table payment system can be operated simply by registering the sub-unit identification information of the provided sub-units 400 and the identification information and related information of the QR 500 and 501 in the sub-unit QR management information 112a.

[0212] Conventional technology requires embedding specific information in the QR code, depending on the restaurant operator and store where the system is implemented. However, the table payment system according to the first embodiment does not require this; it is sufficient to simply register the ID of the pre-prepared and provided slave device 400, the QR IDs of QR codes 500 and 501, and related information in the slave device QR management information 112a.

[0213] Furthermore, for example, if the table payment system is to be introduced to a restaurant operated by a different restaurant operator than restaurant operator X, the required number of sets of sub-units 400 and QR500,501 will be provided to the other restaurant operator from a pre-prepared set of sub-units 400 and QR500,501. Even in this case, the table payment system can be operated simply by registering the sub-unit ID of the provided sub-unit 400 and the QRID and related information of the QR500,501 in the sub-unit QR management information 112a. <Effects> As described above, the table payment system according to the first embodiment allows customers to order food and beverages, make payments for food and beverage services, and issue (print) receipts without contact with employees at the location where the sub-unit 400 and QR 500, 501 are installed.

[0214] In the table payment system according to the first embodiment, the child units 400 and QR codes 500 and 501 are installed in any location (tables A800A to C800C in the example in Figure 7), and table identification information indicating the installation location (table 800) is associated with the identification information of the child units 400 and QR codes 500 and 501 installed in table 800 in the child unit QR management information 112a. Furthermore, the table payment system allows the association between the related information held by the management server 100 and the QR ID and child unit ID to be changed. As a result, the table payment system can reuse sets of child units 400 and QR codes 500 and 501 in tables 800 within the store simply by changing the related information (table identification information) associated with the QR ID and child unit ID, making it easy to respond to changes in the table layout in the store, substitutions of child units 400 and QR codes 501, and changes in the number of child units 400 and QR codes installed in table 800.

[0215] Furthermore, the table payment system can easily accommodate changes in restaurant operators, as it only requires updating the associated information (restaurant operator identification information) linked to the 400 and QR500 / 501 sets. This allows the 400 and QR500 / 501 sets to be reused by a different restaurant operator.

[0216] Furthermore, the table payment system allows the set of sub-units 400 and QR500 to be reused in a different store simply by changing the associated information (store identification information) linked to the set of sub-units 400 and QR500 / 501. This makes it easy to adapt to changes in the stores using the sub-units 400 and QR500 / 501.

[0217] The table payment system according to the first embodiment can significantly reduce the lead time for system implementation compared to conventional systems that require a QR code to be placed on the table to embed specific table information. <Second Embodiment> A table payment system according to a second embodiment of the present invention will now be described. The table payment system according to the second embodiment differs from the table payment system according to the first embodiment in that, as shown in Figure 22, the slave unit 400 and QR500,501 are installed separately on the table 800.

[0218] The following explanation will focus on these differences.

[0219] Figure 23A shows an example of the configuration of a table payment system according to the second embodiment. As shown in Figure 23A, the table payment system has the slave unit 400 and QR500,501 installed separately on the table 800.

[0220] When the sub-unit 400 and QR500,501 are installed separately on table 800, due to vandalism or employee negligence, as shown in Figure 23B, the payment sticker 500b may be moved to table A800A and the payment sticker 500a may be moved to table B, resulting in payment stickers 500b and 500a not being installed on the correct table 800.

[0221] In this case, with the table payment system, when a customer sits down at table A and operates the sub-unit 400, the sub-unit ID 1 is transmitted from the sub-unit 400 to the management server 100 via the master unit 200. When the user terminal 700 reads the payment sticker 500b, the QR ID (QRID:12) is transmitted to the management server 100.

[0222] The management server 100 determines that, in the child device QR management information 112a in Figure 9B, there is no corresponding information (record) where the received child device ID (child device ID: 1) and QR ID (QR ID: 12) are associated, and therefore either the payment sticker 500a or the child device 400a is not placed in the correct table 800 (improper placement). In this case, the management server 100 sends a warning to the master device 200. Upon receiving the warning, the master device 200 displays a warning on the display 340 of the terminal with display 300 indicating that there is an improper placement of the payment sticker 500a and the child device 400a.

[0223] By checking the warning displayed on display 340, employees can recognize that either the payment sticker 500a or the sub-unit 400a is not placed on the correct table 800 and take action to correct the installation error. <Effects> As described above, the table payment system according to the second embodiment of the present invention has the same effects as the first embodiment. Furthermore, the table payment system according to the second embodiment can notify employees of improper installation of the sub-unit 400 and QR 500, 501 due to vandalism or employee negligence. <Variation> The present invention is not limited to the embodiments described above, and various modifications can be adopted within the scope of the invention. Furthermore, the embodiments described above can be combined with each other as long as they do not depart from the scope of the invention. In the embodiments described above, the store may be a mobile store.

[0224] In each of the above embodiments, the sub-unit 400 may be equipped with two buttons: a button for entering the store and sitting down, and a button for payment. In this case, the button for entering the store and sitting down is operated when the customer enters the store and sits down at a table 800, and the button for payment is operated when the customer makes a payment.

[0225] In each of the above embodiments, a QR code 500 for entry and seating and a QR code 500 for payment may be installed together with the sub-unit 400. The QR code 500 for entry and seating must be read by the customer using the user terminal 700 when entering and seating. The QR codes 500 for payment and receipt issuance must be read by the customer using the user terminal when making a payment.

[0226] In each of the above embodiments, the terminal with a display 300 may be a smartphone or tablet used by an employee.

[0227] It should be noted that the present invention is not limited to the embodiments described above, and various modifications are included. For example, the embodiments described above are described in detail for the purpose of clearly illustrating the present invention, and are not necessarily limited to those having all the configurations described. Furthermore, it is possible to replace some of the configurations of one embodiment with those of other embodiments, and it is also possible to add configurations from other embodiments to the configuration of one embodiment. In addition, it is possible to add, delete, or replace some of the configurations of each embodiment with those of other embodiments.

[0228] Furthermore, some or all of the above configurations and functions may be implemented in hardware, for example, by designing them as integrated circuits. Alternatively, the above configurations and functions may be implemented in software by having the processor interpret and execute programs that implement each function. Information such as programs, tables, and files that implement each function can be stored in memory, a recording device such as a hard disk or SSD (Solid State Drive), or a recording medium such as an IC card, SD card, or DVD. [Explanation of symbols]

[0229] 1A, 1B, 1C Electronic Payment System 10A, 10B, 10C, 10D Master Unit 11,21,51 Control Unit 12A, 12B Payment and receipt processing section 13A, 13B Printing Processing Unit 14 Printing Department 15,41 Input / output section 20 Handset 22 Instruction section 24. Usage Status Detection Device 30A, 30B POS terminals 31 Settlement Department 40 User terminals 50A, 50B Management Server 52 Verification section 53 Settlement Determination Unit 60 Payment service provider servers 70 Vending machines 71 Settlement Department 80 Printers

Claims

1. An electronic payment system that uses a user terminal to perform payments, A component placed in each user-accessible location, with identification information added to identify that location, A detection device for detecting the usage status of each location, Each of the aforementioned locations has a sub-unit that uses identification information to request payment or receipt issuance, A master unit that issues payment instructions or issues receipts in response to a request from the aforementioned slave unit, A management server that performs settlement by matching the identification information of the component obtained from the user terminal with the identification information obtained from the slave unit via the master unit, Equipped with, The aforementioned master unit is characterized by issuing a receipt when payment is completed by the management server.

2. An electronic payment system according to claim 1, characterized in that the management server has a table that stores the correspondence between identification information attached to the component and the identification information of the slave device.

3. An electronic payment system according to claim 2, characterized in that the management server changes the correspondence between the identification information in the table when the slave devices are moved or relocated.

4. An electronic payment system according to claim 1, characterized in that the identification information added to the member consists of two types: one for payment and one for receipt issuance.

5. An electronic payment system according to claim 1, characterized in that the identification information attached to the member includes a URL for distinguishing between payment and receipt issuance.

6. An electronic payment system according to claim 1, characterized in that the master unit is connected to an external POS (Point of Sales) terminal and acquires the payment amount in cooperation with the POS.

7. An electronic payment system according to claim 1, characterized in that the master unit is connected to a printer that prints receipts, and instructs the printer to print receipts to issue the receipts.

8. An electronic payment system according to claim 1, characterized in that the master unit has a printing unit that prints a receipt and performs receipt issuance.

9. An electronic payment system according to claim 1, characterized in that the master unit is connected to a vending machine and issues a receipt based on the settlement result of the vending machine.

10. An electronic payment system according to claim 1, characterized in that the master unit is connected to a vending machine equipped with a printer, and the printer is used to issue the receipt.

11. An electronic payment system according to claim 1, wherein the identification information added to the member is code information, and the user terminal reads the code information to obtain the identification information.

12. An electronic payment system according to claim 11, characterized in that the code information is a QR code.

13. An electronic payment system according to claim 1, wherein the component is an NFC (Near Field Communication) tag, and the user terminal reads the NFC tag to obtain the identification information.

14. An electronic payment system according to claim 1, characterized in that the detection device is a sensor placed at each location accessible to the user.

15. An electronic payment system according to claim 1, characterized in that the detection device is at least one camera.

16. An electronic payment system according to claim 1, wherein the sub-unit has buttons, and accepts the operation of the buttons to request payment or receipt issuance.

17. An electronic payment system according to claim 1, characterized in that each of the aforementioned locations is a table.

18. An electronic payment system according to claim 1, characterized in that each of the locations is a parking space in a parking lot.

19. An electronic payment system that uses a user terminal to perform payments, A component placed in each user-accessible location, with identification information added to identify that location, A detection device for detecting the usage status of each location, Each of the aforementioned locations has a sub-unit that requests receipt issuance using identification information that identifies itself, A master unit that issues a receipt in response to a request from the aforementioned slave unit, A management server that performs a comparison between the identification information of the component obtained from the user terminal and the identification information obtained from the slave unit via the master unit, Equipped with, The electronic payment system is characterized in that the management server compares the identification information of the component obtained from the user terminal with the identification information obtained from the slave unit via the master unit, and the master unit issues the receipt when it receives the result of the comparison from the management server.

20. An electronic payment system according to claim 19, characterized in that the management server generates receipt data for issuing the receipt when the matching result is a match, transmits the receipt data to the user terminal, and the master unit obtains the receipt data from the user terminal and issues the receipt.

21. An electronic payment system according to claim 20, characterized in that the data relating to the receipt is a QR code, and the master unit reads the QR code and issues the receipt.

22. An electronic payment system according to claim 19, characterized in that the master unit is connected to an external printer and the receipt is issued using the printer.

23. An electronic payment method that performs payment using detection devices, slave units, master units, management servers, and user terminals connected to a network, An electronic payment method characterized in that a component with identification information that identifies the location is placed in each location where a user can use the service, the detection device detects the usage status of each location, the slave unit placed in each location requests payment or receipt issuance from the master unit using the identification information that identifies the slave unit, the management server performs payment upon matching the identification information of the component obtained from the user terminal with the identification information obtained from the slave unit via the master unit, and the master unit issues a receipt after the management server has completed the payment.

24. An electronic payment method that uses a user terminal to perform a payment, An electronic payment method characterized in that a component with identification information that identifies the location is placed in each location where a user can use the service, the detection device detects the usage status of each location, the slave unit placed in each location requests payment or receipt issuance from the master unit using the identification information that identifies the slave unit, the management server compares the identification information of the component obtained from the user terminal with the identification information obtained from the slave unit via the master unit, and the master unit issues the receipt when it receives a matching result from the management server.

Images