WO2024116299A1 - Retrofitted cashless payment unit and method of retrofitting with cashless payment function and customer information collection function - Google Patents

Abstract

[Problem] To add a cashless payment function at low cost to a cash payment apparatus only capable of cash payments. [Solution] In the present invention, a cash payment apparatus 1 is retrofitted with a cashless payment function. When a payment code symbol displayed on a display 11 is read by a user terminal, then specific information about the cash payment apparatus 1, a payment amount, and a user ID are transmitted to a payment server 7, and a payment program 71 is executed. When a communication unit 4 receives a payment completion signal transmitted by the payment server 7, then a cashless output unit 3 outputs the payment completion signal to a fee reception input unit 93 by the same communication specifications as those for cash reception confirmation by cash reception confirmation units 81, 82.

Description

Retrofit cashless payment unit, and method for retrofitting cashless payment function and customer information collection function

The invention of this application relates to improvements to various devices that operate as devices that can only handle cash payments.

Among the devices used to provide goods or services, devices that handle cash payments are equipped with units such as a coin mechanism and a bill validator. A coin mechanism and a bill validator are units that determine the authenticity of inserted cash (coins or bills), and if it is genuine, count and output the quantity (amount inserted). In the rest of 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 paying out change or refunds in the event of a cancellation.

Cash receipt confirmation units such as coin mechs 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 reached unmanned payment devices, and many newly developed and manufactured devices 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 unmanned cash payment is referred to as a cash payment device.

JP 2021-051436 A

However, cash payment machines that were manufactured and sold in the past and are currently in operation still only allow cash payments. For example, let's say that the latest cash payment machines have a cashless payment function. Businesses that purchase this type of cash payment machine feel that it would be more convenient for customers if they could make cashless payments possible, but are often hesitant to introduce it because the cost of the current cash payment machine has not yet been amortized, or because they feel that it is not rational to change the current cash payment machine to one with an expensive cashless payment function when it is still usable.

In addition, for manufacturers of cash payment machines, if the market for the machines themselves is not large and the number of units sold is not high, there is often little incentive to develop new machines with cashless payment functions.
Examples of such machines that only accept cash payments include ticket vending machines and soft drink vending machines, as well as payment machines in coin parking lots, unmanned kerosene vending machines, and automatic rice polishing machines.
In view of the above-mentioned circumstances, the present invention aims to make it possible to add a cashless payment function at low cost to cash payment machines currently operating as machines that can only handle cash payments.

In order to solve the above problems, this specification discloses a first invention and a second invention as an invention of a retrofit cashless payment unit. The retrofit cashless payment unit according to these inventions is a unit that adds a cashless payment function to a cash payment device having a function of performing unmanned cash payment by having a cash receipt confirmation unit that confirms that the cash inserted through the cash insertion slot is genuine and outputs a signal of the received amount of the cash.
The add-on cashless payment unit according to the first aspect of the present invention includes a cashless control unit, a cashless output unit, a communication unit, and a code display unit.
The cashless control unit is provided within 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 disposed between the cashless control unit and the fee receipt input unit, and outputs an output signal in the same communication format as the output signal from the cash receipt confirmation unit.
The code display section displays a code symbol for settlement.
The settlement code symbol is a symbolized code that, when read by a user terminal, which is a portable terminal operated by a user, causes the user terminal to access a settlement server, transmit specific information of the cash settlement device, the settlement amount, and a user ID, and execute a settlement program on the settlement server, and includes the specific information of the cash settlement device and the settlement amount.
The communication unit is connected to the payment server via a network, and when the payment server executes the payment program and sends a payment completion signal indicating that the payment has been completed successfully, it receives the payment completion signal and inputs it to the cashless control unit.
The cashless control unit is implemented with a payment completion output program, which is a program that, when a payment completion signal is input from the communication unit, outputs the payment completion signal to the cashless output unit in the same communication specifications as the cash receipt confirmation by the cash receipt confirmation unit.
The first invention may have a configuration in which a display is provided, the code display section includes a symbol display program, and the symbol display program causes the display section to display the settlement code symbol.
The first invention may have a configuration in which the code display portion is a sticker on which a code symbol for payment is printed.
In addition, the add-on cashless payment unit according to the second invention includes a cashless control unit, a cashless output unit, a communication unit, and a camera.
The cashless control unit is provided within 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 disposed between the cashless control unit and the fee receipt input unit, and outputs an output signal in the same communication format as the output signal from the cash receipt confirmation unit.
The cashless control unit is implemented with an ID acquisition program that acquires the user ID contained in the payment code symbol by having a camera read the payment code symbol displayed on the user terminal, which is a portable terminal operated by the user, and a payment request program that, when the ID acquisition program acquires the user ID, transmits the user ID, specific information of the cash payment device, and the payment amount to execute the payment program on the payment server.
The communication unit is connected to the payment server via a network, and when the camera reads the payment code symbol and the payment request program executes the payment program on the payment server, it receives a payment completion signal indicating that the payment has been completed successfully, and inputs the payment completion signal to the cashless control unit.
The cashless control unit is implemented with a payment completion output program, which is a program that, when a payment completion signal is input from the communication unit, outputs the payment completion signal to the cashless output unit in the same communication specifications as the cash receipt confirmation by the cash receipt confirmation unit.
In addition, the add-on cashless payment unit of each of the above inventions is
The cashless output unit is in a state of being interposed between the fee receipt input unit and both the cashless control unit and the cash receipt confirmation unit, and when a cash receipt output signal is received from the cash receipt confirmation unit, the output signal is input to the fee receipt input unit with the communication specifications as it is,
The device may be configured to have a cash settlement information output program implemented which, when a cash receipt output signal is received from the cash receipt confirmation unit, outputs the amount of cash received in the output signal and the date and time when the output signal was output so that the amount is stored in a memory unit and can be referenced.
In addition, the method for retrofitting a cashless payment function and a customer information collection function according to the disclosed invention is a method for adding a cashless payment function and a customer information collection function to a cash payment device having a function of performing unmanned payments with cash, by using the retrofit cashless payment unit according to the first invention, which is equipped with a cash receipt confirmation unit that confirms that the cash inserted through the cash insertion slot is genuine and outputs a signal of the amount of the received cash.
In this method,
A payment performance information recording program is installed in a separate server connected to the payment server or the cashless control unit via a network.
The payment performance information recording program is a program that, when the payment code symbol is read, the payment program is executed, and the payment is completed normally, records the specific information of the cash payment device and the payment amount contained in the payment information relating to the payment, as well as the user's personal information related to the user ID, in a payment performance information file on the payment server or another server.
And this method is,
a code reading step of having a user terminal read the code symbol for settlement displayed on the code display unit;
a payment request step of transmitting specific information of the cash payment device, a payment amount, and a user ID to request execution of a payment program on a payment server;
After the payment request step, when a payment completion signal is received indicating that the payment has been completed normally, a customer information recording step is provided in which the payment performance information recording program records specific information of the cash payment device related to the payment, the payment amount, and personal information of the user in a payment performance information file.
In addition, a method for retrofitting a cashless payment function and a customer information collection function according to another disclosed invention is a method for retrofitting a cashless payment function and a customer information collection function to a cash payment device having 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 the received cash, and has the function of performing unmanned payments with cash, by using a retrofit cashless payment unit according to the second invention.
In this method,
A payment performance information recording program is installed in a separate server connected to the payment server or the cashless control unit via a network.
The payment performance information recording program is a program that, when the camera reads the payment code symbol, the payment program is executed, and the payment is completed normally, records the specific information of the cash payment device and the payment amount contained in the payment information relating to the payment, as well as the user's personal information related to the user ID, in a payment performance information file on the payment server or another server.
And this method is,
a payment request step of reading a code symbol for payment on the user terminal using a camera and executing a payment request program;
After the payment request step, when a payment completion signal is received indicating that the payment has been completed normally, a customer information recording step is provided in which the payment performance information recording program records specific information of the cash payment device related to the payment, the payment amount, and personal information of the user in a payment performance information file.

As described below, the retrofit cashless payment unit according to the disclosed invention allows a cashless payment function to be added to a currently operating cash payment device that only accepts cash payments, improving the convenience of the device. This can promote the sale of products or services using 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 add-on cashless payment unit of the disclosed invention, the cashless output unit outputs a cashless payment completion signal to the fee receipt input unit of the cash payment device using a signal with the same communication specifications as the output signal from the existing cash receipt confirmation unit, so modifications to the fee receipt input unit are basically unnecessary, and cashless payment function can be easily and inexpensively introduced.
In addition, according to a configuration in which the monitor transmission program outputs cash payment information to the outside in the case of cash payment, it is possible to obtain an effect that cash payment information that could not be collected conventionally can be collected.
In addition, according to the disclosed invention of the method for retrofitting a cashless payment function and a customer information collection function, a customer information collection function can be retrofitted in addition to a cashless function to a cash payment device that does not have such a function, making it possible to collect information on the type of customers who use the cash payment device without incurring significant cost.

1 is a perspective schematic diagram showing a retrofit cashless payment unit of the first embodiment and its installation. FIG. A cross-sectional schematic diagram showing the mounting structure of the retrofit cashless payment unit of the first embodiment. A block diagram showing the general configuration of a retrofit cashless payment unit of the first embodiment. 1 is a schematic diagram showing an example of the configuration of a cashless output unit and wiring when installed as an add-on unit. FIG. 4 is a flowchart showing the execution relationship between a main program and other sub-programs. FIG. 4 is a schematic diagram showing screen transitions on the display according to each program. 1 is a schematic diagram showing the function of a payment code symbol. FIG. FIG. 13 is a schematic diagram showing an application for a retrofit unit. 13 is a schematic diagram showing an example of screen transition of the display when the main device has multiple charges. FIG. FIG. 11 is a schematic perspective view showing an add-on unit according to a second embodiment and its installation. FIG. 11 is a block diagram showing a schematic configuration of an add-on unit according to a second embodiment. 10 is a flowchart showing an execution relationship between a main program and other sub-programs in the second embodiment. 13A to 13C are schematic diagrams showing screen transitions on a display in a second embodiment. FIG. 11 is a schematic diagram illustrating an application for an add-on unit according to a second embodiment. 1 is a schematic diagram showing an embodiment of a method for retrofitting a cashless payment function and a customer information collection function according to the present invention. FIG. 13 is a schematic diagram showing an example of a payment status viewing page. FIG. 13 is a schematic diagram showing a modification example of a server.

Next, a mode (embodiment) for carrying out the invention of this application will be described. First, a retrofit cashless payment unit according to a first embodiment will be described.
Figure 1 is a schematic oblique view showing a retrofit cashless payment unit of the first embodiment and its installation, Figure 2 is a schematic cross-sectional view showing the installation structure of the retrofit cashless payment unit of the first embodiment, and Figure 3 is a block diagram showing the general configuration of the retrofit cashless payment unit of the first embodiment.

The add-on cashless payment unit of the embodiment (hereinafter abbreviated as add-on unit) is a unit that adds a cashless payment function to the cash payment device 9 by retrofitting it. As described above, the cash payment device 9 is a variety of devices that have a cash payment function and are used to provide products or services with unmanned payment, such as ticket vending machines, soft drink vending machines, coin parking settlement machines, automatic rice polishing machines, etc. These cash payment devices are hereinafter referred to as the main device.

The main device 9 has a cash settlement function and is therefore 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 genuine and outputs a signal of the amount of the received cash. In the example shown in Figures 1 to 3, the main device 9 is equipped with a coin mechanism 81 and a bill validator 82 as a cash receipt confirmation unit.

The main device 9 has a fee receipt input unit 93 as an element for receiving fee deposit signals from these cash receipt confirmation units 81, 82. The fee receipt input unit 93 is an element for inputting a signal indicating that a fee for a product or service provided using the main device 9 has been deposited, and is an element for inputting signals from the coin mechanism 81 and bill validator 82. The signal input by the fee receipt input unit 93 is input to a determination unit (not shown) which determines whether the paid fee has reached a specified fee. If it is determined that the specified fee has been paid, the main device 9 performs an operation to provide the product or service.
The add-on unit is mounted on such a main device 9 after it has been installed. "After it" means that it is additionally attached after the main device 9 has been manufactured and completed. In many cases, the add-on unit of the embodiment is attached to the main device 9 after it has been installed and started to operate.

As shown in FIG. 1, the add-on unit has a unit box 1, and each element is housed within the unit box 1. The add-on unit is attached to the main device 9 by fixing the unit box 1 to the operation surface 90 of the main device 9. The operation surface 90 of the main device 9 is the surface on which a user of the main device 9 performs operations such as payment, and is usually the surface of the front panel. As shown in FIG. 1, the operation surface 90 is provided with cash insertion slots 811, 821. In this example, the main device 9 is provided with a coin mechanism 81 and a bill validator 82, and therefore has a coin insertion slot 811 and a bill insertion slot 821 as cash insertion slots.

The unit box 1 is fixed to the operation surface 90 of the main device 9 by screws or rivets, etc. At this time, as shown in FIG. 2, an opening 92 is formed in the front panel 91 forming the operation surface 90. The opening 92 is for passing cables through, and is smaller than the rear surface of the unit box 1. Therefore, when the unit box 1 is fixed to the front panel 91, the opening 92 is blocked (concealed) by the unit box 1.

A cashless control unit 2, a cashless output unit 3, a communication unit 4, etc. are provided within the unit box 1 as elements of the retrofit unit.
The cashless control unit 2 is a central element of the retrofit unit, and in this embodiment, a very small computer such as a Raspberry Pi (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. An OS that operates the CPU 21 is installed in the storage unit 22.

In this embodiment, the cashless output unit 3 is composed of a microcomputer that can write programs. As shown in FIG. 3, the cashless output unit 3 is wired between the coin mech 81 and bill validator 82 and the fee receipt input unit 93 of the main device 9. That is, the wiring from the coin mech 81 and bill validator 82 is connected to the input terminals of the cashless output unit 3, and the output terminals of the cashless output unit 3 are connected to the fee receipt input unit 93 of the main device 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 is installed) between the coin mech 81 and bill validator 82 and the fee receipt input unit 93. The direction in which the signals are transmitted is indicated by an arrow in FIG. 3.

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

3, the cashless control unit 2 is connected to another input terminal of the cashless output unit 3. In this embodiment, the cashless control unit 2 and the cashless output unit 3 communicate with each other via microcomputers, and any communication specifications may be adopted.
The payment completion signal output by the payment completion output program described above is input to the cashless control unit 2. 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. If the cashless control unit 2 and cashless output unit 3 are configured to communicate with each other using the same specifications as those used between the coin mech 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.

An example of the configuration of such a cashless output unit 3 and the wiring when a retrofit unit is installed will be described with reference to Fig. 4. Fig. 4 is a schematic diagram showing an example of the configuration of a cashless output unit and the wiring when a retrofit unit is installed. In Fig. 4, as an example, a coin mechanism 81 of a certain model is connected to the fee receipt input unit 93 of the main device 9, and an example of installing a retrofit unit to this is shown.
In the example of Fig. 4, the coin mechanism 81 and the fee receiving input unit 93 have seven terminals, which are currently (before the retrofit unit is installed) connected to each other as shown in Fig. 4 (1). The terminals are as follows:
No. 1: 100 yen deposit No. 2: 100 yen control No. 3: 500 yen deposit No. 4: 500 yen control No. 5: +12V power supply voltage No. 6: +24V power supply voltage No. 7: Earth The 100 yen deposit is a signal that one 100 yen coin has been deposited, and the 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.

The 100 yen control is a terminal for transmitting and receiving a signal when the deposit of a 100 yen coin is blocked for some reason, and the 500 yen control is a terminal for transmitting and receiving a signal when the deposit of a 500 yen coin is blocked for some reason. These are usually transmitted from the main device 9 to the coin mech 82. For example, a control signal (block signal) is transmitted when the main device 3 is stopped or when the main device 3 is in operation and is providing a product or service and cannot receive new fees.
The power supply terminals No. 5 and No. 6 are terminals for receiving the supply of power supply voltage from the main device 9, and either one of the terminals is selected and made active.

When mounting an add-on unit on a cash settlement device having a coin mechanism 81 configured as described above, the terminals are disconnected and then connected as shown in Fig. 4 (2). As shown in Fig. 4 (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 mounting an add-on unit, remove the coin mechanism 81 and the charge receipt input unit 93. Then, as shown in Figure 4 (2), connect the coin mechanism 81 to the first terminal group 31 (No. 1 to No. 4), and connect the charge receipt input unit 93 to the second terminal group 32 (No. 1 to No. 4).

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.

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

The retrofit unit of this embodiment is equipped with a small display 11. As shown in Figures 1 and 2, the display 11 is attached to the front of the unit box 1. The display 11 is, for example, an approximately 3.5-inch liquid crystal display 11. In this embodiment, the display 11 is a touch panel display, and also serves as an input unit for the user. The cashless control unit 2 is equipped with an interface for the display 11, such as a DIS connector, and the display 11 is connected to the interface by a cable.

The cashless control unit 2 also has several programs implemented, including a symbol display program 202 that displays a payment code symbol on the display 11. These programs are stored in the memory unit 22 and are executable by the CPU 21. One program stored in the memory unit 22 is the main program 201, and the other programs are sub-programs that are called and executed by the main program 201. In addition to the symbol display program 202, other programs implemented include a notification request program 203 and a payment completion output program 204.

Fig. 5 is a flow chart showing the execution relationship between the main program and other sub-programs, and Fig. 6 is a schematic diagram showing the screen transition of the display by each program. Fig. 5 and Fig. 6 are examples in which the usage fee for the main device 9 is a fixed fee (only one type of fee).
The main program 201 is a resident program that is automatically executed when the power supply of the retrofit unit is turned on and the retrofit unit is operating. As shown in Fig. 5, the main program 201 displays a standby screen to be started on the display 11. An example of the standby screen is shown in Fig. 6 (1). As shown in Fig. 6 (1), the standby screen is provided with a cashless button 111, and a message is displayed requesting the user to press the cashless button 111 when making a cashless payment.

The cashless button 111 is an execution button for the symbol display program 202. The symbol display program 202 is a program that reads an image file of a payment code symbol from the memory unit 22 and displays it on the display 11. FIG. 6 (2) shows the state in which the payment code symbol 112 is displayed. As shown in FIG. 6 (2), in this embodiment, the payment code symbol 112 is a two-dimensional code symbol such as a QR code (registered trademark).

7 is a schematic diagram showing the function of the payment code symbol. In this embodiment, a user terminal 6 and a payment server 7 are used as elements that cooperate with the retrofit unit. The user terminal 6 is a mobile terminal, typically a smartphone, that can read the payment code symbol 112 and execute the code.
The payment code symbol 112 is a symbol that visualizes a code containing information to be transmitted to the payment server 7, and is a code symbol that visualizes a code for executing the payment program 71 on the payment server 7 when read by the camera provided on the user terminal 6.

The payment code symbol 112 includes the payment amount, the device type ID, and the device ID. In the example shown in Fig. 7, the payment amount is passed as a variable named fee, the device ID is passed as a variable named mkid, and the device ID is passed as a variable named mid. The device type ID and the device ID are information recorded and managed in a device information file 54 recorded in a storage unit 50 on the add-on application server 5, which will be described later.
The device type ID is an ID that identifies the type of main device 9. For example, a ticket vending machine for a restaurant is designated as K1, other ticket vending machines as K2, a vending machine for soft drinks as K3, other vending machines as K4, and so on.

The device ID is an ID that identifies each main device 9. It is determined when the retrofit unit is installed, and is recorded in the device information file 54. Usually, a registration program (not shown) that registers the main device 9 in the device information file 54 is implemented, and the registration program automatically generates and records the ID.
In addition, information about the business operator that owns the main device 9 (such as the device operator ID and the business operator name) is recorded in the device information file 54. In addition, the ID of the retrofit unit itself may be recorded in association with the device ID.

In this embodiment, an application program (app) 61 for payment via the retrofit unit is pre-downloaded and executable on the user terminal 6. Hereinafter, this app 61 will be referred to as the retrofit unit app. The payment code symbol 112 shown in FIG. 5 is a symbolized code that passes the device type ID, device ID, and payment amount as arguments to the retrofit unit app 61, and is sent to the payment server 7 by a program included in the retrofit unit app 61. Below, the retrofit unit app 61 will be explained as a supplementary explanation of the payment code symbol 112. FIG. 8 is a schematic diagram showing the retrofit unit app.

When the payment code symbol 112 shown in FIG. 5 is read by the user terminal 6, if the retrofit unit app 61 is not installed on the user terminal 6, an installation page for the retrofit unit app is displayed on the user terminal 6, and if the retrofit unit app 61 is installed, the retrofit unit app 61 is launched on the user terminal 6. This part of the program is a program on the server 7 (hereinafter referred to as the app installation/launch program), and the payment code symbol 61 is a code symbol that directly executes this app installation/launch program.

If the application for the retrofit unit is not installed, an installation page for the application for the retrofit unit is displayed on the user terminal 6 by the application introduction/startup program. As shown in Fig. 3, a server 5 operated by a business providing the application for the retrofit unit (hereinafter referred to as a retrofit application server) is provided on the Internet 700. The installation page for the application for the retrofit unit is a page on the retrofit application server 5. When the payment business operating the payment server 7 provides the application for the retrofit unit, the installation page is provided on the payment server 7.
In either case, the installation page has an installation button for the application for the retrofit unit, and when the installation button is tapped, the application for the retrofit unit is downloaded and installed on the user terminal 6 .

8A shows an initial screen immediately after the installed retrofit unit application 61 is started on the user terminal 6. The initial screen includes a member registration button 62, payment buttons 631 and 632, and the like.
The member registration button 62 is a button for registering as a member by inputting personal information such as name and address, and is basically the same as other services on a website that are used after member registration. Therefore, detailed explanations are omitted. A member information file 51 is stored in the memory unit 50 on the retrofit application server 5. The member information file 51 is a database file in which each piece of information entered when registering as a member is recorded. Each piece of personal information entered when registering as a member is recorded in the member information file 51 by a program on the retrofit application server 5.

Two payment buttons are provided. One is a button 631 for accessing the payment server 7 using the payment code symbol 112 (hereinafter, the code reading payment button). The other is a button 632 for displaying the payment code symbol 112 and having the retrofit unit read it (hereinafter, the code display payment button). In the first embodiment, the code reading button 631 is used. A payment code reading screen included in the retrofit unit app 61 is linked to the code reading payment button 631, and pressing the code reading payment button 631 displays the payment code reading screen shown in FIG. 8 (2).

As shown in FIG. 8 (2), the payment code reading screen includes a message requesting that the payment code symbol 112 be read, and a frame 64 displaying the screen captured by the camera of the user terminal 6. The retrofit unit application 61 implements a general-purpose module (API, library, etc.) for reading two-dimensional code symbols, and the payment code symbol 112 is read and the code is executed using the functions of the general-purpose module.

The retrofit unit app 61 includes an app-side payment request program. The app-side payment request program is a program that transmits a member ID, payment amount, device type ID, and device ID to the payment server 7. In this embodiment, the payment request is sent to the payment server 7 via the retrofit app server 5. The payment server 7 is implemented with a payment program 71, and the retrofit app server 5 is implemented with a payment intermediation program 56. The payment intermediation program 56 is a program that transmits the member ID and payment amount, which are included in the app-side payment request, to the payment server 7 and executes the payment program 71 on the payment server 7. The device type ID and device ID are temporarily held in variables in the retrofit app server 5.

When the retrofit unit app 61 is installed and a member is registered, a member ID and password are issued and notified to the user terminal 6. The member ID is stored as a constant in the retrofit unit app 61. The application-side payment request program adds the member ID to the payment amount, device type ID, and device ID received as arguments, and sends the request to the retrofit app server 5. The payment intermediary program 56 on the retrofit app server 5 then executes the payment program 71 on the payment server 7. The return value of the payment program 71 is a value indicating whether the payment was completed normally or not, and is returned to the retrofit unit app 61 via the retrofit app server 5. The retrofit unit app 61 is programmed to display a message to the user terminal 6 when a return value indicating that the payment was completed normally is returned. An example of a display screen indicating that the payment was completed normally is shown in FIG. 8 (3).

To explain in more detail, as shown in FIG. 3, the retrofit unit has a communication unit 4. The communication unit 4 is an interface for communicating with the payment server 7 via a network 700 such as the Internet. For example, an interface for public wireless communication such as LTE or wired communication such as an optical line via a router is used as the communication unit 4. To increase versatility, the communication unit 4 includes three interfaces, for example, an LTE interface, a wireless LAN interface, and a wired LAN interface (Ethernet). In this case, one is selected and used according to the environment of the installation location. That is, if the location where the main device 9 is installed has a LAN environment connected to the Internet, the wireless LAN interface or the wired LAN interface is used, but if not, the LTE interface is used. In addition, a USB interface is also provided for connecting other devices.

As shown in FIG. 5, the main program 201 on the retrofit unit displays the symbol display program 202, and then executes the notification request program 203. The notification request program 203 is a program that accesses the retrofit application server 5 via the communication unit 4, transmits a device ID to the retrofit application server 5, and requests a server notification. The server notification is a process (so-called server push) in which the retrofit application server 5 notifies the user of the successful completion of the settlement program 71 executed for a device ID that matches the device ID, if the return value is a successful settlement completion. When a notification request is received, the retrofit application server 7 checks the device IDs held in each session of the settlement intermediary program 56 being executed, and determines whether a successful settlement completion has been returned from the settlement program 72 on the settlement server 7 for the matching device ID. If a successful completion has been returned, a push notification of successful completion is sent, and if a payment abnormality has been returned, a push notification of that effect is sent. After requesting a server notification, the notification request program 203 starts a timer, and determines whether a server notification of successful settlement completion is received within a set time. If there is a server notification, a return value indicating successful payment completion is returned to the main program 201; if there is no server notification or if there is a push notification indicating an abnormal payment, a return value indicating incomplete payment is returned to the main program 201.

As shown in FIG. 5, if normal payment completion is returned, the main program 201 executes the payment completion output program 204. If payment incomplete is returned, an error screen is displayed on the display 11. The error screen is a screen that displays a message to the effect that the cashless payment was not completed within the specified time. Details are omitted, but the error screen is provided with buttons to select whether to perform another cashless payment (retry) or to make a cash payment. If it is selected to perform another cashless payment, the symbol display program 202 is executed again, and, although not shown, if cash payment is selected or a specified time lag has passed, the screen returns to the standby screen.

When a normal completion of payment is returned and the main program 201 executes the payment completion output program 204, the payment completion output program 204 causes the cashless output unit 3 to output a payment completion signal. The cashless output unit 3 converts the output signal into a signal with the same communication specifications as the output signal of the coin mechanism 81 and bill validator 82, and inputs this signal to the fee receipt input unit 93 of the main device 9. Explaining the above example, if the fee for the cashless payment 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 payment unit 3 outputs three pulses in 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 deposit of 300 yen had been made at the coin mechanism 81, and subsequent processing is carried out.

The above explanation was for an example in which the main device has a single fee, but the following explains the case in which there are multiple different fees for a product or service (multiple fees). In the case of multiple fees, an image file of the payment code symbol is created in advance for each fee and stored in the memory unit 22. Then, depending on the user's selection, one of the payment code symbols is displayed on the display 11. An example of this is shown in Figure 9. Figure 9 is a schematic diagram showing an example of screen transitions on the display when the main device has multiple fees.

In the case of multiple fees, as shown in FIG. 9 (1), a cashless button 111 is also provided on the standby screen. The cashless button 111 is linked to a fee selection screen, and pressing the cashless button 111 switches to the fee selection screen as shown in FIG. 9 (2). The fee selection screen displays buttons (hereinafter, amount buttons) 113 that display each fee that may be incurred in one use on the main device equipped with this retrofit unit.

Figure 9 (3) shows the state when a certain amount button 113 has been pressed. Each amount button 113 is configured to execute the symbol display program 202 using the displayed amount as an argument, and as shown in Figure 9 (3), the symbol display program 202 is programmed to retrieve from the storage unit 22 a file of the settlement code symbol 112 corresponding to the argument amount and display it on the display 11.
The subsequent processing is similar, and by reading the payment code symbol 102 with the user terminal 6 on which the payment code reading screen of the retrofit unit application 61 is displayed, the payment server 7 is accessed via the retrofit application server 5, and the payment program 71 is executed. If the payment is completed normally, a message to that effect is returned to the user terminal 6, and in response to the notification request program 103, the retrofit application server 5 sends a push notification of normal payment completion to the retrofit unit.

The above-mentioned cashless output unit 3 also serves as a means for recording and referencing information on a cash payment made at the coin mechanism 81 or the bill validator 82. This point will be described below.
As described above, the output terminal of the third terminal group 33 of the cashless output unit 3 is connected to the cashless control unit 2. When the cashless output unit 3 receives a cash deposit signal 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 of the main device 9 as described above, and is also configured to input the cash deposit signal to the cashless control unit 2. The cashless control unit 3 is equipped with a monitor transmission program 207, which is programmed to automatically start and transmit the cash deposit information to the post-installation application server 5 when a cash deposit signal is input. That is, in this embodiment, the monitor transmission program 207 is implemented to perform the function of the cash payment information output program. The cash payment information is the payment type indicating that the payment is a cash payment, the payment amount indicated by the cash deposit signal, and the payment date and time (the execution date and time of the program). The cash payment information output program may be implemented in the cashless output unit 3.

The add-on application server 5 is equipped with a payment history information recording program 52, and the memory unit of the add-on application server 5 stores a payment history information file 53. The payment history file 53 is a database file that records information such as the payment type, payment date and time, payment method, payment amount, user ID, device ID, and device operator ID. The payment type is whether it is a cash payment or a cashless payment. When the payment receiving program receives cash deposit information, it is programmed to record the payment type indicating that it is a cash payment, the payment amount, and the payment date and time in the payment history information file 53.

The payment history information recording program 52 on the add-on application server 5 is also executed when a return value indicating successful payment completion is returned from the payment server 7. That is, when successful payment completion is returned, the payment intermediary program 56 temporarily stores the information for push notification and executes the payment history information recording program 52 as a subroutine. In this case, the payment history information recording program 52 is programmed to record the payment type indicating that it is a cashless payment, the payment amount, the payment date, and the user ID in the payment history information file 53. In addition, when multiple different cashless payments are possible, the type of cashless payment service and/or specific information of the cashless payment service may be transmitted and recorded in the payment history information file 53.

Next, a method of using the retrofit unit according to the embodiment having the above configuration will be described.
At the request of a business owner who already owns an operating main device 9, a vendor who sells the retrofit unit of the embodiment goes to the installation location of the main device 9 and installs the retrofit unit. That is, as shown in FIG. 1, the unit box 1 is fixed to the front panel 91 of the main device 9. At this time, a part of the front panel 91 is cut out to provide an opening 92 for wiring. Then, the cashless output unit 3 is connected through the opening 92. That is, the connection between the existing cash receipt confirmation unit such as the coin mechanism 81 and the bill validator 82 and the fee receipt input unit 93 of the main device 9 is temporarily removed. Then, the cash receipt confirmation units 81 and 82 are connected to a predetermined terminal of the cashless output unit 3, and a predetermined terminal of the cashless output unit 3 is connected to the fee receipt input unit 93. Also, the power cable extending from the power supply circuit is connected to a commercial power outlet prepared at the installation location of the main device 9. Furthermore, the retrofit unit is connected to the Internet 700 via an interface such as a wireless LAN, a wired LAN, or LTE.

This completes the installation of the retrofit unit. Note that an image file of the cashless payment code symbol 112 is created in advance and stored in the memory section 22 of the retrofit unit according to the main device 9 to which the retrofit unit is to be installed. The main program 201 and the symbol display program 202 are also created in advance according to whether the main device 9 is a single-fee or multiple-fee device, and stored in the memory section 22. A program for conversion as necessary is written in advance in the cashless output section 3 according to the communication specifications between the cash receipt confirmation units 81, 82 to which the retrofit unit is to be installed and the fee receipt input section 93 of the main device 9.
The power supply of the retrofit unit is turned on in conjunction with the power supply of the main device 9, so that the retrofit unit is in operation when the main device 9 is in operation. When the power supply is turned on, the main program 201 of the retrofit unit is started, and a standby screen is displayed on the display 11.

When a user comes to the main device 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. The user has previously installed the add-on unit app 61 on the user terminal 6 and has completed member registration. For this reason, a member ID is stored in the user terminal. If the add-on unit app 61 is not installed, an installation page for the add-on unit app 61 is displayed, so the user installs it and presses the member registration button 62 to register as a member. At this time, each piece of personal information is recorded in the member information file 51.

The user presses the cashless button 111 displayed on the display 11. This causes the payment code symbol 112 to be displayed on the display 11. Following the message on the display 11, the user launches the add-on unit app 61 on their own user terminal 6 and presses the code reading payment button 631 on the initial screen to display the payment code reading screen. The user terminal 6 then reads the payment code symbol 112 and executes the payment code symbol 112. This causes the member ID to be obtained from the user terminal 6, and the app-side payment request program sends a payment request to the add-on app server 5 using the member ID, payment amount, device type ID, and device ID as arguments, and the payment intermediary program 56 on the add-on app server 5 transfers the payment request to the payment server 7, and the payment program 71 on the payment server 7 is executed.

When the main device 9 is used for multiple charges, pressing the cashless button 111 displays amount buttons 113 for each charge. When the user presses the amount button 113 for the charge they wish to pay, the payment code symbol 112 for that amount is displayed. The user reads the payment code symbol 112 with the user terminal 6. This similarly executes a code in which that charge is incorporated as the payment amount, and similarly executes the payment program 71 on the payment server 7 via the add-on app server 5.

On the other hand, when the cashless button 111 is pressed, the main program 201 on the retrofit unit executes the notification request program 203 and requests a server notification from the retrofit application server 5. If successful payment completion is returned as the execution result of the payment program 71, the retrofit application server 5 notifies the user terminal 6 of this fact. Successful payment completion is displayed on the user terminal 6. At the same time, the retrofit application server 5 sends a server notification of successful payment completion to the retrofit unit identified by the device ID according to the device ID.

When the main program 201 on the retrofit unit receives a server notification of successful payment completion via the communication unit 4, it causes the cashless output unit 3 to output successful payment completion. As a result, a signal with the same specifications as the communication specifications with the coin mechanism 81 and bill validator 82 is input to the fee receipt input unit 93 of the main device 9. As a result, the main device 9 confirms that the payment has been completed successfully, and the product or service that was the subject of the payment is provided. In parallel, the payment history information recording program 52 is executed on the retrofit app server 5, and the payment type, payment amount, payment date, and user ID are recorded in the payment history information file 53.

If the user selects normal cash payment, they insert cash into the cash slot of the coin mechanism 81 and/or bill validator 82. A cash deposit signal is input from the coin mechanism 81 and/or bill validator 82 to the cashless output unit 3, which in turn inputs it directly to the fee receipt input unit 93 of the main device 9. The product or service that was the subject of the payment is then provided in the same manner. At this time, the cash deposit signal is also input to the cash control unit 2, which executes the monitor transmission program 207 and transmits the payment type, payment amount, and payment date to the add-on application server 5 via the Internet 700, and the payment history information recording program 52 records them in the payment history information file 53.

According to the add-on unit of the embodiment relating to the above configuration and operation, a cashless payment function can be added to a currently operating main device 9 that only accepts cash payments, thereby improving the convenience of the main device 9. This can promote the sale of products or services by the main device 9, and is expected to increase profits. In this case, there is no need to replace the main device 9, so no large costs are required, which also contributes to increased profits.
Furthermore, in the retrofit unit of the embodiment, the cashless output unit 3 outputs a cashless payment completion signal to the fee receipt input unit 93 of the main device 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 main device 9, and the cashless payment function can be easily and inexpensively introduced.

In addition, in the case of cash payment, the monitor transmission program 207 transmits the cash payment information to the add-on application server 5, and the cash payment information is recorded in the payment record information file 53, which has the effect of making it possible to collect cash payment information that could not be collected in the past. In the case of cash payment in the past, it was not possible to know when the payment (sales) occurred or how much the amount of each payment was. The total amount of sales in cash payment is known when the cash stored in the coin mechanism 81 and the bill validator 82 is collected, but it is not possible to identify when each payment was made or how much it was. On the other hand, if the add-on unit of the embodiment is implemented, information on the date and time and the amount of each payment can be collected for cash payment, as well as cashless payment. This information is useful information when deciding on a policy for the operation of the main device 9. For example, it is possible to stop the operation of the main device 9 during times of low usage to save power.

In the configuration of the first embodiment described above, the display 11 constitutes the code display unit, and the payment code symbol 112 is displayed by the display 11, but other configurations are also possible as long as the user can read the payment code symbol on the user terminal 6 with a camera. For example, it is possible to make the payment code symbol readable by attaching a sticker on which the payment code symbol is printed to the front of the main device 9 or the front of the unit box 1. Also, a sheet on which the payment code symbol is printed may be placed in a transparent case or covered with a transparent cover and fixed to the front of the main device 9. In these cases, such stickers or sheet pieces will be provided as accessories to the add-on cashless payment unit, but conceptually the stickers or sheet pieces are components of the unit.

In such a configuration, the retrofit unit does not require a display, so it can be provided at low cost. The necessary information is similarly communicated to the user by stickers or the like. If a display is not used, there is no need to provide an opening in the front panel, making installation easy. Also, since the main device 9 only has a code display section displayed by stickers or the like, there is also the advantage that there is almost no change in appearance. Furthermore, each element of the retrofit unit and the main device 9 can be located separately, and the cashless output unit 3 can communicate with them by wire or wirelessly. In this case, it is also possible to centralize the payment processing of multiple main devices 9 in one location. However, if a payment code symbol is displayed by stickers or the like, there is a possibility of mischief or malicious acts such as pasting a fake code symbol on top, so a configuration that uses a display is superior in terms of security.

Next, a description will be given of an add-on unit according to a second embodiment of the present invention, with reference to Fig. 10 being a schematic perspective view of the add-on unit according to the second embodiment, and Fig. 11 being a block diagram showing a schematic configuration of the add-on unit according to the second embodiment.
The add-on unit of the second embodiment differs from the first embodiment in the exchange of information with the user terminal 6. That is, the add-on unit of the second embodiment includes a camera 12, and is configured to display a payment code symbol 112 on the user terminal 6 and read it with the camera 12.

As shown in FIG. 10, the camera 12 is attached to the front of the unit box 1 and is oriented to take pictures of what is ahead. In the second embodiment, a display 11 is also attached, and the camera 12 is attached slightly above it. Camera modules that include a camera such as a CCD camera and its interface, connected by a cable, are commercially available, so an appropriate one can be selected and used.

Fig. 12 is a flow chart showing the execution relationship between the main program and other sub-programs in the second embodiment, and Fig. 13 is a schematic diagram showing screen transitions on the display in the second embodiment. These are examples in which the main device 9 is a single-fee device. Fig. 14 is a schematic diagram showing an application for an add-on unit in the second embodiment.
In the second embodiment, an ID acquisition program 205, a unit-side payment request program 206, a payment completion output program 204, and the like are implemented in the add-on unit as programs that are called and executed by the main program 201.

In the second embodiment, when the main program 201 is started, it displays a standby screen on the display 11. As shown in Fig. 13(1), the standby screen includes a cashless button 111. The cashless button 111 is a start button for the ID acquisition program 205.
When the ID acquisition program 205 is started, it operates the camera 12 and displays a code acquisition screen on the display 11. As shown in Fig. 13 (2), the code acquisition screen includes a message such as "Start the unit payment application on your smartphone, display the payment code symbol 112, and have the camera 12 read it," and includes a captured image display frame 114 that displays the image captured by the camera 12.

Meanwhile, as mentioned above, the initial screen of the retrofit unit app 61 includes a code display payment button 632. When the code display payment button 632 is pressed, a payment code symbol 633 is displayed on the user terminal 6, as shown in FIG. 14 (2). The payment code symbol 633 here is a symbolized version of the member ID or a code including the member ID issued at the time of member registration on the user terminal 6. Therefore, when this payment code symbol 633 is read by the camera 12 on the retrofit unit, the member ID is obtained.

When the ID acquisition program 205 is started, it starts a timer and determines whether the member ID is acquired within a predetermined time. If the member ID is acquired, it stores the member ID in a variable and returns a normal end to the main program 201 and ends. If the member ID is not acquired, it returns an abnormal end to the main program 201 and ends.
If an abnormal end is returned, the main program 201 displays an error message on the display 11 and returns to the standby screen after a predetermined time. If a normal end is returned, the main program 201 reads the member ID from the variable, and executes the unit side payment request program 206 with the payment amount as a constant, the device type ID, and the device ID as arguments.

The unit-side payment request program 206 is similar to the application-side payment request program, but the way in which it returns a return value is slightly different from that of the application-side payment request program. The payment intermediary program 56 on the add-on application server 5, which is called and executed by the unit-side payment request program 206, is programmed to return a notification of successful payment completion to the add-on unit that called it (the main program 201 running on the add-on unit) when the successful payment completion is returned from the payment program 71 on the payment server 7, and also to send a push notification (server push) to the user terminal 6 associated with that member ID. Therefore, when payment is completed successfully, a successful payment completion notification is displayed on the user terminal 6, as shown in FIG. 14 (3). Although not shown in the figure, if payment is not completed successfully, a push notification to that effect is sent.

On the other hand, when normal payment completion is returned, the main program 201 executes the payment completion output program 204 as shown in FIG. 12. The payment completion output program 204 is the same as in the first embodiment, and outputs payment completion to the cashless output unit 3. As a result, a payment completion signal is output from the cashless output unit 3 in the same communication specifications as the output signals of the cash receipt confirmation units 81, 82, and input to the fee receipt input unit 93 of the main device 9. If a payment abnormality is returned from the payment program 71, the main program 201 displays an error message to that effect on the display 11, and displays a screen that allows the user to select whether to retry or cancel. If retry is selected, the ID acquisition program 205 is executed again. If cancel is selected, the screen returns to the standby screen.

When the main device 9 has multiple fees, the main program 201 displays a fee selection screen on the display 11 before or after executing the ID acquisition program 205. The fee selection screen is a screen on which buttons for selecting a usage fee for the main device 9 are arranged. Each button has embedded therein a code for storing the selected usage fee in a variable as the payment amount.
After displaying the fee selection screen, the main program 201 reads the payment amount from the variables and transmits it as an argument together with the acquired member ID, the device type ID, and the device ID, which are constants, to the add-on application server 5. The payment intermediary program 56 on the add-on application server 5 transfers the payment request to the payment server 7, and the payment program 71 is executed on the payment server 7. The subsequent processing is similar.

In the second embodiment, similarly to the first embodiment, the convenience of the main device 9 is improved by retrofitting the cashless function, and the sales of products or services by the main device 9 can be promoted without requiring a large cost. In addition, the cashless output unit 3 outputs a signal with the same communication specifications as the cash receipt confirmation units 81 and 82, so that the introduction cost is low.
In the second embodiment, the camera 12 is necessary, but the display 11 is not essential. Any necessary messages may be displayed on the front panel 91 by sticking a sticker or the like, and the cashless button 111 and the button for selecting the amount may be mechanical push buttons or the like.

In the second embodiment, if the application for the retrofit unit is not installed on the user terminal 6, it is necessary to install it in advance. To achieve this, a code symbol for installation that symbolizes the URL of the installation page is printed on a sticker and affixed to the front panel 91, etc.

Next, the invention of a method for retrofitting a cashless payment function and a customer information collection function will be described. Fig. 15 is a schematic diagram showing an embodiment of the invention of a method for retrofitting a cashless payment function and a customer information collection function.
In each of the above-described embodiments, the add-on unit application 61 constitutes an invention of a method for adding a cashless payment function and a customer information collection function (hereinafter, abbreviated as a function adding method).

As mentioned above, when registering as a member after installing the retrofit unit app 61 on the user terminal 6, the user's personal information is entered on the user terminal 6 and recorded in the member information file 51 on the retrofit app server 5. This is also the case in the second embodiment. Furthermore, when each cashless payment is made, the payment history information recording program 52 on the retrofit app server 5 is executed, and the payment type, payment amount, payment date, and user ID are recorded in the payment history information file 53. Furthermore, when a cash payment is made, the monitor transmission program 207 is executed, and each piece of information is recorded in the payment history information file 53 as cash payment information.

On the other hand, the add-on application server 5 also provides a page for each business operator (hereinafter referred to as the equipment operator) who owns each cash payment device equipped with an add-on unit and conducts business. Each equipment operator is given an ID (equipment operator ID) and password as an equipment operator, and each equipment operator can log in to the add-on application server 5 as an equipment operator by inputting the equipment operator ID and password on a terminal (hereinafter referred to as the equipment operator terminal) 500 operated by a person in charge at that business.

One of the pages for the device business operator (hereinafter, the device business operator page) provided by the add-on application server 5 is a page for viewing the payment status of the owned cash payment device (hereinafter, the payment status viewing page). Fig. 16 is a schematic diagram showing an example of the payment status viewing page.
The storage unit 50 of the retrofit application server 5 stores a device information file 54. The device information file 54 is a database file that records information on all cash settlement devices equipped with retrofit units, and stores information such as the device operator ID of the device operator that owns the device, the device ID, and the device name in a database.

The add-on application server 5 is programmed with a program (hereinafter referred to as the viewed page display program) 55 for displaying a payment status viewing page as shown in FIG. 16. The viewed page display program 55 searches the device information file 54 with the device operator ID entered at login, and obtains the device IDs of all matching records. The viewed page display program 55 is then programmed to search the payment history information file 53 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. 16. The viewed page display program is also programmed to search the member information file 51 with the user ID, obtain personal information such as age and gender, and incorporate it as shown in FIG. 16.

As shown in Figure 16, the payment status viewing page allows device operators to view when, who used which device, and how much was paid for. In the example of Figure 16, for privacy reasons, personal user names are not displayed. Furthermore, each user must consent in advance to allowing personal information other than name, such as gender and age, to be viewed by device operators for sales promotion purposes.

With this type of retrofitting method, not only can cashless payment functionality be added to existing cash payment devices, but customer information can also be collected via the cash payment devices, and the information can be viewed by device operators as shown in Figure 16. This allows device operators to make decisions regarding the installation and operation of each cash payment device while referring to the payment status, which is extremely useful for optimizing business using cash payment devices. It may also be possible to calculate the total payment amount for each cash payment device, calculate the total amount for cash payments and cashless payments separately for one cash payment device, or calculate the total amount for multiple cash payment devices at one installation location.

What is important in this case is that such customer information can be collected while making use of the current cash payment equipment. The same thing can be done by discarding the current cash payment equipment and introducing the latest equipment (with cashless payment function) that has customer information collection functionality. However, replacing with the latest equipment is very costly, and if the current cash payment equipment has not yet been depreciated, the equipment operator will be hesitant to do so. On the other hand, according to the function retrofitting method of the embodiment, the customer information collection function is added retrofit by installing a retrofit unit, so the investment cost for the equipment operator is much smaller.

In addition to collecting information by transmitting it from the retrofit unit as described above, a configuration is also possible in which information is transmitted to the retrofit unit and operated remotely. For example, the cashless control unit 2 may be configured to accept access via the Internet 700, and if access authority is confirmed, information from outside may be received. The storage unit of the retrofit application server 5 (or another management server) stores information such as an IP address that identifies each retrofit unit and access authority information (password, etc.), enabling access to each cashless control unit 2.

Remote operation may occur, for example, when the coin mechanism 81 or bill validator 82 does not work properly for some reason, causing the cash payment device to not work even though the user has made a correct deposit. In this case, the user may call the administrator using a smartphone or other device, who may confirm the malfunction and remotely control the cash deposit signal to be output from the cashless output unit 3. The same is true for cashless payments; if the cashless payment does not work for some reason, and it is not the user's fault but a problem with the system, and the user has already incurred a cost, the cashless output unit 3 may be remotely controlled to output a successful payment completion.

In each embodiment, the display 11 can be configured to have additional functions such as advertisements and questionnaires in addition to the function for cashless payment. That is, a file for displaying an advertisement page and a file for a questionnaire page are stored in the memory unit 22, and the main program 201 can be programmed to display an advertisement page in the standby state and to display a questionnaire page after a cashless payment is completed. In this case, the add-on application server 5 (or another management server) can be implemented with a program that updates the file for the advertisement page from time to time so that new ones are displayed, and receives information entered on the questionnaire page and stores it in a database file.

Next, a modification of each embodiment regarding the server will be described below. Fig. 17 is a schematic diagram showing a modification regarding the server.
In each of the above embodiments, a retrofit application server 5 is provided separately from the payment server 7, and the retrofit application server 5 provides an application for the retrofit unit and also mediates the payment request and transfers it to the payment server 7. In other configurations, for example, the payment server 7 may be configured to perform each function as shown in FIG. 17 (1). That is, there may also be a configuration in which the payment server 7 provides an application for the retrofit unit, directly receives a payment request, performs payment, and transmits a successful payment completion directly to the retrofit unit. In this configuration, the member information file 51, the device information file 54, the payment record information file 53, etc. are usually stored in the storage unit 70 of the payment server 7.

This type of format can be adopted when a machine operator who operates by installing cash payment machines provides a cashless payment service himself. For example, an operator that operates many coin laundry stores may provide a common prepaid service (a service for issuing prepaid payment instruments) at each store. Users deposit funds into a prepaid service account in advance and use the prepaid money when using washing machines, etc. at the coin laundry store. In such cases, all functions may be provided by a server operated by the machine operator.

In the case where such a cashless payment service operated by the device operator itself is a prepaid service, the description and drawings of Japanese Patent Application No. 2021-130396 may be referred to. For example, in the case of a coin laundry store, a charging machine is installed in the store, and the user's terminal 6 is used to cause the charging machine to obtain a user ID, and the user inserts the charging money to charge the machine. The charged prepaid money can be used in the store or other stores of the same business. In the case of a manned brick-and-mortar store, the charging money may be received by a store clerk and transmitted to a server by a charging amount transmitter provided in the store, whereby the charge is made. In either case, the prepaid money is used in a cash payment device installed in the store.
In some cases, a service that operates and manages such cashless payment services that can be used at common stores of the same device operator may be provided on behalf of the device operator. For example, a company that provides an app for retrofit units may provide its own cashless payment service platform to each device operator.

As another possible embodiment, as shown in FIG. 17 (2), there may be multiple payment servers 7A-7E, and one of them may be selected and used. This embodiment may also be used when an app for a retrofit unit supports multiple different payment services. For example, suppose that there are companies A and B that offer cashless payments via smartphone using accounts linked to bank accounts, there is a company C that offers a mobile cashless payment service for transportation, and there are companies D and E that offer credit card payment services.

If the application for the retrofit unit supports all of these payment services, the retrofit application server 5 will be able to access servers 7A-7E where each company provides its payment service, as shown in FIG. 17 (2). A screen for selecting a payment service will be displayed on the user terminal 6, and the payment intermediary program 56 will transfer the payment request to the payment server 7A-7E of the selected payment service, causing the payment to be made. Other functions and processing are similar. Note that a service that consolidates and intermediates each payment service on a platform may be used, and the payment request may be sent via the server of such a payment platform.

If the application for the retrofit unit supports multiple different payment services, information identifying the cashless payment service used is recorded in each record of the payment history information file 53. In this case, the information in the payment history information file 53 indicates the frequency of use of each cashless payment service, and has value as market share information for the cashless payment service. For example, the data may show that the usage rate of Company A's cashless payment service exceeds 50% in each cash payment device operated by a certain device operator. In addition, by aggregating data on each cash payment device operated by each device operator belonging to the same industry, it is possible to know the proportion of each cashless payment service used in that industry. Therefore, it is preferable to store an operator information file, which is a database file in which each record is linked by the device operator ID recorded in the payment history information file 53, in the storage unit 50 of the retrofit application server 5, for example, and record information identifying the industry or industry therein so that the data can be aggregated by industry or by industry.

In each of the above-described embodiments, the cashless output unit 3 is wired between the coin mech 81 and bill validator 82 and the fee receipt input unit 93 of the main device 9, but the configuration may be such that the wiring extending from the cashless output unit 3 is simply connected to the wiring between the coin mech 81 and bill validator 82 and the fee receipt input unit 93 of the main device 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.

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 state where cash payment and cashless payment proceed 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 main device 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 main device 9 is completed.

In each of the above-mentioned embodiments, it is not essential that the main device 9 is equipped with a coin mech 81 and a bill validator 82; either one is acceptable, 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 mech 81 may be provided, and if the fee is only in 1,000 yen increments, only the bill validator 82 may be provided.

1 Unit box 11 Display 12 Camera 2 Cashless control unit 21 CPU
22 Storage unit 3 Cashless output unit 4 Communication unit 5 Post-installation application server 51 Member information file 53 Payment record information file 54 Device information file 55 Browse page display program 6 User terminal 61 Post-installation unit application 7 Payment server 71 Payment program 81 Coin mech 82 Bill validator 9 Main device 93 Fee receipt input unit

Claims (7)

1. A retrofit cashless payment unit that adds a cashless payment function to a cash payment device having a function of performing unmanned payment by cash, the cash payment device including a cash receipt confirmation unit that confirms that cash inserted from a cash insertion port is genuine and outputs a signal of the received amount of the cash,
   A cashless control unit;
   A cashless output unit;
   The Communications Department and
   It is equipped with a code display unit,
   The cashless control unit is provided in a 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 format as the output signal of the cash receipt from the cash receipt confirmation unit;
   The code display unit displays a code symbol for payment,
   The code symbol for payment is a symbolized code that, when read by a user terminal, which is a portable terminal operated by a user, causes the user terminal to access a payment server, transmit specific information of the cash payment device, the payment amount, and a user ID, and execute a payment program on the payment server, and includes specific information of the cash payment device,
   the communication unit is connected to the payment server via a network, and when the payment server executes a payment program and transmits a payment completion signal indicating that the payment has been normally completed, receives the payment completion signal and inputs it to the cashless control unit;
   A retrofit cashless payment unit is characterized in that the cashless control unit is implemented with a payment completion output program, and the payment completion output program is a program that, when a payment completion signal is input from the communication unit, outputs a payment completion signal to the cashless output unit in the same communication specifications as the cash receipt confirmation by the cash receipt confirmation unit.
2. It has a display,
   The cashless payment unit according to claim 1, characterized in that the code display unit includes a symbol display program and displays the payment code symbol on a display using the symbol display program.
3. The cashless payment unit according to claim 1, characterized in that the code display unit is a sticker on which the payment code symbol is printed.
4. A retrofit cashless payment unit that adds a cashless payment function to a cash payment device having a function of performing unmanned payment by cash, the cash payment device including a cash receipt confirmation unit that confirms that cash inserted from a cash insertion port is genuine and outputs a signal of the received amount of the cash,
   A cashless control unit;
   A cashless output unit;
   The Communications Department and
   It is equipped with a camera,
   The cashless control unit is provided in a 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 format as the output signal of the cash receipt from the cash receipt confirmation unit;
   The cashless control unit is implemented with an ID acquisition program that acquires a user ID contained in a payment code symbol by having a camera read the payment code symbol displayed on a user terminal, which is a portable terminal operated by a user, and a payment request program that, when the ID acquisition program acquires the user ID, transmits the user ID, specific information of the cash payment device, and the payment amount, and requests execution of a payment program on a payment server;
   the communication unit is connected to the payment server via a network, and when the camera reads the payment code symbol and a payment program on the payment server is executed, receives a payment completion signal indicating that the payment has been completed normally, and inputs the payment completion signal to the cashless control unit;
   A retrofit cashless payment unit is characterized in that the cashless control unit is implemented with a payment completion output program, and the payment completion output program is a program that, when a payment completion signal is input from the communication unit, outputs a payment completion signal to the cashless output unit in the same communication specifications as the cash receipt confirmation by the cash receipt confirmation unit.
5. the cashless output unit is interposed between the fee receipt input unit and both the cashless control unit and the cash receipt confirmation unit, and when a cash receipt output signal is received from the cash receipt confirmation unit, the output signal is input to the fee receipt input unit with the communication specifications unchanged;
   A retrofit cashless payment unit as described in any one of claims 1 to 4, characterized in that a cash payment information output program is implemented which, when a cash receipt output signal is received from the cash receipt confirmation unit, outputs the amount of cash received in the output signal and the date and time when the output signal was output so that the amount can be stored in a memory unit and made available for reference.
6. A method for retrofitting a cashless payment function and a customer information collection function, using the retrofit cashless payment unit according to any one of claims 1 to 3, to a cash payment device having a function of performing unmanned cash payment by having a cash receipt confirmation unit that confirms that cash inserted through a cash insertion port is genuine and outputs a signal of the amount of the received cash, the method comprising:
   A payment history information recording program is installed in the payment server or another server connected to the cashless control unit via a network,
   the payment performance information recording program is a program for recording, when the code symbol for payment is read, the payment program is executed, and the payment is normally completed, specific information of the cash payment device related to the payment, the payment amount, and personal information of the user related to the user ID in a payment performance information file on the payment server or another server;
   a code reading step of having a user terminal read the settlement code symbol displayed on the code display unit;
   a payment request step of transmitting specific information of the cash payment device, a payment amount, and a user ID to request execution of a payment program on a payment server;
   A method for retrofitting a cashless payment function and a customer information collection function, characterized in that it comprises a customer information recording step of recording, when a payment completion signal indicating that the payment has been completed successfully after the payment request step, specific information of the cash payment device related to the payment, the payment amount, and personal information of the user in a payment history information file using a payment history information recording program.
7. A method for retrofitting a cashless payment function and a customer information collection function, using the retrofit cashless payment unit according to claim 4, to a cash settlement device having a function of performing unmanned settlement by cash, the method comprising the steps of:
   A payment history information recording program is installed in the payment server or another server connected to the cashless control unit via a network,
   the payment performance information recording program is a program for recording, when the camera reads the code symbol for payment and the payment program is executed to normally complete the payment, specific information of the cash payment device related to the payment, the payment amount, and personal information of the user related to the user ID in a payment performance information file on the payment server or another server;
   a payment request step of causing the camera to read a code symbol for payment on the user terminal and executing a payment request program;
   A method for retrofitting a cashless payment function and a customer information collection function, characterized in that it comprises a customer information recording step of recording, when a payment completion signal indicating that the payment has been completed successfully after the payment request step, specific information of the cash payment device related to the payment, the payment amount, and personal information of the user in a payment history information file using a payment history information recording program.

Images