Device, cash payment history information collection method, retrofit cashless payment unit, and application program

Abstract

To provide a device that prevents erroneous payments during use, reduces introduction costs and initial costs, enables grasping of sales information based on cash payments, and allows a cashless payment function to be easily and inexpensively introduced.SOLUTION: A retrofit unit 1 that is mounted in an add-on manner to a device capable of cash payment to add a cashless payment function includes a code display portion to which a printed sticker displaying a two-dimensional code symbol is attached. When a user terminal 6 reads the code symbol, pairing by short-range wireless communication is performed. A cashless control unit 2 transmits payment information including a payment amount to the user terminal, and a payment request is made to a payment server 5 via a device use support server 7 by a device application 6 on the user terminal. When normal completion of payment is transmitted to a short-range wireless communication unit 4 via the user terminal, the cashless control unit outputs a payment completion signal to a cashless output unit 3 with the same communication specifications as those used for confirmation of cash receipt by cash receipt confirmation units 81, 82, thereby enabling use of the device.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The invention of this application relates to cashless payment technology, and relates to technology that is particularly suitable for application to various devices that operate as devices that can only accept cash payments. [Background technology]

[0002] Among the devices used to provide goods or services, devices that handle cash payments are equipped with units such as coin mechanisms and bill validators. Coin mechanisms and bill validators are units that determine the authenticity of inserted cash (coins or banknotes) and, if genuine, count and output the quantity (amount inserted). Hereinafter, in this specification, the unit that confirms the amount of genuine cash inserted and outputs a signal representing that amount is referred to as a cash receipt confirmation unit. Cash receipt confirmation units usually have the function of dispensing change or refunds in the event of a cancellation.

[0003] Cash receipt confirmation units such as coin mechanisms and bill validators have a long history of being developed as technology to eliminate human intervention in payments. Cash receipt units are often installed in unmanned payment devices such as vending machines and ticket vending machines. Meanwhile, advances in IT have led to a remarkable spread of cashless technology. This influence has also extended to unmanned payment devices, and many newly developed and manufactured devices now enable cashless payment in addition to cash payment using a cash receipt confirmation unit. Hereinafter, in this specification, a device equipped with a cash receipt confirmation unit and capable of performing unmanned cash payment is referred to as a cash payment device. Note that this specification also discloses devices that have a cashless payment function but do not have a cash payment function, and when simply referring to a device, these are included. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Publication No. 2021-051436 [Patent Document 2] WO2022 / 191696A1 [Patent Document 3] WO2018 / 042669A1 [Patent Document 4] Special Publication No. 2008-505402 Summary of the Invention [Problem to be solved by the invention]

[0005] As mentioned above, an increasing number of newly developed and manufactured machines are being equipped with cashless payment functions. However, cash payment machines that were manufactured and sold in the past and are currently in operation still only accept cash payments. For example, let's say that the latest models of a certain type of cash payment machine are equipped with cashless payment functions. Businesses that have purchased older types of cash payment machines in the past feel that it would be more convenient for customers to accept cashless payments, but are often hesitant to introduce them because the cost of the current cash payment machine has not yet been amortized, or because they feel it is not reasonable to replace the current cash payment machine with an expensive cashless payment function when it is still usable.

[0006] One of the reasons businesses hesitate to introduce cashless payment systems is the running costs. Currently, to introduce cashless payment systems, devices must be equipped with communication functions to communicate with servers on the Internet, and communication costs are incurred as running costs. This makes businesses hesitant to introduce devices with cashless payment functions and operate their businesses.

[0007] On the other hand, manufacturers of cash payment machines often lack incentive to develop new machines with cashless payment functions if the market for the machines themselves is not large and sales volumes are not high. Examples of such machines that only accept cash payments include ticket vending machines, soft drink vending machines, payment machines in coin parking lots, unmanned kerosene vending machines, automatic rice polishing machines, massage machines, etc. In view of the above-described circumstances, the primary objective of the present invention is to provide practical technology that can reduce the running costs and initial costs involved in introducing cashless payment functions.

[0008] Another issue with unmanned operations using cash settlement machines is that it is not possible to grasp sales information such as when and how much sales were made. Only the sales amount for the cycle of collecting cash accumulated in the cash box in the cash receipt confirmation unit can be confirmed, but detailed sales information such as when and how much was made cannot be grasped. A second object of the present invention is to enable the understanding of cash sales information while reducing the cost of introducing cashless payment functions. [Means for solving the problem]

[0009] In order to solve the above problems, this specification discloses inventions for a device, a cash payment history information collection method, a retrofit cashless payment unit, and an application program. The device of the disclosed invention is a cashless payment device used by a user, and is equipped with a device control means for controlling the device, a short-range wireless communication unit that pairs with a user terminal, which is a mobile terminal operated by the user, to perform one-to-one short-range wireless communication, a code display unit, a payment information transmission unit, and a payment completion receiving unit. The code display unit is a display unit that displays a code including information for pairing. The short-range wireless communication unit is a communication unit that pairs with the user terminal in accordance with the code displayed by the code display unit when the device is not paired with another terminal, and does not pair with the user terminal when the device is paired with another terminal. The payment information transmission unit is a transmission unit that transmits payment information including a payment amount to the paired user terminal via the short-range wireless communication unit. The payment completion receiving unit is a receiving unit that receives the payment completion notification via the short-range wireless communication unit when the payment amount is transmitted and then the payment completion notification is sent from the paired user terminal. The device control means is a control unit that controls the device so that the user can use it after the payment completion receiving unit receives the notice that payment has been completed. The device control means includes: The device control means is a means for outputting a pairing cancellation signal to the short-range wireless communication unit, and the short-range wireless communication unit is a communication unit that cancels the pairing when the pairing cancellation signal is output from the device control means, except when the pairing has already been canceled by a request from the user terminal side. Furthermore, the device control means may be a means capable of controlling the output of a pairing cancellation signal to the short-range wireless communication unit after the payment completion receiving unit receives notification that payment has been completed and after use of the device has ended.

[0010] Another disclosed device according to the invention is a cashless payment device used by a user, and includes a device control means for controlling the device, a short-range wireless communication unit that pairs with a user terminal, which is a mobile terminal operated by the user, to perform one-to-one short-range wireless communication, a camera, a payment information transmission unit, and a payment completion receiving unit. In the device according to this other invention, the short-range wireless communication unit is a communication unit that, when the code symbol displayed on the display unit is read by the user terminal, pairs with the user terminal if the terminal is not currently paired with another terminal, and does not pair with the user terminal if the terminal is currently paired with another terminal. The device control means is a control means that, when the short-range wireless communication unit is not paired with another terminal, causes the short-range wireless communication unit to pair with the user terminal when a code symbol that symbolizes a code containing information necessary for pairing is displayed on the user terminal and the camera reads the code symbol.

[0011] In addition, the cash payment history information collection method according to the disclosed invention is a cash payment history information collection method that collects cash payment history information in a device that has a cash receipt confirmation unit that confirms that the cash inserted into a cash insertion slot is authentic and outputs a signal of the amount of cash received, and has the function of performing unmanned cash payments and the function of performing cashless payments. This method is a storage step in which, when a cash payment is made, the device stores cash payment information including the date and time of the cash payment in a storage unit provided in the device; a pairing step in which, when the user selects cashless payment, the device pairs with the user terminal operated by the user to enable short-range wireless communication; a payment step in which the device transmits the payment amount to the paired user terminal via short-range wireless communication, the user terminal transmits payment application information including the payment amount to the payment server, and the payment server executes a payment program to make the payment; a payment completion sending step in which, when the payment server returns payment completion information indicating that the payment has been successfully completed to the user terminal that sent the payment application information, the user terminal sends the payment completion information to the device via short-range wireless communication; a use step in which, after the payment completion signal is transmitted to the device, a device control means provided in the device controls the device to allow the user to use the device; It is equipped with: Then, in the pairing step, the device reads cash payment history information from the memory unit and transmits it via short-range wireless communication to the paired user terminal, and the cash payment history information is transmitted from the user terminal to the payment server or another server, so that the payment server or another server collects the cash payment history information.

[0012] In addition, the retrofit cashless payment unit of the disclosed invention is a retrofit cashless payment unit that adds cashless payment functionality to a cash payment device that has the function of performing unmanned cash payments, and is equipped with a cash receipt confirmation unit that confirms that the cash inserted into the cash insertion slot is authentic and outputs a signal of the amount of cash received. This retrofit cashless payment unit includes a cashless control unit, a cashless output unit, a short-range wireless communication unit that can be paired with a user terminal, which is a mobile terminal operated by the user, to perform short-range wireless communication, and a code display unit. The cashless control unit is provided in the housing of the cash settlement device and is connected in parallel to the cash receipt confirmation unit to a fee receipt input unit to which a signal from the cash receipt confirmation unit is input. The cashless output unit is positioned between the cashless control unit and the fee receipt input unit and outputs an output signal with the same communication specifications as the cash receipt output signal from the cash receipt confirmation unit. The code display unit is a display unit that displays a code including information necessary for pairing. The short-distance wireless communication unit is a communication unit that pairs with the user terminal according to the code displayed by the code display unit. The cashless control unit is a control unit that transmits payment information including the payment amount to the paired user terminal via the short-range wireless communication unit. The cashless control unit is a control unit that, after transmitting payment information, when the short-range wireless transmission unit receives a notification that payment has been completed from the paired user terminal, outputs a payment completion signal to the cashless output unit using the same communication specifications as the cash receipt confirmation by the cash receipt confirmation unit. In this add-on cashless payment unit, the code display unit may be a sticker on which a code symbol is printed, symbolizing a code containing information necessary for pairing.

[0013] Another disclosed invention relates to a retrofit cashless payment unit, which is a retrofit cashless payment unit that adds a cashless payment function to a cash payment device that has the function of performing unmanned cash payments and is equipped with a cash receipt confirmation unit that confirms that the cash inserted into the cash insertion slot is genuine and outputs a signal of the amount of cash received, and is equipped with a cashless control unit, a cashless output unit, a short-range wireless communication unit that can be paired with a user terminal, which is a mobile terminal operated by the user, to perform short-range wireless communication, and a camera. In this add-on cashless payment unit according to another invention, the near-field wireless communication unit is a communication unit that pairs with the user terminal according to the information contained in the code symbol when the camera photographs the code symbol displayed on the user terminal.

[0014] In addition, the application program of the disclosed invention is an application program installed on a user terminal operated by a user of the device of the invention or a device equipped with a retrofit cashless payment unit of the invention. This application program is a pairing program that performs pairing for near field wireless communication according to the code displayed on the code display unit; a payment application program that, after pairing is performed by the pairing program, when payment information is received from the short-range wireless transmission unit that is the pairing partner, transmits the payment information and causes the payment server to execute the payment program; a payment completion sending program that, after sending payment information by a payment application program and causing a payment server to execute the payment program, receives payment completion information indicating that the payment has been successfully completed and sends the payment completion information to the short-range wireless communication unit being paired; It is equipped with:

[0015] In addition, the application program relating to another disclosed invention is an application program installed on a user terminal operated by a user of an apparatus relating to the other invention or an apparatus equipped with a retrofit cashless payment unit relating to the other invention. This application program is a chord display program that displays chord symbols; a pairing program that, when the camera reads a code symbol displayed by the code display program, performs pairing with the near-field wireless communication unit in accordance with information included in the code symbol; a payment request program that, after pairing is performed by the pairing program, when payment information is received from the short-range wireless communication unit that is the pairing partner, transmits the payment information and causes the payment server to execute the payment program; a payment completion sending program that, after sending payment information by a payment application program and causing a payment server to execute the payment program, receives payment completion information indicating that the payment has been successfully completed and sends the payment completion information to the short-range wireless communication unit that is currently paired; It is equipped with:

[0016] Furthermore, a device according to yet another disclosed invention is a device that can be used by a user to make cashless payments, device control means for controlling the device; a short-range wireless communication unit that performs short-range wireless communication with a user terminal that is a mobile terminal operated by a user; A payment information transmission unit; Payment completion receiving unit and It is equipped with: the payment information transmission unit is a transmission unit that transmits payment information including a payment amount to the user terminal via the short-range wireless communication unit; the payment completion receiving unit is a receiving unit that, after the payment information is transmitted, receives a notice of payment completion from the user terminal that transmitted the payment information via the short-range wireless communication unit; The device control means is a control means that controls the user to use the device after the payment completion receiving unit receives the notice of payment completion. The payment information transmitted by the payment information transmitting unit includes a recipient ID or is provided with a code display unit that displays a code including the recipient ID. The recipient ID is an ID that identifies the recipient who allows a user to use the device and receives the fee related to the payment amount.When the user terminal that has received the payment information accesses the payment server, this ID is referenced when making a payment to the recipient identified by the recipient ID using prepaid money that has been paid and deposited in advance by the user operating the user terminal. Furthermore, a device according to yet another disclosed invention is a device that can be used by a user to make cashless payments, device control means for controlling the device; a short-range wireless communication unit that performs short-range wireless communication with a user terminal that is a mobile terminal operated by a user; A camera and A payment information transmission unit; a payment completion receiving unit; It is equipped with: the payment information transmission unit is a transmission unit that transmits payment information including a payment amount to the user terminal via the short-range wireless communication unit; the payment completion receiving unit is a receiving unit that receives, when a notice of payment completion is transmitted from the user terminal after the payment information is transmitted, the notice of payment completion via the short-range wireless transmitting unit; the device control means is a control means that controls the device so that the user can use the device after the payment completion receiving unit receives notification that payment has been completed; The device control means is a control means that, when the code symbol is displayed on the user terminal and the camera reads the code symbol, causes the payment information transmission section to transmit payment information to the user terminal. The payment information sent by the payment information sending unit includes a recipient ID in addition to the payment amount. The recipient ID is an ID that identifies the recipient who allows the user to use the equipment and receives the fee related to the payment amount. When the user terminal that received the payment information accesses the payment server, the ID is referenced by the payment server when making a payment to the recipient identified by the recipient ID using prepaid money that has been paid and deposited in advance by the user operating the user terminal. Furthermore, a retrofit cashless payment unit according to yet another disclosed invention is a retrofit cashless payment unit that adds a cashless payment function to a cash payment device that has a function of performing unmanned cash payments, and that includes a cash receipt confirmation unit that confirms that the cash inserted through the cash insertion slot is authentic and outputs a signal indicating the amount of the received cash, and A cashless control unit; a cashless output unit; a short-range wireless communication unit capable of performing short-range wireless communication with a user terminal, which is a portable terminal operated by a user; It is equipped with: the cashless control unit is provided in the housing of the cash settlement device and is connected in parallel to the cash receipt confirmation unit to a fee receipt input unit to which a signal from the cash receipt confirmation unit is input, The cashless output unit is interposed between the cashless control unit and the fee receipt input unit, and outputs an output signal in the same communication specifications as the output signal of cash receipt from the cash receipt confirmation unit; The cashless control unit is a control unit that transmits payment information including a payment amount to the user terminal via the short-range wireless communication unit, The cashless control unit is a control unit that, after transmitting the payment information, when the short-range wireless transmission unit receives a notification that the payment has been completed from the user terminal that transmitted the payment information, outputs a payment completion signal to the cashless output unit using the same communication specifications as the cash receipt confirmation by the cash receipt confirmation unit. The payment information sent by the cashless control unit includes a recipient ID or is provided with a code display unit that displays a code including the recipient ID. The recipient ID is an ID that identifies the recipient who allows the user to use the equipment and receives the fee related to the payment amount, and is an ID that is referenced by the payment server when the user terminal that received the payment information accesses the payment server and makes a payment to the recipient identified by the recipient ID using prepaid money that has been paid and deposited in advance by the user operating the user terminal. Furthermore, a retrofit cashless payment unit according to yet another disclosed invention is a retrofit cashless payment unit that adds a cashless payment function to a cash payment device that has a function of performing unmanned cash payments, and that includes a cash receipt confirmation unit that confirms that the cash inserted through the cash insertion slot is authentic and outputs a signal indicating the amount of the received cash, and A cashless control unit; a cashless output unit; a short-range wireless communication unit capable of pairing with a user terminal, which is a mobile terminal operated by a user, and performing one-to-one short-range wireless communication; Camera and It is equipped with: the cashless control unit is provided in the housing of the cash settlement device and is connected in parallel to the cash receipt confirmation unit to a fee receipt input unit to which a signal from the cash receipt confirmation unit is input, The cashless output unit is interposed between the cashless control unit and the fee receipt input unit, and outputs an output signal in the same communication specifications as the output signal of cash receipt from the cash receipt confirmation unit; The camera is capable of capturing an image of a code symbol when the code symbol is displayed on a user terminal, which is a mobile terminal operated by a user; the cashless control unit is a control unit that, when the camera reads the code symbol displayed on the user terminal, transmits payment information including the payment amount to the user terminal via the short-range wireless communication unit; The cashless control unit is a control unit that, after transmitting the payment information, when the short-range wireless transmission unit receives a notification that the payment has been completed from the user terminal that transmitted the payment information, outputs a payment completion signal to the cashless output unit using the same communication specifications as the cash receipt confirmation by the cash receipt confirmation unit. The payment information sent by the cashless control unit includes a recipient ID, which is an ID that identifies the recipient who allows the user to use the equipment and receives the fee related to the payment amount.When the user terminal that received the payment information accesses the payment server, this ID is referenced when making a payment to the recipient identified by the recipient ID using prepaid money that the user operating the user terminal has paid and deposited in advance. Furthermore, an application program according to yet another disclosed invention is an application program installed on a user terminal operated by a user of the device, a payment application program that, when receiving payment information from the short-range wireless transmission unit, transmits the payment information and causes the payment server to execute a payment program; a payment completion sending program that, after sending payment information by a payment application program and causing a payment server to execute the payment program, receives payment completion information from the payment server indicating that the payment has been successfully completed and sends the payment completion information to the short-range wireless communication unit; It is equipped with: The payment application program is a program that transmits the recipient ID sent from the payment information transmission unit or entered by the user to the payment server along with the payment amount, and executes payment to the recipient identified by the recipient ID using prepaid money that has been paid and deposited in advance by the user operating the user terminal. Furthermore, an application program according to yet another disclosed invention is an application program installed on a user terminal operated by a user of the device, a chord display program that displays chord symbols; a payment application program that, when receiving payment information from the short-range wireless communication unit after the code symbol displayed by the code display program is read by the camera, transmits the payment information and causes the payment server to execute the payment program; a payment completion sending program that, after sending payment information by a payment application program and causing a payment server to execute the payment program, receives payment completion information indicating that the payment has been successfully completed from the payment server and sends the payment completion information to the short-range wireless communication unit; It is equipped with: The payment application program is a program that can send the payment amount and recipient ID to the payment server and execute payment to the recipient identified by the recipient ID using prepaid funds that have been paid and deposited in advance by the user operating the user terminal. Furthermore, an application program according to yet another disclosed invention is an application program installed on a user terminal operated by a user of a device equipped with an add-on cashless unit, a code reading program for reading the code symbol displayed by the code display unit; a payment application program that, when receiving payment information from the short-range wireless communication unit after the code reading program reads the code symbol, transmits the payment information and causes the payment server to execute the payment program; a payment completion sending program that, after sending payment information by a payment application program and causing a payment server to execute the payment program, receives payment completion information from the payment server indicating that the payment has been successfully completed, and sends the payment completion information to the short-range wireless communication unit being paired; It is equipped with: The payment application program is a program that sends the recipient ID sent by the cashless control unit or entered by the user to the payment server along with the payment amount, and can execute payment to the recipient identified by the recipient ID using prepaid money that has been paid and deposited in advance by the user operating the user terminal. Furthermore, an application program according to yet another disclosed invention is an application program installed on a user terminal operated by a user of a device equipped with an add-on cashless unit, a chord display program that displays chord symbols; a payment application program that, when receiving payment information from the short-range wireless communication unit after the code symbol displayed by the code display program is read by the camera, transmits the payment information and causes the payment server to execute the payment program; a payment completion sending program that, after sending payment information by a payment application program and causing a payment server to execute the payment program, receives payment completion information from the payment server indicating that the payment has been successfully completed, and sends the payment completion information to the short-range wireless communication unit being paired; It is equipped with: The payment application program is a program that can send the payment amount and recipient ID to the payment server and execute payment to the recipient identified by the recipient ID using prepaid funds that have been paid and deposited in advance by the user operating the user terminal. [Effects of the Invention]

[0017] As described below, with the devices, add-on cashless payment units, and application programs according to the disclosed inventions, payment requests to a payment server are sent from the user's terminal, eliminating the need for the device to have network communication capabilities. This allows for cashless payments while reducing manufacturing and running costs. One-to-one short-range wireless communication is performed between the user's terminal and the device, and the device is not paired with another user's terminal while in use, preventing accidental payments from being made while in use. Furthermore, according to the add-on cashless payment unit of the embodiment, the above-described advantageous functions can be added to a device that only has a cash payment function, thereby improving the convenience of the device. This can promote sales of products or services through the device, and is expected to increase profits. In this case, there is no need to replace the device, so no large costs are required, which also contributes to increased profits. Furthermore, in the retrofit cashless payment units according to each invention, the cashless output unit outputs a cashless payment completion signal to the fee receipt input unit of the equipment using the same communication specifications as the output signal from the existing cash receipt confirmation unit, so there is basically no need to modify the fee receipt input unit of the equipment, and cashless payment functionality can be easily and inexpensively introduced.

[0018] Furthermore, the cash transaction history information collection method according to the disclosed invention has the advantage that when collecting cash transaction information on a device, the device does not need to have a network communication function. Therefore, there are no hardware costs or running costs (communication costs) for collecting cash transaction history information, and cash transaction history information can be collected at extremely low cost. The add-on cashless payment unit according to each of the disclosed inventions has the significance of being able to provide such an effect after the fact. In other words, it has the effect of making it possible to collect cash payment information that could not be collected before, and achieving this at low cost.

[0019] In addition, the disclosed device, add-on cashless payment unit, and application program according to another invention encourage users to deposit prepaid money with device operators, which is expected to contribute to the management of device operators. At this time, the recipient ID that identifies the device operator is transmitted to the server via the user terminal, thereby reducing the cost of transmitting the recipient ID. [Brief explanation of the drawings]

[0020] [Figure 1]1 is a schematic perspective view of a device equipped with a retrofit cashless payment unit according to a first embodiment. FIG. [Figure 2] A block diagram showing the general configuration of a device equipped with a retrofit cashless payment unit of the first embodiment. [Figure 3] 10 is a schematic diagram showing an example of the configuration of a cashless output unit and wiring when an add-on unit is installed. FIG. [Figure 4] 10 is a flowchart showing a schematic configuration of a main program on a cashless control unit. [Figure 5] 10 is a flowchart illustrating a schematic configuration of an application main program included in the application program according to the embodiment. [Figure 6] 3A to 3C are schematic diagrams illustrating screens displayed on a user terminal by an application program according to an embodiment. [Figure 7] 3A to 3C are schematic diagrams illustrating screens displayed on a user terminal by an application program according to an embodiment. [Figure 8] FIG. 10 is a schematic perspective view of a device equipped with a retrofit cashless payment unit according to a second embodiment. [Figure 9] 10 is a flowchart showing a schematic configuration of a unit main program in the second embodiment. [Figure 10] 10 is a schematic diagram illustrating the display of a terminal symbol in a device application according to a second embodiment. FIG. [Figure 11] FIG. 10 is a schematic diagram showing an example of a payment application confirmation screen in the case of multiple fees. [Figure 12] FIG. 10 is a schematic diagram showing an example of a price setting screen displayed on the device operator terminal by the device operator app. [Figure 13] FIG. 10 is a schematic diagram showing an example of a display of the operating status of a device on a user terminal. [Figure 14] FIG. 10 is a schematic diagram showing an example of a payment status viewing page. [Figure 15] FIG. 10 is a schematic diagram of a third embodiment in which the first embodiment is modified so that a house money agency service is used. [Figure 16] FIG. 10 is a schematic diagram showing an example of the structure of an agency service provider information file. [Figure 17] FIG. 10 is a schematic diagram showing an example of the structure of a house money balance information file. [Figure 18] 10 is a schematic diagram showing an example of a payment application screen and a payment application confirmation screen in which house money can be selected as a payment method. FIG. DETAILED DESCRIPTION OF THE INVENTION

[0021] Next, a description will be given of modes (embodiments) for carrying out the invention of this application. The devices in each embodiment are various types of devices capable of cashless payment of fees. In the following description, an example will be given in which the cashless payment function in the device is achieved by retrofitting. The means for achieving this is the retrofit cashless payment unit in each embodiment. Therefore, the following description also includes a description of the retrofit cashless payment unit in each embodiment. "Retrofit" means that it is added after the device is manufactured and sold, and a retrofit cashless payment unit is a unit for adding cashless payment functionality to a cash payment device (a device that only accepts cash payments). Hereinafter, a retrofit cashless payment unit will be abbreviated as a retrofit unit. Furthermore, a business that purchases (or leases) the device and operates it will be referred to as a device business operator.

[0022] When using a device equipped with (retrofitted with) the add-on unit described below, it is assumed that the user will install an application program on the user terminal. Therefore, the following description also includes a description of an embodiment of the application program. The user terminal is a mobile terminal operated by the user, such as a smartphone, a mobile phone with network communication capabilities, a tablet PC, or a PDA.

[0023] Fig. 1 is a perspective schematic diagram of a device equipped with an add-on unit according to the first embodiment, and Fig. 2 is a block diagram showing a schematic configuration of a device equipped with an add-on unit according to the first embodiment. As described above, the device 9 is a device that allows cashless payment, and corresponds to a ticket vending machine, a soft drink vending machine, a coin parking adjustment machine, an automatic rice polisher, etc. Hereinafter, the device 9 will be referred to as the device main body. In this embodiment, the device main body 9 has a cash settlement function and is equipped with a cash receipt confirmation unit. The cash receipt confirmation unit is a general term for a unit that confirms that the cash inserted through the cash slot is authentic and outputs a signal indicating the amount of the received cash. In the example shown in Figures 1 and 2, the device main body 9 is equipped with a coin mechanism 81 and a bill validator 82 as the cash receipt confirmation unit.

[0024] The device main body 9 has a fee receipt input unit 93 as an element that receives fee deposit signals from these cash receipt confirmation units 81, 82. The fee receipt input unit 93 is an element that receives a signal indicating that a fee for a product or service provided using the device main body 9 has been deposited, and is an element that receives signals from the coin mechanism 81 and bill validator 82. The signal received by the fee receipt input unit 93 is input to a determination unit (not shown) that determines whether the paid fee has reached the specified fee. If it is determined that the specified fee has been paid, the device main body 9 performs an operation to provide the product or service.

[0025] The add-on unit 1 is mounted on such a device main body 9 after installation. In many cases, the add-on unit 1 according to the embodiment is attached to a device main body 9 that has already been installed and started operating. The device main body 9 has a housing 90. As shown in FIG. 1 , the add-on unit 1 is installed inside the housing 90 and is not visible from the outside. However, the add-on unit 1 is provided with a code display unit 92. The code display unit 92 displays a code symbol 921, which symbolizes a code including information for pairing, which will be described later. In this embodiment, the code symbol 921 is a two-dimensional code symbol, and more specifically, a QR code (a registered trademark of Denso Wave Inc., omitted below). To reduce costs, the code display unit 92 is a sticker on which a sticker with the code symbol 921 printed is attached. The sticker is attached to the outer surface of the housing 90, so that the code symbol 921 is visible from the outside.

[0026] The add-on unit 1 has a unit box 10, and each element is housed within the unit box 10. The add-on unit 1 is mounted by fixing the unit box 10 to an appropriate position within the device main body 9 by means of screws or the like. As shown in FIG. 1, cash slots 811, 821 are provided on the front surface (operation surface) of the housing 90. In this example, the device main body 9 is equipped with a coin mechanism 81 and a bill validator 82, and therefore has a coin slot 811 and a bill slot 821 as cash slots.

[0027] As shown in FIG. 2, the add-on unit 1 includes a cashless control unit 2, a cashless output unit 3, a near-field wireless communication unit 4, and the like, all of which are provided in a unit box 10. The cashless control unit 2 is a central element of the add-on unit 1, and in this embodiment, a microcomputer such as a Raspberry Pi (a registered trademark of Raspberry Pi Ltd.) is used as the cashless control unit 2. In addition to a CPU 21, the cashless control unit 2 includes a storage unit 22 such as a microSD memory (hereinafter referred to as a unit storage unit). An OS that operates the CPU 21 is installed in the unit storage unit 22.

[0028] In this embodiment, the cashless output unit 3 is configured with a programmable microcomputer. As shown in Fig. 2, the cashless output unit 3 is wired so as to be interposed between the coin mechanism 81 and bill validator 82 and the fee receipt input unit 93 of the device main body 9. That is, the wiring from the coin mechanism 81 and bill validator 82 is connected to the input terminal of the cashless output unit 3, and the output terminal of the cashless output unit 3 is connected to the fee receipt input unit 93 of the device main body 9. These input and output terminals are terminals through which signals are input and output according to the current communication specifications (before the retrofit unit 1 is installed) between the coin mechanism 81 and bill validator 82 and the fee receipt input unit 93. The direction in which signals are transmitted is indicated by arrows in Fig. 2.

[0029] Cash receipt confirmation units such as coin mech 81 and bill validator 82 mounted on device main body 9 that were manufactured and sold in the past and are currently in operation generally use 24V serial communication (JVMA method). Therefore, cashless output unit 3 is configured in hardware and software to receive signals from coin mech 81 and bill validator 82 using 24V serial communication specifications, and transmit those signals directly to fee receipt input unit 93 using 24V serial communication specifications.

[0030] 2, the cashless control unit 2 is connected to another input terminal of the cashless output unit 3. In this embodiment, communication between the cashless control unit 2 and the cashless output unit 3 is between microcomputers, and any communication specifications may be adopted. As will be described later, the cashless control unit 2 inputs a signal indicating that the payment has been completed successfully (a payment completion signal) to the cashless output unit 3. The logic circuit within the cashless output unit 3 is configured to convert this into a 24V serial signal and output it to the fee receipt input unit 93. Note that if the cashless control unit 2 and cashless output unit 3 are configured to communicate using the same specifications as those between the coin mechanism 81 or bill validator 82 and the fee receipt input unit 93, the cashless output unit 3 is configured to output the signal to the fee receipt input unit 93 without performing any particular conversion.

[0031] An example of the configuration of such a cashless output unit 3 and the wiring when the add-on unit 1 is installed will be described with reference to Fig. 3. Fig. 3 is a schematic diagram showing an example of the configuration of a cashless output unit and the wiring when the add-on unit is installed. Fig. 3 shows, as an example, an example in which a certain model of coin mechanism 81 is connected to the fee receipt input unit 93 of the device main body 9, and the add-on unit 1 is installed thereto. In the example of Figure 3, the coin mechanism 81 and the fee receipt input unit 93 have seven terminals, which are currently (before the retrofit unit 1 is installed) connected to each other as shown in Figure 3(1). The terminals are as follows: No.1: Deposit 100 yen No.2: 100 yen control No.3: Deposit 500 yen No.4: 500 yen control No.5: +12V power supply voltage No.6: +24V power supply voltage No.7: Earth A 100 yen deposit is a signal that one 100 yen coin has been deposited, and a 500 yen deposit is a signal that one 500 yen coin has been deposited. For example, when 300 yen (three 100 yen coins) is deposited, three pulses are sent and received at terminal No. 1. Note that the voltage value of each pulse is often lower than the power supply voltage.

[0032] The 100 yen control is a terminal that sends and receives a signal when the deposit of a 100 yen coin is blocked for some reason, and the 500 yen control is a terminal that sends and receives a signal when the deposit of a 500 yen coin is blocked for some reason. These signals are usually sent from the device main body 9 to the coin mechanism 82. For example, a control signal (block signal) is sent when the device main body 3 is stopped, or when the device main body 3 is in operation and is providing a product or service and is unable to receive new fees. The power supply terminals No. 5 and No. 6 are terminals for receiving the supply of power supply voltage from the device main body 9 side, and either terminal is selected and made active.

[0033] When mounting the add-on unit 1 on the device main body 9 having the coin mechanism 81 configured as described above, the terminals are disconnected and connected as shown in Fig. 3(2). As shown in Fig. 3(2), the cashless output unit 3 has a first terminal group 31 (No. 1 to 4) for the coin mechanism 81 and a second terminal group 32 (No. 1 to 4) for the fee receipt input unit 93. When installing the retrofit unit 1, remove the coin mechanism 81 and the fee receipt input unit 93. Then, as shown in Figure 3 (2), connect the coin mechanism 81 to the first terminal group 31 (No. 1 to No. 4), and connect the fee receipt input unit 93 to the second terminal group 32 (No. 1 to No. 4).

[0034] As a result, the deposit confirmation signal (100 yen, 500 yen) from the coin mechanism 81 is input to the terminals (No. 1, No. 3) of the first terminal group 31 of the cashless output unit 3, and this signal is output from the terminals (No. 1, No. 3) of the second terminal group 32 and input to the fee receipt input unit 93. In addition, the control signal (block signal) from the fee receipt input unit 93 is input to the terminals (No. 2, No. 4) of the second terminal group 32, and this signal is output from the terminals (No. 2, No. 4) of the first terminal group 31 and input to the coin mechanism 81.

[0035] The cashless output unit 3 also has a third terminal group 33 (input terminals, output terminals) for the cashless control unit 2. As shown in FIG. 3(2), the third terminal group 33 is connected to the cashless control unit 2 in advance (when the retrofit unit 1 is manufactured). Therefore, when the wiring is done as shown in FIG. 3(2), the cashless control unit 2 is connected to the fee receipt input unit 93 of the device main body 9 via the cashless output unit 3. As can be seen from FIGS. 2 and 3(2), in the installed state, the cashless control unit 2 is connected in parallel to the coin mechanism 81 and bill validator 82 with respect to the fee receipt input unit 93.

[0036] As described above, in this embodiment, the code display unit 92 is provided on the outer surface of the housing 90 of the device main body 9. The code symbol 921 displayed by the code display unit 92 is a symbolized code for pairing in short-range wireless communication between the user terminal 6 and the retrofit unit 1. In this embodiment, one-to-one short-range wireless communication is performed, and the user terminal 6 and the retrofit unit 1 communicate by identifying each other using their IDs. The code symbol 921 allows the user terminal 6 to obtain the device ID for this pairing.

[0037] Regarding the short-distance wireless communication unit 4, in this embodiment, "short-distance wireless communication" is assumed to be used for direct communication at a short distance of 100 meters or less, such as the international standard NFC (Near Field Communication) or Bluetooth (a registered trademark of Bluetooth SIG, Inc., hereinafter omitted). In this sense, wireless LAN is not assumed, since communication is performed via a parent device (router). In this embodiment, the short-distance wireless communication unit 4 is configured to communicate according to the Bluetooth standard, and serves as a Bluetooth interface unit. However, it may also be configured to perform short-distance wireless communication according to other standards.

[0038] The cashless control unit 2 also has several control programs implemented. Specifically, it has implemented therein a unit main program 201 that is automatically executed when the power is turned on, a unit pairing program 202 that performs pairing with the user terminal 6 via short-range wireless communication, a payment completion output program 203 that outputs payment completion when payment completion information is sent from the user terminal 6, and a pairing cancellation program 204 that cancels pairing when use of the device is finished, etc. These programs are stored in the unit storage unit 22 and are executable by the CPU 21.

[0039] The unit storage unit 22 stores a device setting information file 221 that stores setting information for the device main body 9. The device setting information file 221 is a file in which information such as a device ID and a payment amount is recorded in advance. The unit storage unit 22 is equipped with a setting program (reference numeral omitted) as a management program for storing this setting information in advance.

[0040] The device main body 9 has a usage operation status output unit 91 that outputs a signal indicating the operation status of the user's use of the device main body 9. A terminal of the cashless control unit 2 is connected to the usage operation status output unit 91, and a signal corresponding to the usage operation status is input. The usage operation status signal is determined appropriately depending on the type of device main body 9, but as a simple example, information identifying two states, a device standby state (a state in which the power is on and a usage operation can be started) and a usage operation in progress state, is output.

[0041] The user terminal 6 is assumed to have a function that allows it to perform short-distance wireless communication with the short-distance wireless communication unit 4. The user terminal 6 is typically a smartphone, and smartphones that are generally available on the market are equipped with a short-distance wireless function such as Bluetooth as standard, and are capable of performing short-distance wireless communication with the short-distance wireless communication unit 4.

[0042] Cashless payment using the add-on unit 1 is realized through collaboration between a group of programs implemented in the cashless control unit 2 and an application program (hereinafter referred to as the device app) installed on the user terminal 6 to use the cash payment device equipped with the add-on unit 1. These pieces of software are described below. Note that the description of the device app also describes an embodiment of the invention of the application program.

[0043] First, a description will be given of the programs implemented in the cashless control unit 2 of the retrofit unit 1. Fig. 4 is a flowchart showing the general configuration of the unit main program 201. A pairing permission setting value is stored in the unit storage unit 22 as a variable referenced by the unit main program 201. Therefore, the unit storage unit 22 includes a pairing permission setting unit in which the pairing permission setting value is stored. As shown in FIG. 4, when the unit main program 201 is started, it enters a payment standby state in which it waits for a pairing request from the user terminal 6. When a pairing request is received from the user terminal 6, the unit main program 201 refers to the usage operation status signal and the pairing permission setting value. If the usage operation status is a false value (device standby state) and the pairing permission setting value is a true value (pairing possible), it permits pairing, executes the pairing program 202, and performs pairing with the user terminal 6. If any of the conditions is not met, the pairing program 202 is not executed. In this case, the unit main program 201 sends an error message to the user terminal 6 and returns to the payment standby state.

[0044] As shown in FIG. 4, the unit main program 201 executes the pairing program 202, and when a return value indicating successful pairing is received, it changes the pairing permission / prohibition setting value to a false value (pairing is not possible). Next, it transmits payment information to the paired user terminal 6. As will be described later, the short-range wireless communication unit 4 transmits the payment information in response to an acquisition request from the device app, and the short-range wireless communication unit corresponds to the payment information transmission unit. The payment information includes the device ID, device name, payment amount, etc. The unit main program 201 starts a timer when pairing is completed, and waits to receive payment completion information from the user terminal 6.

[0045] A payment waiting time is set as a constant in the unit main program 201. As shown in Fig. 4, if the unit main program 201 does not receive payment completion information until the timer count reaches the payment waiting time, it sends an error message to the user terminal 6 and returns to the payment standby state. At this time, the unit main program 201 resets the pairing availability setting value to a true value (pairing possible). The same applies if pairing is canceled by a request from the user terminal 6 before the payment waiting time is reached; it sends an error message to the user terminal 6, resets the pairing availability setting value to a true value, and returns to the payment standby state.

[0046] If payment completion information is sent from the user terminal 6 before the timer count reaches the payment waiting time, the unit main program 201 executes the payment completion output program 203. The payment completion output program 203 causes the cashless output unit 3 to output a payment completion signal. The cashless output unit 3 converts the signal into a signal with the same communication specifications as the output signals of the coin mechanism 81 and bill validator 82 and inputs this signal to the fee receipt input unit 93 of the device main body 9. Using the above example, if the cashless payment fee is, for example, 300 yen, a 300 yen payment completion signal is input to the input terminal of the third terminal group 33 of the cashless output unit 3, and the cashless output unit 3 outputs three pulses via 24V serial from terminal No. 1 of the second terminal group 32. The three pulses are input to terminal No. 1 of the fee receipt input unit 93 and are treated as if a 300 yen deposit had been made at the coin mechanism 81, and subsequent processing is carried out.

[0047] When payment completion is input to the fee receipt input unit 93 in this way, the device main body 9 is put into operation. In other words, the device becomes available for use by the user. At this time, the usage operation status output unit 91 of the device main body 9 switches to usage operation in progress. After receiving the payment completion information, the pairing cancellation program 204 is executed to cancel the pairing with the currently paired user terminal 6. Then, the pairing availability setting value is returned from a false value to a true value, and the device transitions to a payment standby state. This completes the series of processes for cashless payment. After that, when use is completed, the output of the usage operation status output unit 91 returns to the device standby state. The unit main program 201 is implemented to perform such processing.

[0048] Next, the device application will be described. It is assumed that the device app is downloaded in advance when the device main body 9 equipped with the retrofit unit 1 is used. The app is downloaded by accessing a website operated by a business that provides a service to support sales activities involving the installation of the device main body 9 equipped with the retrofit unit 1 (hereinafter referred to as the support service business). As shown in FIG. 2, the support service business manages a server 7 that provides this website (hereinafter referred to as the device usage support site). Hereinafter, this server 7 will be referred to as the device usage support server.

[0049] Access to the device usage support site to download a device app may occur when the user is performing a web search or the like on the user terminal 6, but may also occur when attempting to use the device main body 9. With this in mind, as shown in FIG. 1, the device main body 9 has an installation code display unit 94 that displays an installation code symbol 941. The installation code display unit 94 is also a portion where a sticker on which a two-dimensional installation code symbol 941, such as a QR code, is printed is affixed. The configuration of the installation code symbol 941 can be the same as when installing a normal application program, so a detailed description will be omitted. In FIG. 2, the device app installed on the user terminal 6 is indicated by the reference numeral 60.

[0050] The device application 60 is a program that is used after user registration. A user information file 71 is recorded in a memory unit (hereinafter referred to as a server memory unit) 70 on the device usage support server 7, and user registration is a process of recording a user ID and password in the user information file 71. After installation, the installation program for the device application 60 displays a user registration screen on the user terminal 6, where an arbitrary ID (usually an email address) and password are entered and sent, and then recorded in the user information file 71. This part is similar to an application program that is used by setting an ID and password, so further explanation will be omitted.

[0051] Fig. 5 is a flowchart showing a schematic configuration of the application main program 601 included in the device application 60. Figs. 6 and 7 are schematic diagrams showing each screen displayed on the user terminal 6 by the device application 60. The device application 60 starts a short-range wireless communication API that is pre-installed in the user terminal 6. In this embodiment, the short-range wireless communication is Bluetooth, so the device application 60 first automatically starts the Bluetooth API. However, automatic pairing is not performed. In other words, the Bluetooth API is started without pairing. Although not shown in the figure, in this example, code is embedded that checks whether pairing has occurred and, if so, cancels the pairing.

[0052] After starting the Bluetooth API, the application main program 601 displays a home screen on the user terminal 6 as shown in FIG. 6(1). As shown in FIG. 6(1), the home screen has a button 61 labeled "Read QR Code" (hereinafter referred to as the "read start button"). The device application 60 includes a symbol reading program 602 that reads and executes a code symbol 921, and the read start button 61 is an execution button for the symbol reading program 602. In this embodiment, the code symbol 921 is a QR code, so the symbol reading program 602 is a program that reads the QR code using a QR code reading API. When the read start button 61 is pressed, the application main program 601 switches to a reading screen that includes a window 611 that displays an image captured by the camera on the user terminal 6 as shown in FIG. 6(2). When an image of a QR code is included in the window 611, the QR code reading API automatically analyzes and decodes the code.

[0053] The device application 60 includes an application pairing program 603 that performs pairing between the add-on unit 1 and the user terminal 6. Pairing is a process of enabling one-to-one short-range wireless communication between the add-on unit 1 having the code symbol 921 read by the user terminal 6 and the user terminal 6, and preventing the user terminal 6 from communicating with other add-on units 1 within a communication range. In this embodiment, the short-range wireless communication is Bluetooth, so the pairing is Bluetooth pairing.

[0054] In this example, the code symbol 921 displayed by the code display unit 92 of the retrofit unit 1 is a symbolized execution code of the application pairing program 603. The code symbol 921 includes a device ID, and the code for executing the application pairing program 603 using the device ID as an argument is represented as a two-dimensional symbol. The device ID serves as a public key for pairing. The symbol reading program 602 is programmed to automatically execute the application pairing program 603 by using the device ID included therein as an argument upon reading the code symbol 921. Note that, for security reasons, a PIN code (secret key) may be set in the short-range wireless communication unit 4 for pairing. In this case, the code symbol 921 is considered to include the PIN code, and the pairing program 603 is executed by using the device ID and PIN code as arguments.

[0055] 5, after displaying the home screen, the application main program 601 waits for a return value from the application pairing program 603. When the application pairing program 603 returns a value indicating that pairing has been completed, the application main program 601 performs short-range wireless communication with the retrofit unit 1 identified by the device ID and acquires information about the payment. Specifically, it acquires information about the device 9, such as the store name, device name, and device number, as well as the payment amount. This information is recorded in the device setting information file 221 and is read from there and acquired by the application main program 601.

[0056] As shown in FIG. 5, when the application main program 601 acquires payment information, it temporarily stores the payment information in a variable, and then acquires information identifying the payment method used in the most recent payment (most recent method identification information) from the memory on the user terminal 6. The most recent method identification information is stored in the memory as a variable on the device app. After acquiring this information, the application main program 601 incorporates this information and displays a screen for confirming the payment request (hereinafter referred to as the payment request confirmation screen) on the user terminal 6. This state is shown in FIG. 7(1).

[0057] As shown in Figure 7(1), in this embodiment, cashless payment can be made by selecting any cashless payment method from a number of different cashless payment methods, and a method selection field 62 for selecting a cashless payment method is displayed on the user terminal 6 by the application main program 601. As described above, the most recent method specification information has been acquired, so this is selected by default.

[0058] As shown in Figure 7(1), the payment request confirmation screen includes a payment button 63 labeled "Make Payment." The device usage support server 7 is equipped with a payment request program 72, and when the payment button 63 is pressed, the application main program 601 is coded to call and execute the payment request program 72. As shown in Figure 2, there are payment servers 5 corresponding to each cashless payment method on the network. The payment request program 72 is a program that performs server transition to the corresponding payment server 5 according to the cashless payment method selected in the payment method selection field 62, causes the payment server 5 to execute a payment program (not shown), and obtains its return value. For example, in the case of a prepaid service in which payment is made using a prepaid account linked to a bank account, the cashless payment is made by transitioning to a server 5 operated by the provider of the prepaid service (hereinafter referred to as the "prepaid server") 5. In this case, information linking the prepaid service account with the user ID in the device application 60 is recorded in the user information file 71, and this information and the payment amount are sent to the prepaid server to perform the cashless payment. In addition, credit cards can also be used as a cashless payment method, but this can be configured in the same way as on regular e-commerce sites, so a detailed explanation will be omitted.

[0059] When the payment application program 72 receives a return value indicating that the payment has been completed successfully, it returns this information to the application main program 601. As shown in Fig. 5, when the application main program 601 receives the return value indicating that the payment has been completed successfully, it sends a signal indicating that the payment has been completed successfully to the short-range wireless communication unit of the paired retrofit unit 1. At the same time, as shown in Fig. 7(2), the application main program 601 displays a confirmation screen (operation confirmation screen) on the user terminal 6 indicating that the payment has been completed successfully and that the device main body 9 will be operated.

[0060] Thereafter, the pairing is released under control of the unit main program 201 (although it may also be released from the device application 60). This marks the end of the exemplary process that begins with reading the code symbol 921. The application main program 601 then displays a message indicating that the pairing has been released and a button (home button) for returning to the home screen. Normally, the application main program 601 is closed on the user terminal 6 at this stage, but the home button may be pressed to display the home screen again in order to use another device main unit 9 or to use the same device main unit 9 again. Although not shown in FIG. 5 , the application main program 601 starts a timer after executing the payment request program 72. If there is no return value from the payment request program 72 when the timer count reaches a predetermined value, an error message indicating that the payment was not completed successfully is displayed on the user terminal 6. The same applies when the payment request program 72 returns a value indicating that the payment was not completed successfully.

[0061] The operation of the device of the embodiment in which the retrofit unit of this embodiment is installed will be briefly described below. In response to a request from a device business owner who owns an already operating device main body 9, a worker from a business selling the add-on unit 1 of the embodiment (hereinafter, the unit business owner) goes to the installation location of the device main body 9 and installs the add-on unit 1. The worker opens the housing 90, fixes the unit box 10 in an appropriate position within the housing 90, and then connects the cashless output unit 3. That is, the worker temporarily disconnects the wiring between the existing cash receipt confirmation units, such as the coin mechanism 81 and bill validator 82, and the fee receipt input unit 93 of the device main body 9. The worker then connects the cash receipt confirmation units 81 and 82 to predetermined terminals of the cashless output unit 3, and connects the predetermined terminal of the cashless output unit 3 to the fee receipt input unit 93. The worker also connects the power cable extending from the power circuit to a commercial power outlet provided at the installation location of the device main body 9. The worker then closes the housing 90 to return it to its original state. Then, the worker attaches a sticker with a code symbol 921 printed on it in a conspicuous position on the exterior of the housing 90 to serve as the code display unit 92.

[0062] This completes the installation of the retrofit unit 1. After that, various settings necessary for operation are made. That is, the worker starts the setting program and inputs the device ID and payment amount on the displayed setting screen. The input device ID and payment amount are recorded in the device setting information file 221 on the unit storage unit 22 by the setting program. This puts the retrofit unit 1 into an operational state. The power supply of the retrofit unit 1 is turned on in conjunction with the power supply of the device main body 9, so that the retrofit unit 1 is in operation when the device main body 9 is in operation. When the power is turned on, the unit main program 201 of the retrofit unit 1 is started up and is kept in a running state while the device main body 9 is in operation.

[0063] When a user comes to the device main body 9 and attempts to use it, they would normally insert cash, but upon learning that a cashless payment function has been added, they attempt to make a cashless payment. If the device app 60 is not installed, the user reads the installation code symbol 941 with the user terminal 6 and installs the device app 60 on the user terminal 6. Then, they enter personal information and the like on the user registration page to register as a user. At this time, the user ID and password are recorded in the user information file 71.

[0064] The user launches the device app 60 on the user terminal 6 and displays the home screen. At this time, a short-range wireless communication program such as Bluetooth API is automatically launched on the user terminal 6. The user then taps the login button on the home screen and enters their user ID and password to log in to the device usage support site. If the user has logged in from a previous use and that status is retained, this operation is omitted.

[0065] While logged in, the user taps the read start button 61 to display the code reading screen on the user terminal 6. Then, the user reads the code symbol 921 on the device main body 9 using the camera function of the user terminal 6. This executes the pairing program 602 included in the device app 60, and a pairing request is sent to the retrofit unit 1 via short-range wireless communication. The unit main program 201 permits pairing and performs pairing only if the device is not currently paired with another user terminal 6 and the pairing permission setting value is not a false value (pairing is not possible). Once pairing is complete, the unit main program 201 changes the pairing permission setting value to a false value (pairing is not possible). Note that if a value indicating pairing is not possible is returned from the retrofit unit 1, the device app 60 displays an error message such as "This device is in use" on the user terminal 6.

[0066] When a signal indicating that pairing has been successfully completed is returned, the application main program 601 performs short-range wireless communication with the retrofit unit 1, obtains the device name, payment amount, etc. from the device setting information file 221 in the unit storage unit 22, embeds these, and displays a payment request confirmation screen on the user terminal 6. The user confirms the payment amount, etc. and taps the payment request button 62. This causes the payment request screen, which includes a payment method selection field 62, to be displayed on the user terminal 6. The user selects a payment method in the payment method selection field 62 and then taps the payment button 63. This causes the payment request program 72 to be executed on the device usage support server 7, and payment is made using the selected payment method.

[0067] When the payment application program 72 receives a return value from the payment server 5 indicating that the payment has been completed successfully, it returns this information to the application main program 601, and the application main program 601 sends a signal indicating that the payment has been completed successfully to the short-range wireless communication unit 4 of the paired retrofit unit 1. At the same time, the application main program 601 displays an operation confirmation screen on the user terminal 6 indicating that the device main body 9 is operating.

[0068] Thereafter, the application main program 601 performs processing to cancel pairing with the retrofit unit 1 with which it had been paired. The device main program 9 starts a usage operation, and depending on the functions of the device main program 9, the usage operation status is displayed by an operation lamp or the like on the device main program 9. The unit main program 201 constantly monitors the usage operation status output unit 91 on the device main program 9, and when an operation end signal is output from this terminal, it changes the setting value of the pairing availability setting unit to a true value (pairing possible). Thereafter, if another user (which may be the same user) reads the two-dimensional code symbol with the user terminal 6 and performs pairing, the same operation is repeated.

[0069] According to the device and device app 60 of this embodiment, a payment request to the payment server 5 is sent from the user terminal 6, so the device (device main body 9 and add-on unit 1) does not need to have a network communication function. This allows for cashless payment, while reducing manufacturing and running costs. In this case, one-to-one short-range wireless communication is performed between the user terminal 6 and the add-on unit 1, and pairing with another user terminal 6 is not performed while the device main body 9 is in use, preventing erroneous payments from being made while the device main body 9 is in use.

[0070] Furthermore, according to the add-on unit 1 of the embodiment, the function having the above-described effect can be added to the device main body 9 that only accepts cash payments, thereby improving the convenience of the device main body 9. This can promote the sale of products or services through the device main body 9, and is expected to increase profits. In this case, there is no need to replace the device main body 9, so no large costs are required, which also contributes to increased profits. Furthermore, in the retrofit unit 1 of the embodiment, the cashless output unit 3 outputs a cashless payment completion signal to the fee receipt input unit 93 of the device main body 9 using the same communication specifications as the output signal from the existing cash receipt confirmation unit, so there is basically no need to modify the fee receipt input unit 93 of the device main body 9, and the cashless payment function can be introduced easily and inexpensively.

[0071] In the above embodiment, the device application 60 first requests pairing, and the short-range wireless transmission unit 4 responds to that request to perform pairing. However, the reverse is also possible. That is, the short-range wireless transmission unit 6 may constantly transmit a pairing request, and the user terminal 6 that reads the code symbol 921 may respond to this request to perform pairing. In this case, the code symbol 921 contains a private key for pairing, and pairing is established by confirming that the private key has been acquired.

[0072] Furthermore, during pairing, the code display unit may display a code that is not symbolized. For pairing, the user terminal 6 simply requests pairing by specifying the short-range wireless communication unit 4 of the retrofit unit 1. Therefore, the device side only needs to display the device ID (public key), and the code display unit may display the device ID as is. In this case, the communication function of the user terminal 6 is used to perform pairing according to the device ID. For example, the Bluetooth API includes a function that detects radio waves constantly emitted from Bluetooth devices and displays a list of Bluetooth devices that can be paired. Since the display of pairable Bluetooth devices is a display of public keys, when the short-range device app 60 launches the Bluetooth API, the user may select a public key from the list that matches the device ID displayed on the code display unit and request pairing. In this case, the pairing request may be a function of the Bluetooth API or a function of the device app 60.

[0073] The device, device application 60, and add-on unit 1 of the above embodiment may have a suitable configuration in terms of collecting cash payment information, which will be described below. 2, a cash payment history information file 223 is recorded in the memory unit 22 on the retrofit unit 1. The cash payment history information file 223 is a relatively simple database file such as a CSV file that records the date and time of cash payments and the payment amount. As described above, the output terminals of the third terminal group 33 of the cashless output unit 3 are connected to the cashless control unit 2. When a cash deposit signal is input from the coin mechanism 81 or the bill validator 82, the cashless output unit 3 outputs the cash deposit signal as is to the fee receipt input unit 93 of the device main body 9 as described above, and is also configured to input the cash deposit signal to the cashless control unit 2. The cashless control unit 2 is equipped with a cash payment recording program 207, which is programmed to record cash deposit information in the cash payment history information file 223 when a cash deposit signal is input.

[0074] Meanwhile, as shown in Fig. 2, a cash payment history information master file 74 that accumulates and records cash payment history is stored in the memory unit 70 on the device usage support server 7. The master cash payment record information master file 74 is created for each device and can be identified by the device ID, for example, by using the device ID as the file name. In addition, the device usage support server 7 is equipped with a cash payment history recording program 75 that records the cash payment history information of each device.

[0075] The device app 60 described above is equipped with a function for transmitting cash payment history information for a device equipped with the paired add-on unit 1 to the device usage support server 7 and recording it. This function can take several forms, but for example, the device app 60 may include an application / transfer program for transferring the cash payment history information file 223 and executing the payment request program 72 on the device usage support server 7. The application / transfer program includes code for retrieving the cash payment history information file 223 from the memory 22 on the add-on unit 1 and temporarily storing it in the memory of the user terminal 6, code for executing the payment request program 72 on the device usage support server 7 using the user ID and payment amount as arguments, and code for executing the cash payment history recording program 75 on the device usage support server 7 using the temporarily stored cash payment history information file 223 as an argument. Therefore, when the payment request button 62 on the payment request confirmation screen is pressed, the cash payment history information file 223 is automatically transferred along with the payment request.

[0076] The cash payment history recording program 75 on the device usage support server 7 opens the corresponding cash payment history information master file 74 according to the device ID acquired when the payment application program 72 is executed, and adds the contents of the transferred cash payment history information file 223. At this time, if there is information with the same device ID and the same time on the same day, it is overwritten and recorded. This configuration has the advantage that when collecting cash payment information on a device, the device does not need to have a network communication function. Therefore, there are no hardware costs or running costs (communication costs) for collecting cash payment history information, and cash payment history information can be collected at extremely low cost.

[0077] Note that the cash payment history information may be sent by the user terminal 6 separately from the payment request. For example, after the payment request program 72 is executed, a successful payment completion is returned, and the main device 9 starts using the device, the device app 60 may obtain the cash payment history information from the unit storage unit 22 while maintaining pairing and send it to the device usage support server 7. The destination of the cash payment history information may also be a server other than the device usage support server 7. An example of this is when a separate server is provided for collecting cash payment history information.

[0078] The add-on unit 1 is significant in that it can provide such an effect retrofit. In other words, it enables the collection of cash payment information that was previously impossible, and this can be achieved inexpensively. Conventionally, in the case of cash payments, it is impossible to know when the payment (sales) occurred or the amount of each payment. The total amount of cash payment sales is determined when the cash stored in the coin mechanism 81 and the bill validator 82 is collected, but it is impossible to determine when each payment was made or how much it amounted. On the other hand, by installing the add-on unit 1 of the embodiment, it is possible to collect information on the date, time, and amount of each cash payment, not just cashless payments. This information is useful when determining policies for the operation of the device main body 9. For example, it is possible to conserve energy by shutting down the device main body 9 during periods of low usage.

[0079] In addition, since each user terminal 6 communicates via a network when collecting the cash payment history information, there is a possibility that communication costs will be incurred. Therefore, it is preferable to obtain prior consent from each user regarding this point. For example, when downloading the device application 60, a message indicating that the application will be used for such file transfer and an acknowledgement button (e.g., a check button) are displayed, and when the acknowledgement button is pressed, the user's acknowledgement is transmitted to the device support server and recorded in the user information file 71, etc., and a configuration is preferably adopted.

[0080] Next, a device, a device application 60, and an add-on unit 1 according to the second embodiment will be described. FIG. 8 is a schematic perspective view of the retrofit unit 1 according to the second embodiment, and FIG. 9 is a flowchart showing the schematic configuration of the unit main program 201 according to the second embodiment. The device of the second embodiment differs from the first embodiment in the configuration for pairing with the user terminal 6. That is, in the first embodiment, pairing is performed by the user terminal 6 reading the code symbol 921 on the device, but in the second embodiment, the device is equipped with a camera 12, and pairing is performed by the camera 12 on the device reading a code symbol (hereinafter referred to as the terminal symbol) displayed on the user terminal 6. As shown in Fig. 8, the camera 12 is attached by being fitted into an opening provided in the front panel of the unit box 10, and is oriented to capture images ahead.

[0081] In this embodiment, the unit main program 201 also starts when the device starts operating and remains in an execution state while the device is operating. As shown in Fig. 9, when the unit main program 201 starts, it waits for image data to be acquired by the camera 12. In addition, a unit pairing request program 205 is installed in the storage unit 22 of the retrofit unit 1 as a program that is called and executed by the unit main program 201.

[0082] Meanwhile, the device app 60 in this embodiment includes a program for displaying a terminal symbol. Fig. 10 is a schematic diagram showing the display of a terminal symbol in the device app 60 of the second embodiment. As shown in Fig. 10(1), the device app 60 of the second embodiment displays a symbol display button 64 on the home screen. When this button is tapped, a terminal symbol 65 is displayed on the user terminal 6, as shown in Fig. 10(2). The terminal symbol 65 is a static code that includes a unique code (hereinafter referred to as the application identification code) that identifies the device application 60 and the user ID for the device application 60. Each piece of information is a fixed value (constant), and when the device application 60 is installed and the user is registered, an image (code symbol) is automatically generated and stored in the memory of the user terminal 6. The symbol display button 64 is a button in which code is embedded that executes a module that calls and displays this image.

[0083] As shown in FIG. 9, when the camera 12 captures the image of the terminal symbol 65, the unit main program 201 analyzes the code contained therein and determines whether it contains an application identification code (whether it was generated by the device application 60). If the application identification code is included, the unit main program 201 also acquires a user ID. Then, the unit main program 201 starts a short-range wireless communication program (Bluetooth API in this example) and executes a pairing request program 205 to establish pairing with the user terminal 6. Since the user ID serves as a public key, pairing is established only with the user terminal 6 that displays the terminal symbol 65. The device application 60 confirms that the pairing request is correct using the user ID and establishes pairing. If the application identification code is not included or if pairing has already been established at the time the terminal symbol 65 is read, the unit main program 201 does not execute the pairing request program 205 and returns to the standby state.

[0084] When the user terminal 6 sends a signal to the add-on unit 1 indicating that the pairing request has been approved and pairing has been established, the unit main program 201 changes the pairing availability setting value to a false value (pairing is not possible). On the other hand, once pairing is established, the device app 60 on the user terminal 6 acquires the device name, payment amount, etc. from the device setting information file 221 in the unit storage unit 22 of the paired add-on unit 1, embeds these information, and displays a payment request confirmation screen on the user terminal 6. Subsequent processing and operations are the same as those in the first embodiment. Once the payment is successfully completed and the device 9 operates, and the operation is completed, the unit main program 201 resets the value of the pairing availability setting value to a true value (pairing is possible). If pairing is not established within a predetermined time after executing the pairing request program 205, the unit main program 201 times out and returns to standby mode. In this case, pairing is also canceled, and the pairing availability setting value is reset to a true value. In addition, in the second embodiment, the device app 60 may also include an application / transfer program that transfers the cash payment history information file 223 on the retrofit unit 1 and executes the payment application program 72 on the device usage support server 7.

[0085] In the device of the second embodiment, a payment request to the payment server 5 is also made in response to a transmission from the user terminal 6, so the device does not need to have a network communication function, and the cashless payment function can be implemented at low cost. Since the device is not paired with another user terminal 6 while the device main body 9 is in use, erroneous payments are prevented while the device main body 9 is in use. The cashless function can be implemented as a retrofit without requiring a large additional investment. Furthermore, cash payment history information can be collected without requiring a network communication function in the device. However, compared to the first embodiment, a camera 12 is required, which increases costs.

[0086] In the above-described embodiments, the usage fee (payment fee) for the device is a single fee, but the present invention can also be implemented in cases where there are multiple usage fees and the user selects one of them and pays for it. This point will be explained below. If there are multiple fees, the payment amount is also recorded in the device setting information file 221 on the storage unit 22 of the add-on unit 1. After pairing is established, the application main program 601 acquires the multiple fees as setting information along with the device name and the like from the storage unit 22 of the add-on unit 1, and displays them on the user terminal 6. An example of this is shown in FIG. 11. FIG. 11 is a schematic diagram showing an example of a payment request confirmation screen for multiple fees. As shown in FIG. 11, the device application 60 is coded to display the acquired multiple fees on the payment request confirmation screen along with fee selection buttons 66. In this example, each fee selection button 66 is a radio button displaying the corresponding amount. Alternatively, it may be a command button or the like with code embedded for making payment with the corresponding amount.

[0087] In this example, the payment request confirmation screen also includes a fee selection and payment button 67. The fee selection and payment button 67 is the same as the payment button 63 shown in FIG. 7(1), except that the amount selected with the fee selection button 66 is used as an argument. The fee selection and payment button 67 transmits the selected fee and selected payment method information along with the user ID to the device usage support server 7, and executes the payment request program 72 on the device support server 7. When the payment is successfully completed, a notification to that effect is returned to the application main program 601, which in turn returns this to the retrofit unit 1. This allows the device 9 to be used for the amount. In other words, a signal equivalent to the amount deposited via the coin mechanism 81 or bill validator 82 is input from the cashless output unit 3 to the device main body 9. Note that a configuration may also be adopted in which a confirmation screen for the selected fee is displayed and the payment request program 72 is executed using a command button provided thereon.

[0088] In addition, the device usage fee can be set to be different for cash payments and cashless payments. This point will be explained below. For example, to promote the use of cashless payments, a device provider may offer a flat 10 yen discount on the usage fee for cashless payments. In this case, the payment fee discounted by 10 yen is recorded in the device setting information file 221 on the storage unit 22 of the retrofit unit 1. Therefore, when the user operates the user terminal 6 to display the payment application confirmation screen as described above, the payment fee discounted by 10 yen is displayed. When payment is successfully completed at this fee, the unit main program 201 outputs a payment completion signal from the cashless output unit 3 as if the payment had been made with an additional 10 yen. Therefore, a product or service equivalent to the 10 yen price is provided for the 10 yen discounted price.

[0089] Such price setting may be performed by a person in charge at the unit provider when the retrofit unit 1 is installed, but it is preferable that the device provider be able to set it at any time at their own discretion. One possible configuration for this would be to provide an operation panel or touch panel on the retrofit unit 1 to enable input, but this would have the disadvantage of making the structure complicated and increasing costs. Therefore, it is preferable to be able to set the price using short-range wireless communication, as with the user terminal 6. In other words, it is preferable to provide an application program (hereinafter referred to as a device provider app) that runs on a terminal (hereinafter referred to as a device provider terminal) 11 operated by a person in charge at the device provider. The device provider terminal 11 is also a mobile terminal with short-range wireless communication capabilities, such as a smartphone.

[0090] FIG. 12 is a schematic diagram showing an example of a price setting screen displayed on the device provider terminal 11 by the device provider app. Device providers are given access authority to access the storage unit 22 on the retrofit unit 1 owned by their company. To authenticate the access authority, an ID (carrier ID) and password are issued to the device provider. When the retrofit unit 1 is installed, the person in charge at the unit provider stores the carrier ID and password as authentication information as initial settings in the storage unit 22 of the retrofit unit 1. After installing and launching the device provider app on the device provider terminal 11 and performing pairing for short-range wireless communication (or during pairing), the carrier ID and password are entered for authentication, and the price setting screen of FIG. 12 is displayed.

[0091] The amount setting screen in this example has an increase / decrease amount selection field 111 for selecting the amount to increase or decrease the cash payment amount. In this example, the field allows the amount to be increased or decreased in increments of 10 yen. The amount setting screen also has a register button 112. A payment amount change program 206 is implemented in the memory section 22 of the retrofit unit 1, and the register button 112 is an execution button for the payment amount change program 206. The payment amount change program 112 is a program that updates the payment fee in the device setting information file 221 with the increase / decrease amount selected in the increase / decrease amount selection field 111.

[0092] Device operators do not need additional hardware such as an operation panel or touch panel to change the cashless payment amount on the devices they operate, and because the device also uses the near-field wireless communication function for cashless payments made by users, no special additional functions are required. As a result, the amount change function for cashless payments can be implemented at extremely low cost. The above example was a change in price, but other factors may also be changed. For example, in the case of a service, the service duration may change. Similarly, in the case of a coin laundry, a possible example would be that the drying time of the dryer would be longer if cashless payment was made for the same price. Another example would be that in the case of a paid massage chair, the operating time would be longer if cashless payment was made for the same price.

[0093] In the above embodiments, when a pairing request is received from the device app 60 on the user terminal 6 while the device is already paired with another user terminal, the unit main program 201 rejects the pairing by referencing the value of the pairing permission setting section, but this may also be done using the function of the short-range wireless communication unit 4. For example, when the short-range wireless communication unit 5 functions as a Bluetooth master device, it is configured to be set not to change (switch) the pairing when pairing is already in progress, and to return a message indicating that pairing is not possible. In this case, the short-range wireless communication unit 5 cannot cancel the pairing by itself, but cancels it by a pairing cancellation signal output by the unit main program 201, so that pairing requests from other user terminals are rejected while the device is in use.

[0094] In this case, if the customer using the device cancels the pairing while using the device, or if the customer holding the user terminal 6 goes out of the range of short-range wireless communication and the pairing is canceled, the short-range wireless communication unit 5 will perform pairing in response to a pairing request from another user terminal. In this case, there is a possibility that another customer will make a payment for the device already in use, but this can be addressed by using a function of the unit main program 201 to restrict access to the unit storage unit 22 that stores the payment information so that payment information will not be sent while the device is in use.

[0095] Furthermore, in each of the above embodiments, a configuration may be preferably adopted in which the usage operation status of the device main body is displayed on the user terminal 6. This configuration will be described below. In the above explanation, the pairing is released when the payment is completed normally, but it may be continued without being released. If the pairing is continued, a suitable configuration (a configuration that utilizes the pairing state) is to display the usage operation status on the user terminal 6. Fig. 13 is a schematic diagram showing an example of the device usage status displayed on the user terminal 6. The device app 60 is programmed to display a usage status screen on the user terminal 6 after transmitting payment completion information to the retrofit unit, and Fig. 13 shows an example of the usage status display screen.

[0096] If pairing continues, the user terminal 6 can receive signals from the add-on unit 1 at any time. When the signal output from the usage status output unit 91 changes, the unit main program 201 transmits a usage status change signal to the user terminal 6 accordingly. The device app 60 includes code for displaying the received usage status signal on the usage status screen. In the example shown in FIG. 13, the device main body 9 is a washing machine at a coin laundry, and the signal output from the usage status output unit 91 indicates the time remaining until the operation ends. FIG. 13(1) is a screen (similar to FIG. 7(2)) at the time when payment is completed and operation begins, and FIG. 13(2) is a screen at a time when operation has progressed. In the usage status screen shown in FIG. 7, a script for displaying the received usage status change signal (time remaining until the operation ends) is embedded in the box 68 displaying the time remaining until the operation ends. In this way, it is preferable that the usage operation status of the device main body 9 is displayed on the user terminal 6, because the usage operation status can be checked even from a remote location as long as it is within the range where short-range wireless communication is possible. In addition to the usage operation status, if the device main body 9 has stopped due to some kind of error, it can also be displayed on the user terminal 6.

[0097] In the above embodiments, a configuration using an output signal from the usage status output unit 91 has been described as a configuration for disabling payments using the device app 60 on another user terminal 6 while the device is in use, but other configurations are also possible. For example, the cash receipt confirmation unit (coin mechanism 81, bill validator 82) often has a function for outputting a prohibition signal. The prohibition signal is a signal indicating that cash cannot be accepted when the main device 9 is in use or is malfunctioning. If the cash receipt units 81, 82 have a prohibition signal output terminal, this output terminal is constantly monitored, and pairing is not permitted when the prohibition signal is output.

[0098] As an alternative configuration, since the end time of use of the main device 9 can often be predicted, a timer may be used to disable pairing while the device is in use. For example, a washing machine in a coin laundry has a set operating time per use, and a dryer's drying time is set according to the installation fee (payment amount). Therefore, these times may be stored as constants in advance in the unit storage unit 22, and a timer may be started when a payment completion signal is output. If the timer count does not reach a set value (usage time), pairing is disabled. When the timer count reaches the set value, pairing is enabled. In the case of devices such as dryers and massagers, additional payment may be made during use, extending the usage time. This can be detected when the additional payment is made, and the set value may be changed to the usage time based on the total amount after the additional payment, and it may be determined whether the value has been reached.

[0099] Depending on the type of device main body 9, it may be impossible for another customer to use the device while it is in use. For example, in the case of a massage machine, if a customer is already sitting in the device while it is in use, the customer will search for another massage machine to use. In such cases, it is not necessary to adopt a configuration that disables pairing while the device main body 9 is in use. Therefore, it is preferable that the cashless control unit 2 is provided with a setting unit that sets whether or not to use the configuration that disables pairing while the device is in use, and that the unit main program 201 is configured to realize the above functions according to the value of this setting unit.

[0100] In the case where the setting for disabling pairing during use is not used, upon receiving a payment completion signal, the unit main program 201 immediately outputs a pairing cancellation signal to the short-range wireless communication unit 4 to cancel the pairing and enable pairing with another user terminal. Even if the device does not have the function for disabling pairing during use, the device does not need to have a communication function for connecting to a network, thereby achieving the effect of lower manufacturing and running costs. Therefore, such an invention can also be understood as part of this specification. Even if the device does not have the function for disabling pairing during use, pairing will be maintained until the payment completion signal is output (the pairing cancellation signal is output when the payment completion signal is output), preventing the problem of double payment, where another user makes a payment during a payment procedure.

[0101] It is also possible to employ a configuration in which, when pairing is canceled, pairing is resumed only with the user terminal 6 that was paired immediately before the cancellation. For example, it is possible that pairing is accidentally canceled in the user terminal 6 before receiving a payment completion signal, or pairing is canceled because the battery level runs out. In anticipation of such cases, the unit main program 201 may be implemented to store the ID of the other party (user terminal 6) when pairing is established, and if pairing is canceled before receiving a payment completion signal, to perform pairing (resume pairing) only with the user terminal 6 with the stored ID, for a set period of time.

[0102] Furthermore, in a configuration in which pairing is cancelled upon receipt of payment completion information, a configuration may be adopted in which pairing is maintained (resumed) only with the user terminal 6 with which the device was paired immediately before the device was being used. For example, in a configuration in which the usage method (mode) can be changed during use, it may be necessary to pay an additional fee to change the mode while using the device. In this case, the payment completion output program 203 is implemented so that pairing is cancelled once, but pairing is resumed, payment for the additional fee is made, and the receipt of the payment completion signal is confirmed, after which the device operates in the changed mode.

[0103] In each of the above-described embodiments, a configuration may be adopted in which the collected cash payment history information can be viewed as needed by the device business operators who own and operate each device. An example of this configuration will be described below. The device usage support server 7 shown in Fig. 2 also provides a webpage for device businesses. Each device business is assigned an ID (device business ID) and password as a device business, and each device business can log in to the device usage support server 7 as a device business by entering the device business ID and password on a terminal (hereinafter referred to as device business management terminal) 13 operated by a person in charge at that business.

[0104] One of the pages for device operators (hereinafter referred to as device operator pages) provided by the device usage support server 7 is a page for viewing the payment status of the device owned (hereinafter referred to as payment status viewing page). Figure 14 is a schematic diagram showing an example of the payment status viewing page. A device information file 701 is stored in the storage unit 70 of the device usage support server 7. The device information file 701 is a database file that records information on all devices equipped with the retrofit unit 1, and stores information such as the device company ID of the device company that owns the device, the device ID, and the device name in a database.

[0105] The device usage support server 7 is equipped with a program (hereinafter referred to as the "viewed page display program") 74 for displaying a payment status viewing page such as that shown in Fig. 14. The viewed page display program 74 searches the device information file 201 using the device operator ID entered during login, and obtains the device IDs of all matching records. The viewed page display program 74 is then programmed to search the payment history information file 701 for each device ID over a certain period, and display the information of all matching records for the institution in a list as shown in Fig. 14. The viewed page display program 74 is also programmed to search the user information file 71 using the user ID, obtain personal information such as age and gender, and incorporate it as shown in Fig. 14.

[0106] As shown in Figure 14, the payment status viewing page allows device operators to view when, who, which device, and how much was paid for. In the example of Figure 14, personal user names are not published for privacy reasons. However, each user must consent in advance to having personal information other than their name, such as gender and age, viewed by device operators for sales promotion purposes.

[0107] This retrofitting method not only adds cashless payment functionality to owned devices, but also allows for the collection of customer information via the devices, which can be viewed by device operators as shown in Figure 14. This allows device operators to make decisions regarding the installation and operation of each device while referring to the payment status, which is very useful for optimizing device-based business. It may also be possible to calculate the total payment amount for each device, calculate the total separately for cash and cashless payments for one device, or calculate the total for multiple devices at one installation location.

[0108] What is important in this case is that such customer information collection can be performed while utilizing the current equipment. The same can be achieved by discarding the current equipment and introducing the latest equipment (with cashless payment functionality) that has the customer information collection function. However, replacing the current equipment with the latest equipment is costly, and equipment businesses are hesitant to do so if the current equipment has not yet been depreciated. On the other hand, according to the function retrofitting method of the embodiment, the customer information collection function is added retrofit by installing the retrofit unit 1, so the investment cost for the equipment business is much smaller.

[0109] In each of the above embodiments, a device usage support server 7 is provided separately from the payment server 5, and the device usage support server 7 provides the device app 60 and acts as an intermediary to transfer the payment request to the payment server 5. However, a payment request may be sent directly from the user terminal 6 to the payment server 5, and a successful payment completion notification may be returned directly from the payment server 5. In this case, the payment server 5 may be configured to perform each function of the device usage support server 7. That is, a configuration is also possible in which the payment server 5 provides the device app 60, directly receives the payment request and performs the payment, and a successful payment completion notification is sent directly to the add-on unit 1. In this configuration, the user information file, etc. is normally stored in a memory unit on the payment server 5.

[0110] As described above, a prepaid service may be used for settlement by the settlement server 5. A preferred embodiment relating to the prepaid service will be described below. Prepaid services are generally provided by a prepaid service provider that acts as an intermediary between the user and the provider of the product or service. However, there is also a known service in which the provider of the product or service itself receives and holds prepaid funds, allowing the prepaid funds to be used only for payments related to the provision of the product or service by that provider. This type of service is sometimes called house electronic money or house prepaid, but in the following explanation and drawings, it will be referred to as house money. A suitable configuration for a house money service is disclosed in Japanese Patent No. 7357376.

[0111] Providing house money services to users requires a server for managing prepaid money and making payments using prepaid money, which also requires server management and operation. While large businesses are often able to install, manage, and operate such servers, smaller businesses often face difficulties due to the initial setup and running costs. One solution to this problem is to provide a service that handles house money management for multiple businesses. This service handles the receipt and management of prepaid money and prepaid payments for multiple device operators. Hereinafter, such businesses will be referred to as house money agency businesses. Because house money agency businesses provide house money agency services to multiple device operators using their own servers, the cost per device operator is low, allowing them to provide house money agency services to each device operator at a low fee (agency commission).

[0112] In such a scheme, the server that provides the house money agency service is the device usage support server 7 or the payment server 5 in each of the above embodiments, and the payment application program 72 transmits information to the device usage support server 7 or the payment server 5 that the payment will be made using house money. In this case, the device usage support server 7 or the payment server 5 needs to know which device operator's prepaid funds (house money) are to be used, and the information transmitted by the payment application program 72 includes information that takes this into consideration.

[0113] FIG. 15 is a schematic diagram of a third embodiment, which is a modification of the first embodiment in which a house money agency service is used. The above-mentioned device operator's prepaid funds are to be used for, which is simply the operator ID. In this case, since it is the person receiving the device usage fee, it is referred to as the recipient ID. As shown in Figure 15, a database file (hereinafter referred to as the agency service provider information file) 51 that records information about each device operator that provides house money agency services is stored in the storage unit 50 on the payment server 5. Figure 16 is a schematic diagram showing an example of the structure of the agency service provider information file. The agency service provider information file 51 records the recipient ID, and each record is uniquely identified by the recipient ID.

[0114] Furthermore, as shown in Figure 15, a house money balance information file 52 that records prepaid balance information for each machine operator is stored in the storage unit 50 on the payment server 5. Figure 17 is a schematic diagram showing an example of the structure of a house money balance information file. As shown in Figure 17, a house money balance information file 52 is created for each recipient ID (for each machine operator) and stored in the storage unit 50. The agency service provider information file 51 and the house money balance information file 52 may also be stored in a server other than the payment server 5 that is managed by a house money agency, or in a storage unit on a management terminal.

[0115] Figure 17 is a schematic diagram showing an example of the structure of a house money balance information file. The house money balance information file is created in a state where it can be identified by the recipient ID, for example by using the recipient ID as the file name (or by recording the file name in each record of the agency service provider information file). As shown in Figure 17, the house money balance information file is a database file consisting of fields such as "house money user ID," "name," and "balance." The "house money user ID" is information that uniquely identifies each record in the house money balance information file, and is an ID that identifies the person who has entered into a contract to use the house money service with the recipient (device operator) of the recipient ID corresponding to the house money balance information file. The house money user ID is often a different ID from the user ID in the device app, but they may also be used interchangeably (the same ID). "Balance" is a field where the balance of prepaid money deposited by each user is recorded. The balance is recorded by depositing with a credit card or by inserting cash into a charging machine installed in a store where the machine is installed.

[0116] In this embodiment, the receiver ID is included in the payment information. Specifically, the device setting information file 221 stored in the unit storage unit 22 on the retrofit unit 2 stores the receiver ID in addition to the device ID and payment amount. Meanwhile, the payment information acquired by the application main program 601 on the user terminal 6 includes the receiver ID. If the retrofit unit 2 does not support house money (if the receiver ID is not recorded in the device setting information file 221 on the unit storage unit 22), the receiver ID will be a null value. If the receiver ID included in the payment information is not a null value, the application main program 601 displays a payment application screen in which house money can be selected as a payment method. An example of this is shown in FIG. 18. FIG. 18 is a schematic diagram showing an example of a payment application screen and a payment application confirmation screen in which house money can be selected as a payment method.

[0117] As shown in FIG. 18(1), the payment application confirmation screen has a house money selection section. In this example, the house money selection section is a command button (hereinafter referred to as the house money selection button) 691 that displays "Use house money," but it may also be a radio button or other selection section. Note that to use house money, the user must be registered as a user with the house money agency service and must have a house money user ID. This house money user ID is included in the setting information of the device app 60. The device app 60 displays the house money selection button 691 shown in FIG. 18(1) on the payment application screen only if the house money user ID is not a null value. Note that even if the house money user ID is not a null value, if the recipient ID included in the transmitted payment information is a null value, the device app 60 is implemented to display the house money selection button 691 as unselectable (grayed out) or hide the house money selection button 691 itself. When downloading the device application 60 to the user terminal 6 and registering as a user, if the user is a user of the house money agency service, the user is asked to enter the house money user ID, and the ID entered here is stored in the memory on the user terminal 6 as setting information for the device application 60.

[0118] The device app 60 includes a house money balance display program that displays the house money balance, and the house money selection button 691 is an execution button for the house money balance display program. The house money balance display program sends the recipient ID included in the payment information and the house money user ID held in the user terminal 6 to the device usage support server 7. The device usage support server 7 transfers these to the payment server 5 and executes the balance confirmation program 53 on the payment server 5. The balance confirmation program 53 opens the house money balance information file 52 corresponding to the recipient ID, searches it for the house money user ID, obtains the house money balance of the user, and returns it to the device usage support server 7. The device usage support server 7 then returns this value to the device app 60 on the user terminal 6.

[0119] The device app 60 is implemented so that, when the house money balance information is returned, it incorporates this value and displays a payment request confirmation screen. Figure 18(2) shows an example of a payment request confirmation screen with the house money balance displayed. As shown in Figure 18(2), the payment request confirmation screen in this example has a house money payment button 692 labeled "Pay with house money." The house money payment button 692 has embedded therein code that executes the payment request program 72 using the payment amount, recipient ID, and house money user ID as arguments. The payment request program 72 sends the argument information to the device usage support server 7, and the device usage support server 7 forwards the sent information to the payment server 5, causing the payment server 5 to make the payment. Upon payment, the balance related to the house money user ID in the house money balance information file is deducted by the payment amount, and the file is updated.

[0120] As shown in Figure 18 (2), the payment application confirmation screen has a charge button 693 labeled "Charge." An execution button for a charge program (not shown) on the payment server 5 is embedded in the charge button 693. The charge program is a program for charging house money by credit card payment or by debiting from a bank account. This part can be done in the same way as a regular prepaid service, so a description will be omitted. If the house money balance is less than the payment amount, the device application 60 displays the house money payment button 692 as an unexecutable button. In this case, when the charge button 693 is pressed to charge and update the balance, the payment application confirmation screen is coded to reacquire the balance, and if the reacquired balance is equal to or greater than the payment amount, the house money payment button 692 is changed to an executable button.

[0121] According to the third embodiment described above, payments can be made using house money, which encourages deposits of house money with the equipment provider. This has a positive impact on the equipment provider's cash flow and contributes to the equipment provider's management. When using a regular prepaid service that is not house money, the prepaid amount is paid to and deposited with the prepaid service provider, and is not transferred to the equipment provider until about one month after payment. On the other hand, in the case of house money, the prepaid amount is held by the equipment provider, and the deposited prepaid amount can be used as working capital for the equipment provider. When house money is deposited by credit card payment, etc., the deposit often takes one to several months. However, if a cash charging machine is installed in the store where the equipment is installed, the cash is deposited into the cash charging machine, and the equipment provider can collect the cash on the same day. This allows for more rapid use as working capital. Furthermore, in the above embodiment, the recipient ID is transmitted to the payment server 5 via the user terminal 6. Therefore, the retrofit unit 1 does not need to have an internet communication function for transmitting the recipient ID either, which leads to reduced installation costs and running costs.

[0122] Charging house money with cash can be done using a cash charging machine, or in manned stores, by having a store clerk deposit cash. That is, a charge amount transmitter that can transmit the charge amount to the server is installed in the store, and the store clerk operates the charge amount transmitter to transmit the amount of the deposited cash as the charge amount to the server. This configuration is disclosed in the above-mentioned Patent Publication No. 735376, so a detailed explanation will be omitted.

[0123] In the third embodiment, the recipient ID can also be obtained from the code display unit. Specifically, the code symbol 921 displayed on the code display unit 921 includes the recipient ID. When the user terminal 6 running the device app 60 reads the code symbol 921, the device ID and the recipient ID are obtained as described above. The device app 60 temporarily stores the recipient ID in a variable, and when the house money selection button 691 is pressed, the device app 60 transmits the recipient ID to the payment server 5 together with the house money user ID to obtain the house money balance, as described above. The subsequent processing is the same as described above. Note that, like the information for pairing, the recipient ID does not need to be displayed as a symbol. That is, the recipient ID may be printed as is and attached to the device as a sticker. In this case, the user checks the recipient ID by looking at the code display unit and manually enters the recipient ID into the user terminal 6. In this case, the device app 60 includes a screen for inputting the recipient ID.

[0124] The add-on unit of the second embodiment can also be configured to allow the use of house money. Similarly, the receiver ID is recorded in the device setting information file 221 on the unit storage unit 22, and after the camera 12 reads the terminal symbol 65 and pairing is established, the device app 60 obtains the receiver ID along with the payment amount from the unit storage unit 22. A payment request screen is then displayed on the user terminal 6, along with a house money selection button 691. When this button is pressed, the house money balance is obtained from the payment server 5 and incorporated into the payment request confirmation screen for display. When the house money payment button 692 is pressed, the payment server 5 is caused to perform payment in house money, as described above.

[0125] In each of the configurations that enable the use of house money described above, the receiver ID is a common (identical) ID on the add-on unit of each device installed in one store. Also, if the same device operator operates multiple stores and each store is set up with devices with add-on units, the receiver ID on the add-on units will be a common (identical) ID across all stores. Users can make payments using the same prepaid money (same house money user ID) at stores operated by the same device operator. Note that some device operators do not use a house money agency service, but instead prepare and operate their own servers to manage house money.

[0126] In each of the above embodiments, information on which of various cashless payment methods was used is also important management information, and it is preferable that the device operator can view it. To achieve this, information identifying the cashless payment service used is recorded in each record of the payment history information file 701. In this case, the information in the payment history information file 701 indicates the frequency of use of each cashless payment service and has value as market share information for cashless payment services. For example, data may indicate that the usage rate of Company A's cashless payment service exceeds 50% among devices operated by a certain device operator. Furthermore, by aggregating data from devices operated by device operators belonging to the same industry, it is possible to determine the proportion of each cashless payment service used in that industry. Therefore, it is preferable to store a business operator information file, which is a database file linking each record with the device operator ID recorded in the payment history information file 701, in the storage unit 50 of the device usage support server, for example, and record information identifying the industry or the industry therein so that data can be aggregated by industry or by industry.

[0127] In each of the above-described embodiments, the cashless output unit 3 is wired so as to be interposed between the coin mechanism 81 and bill validator 82 and the fee receipt input unit 93 of the device main body 9, but the configuration may also be such that the wiring extending from the cashless output unit 3 is simply connected to the wiring between the coin mechanism 81 and bill validator 82 and the fee receipt input unit 93 of the device main body 9. In this configuration, the cashless payment completion signal is simply input to the fee receipt input unit 93 through the connection point, and the cash payment signal is input directly to the fee receipt input unit 93 without passing through the cashless output unit 3.

[0128] However, operation is more stable if the cashless output unit 3 is interposed between them. Simply connecting the wires in between can result in a situation where cash payment and cashless payment are progressing simultaneously, which can cause unstable operation. With the cashless output unit 3 in between, for example, when a cash payment signal is input to the fee receipt input unit 93, the cashless payment function can be suspended until use of the device main body 9 is completed, or conversely, when a cashless payment completion signal is input to the fee receipt input unit 93, a control signal (block signal) can be sent to the coin mechanism 81 and bill validator 82 until use of the device main body 9 is completed.

[0129] In each of the above-described embodiments, it is not essential that the device main body 9 is equipped with the coin mechanism 81 and the bill validator 82; either one may be sufficient, or another type of cash receipt confirmation unit may be provided. For example, if the fee is less than 1,000 yen, only the coin mechanism 81 may be provided, and if the fee is in 1,000 yen increments only, only the bill validator 82 may be provided.

[0130] In the above embodiments, the transmission of payment information to the user terminal 6 is based on the function of the device app 60, but it may also be a function on the add-on unit 1. That is, a program for transmitting payment information to the user terminal 6 may be implemented in the add-on unit 1, and this program may be called and executed by the device app 60. In the first embodiment, the code display unit 921 is a sticker on which the code symbol 921 is printed, but it may also be a display. That is, an image of the code symbol may be created in advance and stored in the unit storage unit 22, and the image may be displayed on a display (for example, a small liquid crystal display).

[0131] Furthermore, in the above-described embodiment of the device invention, the cashless payment function is implemented as a retrofit by the add-on unit 1, but it may also be implemented from the beginning (at the time of manufacture and sale). Even in this case, payment information is sent to the payment server 5 via the user terminal 6, and successful payment completion is returned via the user terminal 6, so network communication functions are not required in the device, thereby reducing costs. Furthermore, the device and user terminal 6 are paired one-to-one to perform short-range wireless communication, and the device is not paired with other user terminals while in use, preventing accidents such as erroneous payments being made while another user is using the device. This also applies to the invention of the cash payment history information collection method; even if the cashless payment function is implemented from the beginning rather than via the add-on unit 1, cash payment history information can be collected without the need for network communication functions. It should be noted that the embodiment of the invention of the device may not have a cash payment function. Even if the device only has a cashless payment function, the effects of eliminating the need for a network communication function and preventing other users from making payments by mistake while the device is in use can be obtained in the same way. [Explanation of symbols]

[0132] 1 Retrofit unit 10 unit boxes 11 Device operator terminal 12 Camera 2 Cashless Control Unit 201 Unit Main Program 21 CPU 22 Memory section 3 Cashless output unit 4 Near field wireless communication department 5. Payment Server 6. User terminal 60 Device Apps 7. Device usage support server 71 User Information File 72 Payment Application Program 81 Coin Mech 82 Bill Bali 9. Device body 91 Usage status output section 93 Fee receipt input section

Claims

1. A cashless payment device used by a user, device control means for controlling the device; a short-range wireless communication unit that performs one-to-one short-range wireless communication by pairing with a user terminal that is a portable terminal operated by a user; A code display section; A payment information transmission unit; Payment completion receiving unit and It is equipped with the code display unit is a display unit that displays a code including information for pairing, the short-range wireless communication unit is a communication unit that performs pairing with the user terminal in accordance with the code displayed by the code display unit when the device is not currently paired with another terminal, and does not perform pairing with the user terminal when the device is currently paired with another terminal; the payment information transmission unit is a transmission unit that transmits payment information including a payment amount to the paired user terminal via the short-range wireless communication unit; the payment completion receiving unit is a receiving unit that receives, after the payment information is transmitted, a notification of payment completion from the paired user terminal via the short-range wireless communication unit; the device control means is a control means that controls the device so that the user can use the device after the payment completion receiving unit receives notification that payment has been completed; the device control means is means for outputting a pairing cancellation signal to the short-range wireless communication unit, and the short-range wireless communication unit is a communication unit that cancels the pairing when the pairing cancellation signal is output from the device control means, except when the pairing has already been canceled by a request from the user terminal side; The device control means is a means for outputting a pairing cancellation signal to the short-range wireless communication unit after the payment completion receiving unit receives notification that payment has been completed.

2. The device according to claim 1, characterized in that the device control means is capable of controlling the output of the pairing cancellation signal to the short-range wireless communication unit after the payment completion receiving unit receives notification of payment completion and after use of the device has ended.

3. A cashless payment device used by a user, device control means for controlling the device; a short-range wireless communication unit that performs one-to-one short-range wireless communication by pairing with a user terminal that is a portable terminal operated by a user; A camera and A payment information transmission unit; a payment completion receiving unit; It is equipped with the short-range wireless communication unit is a communication unit that, when a code symbol displayed on the user terminal is read by the camera, pairs with the user terminal if the device is not currently paired with another terminal, and does not pair with the user terminal if the device is currently paired with another terminal; the payment information transmission unit is a transmission unit that transmits payment information including a payment amount to the paired user terminal via the short-range wireless communication unit; the payment completion receiving unit is a receiving unit that receives, after the payment information is transmitted, a notification of payment completion from the paired user terminal via the short-range wireless transmitting unit; the device control means is a control means that controls the device so that the user can use the device after the payment completion receiving unit receives notification that payment has been completed; the device control means is a control means for causing the near field communication unit to pair with the user terminal when a code symbol containing information necessary for pairing is displayed on the user terminal and the camera reads the code symbol while the near field communication unit is not paired with another terminal; the device control means is means for outputting a pairing cancellation signal to the short-range wireless communication unit, and the short-range wireless communication unit is a communication unit that cancels the pairing when the pairing cancellation signal is output from the device control means, except when the pairing has already been canceled by a request from the user terminal side; The device control means is a means for outputting a pairing cancellation signal to the short-range wireless communication unit after the payment completion receiving unit receives notification that payment has been completed.

4. The device according to claim 3, characterized in that the device control means is capable of controlling the output of the pairing cancellation signal to the short-range wireless communication unit after the payment completion receiving unit receives notification of payment completion and after use of the device has ended.

5. A cash payment history information collection method for collecting cash payment history information in a device that has a cash receipt confirmation unit that confirms that cash inserted through a cash insertion slot is authentic and outputs a signal indicating the amount of cash received, and has a function of performing unmanned cash payments and a function of performing cashless payments, a storage step in which, when a cash payment is made, the device stores cash payment information including the date and time of the cash payment in a storage unit provided in the device; a pairing step in which, when the user selects cashless payment, the device pairs with the user terminal operated by the user to enable short-range wireless communication; a payment step in which the device transmits payment information including a payment amount to the paired user terminal via short-range wireless communication, the user terminal transmits the payment information to a payment server, and the payment server executes a payment program to perform the payment; a payment completion sending step in which, when the payment server returns payment completion information indicating that the payment has been successfully completed to the user terminal that sent the payment information, the user terminal sends the payment completion information to the device via short-range wireless communication; a use step in which, after the payment completion information is transmitted to the device, a device control means provided in the device controls the device to allow the user to use the device; It is equipped with A cash payment history information collection method characterized in that the device reads cash payment history information from a memory unit and transmits it via short-range wireless communication to the user terminal that has been paired in the pairing step, and the user terminal transmits the cash payment history information to the payment server or another server, thereby allowing the payment server or another server to collect the cash payment history information.

6. A retrofit cashless payment unit that adds a cashless payment function to a cash payment device that has a function of performing unmanned cash payments and includes a cash receipt confirmation unit that confirms that cash inserted from a cash insertion port is authentic and outputs a signal indicating the amount of the received cash, A cashless control unit; a cashless output unit; a short-range wireless communication unit capable of performing short-range wireless communication by pairing with a user terminal, which is a portable terminal operated by a user; Chord display section and It is equipped with the cashless control unit is provided in the housing of the cash settlement device and is connected in parallel to the cash receipt confirmation unit to a fee receipt input unit to which a signal from the cash receipt confirmation unit is input, The cashless output unit is interposed between the cashless control unit and the fee receipt input unit, and outputs an output signal in the same communication specifications as the output signal of cash receipt from the cash receipt confirmation unit; The code display section displays a code including information necessary for pairing, the short-distance wireless communication unit is a communication unit that pairs with the user terminal according to the code displayed by the code display unit; the cashless control unit is a control unit that transmits payment information including a payment amount to the paired user terminal via the short-range wireless communication unit; A retrofit cashless payment unit characterized in that the cashless control unit is a control unit that, after sending payment information, when the short-range wireless transmission unit receives a notification that payment has been completed from the paired user terminal, outputs a payment completion signal to the cashless output unit using the same communication specifications as the cash receipt confirmation by the cash receipt confirmation unit.

7. The cashless payment unit according to claim 6, wherein the code display unit is a sticker on which a code symbol is printed to symbolize and display the code.

8. A retrofit cashless payment unit that adds a cashless payment function to a cash payment device that has a function of performing unmanned cash payments and includes a cash receipt confirmation unit that confirms that cash inserted from a cash insertion port is authentic and outputs a signal indicating the amount of the received cash, A cashless control unit; a cashless output unit; a short-range wireless communication unit capable of performing short-range wireless communication by pairing with a user terminal, which is a portable terminal operated by a user; Camera and It is equipped with the cashless control unit is provided in the housing of the cash settlement device and is connected in parallel to the cash receipt confirmation unit to a fee receipt input unit to which a signal from the cash receipt confirmation unit is input, The cashless output unit is interposed between the cashless control unit and the fee receipt input unit, and outputs an output signal in the same communication specifications as the output signal of cash receipt from the cash receipt confirmation unit; The camera is capable of photographing a code symbol, in which a code including information necessary for pairing is symbolized, when the code symbol is displayed on a user terminal, which is a mobile terminal operated by a user; the short-range wireless communication unit is a communication unit that, when a camera captures a code symbol displayed on the user terminal, pairs with the user terminal according to information contained in the code symbol; the cashless control unit is a control unit that transmits payment information including a payment amount to the paired user terminal via the short-range wireless communication unit; A retrofit cashless payment unit characterized in that the cashless control unit is a control unit that, after sending payment information, when the short-range wireless transmission unit receives a notification that payment has been completed from the paired user terminal, outputs a payment completion signal to the cashless output unit using the same communication specifications as the cash receipt confirmation by the cash receipt confirmation unit.

9. 2. An application program installed on a user terminal operated by a user of the device according to claim 1, a pairing program for performing pairing for near field wireless communication in accordance with the code displayed by the code display unit; a payment application program that, after pairing is performed by the pairing program, when receiving the payment information from the short-range wireless transmission unit that is the pairing partner, transmits the payment information and causes the payment server to execute the payment program; a payment completion sending program that, after sending payment information by a payment application program and causing a payment server to execute the payment program, receives payment completion information indicating that the payment has been successfully completed from the payment server and sends the payment completion information to the short-range wireless communication unit that is currently paired; An application program comprising:

10. An application program installed on the user terminal operated by a user of the device according to claim 3, a code display program for displaying the code symbols; a pairing program that, when the camera reads the code symbol displayed by the code display program, performs pairing with the near-field wireless communication unit in accordance with information included in the code symbol; a payment application program that, after pairing is performed by the pairing program, when receiving the payment information from the short-range wireless communication unit that is the pairing partner, transmits the payment information and causes the payment server to execute the payment program; a payment completion sending program that, after transmitting payment information by a payment application program and causing a payment server to execute the payment program, receives payment completion information, which is a signal indicating that the payment has been successfully completed, from the payment server and sends the payment completion information to the short-range wireless communication unit that is currently paired; An application program comprising:

11. 7. An application program installed in a user terminal operated by a user of a device equipped with the retrofit cashless unit according to claim 6, a pairing program that performs pairing with the short-range wireless communication unit in accordance with the code displayed by the code display unit; a payment application program that, after pairing is performed by the pairing program, when receiving the payment information from the short-range wireless communication unit that is the pairing partner, transmits the payment information and causes the payment server to execute the payment program; a payment completion sending program that, after transmitting payment information by a payment application program and causing a payment server to execute the payment program, receives payment completion information, which is a signal indicating that the payment has been successfully completed, from the payment server and sends the payment completion information to the short-range wireless communication unit that is currently paired; An application program comprising:

12. An application program installed in a user terminal operated by a user of a device equipped with the retrofit cashless unit according to claim 8, a code display program for displaying the code symbols; a pairing program that, when the camera reads the code symbol displayed by the code display program, performs pairing with the near-field wireless communication unit in accordance with information included in the code symbol; a payment application program that, after pairing is performed by the pairing program, when receiving the payment information from the short-range wireless communication unit that is the pairing partner, transmits the payment information and causes the payment server to execute the payment program; a payment completion sending program that, after transmitting payment information by a payment application program and causing a payment server to execute the payment program, receives payment completion information, which is a signal indicating that the payment has been successfully completed, from the payment server and sends the payment completion information to the short-range wireless communication unit that is currently paired; An application program comprising:

13. A cashless payment device used by a user, device control means for controlling the device; a short-range wireless communication unit that performs short-range wireless communication with a user terminal that is a mobile terminal operated by a user; A payment information transmission unit; Payment completion receiving unit and It is equipped with the payment information transmission unit is a transmission unit that transmits payment information including a payment amount to the user terminal via the short-range wireless communication unit; the payment completion receiving unit is a receiving unit that, after the payment information is transmitted, receives a notice of payment completion from the user terminal that transmitted the payment information via the short-range wireless communication unit; the device control means is a control means that controls the device so that the user can use the device after the payment completion receiving unit receives notification that payment has been completed; The payment information transmitted by the payment information transmitting unit includes a recipient ID, or a code display unit is provided for displaying a code including the recipient ID, The receiver ID is an ID that identifies the receiver who allows a user to use the device and receives the fee related to the payment amount, and is an ID that is referenced by the payment server when a user terminal that has received payment information accesses the payment server and makes a payment to the receiver identified by the receiver ID using prepaid money that has been paid and deposited in advance by the user operating the user terminal.

14. A cashless payment device used by a user, device control means for controlling the device; a short-range wireless communication unit that performs short-range wireless communication with a user terminal that is a mobile terminal operated by a user; A camera and A payment information transmission unit; a payment completion receiving unit; It is equipped with the payment information transmission unit is a transmission unit that transmits payment information including a payment amount to the user terminal via the short-range wireless communication unit; the payment completion receiving unit is a receiving unit that receives, when a notice of payment completion is transmitted from the user terminal after the payment information is transmitted, the notice of payment completion via the short-range wireless transmitting unit; the device control means is a control means that controls the device so that the user can use the device after the payment completion receiving unit receives notification that payment has been completed; the device control means is a control means that, when the code symbol is displayed on the user terminal and the camera reads the code symbol, causes the payment information transmission unit to transmit payment information to the user terminal; The payment information transmitted by the payment information transmitting unit includes a recipient ID in addition to the payment amount, and the recipient ID is an ID that identifies the recipient who allows the user to use the device and receives the fee related to the payment amount, and is an ID that is referenced by the payment server when a payment is made to the recipient identified by the recipient ID using prepaid money that has been paid and deposited in advance by the user operating the user terminal when the user terminal that received the payment information accesses the payment server.

15. A retrofit cashless payment unit that adds a cashless payment function to a cash payment device that has a function of performing unmanned cash payments and includes a cash receipt confirmation unit that confirms that cash inserted from a cash insertion port is authentic and outputs a signal indicating the amount of the received cash, A cashless control unit; a cashless output unit; a short-range wireless communication unit capable of performing short-range wireless communication with a user terminal, which is a portable terminal operated by a user; It is equipped with the cashless control unit is provided in the housing of the cash settlement device and is connected in parallel to the cash receipt confirmation unit to a fee receipt input unit to which a signal from the cash receipt confirmation unit is input, The cashless output unit is interposed between the cashless control unit and the fee receipt input unit, and outputs an output signal in the same communication specifications as the output signal of cash receipt from the cash receipt confirmation unit; The cashless control unit is a control unit that transmits payment information including a payment amount to the user terminal via the short-range wireless communication unit, the cashless control unit is a control unit that, after transmitting the payment information, when the short-range wireless transmission unit receives a payment completion signal from the user terminal that transmitted the payment information, outputs a payment completion signal to the cashless output unit using the same communication specifications as the cash receipt confirmation by the cash receipt confirmation unit; The payment information transmitted by the cashless control unit includes a recipient ID, or a code display unit is provided that displays a code including the recipient ID, A retrofit cashless payment unit characterized in that the recipient ID is an ID that identifies the recipient who allows a user to use the equipment and receives the fee related to the payment amount, and is an ID that is referenced by the payment server when a user terminal that has received payment information accesses the payment server and makes a payment to the recipient identified by the recipient ID using prepaid money that has been paid and deposited in advance by the user operating the user terminal.

16. A retrofit cashless payment unit that adds a cashless payment function to a cash payment device that has a function of performing unmanned cash payments and includes a cash receipt confirmation unit that confirms that cash inserted from a cash insertion port is authentic and outputs a signal indicating the amount of the received cash, A cashless control unit; a cashless output unit; a short-range wireless communication unit capable of performing short-range wireless communication by pairing with a user terminal, which is a portable terminal operated by a user; Camera and It is equipped with the cashless control unit is provided in the housing of the cash settlement device and is connected in parallel to the cash receipt confirmation unit to a fee receipt input unit to which a signal from the cash receipt confirmation unit is input, The cashless output unit is interposed between the cashless control unit and the fee receipt input unit, and outputs an output signal in the same communication specifications as the output signal of cash receipt from the cash receipt confirmation unit; The camera is capable of capturing an image of a code symbol when the code symbol is displayed on a user terminal, which is a mobile terminal operated by a user; the cashless control unit is a control unit that, when the camera reads the code symbol displayed on the user terminal, transmits payment information including the payment amount to the user terminal via the short-range wireless communication unit; the cashless control unit is a control unit that, after transmitting the payment information, when the short-range wireless transmission unit receives a payment completion signal from the user terminal that transmitted the payment information, outputs a payment completion signal to the cashless output unit using the same communication specifications as the cash receipt confirmation by the cash receipt confirmation unit; A retrofit cashless payment unit characterized in that the payment information sent by the cashless control unit includes a recipient ID, which is an ID that identifies the recipient who allows the user to use the equipment and receives the fee related to the payment amount, and is an ID that is referenced by the payment server when a payment is made to the recipient identified by the recipient ID using prepaid money that has been paid and deposited in advance by the user operating the user terminal when the user terminal that received the payment information accesses the payment server.

17. An application program installed on the user terminal operated by a user of the device according to claim 13, a payment application program that, upon receiving the payment information from the short-range wireless transmission unit, transmits the payment information and causes a payment server to execute a payment program; a payment completion sending program that, after sending payment information by a payment application program and causing a payment server to execute the payment program, receives payment completion information indicating that the payment has been successfully completed from the payment server and sends the payment completion information to the short-range wireless communication unit; It is equipped with The payment application program is an application program characterized in that it is a program that can send the recipient ID sent from the payment information sending unit or input by the user to a payment server together with the payment information, and execute payment to the recipient identified by the recipient ID using prepaid money that has been paid and deposited in advance by the user operating the user terminal.

18. An application program installed in the user terminal operated by a user of the device according to claim 14, a code display program for displaying the code symbols; a payment application program that, when the code symbol displayed by the code display program is read by the camera and the payment information is received from the short-range wireless communication unit, transmits the payment information and causes a payment server to execute a payment program; a payment completion sending program that, after sending payment information by a payment application program and causing a payment server to execute the payment program, receives payment completion information indicating that the payment has been successfully completed from the payment server and sends the payment completion information to the short-range wireless communication unit; It is equipped with The payment application program is an application program characterized in that it is a program that can send the payment amount and the recipient ID to a payment server and execute payment to the recipient identified by the recipient ID using prepaid money that has been paid and deposited in advance by the user operating the user terminal.

19. An application program installed in a user terminal operated by a user of a device equipped with the retrofit cashless unit according to claim 15, a code reading program for reading the code symbol displayed by the code display unit; a payment application program that, when receiving the payment information from the short-range wireless communication unit after the code reading program reads the code symbol, transmits the payment information and causes a payment server to execute a payment program; a payment completion sending program that, after sending payment information by a payment application program and causing a payment server to execute the payment program, receives payment completion information indicating that the payment has been successfully completed from the payment server and sends the payment completion information to the short-range wireless communication unit that is currently paired; It is equipped with The payment application program is an application program characterized in that it is a program that can send the recipient ID sent by the cashless control unit or input by the user to a payment server along with the payment information, and execute payment to the recipient identified by the recipient ID using prepaid money that has been paid and deposited in advance by the user operating the user terminal.

20. An application program installed in a user terminal operated by a user of a device equipped with the retrofit cashless unit according to claim 16, a code display program for displaying the code symbols; a payment application program that, when the code symbol displayed by the code display program is read by the camera and the payment information is received from the short-range wireless communication unit, transmits the payment information and causes a payment server to execute a payment program; a payment completion sending program that, after sending payment information by a payment application program and causing a payment server to execute the payment program, receives payment completion information indicating that the payment has been successfully completed from the payment server and sends the payment completion information to the short-range wireless communication unit that is currently paired; It is equipped with The payment application program is an application program characterized in that it is a program that can send the payment amount and the recipient ID to a payment server and execute payment to the recipient identified by the recipient ID using prepaid money that has been paid and deposited in advance by the user operating the user terminal.

Images