JP7357376B2 - Physical stores, physical store payment support systems, coin laundry stores, and coin laundry store payment support systems - Google Patents

Description

The invention of this application relates to a payment technology in relatively small-scale physical stores, such as coin laundry stores.

Currently, the spread of cashless payments is accelerating, and payments using credit cards, electronic money, etc. are being actively carried out.
Although these cashless payments are convenient for users, they are not necessarily welcomed by stores because they have to bear some sort of fee. In particular, for small-scale businesses and businesses that handle products with low profit margins, the amount of fees cannot be ignored and is a factor that makes them hesitant to introduce cashless payments.

Another factor that discourages cashless payments is the sales period that occurs. Stores contract with companies that provide cashless payment services to perform cashless payments, but since payments are made on a monthly basis, sales are held for at least a month, while credit cards, etc., are held for several months. (Deposit may be made later). There are electronic money payment services that transfer the payment amount to the store's bank account the next day, but the bank transfer fee is borne by the store, and when it happens every day, the amount becomes a non-negligible amount.
The existence of the above-mentioned sales period places a burden on relatively small-scale businesses in terms of working capital, and is particularly burdensome for businesses that purchase in cash.

JP 2021-26453 Publication Japanese Patent Application Publication No. 2002-312847

The invention of the present application was made in order to solve the above-mentioned problems in cashless payment, and provides a cashless payment technology that can be suitably introduced in relatively small-scale physical stores and physical stores that mainly accept cash payments. is intended to provide.
The invention of the present application, which aims to solve the above-mentioned points, has a coin laundry store in mind as an example of its application target (actual store), and includes solving the unique problems thereof. This point will be explained below.

Coin-operated laundromats have long been widely used by single people who do not have washing machines at home. Recently, many coin-operated laundry shops are equipped with large, state-of-the-art washing machines that can wash blankets, etc., and people are increasingly using them even if they have a washing machine at home.
Due to this situation, the coin laundry business is gradually attracting attention as an investment target, and there are cases where owners of rental buildings convert the business into coin laundry stores when a space becomes available on the ground floor. ing.

As described above, the coin laundry industry has undergone changes in recent years, and some proposals have been made to utilize IT, as disclosed in Patent Documents 1 and 2. However, many aspects remain unchanged, and there are several important issues that need to be improved.
One of the reasons is that there is no progress toward a cashless society. Payments using smartphones and prepaid cards are rapidly becoming widespread in the retail industry in general, but the coin laundry industry has yet to move toward a cashless system.

When going cashless, you will need to use credit cards, debit cards, electronic money cards, prepaid cards, prepaid electronic money, etc. However, in all cashless payments, if cards or electronic money are versatile (versatile in the sense that they can be used at any affiliated store), a considerable fee will be charged. The fees will be borne by the operator of the coin laundry store (hereinafter referred to as the laundry store operator), but considering the nature of the coin laundry business, which requires a long period of time to recover investment, cashless payment is Fees are a relatively high cost burden that cannot be ignored. In other words, while the highly functional washing machines and dryers of recent years have become expensive equipment, the investment is recovered from the small usage fee of 100 yen per use. For this reason, the investment recovery period is already long, but if you have to pay relatively high cashless fees, the recovery period becomes even longer. For this reason, laundry store operators are forced to postpone the introduction of cashless payments.

It is possible to introduce non-universal prepaid cards as a means of cashless payment, but for the coin laundry industry, where the overwhelming majority are small-scale laundry store operators operating one to several stores, Introducing a dedicated prepaid card system would result in installation costs and maintenance and management costs that would be too high for the scale of business. Even for customers, in the current situation where they already own and use various cards, it is inevitable that they will find it cumbersome to hold additional cards only for use at coin laundry stores.

Another issue facing the current coin laundry industry is the inability to analyze customers. Customer analysis is the analysis of when, by whom, and what kind of purchasing behavior they engage in.
As the name suggests, most coin laundry stores accept payments in cash (coins). For this reason, when collecting cash from the coin box at the end of a day's business, the amount of sales for the day can only be determined, but it is not possible to know when, by whom, and how the laundry equipment was used. Customer analysis, which is an important element in marketing, is hardly possible.

Another problem, which stems from the above problems, is that they are not able to retain customers. Customer retention is a measure to encourage customers who have made a purchase once to become repeat customers by preventing them from going to other stores. Points (granting discount benefits for the next purchase), etc. are often used to retain customers, but it is not possible to introduce such promotions because the customers cannot be identified, and it is difficult to retain customers. Not yet.
In addition, the daily sales amount is determined when cash is collected from the coin box of each laundry machine after business hours, but it is unclear at what point in the day the sales occurred. In other words, it is not possible to grasp real-time sales.

The problems to be solved by the present invention include the problems of the current coin laundry industry as described above, and one of the more specific objectives of the present invention is to solve problems that can be solved while introducing cashless payment at coin laundry stores. In addition to providing a technical configuration that can reduce fees as much as possible, we also provide solutions that are useful from a marketing strategy perspective by enabling customer analysis, customer retention, real-time sales monitoring, etc.

In order to solve the above problems, this specification first discloses an invention for a physical store and an invention for a physical store payment support system.
The physical store according to the disclosed invention is a physical store that is not a virtual store on the Internet, and this physical store is equipped with a charge amount transmitter and a payment permission information receiver.
The charge amount transmitter is equipped with a customer ID acquisition unit that acquires a customer ID that identifies a customer who pays and deposits prepaid money at the physical store from a customer terminal that is carried by the customer without using a card. Prepaid money is money that a customer pays in advance and deposits for future payments at the physical store or another store managed by the same manager as the physical store.
The charge amount transmitter includes an input section into which the charge amount, which is the amount of prepaid money paid and deposited by the customer at the physical store, is input.
The charge amount transmitter is connected to the support server via the network, and the customer ID acquisition unit acquires information that enables the acquisition of the recipient ID of the recipient who receives the prepaid money at the physical store. The customer ID and charge amount entered from the input section are sent to the support server, and the charge amount is added for the customer ID and the recipient ID in the balance information file stored in the storage section on the support server, and the prepaid amount is It is a transmitter that performs the process of updating the balance of money, and the recipient ID is information that identifies the manager of each physical store, and if the manager is the same in multiple physical stores, the same ID is used. is the identification information given.
The payment permission information receiver is equipped with a display and is connected to the support server via a network.
The payment permission information receiver transmits the store ID that identifies the physical store, the customer ID, and the payment amount to the support server from a terminal installed at the physical store or a customer terminal , and receives the prepaid money at the physical store. When the support server sends payment permission information to the payment permission information receiver when the balance of prepaid money for the recipient ID of the recipient and the customer ID is greater than the payment amount, the payment permission information is received and displayed. This is the receiver that displays it.
Further, in the physical store, a store terminal such as a PC or a smartphone may be provided as a charge amount transmitter and a payment permission information receiver.
In addition, the above physical stores are
The physical store is equipped with a payment permission application transmitter,
The payment permission application transmitter allows input of the payment amount, and specifies the entered payment amount, the store ID that identifies the physical store, and the recipient ID of the recipient who will receive the prepaid money at the physical store. a transmitter that transmits information that can be used to make a payment and a customer ID to the support server via a network and executes a payment permission determination program on the support server ;
When the store ID that identifies the physical store, customer ID, and payment amount are sent, the payment permission determination program on the support server determines the recipient ID and customer ID of the recipient who receives the prepaid money at the physical store. A program that transmits payment permission information to the payment permission information receiver when the balance of prepaid money for is equal to or greater than the payment amount,
The payment permission application transmitter is equipped with a customer ID acquisition unit that acquires the customer ID from a customer terminal that is carried by the customer without using a card, and when executing the payment permission determination program, the customer ID is acquired from a customer terminal that is carried by the customer. The acquisition unit may be configured as a transmitter that transmits the acquired customer ID to the support server.
Further, in the physical store, a store terminal such as a PC or a smartphone may be provided as a payment permission application transmitter.
Further, the physical store payment support system according to the disclosed invention is a system that supports payment at a physical store that is not a virtual store on the Internet.
This system includes a support server and a storage unit.
In the memory section,
A store information file that records information including a store ID that identifies each physical store and a recipient ID that identifies the recipient who receives the prepaid money at each physical store;
A customer information file that records customer information including a customer ID that identifies the customer;
A balance information file recording the balance of prepaid money paid in advance by each customer is recorded.
The balance information file is a file in which the balance of prepaid money for each customer is recorded for each recipient ID in the store information file.
The support server is equipped with a charge amount recording program, a payment permission information transmission program, and a balance reduction program.
The charge amount recording program is information that enables the acquisition of the recipient ID of the recipient who receives prepaid money at the physical store where the charge amount transmitter is installed, from the charge amount transmitter installed in the physical store. , When the customer ID that identifies the customer who paid the prepaid money and the charge amount, which is the amount of the paid prepaid money, are sent to the support server, the customer ID is stored in the balance information file stored in the storage unit on the support server. This is a program that updates the balance of prepaid money by adding the charge amount for the recipient ID.
In addition, this physical store payment support system is
When the store ID, customer ID, and payment amount are sent, the payment permission information transmission program transmits the recipient ID of the recipient who receives the prepaid money at the physical store specified by the store ID and the prepaid money for the customer ID. This is a program that sends payment permission information when the balance is greater than or equal to the payment amount.
Each physical store is equipped with a payment permission information receiver that receives payment permission information and displays it on a display, and the payment permission information transmission program transmits the payment permission information provided at the physical store specified by the store ID. This is a program that sends payment permission information to the receiver.
The balance reduction program may have a configuration that, when the payment permission information transmission program transmits payment permission information, it is a program that subtracts the payment amount from the balance and updates the balance information file.
In addition, this physical store payment support system is
It is possible to enter the payment amount at each physical store, and the store ID that identifies the physical store, the customer ID, and the entered payment amount can be sent to the support server via the network. A permit application transmitter is installed,
The payment permission information transmission program may be a program that is executed when the store ID, customer ID, and payment amount are transmitted from the payment permission application transmitter.
In addition, this physical store payment support system is
A payment history information file is recorded in the storage unit.
The payment permission information includes the customer ID of the customer for whom payment is permitted.
The support server is equipped with a payment history recording program that records the payment permission information in the payment history information file when the payment permission information sending program sends the payment permission information.
When the support server is accessed from a recipient terminal, which is a terminal operated by the recipient, the payment authorization information recorded in the payment history information file, the recipient ID related to the recipient is recorded. The receiver may have a configuration in which a payment history viewing page display program is implemented for viewing payment permission information on the recipient terminal when payment is permitted for prepaid money.

Furthermore, in order to solve the above problems, this specification discloses an invention for a coin laundry store and an invention for a coin laundry store payment support system.
The coin laundry store according to the disclosed invention is a coin laundry store that has a plurality of laundry machines installed in the store and allows customers who visit the store to use each laundry machine for a fee.
The laundry equipment includes an access information providing unit that provides access information that is input to a customer terminal, which is a mobile terminal brought by the customer, to connect the customer terminal to the support server via the network. ing.
The access information provided by the access information providing unit includes a store ID for identifying the coin laundry store where the laundry equipment equipped with the access information providing unit is installed, and a store ID for identifying the laundry equipment equipped with the access information providing unit. device ID.
Each laundry device includes a signal input section into which a use permission signal transmitted from the support server is input, and the use permission signal is a signal that can start the operation of the laundry device.
The usage permission signal is the prepaid money received by the coin laundry store manager identified by the store ID included in the transmitted access information when the access information provided by the access information provision department is transmitted from the mobile terminal to the support server. This is a signal that is input to the signal input section when the balance of the laundry equipment is equal to or greater than the usage fee for the laundry equipment associated with the equipment ID.
This coin laundry store
There is a prepaid charge machine in the store that accepts prepaid money to pay for the use of laundry equipment in advance.
The prepaid charge machine has a customer ID acquisition unit that acquires a customer ID that identifies the customer who pays the prepaid money, a charge amount acquisition unit that acquires the charge amount that is the amount of prepaid money that has been inserted, and a support server that sends prepaid information to the support server. It is equipped with a prepaid information transmitting section to transmit ,
The customer ID acquisition unit is an acquisition unit that acquires a customer ID from a customer terminal that is a terminal carried by the customer without using a card,
The prepaid information transmission unit sends the store ID that identifies the coin laundry store where the prepaid charge machine is installed, the customer ID acquired by the customer ID acquisition unit, and the charge amount acquired by the charge amount acquisition unit to the support server as prepaid information. It is a transmitter that sends data to
The use permission signal sent from the support server and input into the signal input section is the prepaid money received at the prepaid charge machine installed at the coin laundry store specified by the store ID included in the access information provided by the access information provision section. In addition, even if the prepaid money is received from a prepaid charge machine installed at another coin laundry store owned by the same operator, if the balance exceeds the usage fee, this signal is input to the signal input section.
It can have the following structure.
Further, in this coin laundry store, the prepaid charge machine may be a device that also functions as a money exchange machine.
In addition, in this coin laundry store, the access information providing unit is a providing unit that passes the device ID and store ID and provides a two-dimensional code, which is the two-dimensional code of the program on the support server , as access information. The code may have a configuration including a device ID and a store ID as arguments.
In addition, the coin laundry store payment support system according to the disclosed invention is a coin laundry store payment support system in which multiple laundry machines are installed in the store and customers who visit the store are allowed to use each laundry machine for a fee. This is a coin laundry store payment support system that supports
This system includes a support server and a storage unit.
In the memory section,
A store information file that records information about each coin laundry store, including a store ID that identifies each coin laundry store;
A device information file that records information on each laundry device including a device ID that identifies each laundry device installed at each coin laundry store;
A customer information file that records customer information including a customer ID that identifies registered customers;
A balance information file recording the balance of prepaid money paid in advance by each customer is recorded.
The store information file records a recipient ID that identifies the recipient of the equipment usage fee at the coin laundry store.
The balance information file is a file in which the balance of prepaid money for each customer is recorded for each recipient ID in the store information file.
The support server is equipped with a charge amount recording program, a payment permission information transmission program, and a balance reduction program.
The charge amount recording program records the customer ID, the store ID of the coin laundry store or the recipient ID of the recipient who receives the prepaid money at the coin laundry store, and the charge amount from the prepaid charge machine installed at the coin laundry store. This is a program that updates the balance of the propaid money by adding the charge amount to the customer ID and the recipient ID of the recipient at the store when receiving this.
When the payment permission information transmission program receives the customer ID, store ID, and device ID from the mobile terminal operated by the customer, it acquires the recipient ID from the store information file according to the store ID, and sends information about the customer ID and the recipient ID. This is a program that sends payment permission information to enable the laundry equipment associated with the equipment ID to operate when the balance of prepaid money recorded in the balance information file is greater than or equal to the usage fee for the laundry equipment associated with the equipment ID. be.
The balance reduction program is a program that, when the payment permission information sending program sends payment permission information, deducts the usage fee from the prepaid money balance recorded for the customer ID and recipient ID and updates the balance. be.
In addition, in this coin laundry store payment support system, the charge amount recording program collects the customer ID and the store ID of the coin laundry store or the manager of the laundry store and the prepaid charge amount from the prepaid charge machine installed at the coin laundry store. This is a program that, when receiving the recipient ID of the recipient who receives the money and the charge amount, adds the charge amount to the customer ID and the recipient ID of the recipient at the store and updates the balance of the propaid money. obtain.
In addition, this coin laundry store payment support system,
A payment history information file is recorded in the storage unit.
The payment permission information includes the customer ID of the customer for whom payment is permitted.
The support server is equipped with a payment history recording program that records the payment permission information in the payment history information file when the payment permission information sending program sends the payment permission information.
When the support server is accessed from a recipient terminal, which is a terminal operated by the recipient, the prepaid money recorded for the recipient ID among the payment permission information recorded in the payment history information file is It may have a configuration in which a payment history viewing page display program is implemented for viewing payment permission information on the recipient terminal when payment is permitted for the recipient.
Furthermore, in order to solve the above problems, an invention of a physical store payment application program is disclosed in this specification. This application program is a physical store payment application program that is downloaded to a customer terminal, which is a terminal operated by a customer, and is used to access the support server in the physical store payment support system.
This application program has a function of displaying on the customer terminal a store list page that lists the names of stores or store chains related to each recipient whose recipient ID is recorded in the balance information file.
A button to pay prepaid money to the recipient of the store or store chain selected on the store list page, and use the prepaid money at any store in the store or store chain selected on the store list page. It has the function of displaying a button on the customer terminal.

As explained below, according to the disclosed inventions of physical stores and physical store payment support systems,
A prepayment method is issued that does not involve a card, and payments can be made using prepaid money. Since the cash paid when charging is received at the store, there are no transfer fees, and since it is prepaid, there is no sales period. For this reason, it is suitably introduced in various small-scale shops and the like.
In the case of manned physical stores, there is no need for a prepaid charge machine; all that is required is a charge amount transmitter that sends the customer ID and charge amount obtained from the customer terminal to the support server, and a PC can be used as the charge amount transmitter. Alternatively, since a general-purpose terminal such as a smartphone can be used, the installation cost is further reduced.
In addition, in a configuration where a payment permission application transmitter is provided that inputs the payment amount and sends it to the support server along with the store ID, recipient ID obtainable information, and customer ID, the payment permission application is made from the store side. , the complexity is eliminated. As for the payment permission application transmitter, a PC or a smartphone can be used, and the installation cost can be reduced.
In addition, by viewing payment history information, recipients who are physical store managers can learn which customers used which laundry machines on what dates and times, making it easier to analyze customers and retain customers. Be able to do it.
In addition, according to the coin laundry stores and coin laundry store payment support systems according to the disclosed inventions, cashless payments are realized, so customers can visit without carrying coins as long as they have charged the coins in advance. Laundry equipment can be used, making it more convenient. Even if you only have high-value bills that cannot be exchanged at the exchange machine, you can still use the laundry equipment.
On the other hand, for coin laundry store managers, such convenience is a means of attracting customers, and since it is a prepaid service, there is no sales period. Furthermore, since it is a prepaid service, it also has the advantage of freeing up working capital (cash flow).
At this time, since the configuration is not one in which prepaid cards are issued, but the prepaid money is managed by a support server on the network, the introduction cost can be extremely low. The service provider that operates and manages the support server provides services by contracting with many recipients, that is, many coin laundry store managers, so the cost of prepaid money management by the support server (cost per recipient) is Very cheap.
Furthermore, since the prepaid charge machine is installed at a coin laundry store, the cash paid at the time of charging goes directly to the coin laundry store manager (recipient), and there is no transfer fee. Therefore, it is extremely suitable as a cashless payment method for coin laundry stores, which are usually small in scale.
Furthermore, since prepaid money is managed by the same recipient, under the Payment Services Act, it is considered an issuer of in-house prepaid payment instruments, and all that is required is notification to the Ministry of Finance and payment of a deposit, and registration is required. No longer needed. If the half-year balance is less than 10 million yen, there is no need to submit a report or pay a deposit.
In addition, by viewing payment history information, the recipient, who is a coin laundry store manager, can learn which customers used which laundry equipment on what date and time, making it easier to analyze customers and retain customers. Be able to do it.

1 is a schematic plan view of a coin laundry store according to an embodiment, and a schematic diagram of a coin laundry store payment support system according to an embodiment. FIG. 2 is a schematic diagram showing an example of the structure of a recipient information file. It is a schematic diagram showing an example of the structure of a store information file. FIG. 2 is a schematic diagram showing an example of the composition of a device information file. It is a diagram showing an outline of the structure of a customer information file. FIG. 2 is a schematic diagram showing an example of the structure of a balance information file for a certain customer. FIG. 2 is a schematic diagram showing an example of the structure of a payment history information file. It is a front schematic diagram of a money exchange charge machine. It is a block diagram showing a schematic structure of a money exchange charge machine. It is a schematic diagram shown about operation of a money exchange charge machine. It is a schematic diagram showing an example of a download page of a physical store payment application. FIG. 2 is a schematic diagram showing an example of a customer registration page executed by a customer registration program. FIG. 2 is a schematic diagram showing the display of a two-dimensional charge code. 3 is a flowchart showing an outline of a charging program. It is a schematic diagram of each screen displayed on the display of a money exchange charge machine by a charge program. FIG. 2 is a schematic perspective view showing an example of laundry equipment installed in the coin laundry store shown in FIG. 1. FIG. FIG. 2 is a block diagram showing a schematic configuration of a device operation centralized management unit. It is a schematic diagram shown about a payment ID transmission program. BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is a schematic diagram of an embodiment of the invention of a physical store and an embodiment of the invention of a physical store payment support system. 1 is a schematic diagram showing the screens of a customer terminal and a store terminal when using charge money in an embodiment of the invention for a physical store and an embodiment of the invention for a physical store payment support system; FIG. It is a schematic diagram showing an example of screen transition for store selection in a physical store payment application of an embodiment.

Next, a mode (embodiment) for carrying out the invention of this application will be described.
In the following explanation, a coin laundry store will be used as an example of a physical store. Therefore, the following description is a description of an embodiment of the invention for a physical store, an embodiment of the invention for a physical store payment support system, and an embodiment of the invention for a coin laundry store, an embodiment of the invention for a coin laundry store payment support system. It's also an explanation.
The technical configuration described below is an explanation of one specific solution as a whole, and the coin laundry store of the embodiment is configured by the individual elements described, and the coin laundry store payment support system of the embodiment is configured. Ru.

FIG. 1 is a schematic plan view of a coin laundry store according to an embodiment, and a schematic diagram of a coin laundry store payment support system according to an embodiment. As shown in FIG. 1, the coin laundry store of the embodiment includes a building 11 having an entrance/exit 111 that is an automatic door, and laundry equipment 12 installed within the building 11. The laundry equipment 12 is a washing machine, a dryer, or the like. Furthermore, a money exchange machine 13 is provided within the building 11.
These laundry machines 12 can be used by the usual payment method, that is, cash payment. That is, each laundry machine 12 operates by inserting a coin and can be used by a customer.

On the other hand, in addition to cash payments, these laundry machines 12 can be used by cashless payments. In this embodiment, the cashless payment is made using prepaid money, which is money paid and deposited in advance. This is supported by the coin laundry store payment support system of the embodiment.

A major feature of the support system of the embodiment is that information on prepaid money is managed on a server on the Internet, while the prepaid money is received by a coin laundry store (real store). In the electronic money type prepaid payment services that are currently in use, the recipient of the loaded prepaid money is the payment service provider. The system is such that prepaid money is paid (deposited) to a payment service provider, and payment is made from the prepaid money when purchasing products or services.
On the other hand, in the embodiment, although the balance information of the prepaid money is managed by the server, the receipt of the prepaid money is not done by the payment service provider but by the product/service seller, that is, the coin laundry store. It is the main body of management.

The coin laundry payment support system of the embodiment includes a support server 2 and a storage unit 3. The support server 2 is a server on the Internet 9, and is a server that receives access from each client terminal via the Internet 9. Therefore, a web server program is implemented.
The storage unit 3 is often a storage such as a hard disk provided in the support server 2, but may also be provided in another server such as a storage server.

The storage unit 3 stores a group of files for providing payment support services. Specifically, the storage unit 3 stores a recipient information file 31, a store information file 32, a device information file 33, a customer information file 34, a balance information file 35, a payment history information file 36, and the like.

FIG. 2 is a schematic diagram showing an example of the structure of a recipient information file. The recipient is the recipient of the prepaid money and the recipient of the payment support service. As shown in FIG. 2, the recipient information file 31 includes "recipient ID", "password", "recipient name", "recipient address", "telephone number", "person in charge", and "store information". This is a database file that records records consisting of fields such as "file name".
“Recipient ID” is a field in which an ID that uniquely identifies a recipient is recorded. The recipient enters into a contract with a service provider company to provide payment support services, and the provision of the service is started. At this time, the recipient ID is determined and recorded in the recipient information file 31.
"Password" is a field in which information necessary for logging into the support server 2 as a recipient is recorded. The password is determined in advance and notified to the recipient along with the recipient ID.
In this embodiment, the "recipient name" is a field in which the name (company name, etc.) of a business operator that operates a coin laundry store is recorded.
"Recipient address" is a field where the location of the business as a recipient (head office address, etc.) is recorded, and "telephone number" and "person in charge" are the contact information of the business as a recipient. be.

FIG. 3 is a schematic diagram showing an example of the structure of a store information file. The store information file 32 is a database file that records information on all coin laundry stores managed by the support server 2. It is also possible to create and store store information as a file for each recipient (each recipient ID), but in this embodiment, all information about stores of different recipients (managers) can be recorded in one file. are doing.

As shown in FIG. 3, the store information file 32 is a database file that records records consisting of fields such as "store ID", "store name", "recipient ID", and "recipient name".
The "store ID" is an ID that uniquely identifies each record in the store information file 32, and is assigned and recorded for each store.
"Store name" is a field recorded in text, such as "XX Laundry XXX Town Store."
The “recipient ID” and “recipient name” are the same as the information in the recipient information file 31.

FIG. 4 is a schematic diagram showing an example of the composition of the device information file. The equipment information file 33 is a database file that records information about the laundry equipment 12 installed in the store. The device information file 33 is created for each store, and can be identified by using the store ID as the file name.
As shown in FIG. 4, the device information file 33 is a file in which records consisting of fields such as "device ID", "device name", and "device type" are recorded. In this embodiment, the "equipment ID" records an ID that can be uniquely identified across all stores recorded in the store information file 32. For example, the device ID is given in the form of store ID + serial number.
As the "equipment name", any name used at the coin laundry store is recorded. For example, it is "Washing machine No. 1". "Device type" is a field in which the type of washing machine or dryer is recorded.

FIG. 5 is a diagram schematically showing the structure of the customer information file. In this embodiment, the prepaid money can be paid as a function of an application program (app) provided by the support server 2. Hereinafter, an application program that can be used for payment at a physical store such as a coin laundry store will be referred to as a physical store payment application. The physical store payment application can be downloaded from the support server 2, and when the physical store payment application is downloaded, a new record is added to the customer information file 34 and user registration is performed.

As shown in FIG. 5, the customer information file 34 includes "customer ID", "password", "name", "gender", "age", "address", "email address", "balance information file name", etc. This is a database file that records records consisting of fields.
"Customer ID" is a field in which an ID automatically generated when downloading, or an ID input (specified) by the customer during user registration after downloading is recorded. In either case, an ID that uniquely identifies the record of the customer information file 34 is recorded.
"Password" is a field in which an initial password is recorded, but if the customer changes it afterwards, it is a field that is updated with the changed password.

"Balance information file name" is a field in which the file name of the balance information file 35 that manages information on prepaid money paid in advance by the customer is recorded.
In this embodiment, the prepaid money paid in advance by the customer is aggregated and the balance is recorded for each same manager of the coin laundry store. The balance information file 35 records this information. The balance information file 35 is created for each customer. That is, one balance information file 35 is created for each customer ID and stored in the storage unit 3. Therefore, the file name of the balance information file 35 is recorded in the customer information file 34.

FIG. 6 is a schematic diagram showing an example of the structure of a balance information file for a certain customer. As shown in FIG. 6, the balance information file 35 is a database file that records records consisting of fields such as "recipient ID", "recipient name", "genre ID", "genre name", and "balance". be.
The "genre name" is a field in which the genre name of the physical store to which the prepaid money is paid for future payment is recorded, and in this embodiment, the text "coin laundry" is recorded.
The “recipient ID” and “recipient name” are the same as those in the recipient information file 31.

“Balance” is a field in which information on the balance of prepaid money for the recipient ID is recorded. In this embodiment, the physical store is a coin laundry store, and a prepaid charge machine is installed at the coin laundry store. In this case, as will be explained later, even if the prepaid money is charged using a prepaid charging machine installed at a different coin laundry store, if the manager of the coin laundry store is the same, that is, if the recipient ID is the same, then the same The total is recorded as the "Balance" value of the record.

FIG. 7 is a schematic diagram showing an example of the structure of a payment history information file. The payment history information file 36 is a database file that records history information of payments made by customers. As shown in FIG. 7, the history information file includes "payment ID", "date and time", "customer ID", "recipient ID", "store ID", "device ID", "device name", "payment amount ” and other fields are recorded. “Payment ID” is a field in which an ID for uniquely identifying a record in the payment history information file is recorded. This value is automatically generated and recorded by a payment history recording program to be described later.

Next, the structure of payment support at a coin laundry store will be explained in more detail.
First, charging of prepaid money by a customer for use of the laundry equipment 12 will be explained. The coin laundry store of the embodiment is equipped with a prepaid charge machine. In this embodiment, the money exchange machine 13 is also used as a prepaid charge machine. Hereinafter, since the money exchange machine 13 is also used as a prepaid charge machine, it will be referred to as a money exchange charge machine.

FIG. 8 is a schematic front view of the exchange charge machine. As shown in FIG. 8, the exchange charge machine 13 has a housing 132 with a front door 131. As shown in FIG. The front door 131 has a money slot and a coin payout slot 135. The money slots are a coin slot 133 and a bill slot 134.
Further, as shown in FIG. 8, a display 136 is provided on the front door 131. Display 136 is a touch panel in this example.
Further, the front door 131 has an opening in which a transparent protective glass 137 is fitted, and a camera 138 that can take pictures through the protective glass 137 is provided inside the housing 132.

FIG. 9 is a block diagram showing a schematic configuration of the exchange charge machine. As shown in FIG. 9, the currency exchange charging machine 13 includes a main control unit 141 that controls the entire currency exchange charging machine 13, a verification unit 142 that checks the authenticity of money inserted from the money slots 133 and 134, and a verification unit 142 that checks the authenticity of money inserted from the money slots 133 and 134. A currency exchange dispensing unit 143 that dispenses exchange money when authenticity is confirmed in the unit 142, a display control unit 144 connected to the display 136, a prepaid processing unit 145 that performs various processes for the premade menu, etc. We are prepared.

The verification unit 142 includes a bill validator and a coin mech, and has the same functions as a normal money exchange machine. The money exchange dispenser 143 also has the same configuration as a normal money changer.
The display control unit 144 is a control unit that generates information to be displayed on the display 136 and inputs the information to be displayed on the display 136, and outputs information according to a pressed location on the display 136.

The prepaid processing unit 145 is a processing unit that performs information processing for prepaid customer registration and prepaid money charging. The prepaid processing unit 145 includes a memory 146 that records necessary programs and data, and a processor 147 that executes programs and displays data on a display.
In addition, as shown in FIG. 9, the prepaid processing unit 145 includes a camera control unit 148 that controls the camera 138, a LAN interface unit (Ethernet board) 149 for accessing the support server 2 via the Internet 9, etc. We are prepared. Incidentally, a coin laundry store is usually provided with a router (wired LAN router or wireless LAN router) 10, and the LAN interface unit 149 is connected to the Internet 9 via the router 10.

FIG. 10 is a schematic diagram showing the operation of the exchange charge machine. FIG. 10(1) shows a display screen (initial screen) in the exchange charge machine 13 in a standby state.
As shown in FIG. 10(1), in the standby state, an exchange button 151 and a prepaid menu button 152 are displayed on the display 136. The display screen in the standby state is a function of the main control section 141, and the main control section 141 sends the data on the display screen to the display control section 144 for display.
When the exchange button 151 is pressed, the main control section 141 performs control to enable the verification section 142 and the exchange payout control section. In this state, when genuine money is inserted, coins (100 yen coins in this example) are dispensed from the currency exchange/dispensing section 143. This part is similar to a normal money changer. Note that even if the exchange button 151 is not particularly pressed, the exchange operation may be configured to be performed as a normal operation.

On the other hand, when the prepaid menu button 152 is pressed, the main control section 141 sends a control signal to the prepaid processing section 145 to perform necessary information processing.
FIG. 10(2) shows an example of the display 136 screen (hereinafter referred to as a prepaid menu screen) when the prepaid menu button 152 is pressed. As shown in FIG. 10(2), when the prepaid menu button 152 is pressed, a customer registration button 153 labeled "New Registration" and a charge button 154 labeled "Charge" are displayed. It has become.

FIG. 10(3) shows the screen display on the display 136 when the customer registration button 153 is pressed. As shown in FIG. 10(3), when the customer registration button 153 is pressed, text explaining prepaid payment is displayed, and access information to the support server 2 is displayed on the display 136 in the form of a two-dimensional code 155. It looks like this. The access information here is the URL of the customer registration page installed in the support server 2, and is a two-dimensional code of the execution code of the customer registration page display program. Hereinafter, this two-dimensional code 155 will be referred to as a two-dimensional code for registration.
Note that when the charge button 154 is pressed, information necessary for charging prepaid money is displayed on the display 136. This will be discussed later.
These screen displays on the display 136 are realized by image data stored in the memory of the prepaid processing section 145 and a display program installed in the prepaid processing section 145.

Next, the support server 2 that performs various information processing including processing for prepaid customer registration will be explained. The support server 2 is operated by a company (hereinafter referred to as a support service provider) that provides payment services to coin laundry stores. Strictly speaking, the service provided by the support service provider is a prepaid money management service and an information provision service for payment.
The support server 2 is a server on the Internet 9 and receives access from the customer terminal 4 via the Internet 9. Therefore, a web server program is implemented.
The customer terminal 4 is a terminal that can access the support server 2 via the Internet 9, and is typically a smartphone.

One of the main functions of the support server 2 is to provide the customer terminal 4 with a physical store payment application 41 at a physical store. The support server 2 is equipped with a download page for a physical store payment application 41. FIG. 11 is a schematic diagram showing an example of a download page of the physical store payment application 41.
As shown in FIG. 11, the download page includes text explaining the physical store payment application 41 and a download button 42. The download button 42 is a button for executing the download program 21 installed on the support server 2. The download button 42 downloads the physical store payment application 41 to the customer terminal 4 and makes it executable, and executes the customer registration program 22 as a subroutine.

FIG. 12 is a schematic diagram showing an example of a customer registration page executed by the customer registration program. When the registration two-dimensional code 155 shown in FIG. 10(3) is executed, the customer registration program 22 is executed. The customer registration program 22 first checks the application registration status of the accessed customer terminal 4 and determines whether the physical store payment application 41 has been downloaded. If the application has not been downloaded, the message "Download the app" and an OK button will be displayed on the customer terminal 4, and when the OK button is tapped, the physical store payment application 41 will be downloaded in the same way as above, and then the customer The registration page is displayed on the customer terminal 4.

As shown in FIG. 12, the customer registration page is provided with fields for inputting personal information such as name, age, gender, address, and email address, and a send button 43. When each piece of information is entered and the send button 43 is tapped, the customer registration program 22 is programmed to add a new record to the customer information file 34 and record the entered information. At this time, the customer registration program 22 is programmed to automatically generate and record a customer ID and initial password. Then, a registration completion report program is executed as a subroutine to send the customer ID and initial password to the customer terminal 4 by e-mail. Note that the customer registration program 22 may be a program included in the physical store payment application 41 (a program on the customer terminal 4).

The following describes how prepaid money can be charged after customer registration is completed in this manner.
Prepaid money is charged by inserting money into the exchange charging machine 13, but since the prepaid money is managed on the support server 2, it is necessary to have the exchange charging machine 13 obtain a customer ID. becomes. Therefore, the physical store payment application 41 is capable of displaying a charging two-dimensional code display page on the customer terminal 4. FIG. 13 is a schematic diagram showing a two-dimensional charging code.

FIG. 13(1) shows an example of the first page (hereinafter referred to as the application top page) that is displayed when the physical store payment application 41 is started and logged in. When the physical store payment application 41 is started, a screen for entering the customer ID and password is displayed. If the customer ID and password are entered correctly here, the user is logged in and the application top page shown in FIG. 13 (1) is displayed. .

As shown in FIG. 13(1), a button 44 labeled "Charge" (hereinafter referred to as "app charge button") is provided on the application top page. The application charge button 44 is linked to a two-dimensional charge code display page shown in FIG. 13(2). As shown in FIG. 13(2), the two-dimensional charge code display page is a screen that displays the customer ID in the form of a two-dimensional charge code 45. When the app charge button 44 is tapped, the customer ID obtained during login is programmed to be converted into a two-dimensional code, transmitted to the customer terminal 4, and displayed.

As shown in FIG. 13 (2), the two-dimensional code display page for charging includes a message stating that the two-dimensional code should be read by the camera installed in the exchange charging machine 13 of the coin laundry store when charging. is now displayed.
The application top page and the charge two-dimensional code display page are pages hosted (provided) by the support server 2, and the programs installed on each page are programs on the support server 2. However, it may also be a program included in the downloaded physical store payment application 41 and a program on the customer terminal 4.

On the other hand, as shown in FIG. 9, a charge program 161 is installed in the prepaid processing unit 145 of the exchange charge machine 13. FIG. 14 is a flowchart showing an outline of the charging program, and FIG. 15 is a schematic diagram of each screen displayed on the display 136 of the exchange charging machine 13 by the charging program 161.
The charge button 154 displayed on the prepaid menu screen of the exchange charge machine 13 shown in FIG. 10(2) serves as a start button for the charge program 161. As shown in FIG. 14, the charge program 161 first displays a customer ID acquisition screen on the display 136. FIG. 15(1) shows an example of a customer ID acquisition screen.

As shown in FIG. 15(1), the charging program 161 first starts the physical store payment application 41, displays a two-dimensional charging code, and displays a message on the display 136 requesting that the camera read it. do. Then, the charging program 161 determines whether a two-dimensional code is output from the camera control unit 148 within a predetermined time, and if it is output, acquires the customer ID from the two-dimensional code. If the two-dimensional code is not output within a predetermined time, an error message is displayed, the program is terminated, and the initial screen returns.

When the two-dimensional code is output and the customer ID is acquired, the charging program 161 displays a charging amount acquisition screen shown in FIG. 15(2) on the display 136. As shown in FIG. 15(2), the charge amount acquisition screen is provided with an amount input field 162 and an OK button 163. Then, there is a display field for displaying a message asking the user to enter the amount to be charged (in units of 100 yen) in the amount input field, press the OK button, and then insert the entered amount into the money slot of the exchange charge machine.

When a number is input into the amount input field 162 and the OK button 163 is pressed, the charge program 161 enters a state of waiting for an input from the verification unit 142. However, if the value entered in the amount input field 162 is not in units of 100 yen, an error message to that effect is displayed and the money input field is zeroed (initialized). In some cases, the screen may be configured so that the amount input field 162 itself can only be entered in units of 100 yen. Hereinafter, the numbers entered in the amount input field 162 will be referred to as input amounts.

When receiving an input from the verification unit 142, the charge program 161 determines whether the verified input amount is equal to or greater than the input amount. If the amount is equal to or greater than the input amount, the charge amount transmission subprogram 164 is executed using the customer ID and the input amount as arguments. Then, the difference between the verification amount and the input amount is calculated, and if the value is larger than 0, a signal is output to the exchange payout unit 143 to pay out the amount as change. The charge program 161 is now finished.

As shown in FIG. 14, when a predetermined time lag has elapsed at each stage, the charging program 161 displays an error message indicating a timeout and ends the program. If there is an input from the verification unit 142 and the input amount is less than the input amount and a timeout occurs, a signal is output to the currency exchange and payout unit 143 to pay out the inserted money as is.

As shown in FIG. 1, a charge amount recording program 23 is installed in the support server 2. The charge amount transmission subprogram 164, which is a subroutine of the charge program 161 on the exchange charge machine 13 described above, is a program that accesses the support server 2 and executes the charge amount recording program 23.
The charge amount recording program 23 on the support server 2 is a program that is executed using the store ID, recipient ID, customer ID, and charge amount as arguments. The charge amount transmission subprogram 164 executes the charge amount recording program 23 by passing the store ID, recipient ID, customer ID, and charge amount. The store ID and recipient ID are incorporated in advance as constants when the charge program 161 is installed in the exchange charge machine 13. In addition, each exchange charge machine 13 is given special access authority to the support server 2 (authority to execute programs on the support server 2), and when executing the charge amount recording program 23, the key is also given. It will also be sent.

The charge amount recording program 23 searches the customer information file 34 using the passed customer ID, and acquires the file name of the balance information file 35 from the corresponding record. Then, the balance information file 35 with that file name is opened and searched using the recipient ID. If there is a matching recipient ID, the value of the passed charge amount is added to the value of the "prepaid balance" of that record, and the "prepaid balance" is updated. If there is no matching recipient, add a new record and record the recipient ID and charge amount.Now, the information on the money inserted at the currency exchange charge machine 13 will be recorded as the charge amount in the balance information file 35. It will be recorded and managed.

Next, the use of the laundry equipment 12 using prepaid money charged in this manner will be explained.
FIG. 16 is a schematic perspective view showing an example of laundry equipment installed in the coin laundry store shown in FIG. 1. The example shown in FIG. 16 is an example of a washing machine.
As shown in FIG. 16, the laundry equipment 12 includes a coin insertion slot 121 into which cash (coins) are inserted as usage fees for operating the laundry equipment 12. Separately, this laundry equipment 12 includes a cashless display section 122 on which is printed an explanation that operation is possible using prepaid money. In this example, the cashless display section 122 is a pasted sticker.

The laundry equipment 12 also includes an access information providing section that provides access information to the support server 2. In this embodiment, the customer is scheduled to bring the customer terminal 4 to the store. The access information providing unit is an element that provides access information to the customer terminal 4.
Several different configurations of the access information providing unit are possible. As a simple configuration, a configuration may be adopted in which the URL including the domain name of the support server 2 is converted into a two-dimensional code, printed, and pasted on the laundry equipment 12. The two-dimensional code is typically a QR code (registered trademark).

Another configuration may be such that a small display 123 and a button 124 are attached to the laundry equipment 12, and when the button 124 is pressed, a two-dimensional code is displayed on the display 123. A configuration can be adopted in which a memory (such as a ROM) that stores image data of a two-dimensional code is provided, and a simple display circuit that reads the image data from the ROM and displays it on the display 123 is incorporated.

Either configuration is fine, but in the case of a configuration in which a sticker with a two-dimensional code printed on it is pasted, a malicious person may paste another two-dimensional code from above, and the customer may accidentally visit a malicious site. It is possible that you may be induced. Therefore, in this embodiment, the laundry equipment 12 is provided with a display 123 (hereinafter referred to as the equipment display) such as a small liquid crystal display, and a configuration is adopted in which the two-dimensional code 125 is displayed on the equipment display 123. ing. However, since coin laundry stores are usually equipped with security cameras and are under surveillance, such crimes are less likely to occur. In terms of cost, it is cheaper to apply stickers printed with two-dimensional codes, so they are sometimes used. Hereinafter, the two-dimensional code 125 displayed on the device display 123 will be referred to as a device two-dimensional code.

Further, as shown in FIG. 1, the coin laundry store is provided with a device operation centralized management unit 5. FIG. 17 is a block diagram showing a schematic configuration of the laundry equipment and the equipment operation centralized management unit.
As shown in FIG. 17, each laundry device 12 includes a coin mech 126, an operation control circuit 127, an operation start switch 128, and the like. These are elements that are also included in ordinary laundry equipment 12, and when the coin mech 126 outputs that a predetermined amount of regular coins have been inserted, the operation control circuit 127 outputs an operation start signal to the operation start switch 128. By doing so, the laundry equipment 12 is configured to start operating.

As shown in FIG. 17, the device operation centralized management unit 5 is a unit connected in parallel to the operation control circuit 127 with respect to the operation start switch 128 of each laundry device 12. Each output port 51 connected to each laundry device 12 is provided with an operation signal output circuit 52, respectively. The operation signal output circuit 52 is a circuit having a similar configuration to the operation control circuit 127 in each laundry device 12, and is a circuit that outputs an operation start signal to the operation start switch 128. For example, in laundry equipment sold by a certain manufacturer (for example, a washing machine for coin laundry stores), a 10V voltage signal is sent from the operation control circuit 127 to the operation start switch 128, so that the operation start switch 128 is turned on. It is configured. In this case, the operation signal output circuit 52 of the device operation centralized management unit 5 is also configured to output a 10V voltage signal via the output port 51.

As shown in FIG. 17, the device operation centralized management unit 5 is connected to the support server 2 via the Internet 9, and is provided with a LAN interface section 53 like the exchange charge machine 13. The central control unit 54 outputs an operation start command to one of the operation signal output circuits 52 in accordance with a signal input from the LAN interface unit 53.
The centralized control unit 54 is constituted by a small computer equipped with a CPU such as a Raspberry Pi. A central control program 55 is installed in the central control unit 54, and the central control program 55 is always in an execution state while the coin laundry store is in business.

The centralized control program 55, like the exchange charge machine 13, is given access authority to the support server 2, and after startup, the program accesses the support server 2, logs in, and maintains the logged-in state. Then, the system enters a state of waiting for input of payment permission information from the support server 2.

On the other hand, the support server 2 implements a payment ID transmission program 24 as one of the menus of the physical store payment application 41. FIG. 18 is a schematic diagram showing the payment ID transmission program.
As shown in FIG. 13(1), the application top page displayed on the customer terminal 4 after login is provided with a use button 46 labeled "Use prepaid money." A genre selection screen is linked to the use button 46. FIG. 18(1) is a schematic diagram showing an example of a genre selection screen.

As shown in FIG. 18(1), the genre selection screen is provided with buttons labeled with genre names. Each button is linked to a two-dimensional code acquisition screen. When the laundry button labeled "Coin Laundry" is tapped, a two-dimensional code acquisition screen for a coin laundry store as shown in FIG. 18(2) is displayed on the customer terminal 4.

As shown in Figure 18 (2), the message "Please read the two-dimensional code displayed on the display of the laundry equipment" is displayed on the two-dimensional code acquisition screen, and the two-dimensional code acquisition screen displays the following message: A frame 47 for photographing the dimensional code is linked. The actual payment application is programmed to use the two-dimensional code photographing API implemented in the customer terminal 4, and when the device two-dimensional code 125 is photographed by the API, the device two-dimensional code 125 is restored to the URL. and is programmed to cause the customer terminal 4 to execute the URL.

The device two-dimensional code 125 is an execution code of the payment determination program 25 on the support server 2. The payment determination program 25 is a program that is executed using the store ID, device ID, recipient ID, and customer ID as arguments.
The device two-dimensional code 125 includes a store ID, a device ID recipient ID, and a payment amount as constants. The payment amount is the fee for using the laundry equipment 12. The payment determination program 25 is a program that receives these as arguments and is executed.

The payment determination program 25 acquires the customer ID held in the session variable upon login, searches the customer information file 34 using the customer ID, and acquires the file name of the balance information file 35 from the corresponding record. Then, the balance information file 35 with this file name is opened and searched using the recipient ID. If there is a record with the corresponding recipient ID, the value of "balance" is acquired. If this value is equal to or greater than the payment amount, the payment permission information program 251 is executed as a subroutine. Furthermore, the balance reduction program 252 and the payment history recording program 253 are executed as subroutines, and the process ends. In the balance information file 35, if there is no record of the corresponding recipient ID, or even if there is, the "balance" value is less than the payment amount, the payment determination program 25 executes the payment disapproval information sending program 254. and exit.

The payment permission information sending program 251 is a program that sends usage permission to two terminals. One is the customer terminal 4 that is logged in, and a page (hereinafter referred to as the payment completion confirmation page) indicating that the use of the laundry equipment 12 is permitted and the prepaid money has been deducted is sent to the customer terminal 4 and displayed. The payment permission information transmission program 251 is programmed to allow the payment permission information to be sent. FIG. 18(3) shows an example of a payment completion confirmation page.

The other is the device operation centralized management unit 5. The device operation centralized management unit 5 is logged in using a login ID using the store ID. The payment permission information sending program 251 is programmed to send payment permission information to the device operation central management unit 5 installed at the store in accordance with the store ID passed as an argument.
The payment permission information sent to the device operation centralized management unit 5 includes the device ID. When the device operation central management unit 5 receives the payment permission information, the central control program 55 executed in the central control section 54 is programmed to output an operation start command to start the operation of the corresponding laundry device 12 according to the device ID. has been done. That is, it is programmed to output an operation start command to the corresponding operation start signal output circuit 52 and cause the laundry equipment 12 to output an operation signal output via the output port 51.

The payment history recording program 253 is a program that records payment history in the payment history information file 36. The payment history recording program 253 adds a new record to the payment history information file 36, records the program execution time in the "date and time", and records the store ID, device ID, device name, recipient ID, customer ID, and payment amount. Record in each field. Regarding the device name, open the device information file 33 according to the store ID, search for the device ID, obtain the value, and record it.

In this embodiment, the support server 2 also provides a service for the recipient to view payment history information. This point will be explained below.
The support server 2 serves as a server that hosts each page for recipients. In addition to the recipient ID, the recipient is also given a password, and when accessed using these passwords, the recipient page can be viewed. As shown in FIG. 1, the recipient can operate the recipient terminal 6, input the recipient ID and password, and display the recipient page on the recipient terminal 6 via the Internet 9. .

One of the recipient pages is a payment history viewing page, and the support server 2 is equipped with a payment history viewing page display program. Although illustration of the payment history viewing page is omitted, the payment history viewing page display program searches the payment history information file 36 using the recipient ID input at the time of login, extracts and displays information on matching records. is programmed to do so. It is also possible to specify a period, and if the same recipient manages multiple stores, it is also possible to specify the store.

A cashless payment performed by a customer visiting a coin laundry store according to an embodiment having such a configuration will be described below. The following description is also a description of the operation of the embodiment of the coin laundry store payment support system.
First, customers visiting a coin laundry store usually pay with cash (coins), but they decided to try cashless payment using the prepaid payment system displayed inside the store. At 136, the prepaid menu button 152 is pressed. Then, the user presses the customer registration button 153 on the screen that is displayed thereafter. As a result, a two-dimensional registration code 155 is displayed on the display 136, and the customer reads it with the customer terminal 4. As a result, the customer terminal 4 accesses the support server 2, and the customer registration page display program is executed.

The customer enters each piece of information on the customer registration page displayed on the customer terminal 4, and taps the OK button. As a result, the physical store payment application 41 is downloaded to the customer terminal 4, and a new record is added to the customer information file 34 on the support server 2, and the customer ID, password, etc. are recorded. Then, a registration completion report is sent to the customer terminal 4 by e-mail.

Then, the customer charges the money using the exchange charge machine 13. That is, the user presses the charge button 154 on the prepaid menu screen shown in FIG. 10(2). As a result, the charging program 161 on the exchange charging machine 13 is executed. The charge program 161 displays a customer ID acquisition screen on the display 136, and the customer starts the physical store payment application 41 on the customer terminal 4 in accordance with this display. Then, the user taps the app charge button 44 in the physical store payment application 41 to display the two-dimensional charge code 45 on the customer terminal 4. Then, the two-dimensional charge code 45 is read by the camera 138 of the exchange charge machine 13. Thereby, the charge program 161 obtains the customer ID of this customer.

Next, the charge program 161 displays a charge amount acquisition screen on the display 136. When the charge amount is input into the amount input field 162 on the charge amount acquisition screen and the OK button 163 is pressed, the charge program 161 displays a message on the display 136 prompting the user to insert money for the charge amount. After that, when the verification unit 142 outputs a signal indicating that money greater than the charge amount has been inserted within a predetermined time, the charge program 161 sends the charge amount using the customer ID and the input amount (charge amount) as arguments. Execute subprogram 164. Further, if there is a difference between the verified amount and the input amount, that amount will be paid out as change.

The charge amount transmission subprogram 164 passes the store ID, recipient ID, customer ID, and charge amount as arguments, and executes the charge amount recording program 23 on the support server 2. The charge amount recording program 23 searches the balance information file 35 created for the corresponding customer using the recipient ID, adds the charge amount to the "balance" value of the corresponding record, and updates the "balance".

After the charging process is performed in this way, the customer makes a payment with prepaid money and uses the laundry equipment 12. That is, the user goes to a vacant (unused) laundry machine 12 in the store and presses the button 124 to display the machine two-dimensional code 125 on the machine display 123. Then, the customer starts the physical store payment application 41 on the customer terminal 4, and presses the "Con Laundry" button on the genre selection page. As a result, a two-dimensional code acquisition screen for the coin laundry store is displayed on the customer terminal 4. The customer causes the customer terminal 4 to read the equipment two-dimensional code 125 displayed on the equipment display 123 of the laundry equipment 12. As a result, the payment permission determination program 25 on the support server 2 is executed, and if the payment amount is less than or equal to the balance, payment permission information is sent via the Internet 9 to the device operation central management unit 5 in the store. At the same time, the payment amount is subtracted from the value of "Balance" of the record in the balance information file 35, and the "Balance" is updated.

The device operation centralized management unit 5 acquires the device ID from the transmitted payment permission information, and outputs an operation start signal to the laundry device 12 having the device ID. As a result, the laundry equipment 12 starts operating. The subsequent operation of the laundry equipment 12 is the same as normal (in the case of cash payment).
In this way, each customer uses each laundry machine 12 by making a cashless payment using prepaid money. On the other hand, the recipient collects cash from each laundry machine 12 and exchange charge machine 13, and operates the recipient terminal 6 to view payment history information as appropriate. That is, the user inputs the recipient ID and password to access the support server 2 and view payment history information.

In the above configuration and operation, the laundry equipment 12 may be able to operate under a plurality of different conditions, and the payment amount may differ accordingly. In this case, the device two-dimensional code 125 includes the payment amount under the conditions selected by the customer. For example, in the case of a dryer, customers can select the drying time and pay a usage fee depending on the drying time. In such a case, for example, different two-dimensional codes are displayed on the device display 123 depending on the conditions of use, and the customer selects one and reads it with a mobile terminal. For example, if a dryer costs 10 minutes for 100 yen, 20 minutes for 200 yen, and 30 minutes for 300 yen, there will be a two-dimensional code (drying time 10 minutes) with 100 yen as the payment amount, and 200 yen as the payment amount. A two-dimensional code with the payment amount (20 minutes drying time) and a two-dimensional code (30 minutes drying time) with the payment amount of 300 yen are displayed, and the customer selects one to read. do it like this.

According to the coin laundry store of this embodiment and the coin laundry store payment support system of this embodiment, cashless payments are realized, so customers can visit without having coins if they have previously charged the coins. Laundry equipment 12 can be used, increasing convenience. Even if you only have high-value bills that cannot be exchanged at a currency exchange machine, you can use the laundry equipment 12.
On the other hand, for coin laundry store managers (recipients), this convenience is a means of attracting customers, and since it is a prepaid service, there is no sales period. Furthermore, since it is a prepaid service, it also has the advantage of freeing up working capital (cash flow).

At this time, since the configuration is such that prepaid money is managed by the support server 2 on the Internet 9 instead of issuing prepaid cards, the introduction cost can be extremely small. Since the service providing company that operates and manages the support server 2 provides services by contracting with a large number of recipients, that is, a large number of coin laundry store managers, the cost of prepaid money management by the support server 2 is extremely low.

Furthermore, what is important in the configuration of the above embodiment is that since the currency exchange charging machine 13 is installed at a coin laundry store, the cash paid at the time of charging can be passed directly to the manager (receiver) of the coin laundry store. be. The current e-money prepaid service is a system in which the prepaid money is received by the service provider from the customer's bank account (or customer's wallet), and then the service provider transfers the money to the store manager's bank account for payment. It becomes. Therefore, service provider fees and transfer fees are incurred.
On the other hand, in the coin laundry store and payment support system of the embodiment, such fees do not occur, and only the prepaid money management fee is charged as a fee. Therefore, it is extremely suitable as a cashless payment method for coin laundry stores, which are usually small in scale.

Furthermore, in the coin laundry store and payment support system of the embodiment, prepaid money is managed for each recipient. That is, in the balance information file 35, the charged prepaid money is added up for the same recipient. This point has important significance in relation to regulations under the law (Fund Settlement Act).
Currently, the Payment Services Act requires a notification rather than a registration system if the prepaid payment method can only be used to purchase goods and services from the issuer or a person with a capital relationship with the issuer. . In other words, the coin laundry store manager (recipient) only needs to notify the Ministry of Finance and pay the deposit (1/2 of the balance), and the Ministry of Finance, as in the case of a third-party payment instrument issuer, Registration is not required. If the total balance of prepaid money as of the end of March or June of each year is 10 million yen or less, no notification or deposit payment is required. Even if the total balance exceeds 10 million yen, all you have to do is enter into an issue guarantee deposit agreement with a financial institution and notify the Ministry of Finance.

In the embodiment, the fact that the balance information file 35 records the balance of prepaid money for each of the same recipients (same manager) indicates that the balance information file 35 corresponds to a private prepaid payment method as defined in the Payment Services Act. This will bring about the benefit of making it easier to comply with laws and regulations. Furthermore, under the Payment Services Act, "the same recipient" includes cases where there is a close relationship such as a capital relationship, so it is broadly interpreted as such. In other words, when concluding a contract for a physical store payment service, it is determined whether there is a "close relationship" with each coin laundry store manager under the Payment Services Act, and if so, the same recipient ID is assigned and managed. do.

Further, the configuration of the coin laundry store and the coin laundry store payment support system of the above embodiments has a remarkable effect in that it enables customer analysis and customer retention. By viewing the payment history information, the recipient can know which customer (which customer ID) used which laundry equipment 12 on which date and time. Furthermore, by obtaining prior consent from each customer, it is also possible to learn the customer's gender, age, etc. This means that customer analysis, which was previously impossible in the coin laundry business, will be possible, and will greatly contribute to the management of the coin laundry business.

For example, by knowing the age and gender of customers, it is possible to renovate stores accordingly. If there are a large number of relatively young women, improvements can be made by creating an atmosphere that makes it easier for them to visit the store.
Furthermore, since the customers are identified, it is possible to retain them by giving them special benefits. For example, when you charge prepaid money or make a payment using prepaid money, you will be given points according to the amount, and once you have accumulated points, you can add the remaining amount of prepaid money according to the points, or you can receive one free washing machine. You can implement promotional measures such as In conventional coin laundry stores, such promotional measures were not possible because customers could not be identified, but according to the embodiment, they are possible.

Additionally, since addresses and e-mail addresses are registered as personal information, it is also possible to distribute campaign information. For example, it is possible to adopt a campaign that gives more points on weekdays when the number of visitors to the store is relatively low, and to communicate this to each customer by e-mail.

In the embodiment described above, customer registration was performed by the customer terminal 4 reading the two-dimensional registration code 155 displayed on the display 136 of the exchange charge machine 13; A configuration may be adopted that performs this. That is, the service provider advertises the physical store payment application 41 on its website, and this website is provided with a download button for the physical store payment application 41. When a customer sees this website, they decide to try using it and press the download button. As a result, the physical store payment application 41 is downloaded and customer registration is performed in the same manner as described above.

Further, the charge amount transmission subprogram 164 executed at the time of charging may be a program included in the physical store payment application 41 instead of a program on the exchange charge machine 13. In this case, since the customer terminal 4 needs to acquire at least the recipient ID and the charge amount from the exchange charge machine 13, for example, the exchange charge machine 13 generates a two-dimensional code and causes the customer terminal 4 to read it. It is done by When the verification unit 142 outputs a signal indicating that the input amount of money has been inserted, the charging program 161 on the exchange charging machine 13 generates a two-dimensional code containing the recipient ID and the charging amount, and sends this to the customer. The terminal 4 reads the information, transmits the recipient ID, charge amount, and customer ID to the support server 2, and causes the support server 2 to execute the charge amount recording program 23.
However, there is also a possibility that a malicious customer may modify the physical store payment application 41 to transmit and record an amount greater than the actual charge amount to the support server 2. Considering this, a configuration in which the charge amount is transmitted from the exchange charge machine 13 is preferable.

Furthermore, it is not essential that the laundry equipment 12 displays the equipment two-dimensional code 125, and the two-dimensional equipment code 125 may be displayed at another location. For example, a configuration is adopted in which the device operation centralized management unit 5 includes a display and device selection buttons. The equipment selection button is configured so that only non-operating laundry equipment 12 can be selected, and when a laundry equipment 12 is selected with the equipment selection button, a two-dimensional code containing the store ID and the equipment ID of the selected laundry equipment 12 is displayed. is displayed on the display.

Another simpler configuration may be one in which something like a poster, in which two-dimensional codes for each laundry device 12 are printed side by side, is pasted on the wall. The customer checks the laundry equipment 12 that is not in operation, reads the two-dimensional code for the laundry equipment 12, and makes a payment. However, in this case, there is a possibility that the two-dimensional code of the laundry equipment 12 in operation may be read by mistake. As a countermeasure for this, the support server 2 can check the operating status of each laundry machine 12, and when the machine ID of the laundry machine 12 in operation is sent, an error message is sent back to the customer terminal 4, and the payment is made. It is configured so that it does not occur. As a configuration for checking the operating status of each laundry device 12, a configuration may be adopted in which the device operation centralized management unit 5 acquires information on whether each laundry device 12 is in operation or not and transmits it to the support server 2. Alternatively, each laundry device 12 may be provided with a network function and directly transmit information on whether or not it is in operation to the support server 2.

The payment permission information is sent from the support server 2 to the device operation centralized management unit 5, but the structure is such that it is sent from the support server 2 to the customer terminal 4 and starts the operation of the laundry device 12 via the customer terminal 4. Also good. In this case, payment permission information is generated in the form of a two-dimensional code, for example, and transmitted from the support server 2 to the customer terminal 4, and this two-dimensional code is read by a camera provided in the device operation central management unit 5 or the laundry device 12. do. In the case of this configuration, there is a problem of high costs because the device operation centralized control unit 5 or each laundry device 12 needs to be equipped with a camera. There may be fraud that generates and reads it. Therefore, a configuration in which payment permission information is transmitted to the device operation centralized management unit 5 is preferable.

Note that if each laundry device 12 is equipped with a network function, the support server 2 can send payment permission information to each laundry device 12 to start operation, so the device operation centralized management unit 5 is unnecessary. Become. However, there are cost and durability issues, and considering the characteristics of unmanned coin laundry stores, there is a problem that they may be damaged or used for unauthorized access, so is preferable. The device operation centralized control unit 5 can be placed in a place that cannot be touched by the customer, or the housing or the like can be configured so that important parts cannot be touched by the customer.

In the above embodiment, the exchange of information between the exchange charge machine 13 and the customer terminal 4 and the exchange of information between each laundry device 12 and the customer terminal 4 are performed using a two-dimensional code such as a QR code (registered trademark). A reading configuration was adopted, but this is just an example, and other NFC configurations such as infrared communication or Bluetooth (registered trademark) may be adopted.
Moreover, although the prepaid charge machine was the exchange charge machine 13 which also served as a money exchange machine, a prepaid charge machine may be provided separately from the money exchange machine. However, the prepaid charge machine also requires a coin counter and a bill validator, and since both devices are equipped with common equipment, a shared configuration is preferable in terms of cost reduction and space saving.

Next, an embodiment of the invention for a physical store and an embodiment of the invention for a physical store payment support system will be supplementarily described. FIG. 19 is a schematic diagram of an embodiment of the invention for a physical store and an embodiment of the invention for a physical store payment support system.
The configurations of the support server 2 and the storage unit 3 can be directly adopted as an embodiment of the invention for a physical store or an embodiment of the invention for a payment support system for a physical store. In this case, although the coin laundry store is assumed to be an unmanned store, the configuration of a manned physical store (with a clerk) may be changed as appropriate.

First, in the case of manned stores, prepaid jersey machines can be made unnecessary. In the case of an unmanned store such as a coin laundry store, the prepaid jersey machine collects (receives) cash on the spot and transmits information on the charge amount to the support server 2. In the case of a manned store, cash can only be received by a store clerk, so a prepaid charge machine is not necessary.
However, it is necessary to transmit the charge amount to the support server 2 and execute the charge amount recording program 23, and a charge amount transmitter is required. The charge amount transmitter can also be used as a general-purpose terminal 7 such as a PC, and can be easily configured. For example, a tablet PC equipped with a camera can be used. Hereinafter, the terminal 7 provided in the store will be referred to as a store terminal.
A charge amount sending program 71 for transmitting a customer ID and a charge amount to the support server 2 is installed in the store terminal 7 such as a tablet PC. The store ID and recipient ID are given as constants to the charge amount sending program.

The customer pays cash to top up the prepaid money at a physical store. The clerk uses the store's cash register to issue a receipt and receive cash. At this time, the customer uses the customer terminal 4 to start the physical store payment application 41 and displays the two-dimensional charging code 45 on the customer terminal 4. The clerk reads it with the camera of the store terminal 7 and inputs the charge amount. The charge amount transmission program 71 acquires the customer ID from the two-dimensional code and transmits it to the support server 2 along with the input charge amount, store ID and recipient ID given as constants. The charge amount recording program 23 on the support server 2 is similarly executed, and the charge amount is added and updated in the record of the recipient ID in the balance information file 35 for the customer ID.

The store terminal 7 may be a desktop PC, a notebook PC, or a smartphone as long as it can read the two-dimensional charging code of the customer terminal 4. Similarly, in addition to the configuration in which the customer ID is received using a two-dimensional code, other NFC such as infrared communication can also be adopted.
Regarding customer registration, in addition to a configuration in which the customer downloads the physical store payment application 41 in advance, a two-dimensional code for downloading the physical store payment application 41 may be displayed at the physical store. In the case of a manned store, fraud by pasting a two-dimensional code on top of the code is impossible, so it is sufficient to simply post a poster with the two-dimensional code printed on the wall or hand it out to customers as a flyer.

In order to use the charged prepaid money, the physical store must have a payment permission information receiver that receives and displays payment permission information from the support server 2 in order to confirm that the payment is permitted. become. A general-purpose terminal such as a PC or a smartphone can also be used as the payment permission information receiver. In the following description, a configuration in which the store terminal 7 also serves as a charge amount transmitter will be taken as an example. In the example below, a configuration is adopted in which the store terminal 7 is also used for sending the payment permission application.

FIG. 20 is a schematic diagram showing the screens of the customer terminal 4 and the store terminal 7 when charging money is used in the embodiment of the invention for a physical store and the embodiment of the invention for a physical store payment support system.
When using prepaid money at a physical store other than a coin laundry store, the customer causes the store terminal 7 to obtain a customer ID and makes a payment application from the store terminal 7. Specifically, the customer similarly starts the physical store payment application 41 and displays the application top page. Then, the user taps the use button 46 on the application top page to display the genre selection screen as shown in FIG. 20(1). Then, select the "Other" genre (other than coin laundry) on the genre selection screen. Thereby, the two-dimensional code 48 is displayed on the customer terminal 4, as shown in FIG. 20(2). The two-dimensional code 48 is a two-dimensional image of the customer ID and password. The customer shows the customer terminal 4 on which the two-dimensional code 48 is displayed to the clerk, and verbally tells the customer the desired payment amount.

On the other hand, a payment application program 72 is installed in the store terminal 7. The payment application program 72 is in a constantly running state (payment standby state) while the store is in operation, and is in a state in which it can read two-dimensional codes. This state is shown in FIG. 20(3). When the store terminal 7 reads the two-dimensional code 48 shown in FIG. 20(2), the payment application program 72 displays a payment application screen on the store terminal 7, as shown in FIG. 20(4). The payment application screen is provided with a payment amount input field 73 and a send button 74 in addition to a display field for the customer ID obtained from the two-dimensional code. The clerk enters the payment amount that he/she has heard from the customer into the payment amount input field 73, and taps or clicks the send button 73. The send button 73 is an execution button for the payment permission determination program 25 on the support server 2, and sends the store ID, recipient ID, acquired customer ID and password, and input payment amount to determine payment permission. A code for executing the program 25 is embedded in the send button 73.

By tapping or clicking the send button 73, the payment permission determination program 25 is executed. The payment permission determination program 25 determines that if the customer ID and password match those recorded in the customer information file 34 and the balance recorded in the record of the corresponding recipient ID in the balance information file 35 is greater than or equal to the payment amount. , the payment permission information transmission subprogram is executed to send payment permission information to the store terminal 7 and the customer terminal 4. At the same time, the balance reduction program 252 is executed to subtract the payment amount from the balance and update the balance. FIG. 20 (5) shows the payment permission information being sent to the customer terminal 4 and displayed, and FIG. 20 (6) shows the payment permission information being sent to the store terminal 7 and displayed. The current state is shown.

As shown in Figures 20 (5) and (6), in this example, the payment permission information includes the store name, customer ID, payment amount, and payment ID, and the payment ID is displayed. There is. The payment ID is an ID used by both the store and the customer to confirm payment using prepaid money.
The clerk deducts the payment amount based on the payment permission information displayed on the store terminal 7 and settles the payment. For example, if a customer makes a purchase of 500 yen and payment permission information is sent informing them that they will pay the entire 500 yen with prepaid money, the amount to be collected in cash will be zero and the item will be handed over to the customer. If payment permission information is sent after being informed that a portion of the amount will be paid with prepaid money, the reduced amount will be notified to the customer and collected from the customer.

According to such a physical store and physical store payment support system, as in the case of a coin laundry store, a prepayment means is issued without using a card, and payment can be made using prepaid money charged. Since the cash paid when charging is received at the store, there are no transfer fees, and since it is prepaid, there is no sales period. For this reason, it is suitably introduced in various small-scale shops and the like.

In addition, as mentioned above, in the case of a manned physical store, a prepaid charge machine is no longer necessary, and a two-dimensional code, which is a two-dimensional symbol of the customer ID and password, can be read from the customer terminal 4 to access the support server 2. Since it is only necessary to prepare a capable terminal as the store terminal 7, the introduction cost is further reduced.
In the configuration of the physical store and physical store payment support system described above, the two-dimensional code when using prepaid money includes the password in addition to the customer ID. This is to prevent unauthorized loading into the terminal 7.

Further, it is also possible to configure the physical store and physical store payment support system described above so that the payment permission application is transmitted from the customer terminal 4. In this case, the store presents the customer with a two-dimensional code that includes the store ID and recipient ID, the customer reads it on the customer terminal 4, and the customer enters the payment amount on the payment permission application screen displayed on the customer terminal 4. You will have to enter it and send it. Although this configuration is acceptable, it is complicated for the customer, and since the store is responsible for paying for the purchase, information is exchanged in the opposite direction, which also makes it complicated. Therefore, it is preferable to enter the payment amount at the store terminal 7 and apply for payment permission.

Note that there may be a configuration in which the payment permission information is transmitted only to the customer terminal 4 and the customer shows it (the screen on which the payment permission information is sent and displayed) to the store clerk. However, since there is a possibility of fraud by forging a screen that appears to show payment permission information has been sent to the store clerk, it is preferable that the payment permission information be sent to at least the store terminal 7.

Next, an embodiment of the invention of a physical store payment application will be supplementarily described.
In each of the embodiments described above, the physical store payment application provides a service in which each recipient is virtually issued with a dedicated prepaid card that can only be used at a store run by the recipient. It can be said. The embodiment of the physical store payment application described below is optimized with this point in mind.

Currently, special prepaid cards are issued that can only be used at the company's own stores, but if a special prepaid card is issued at a different store (a different recipient's store), the customer will have to carry another prepaid card as well. , my wallet is full of prepaid cards. A universal prepaid card that can be used at different recipients' stores is convenient, but as mentioned above, each recipient must pay some fees.
On the other hand, according to the physical store payment application according to the embodiment, since a dedicated prepaid card is issued virtually, there is no need for the customer to be complicated and it is extremely convenient. Considering the issuance of virtual-only prepaid cards (i.e., initial charging) at a number of different stores (different recipient stores), in this embodiment, when recharging and using prepaid money, We have a page for selecting stores. An example of this is shown in FIG. FIG. 21 is a schematic diagram showing an example of screen transitions for store selection in the physical store payment application of the embodiment.

FIG. 21(1) shows the top page displayed on the customer terminal 4 after login in the physical store payment application of the embodiment. As shown in FIG. 21(1), the top page of the physical store payment app of this embodiment includes a card button 401 labeled "View issued cards" and a new card button 401 labeled "Create new card". A create button 402 and a coin laundry button 403 labeled "create/use at coin laundry" are provided.

The new creation button 402 is a button with the same function as the app charge button 44 in FIG. This is the execution button for the program to be executed. Similarly, by reading this two-dimensional code with the store terminal 7 of any store, a new record is added to the balance information file 35 of the customer, and prepaid money is registered with the manager of this store as the recipient. . That is, a virtual dedicated prepaid card is issued.

The coin laundry button 403 in FIG. 21(1) is a button for charging and payment at each coin laundry store, and when tapped, the page changes to a page as shown in FIG. 13(1). The following operations are similar to those described above.
The card button 401 in FIG. 21(1) is linked to a store list page that displays stores where the customer has charged in the past. FIG. 21(2) shows an example of a store list page.
As shown in Figure 21 (2), the store list page is a page that displays a list of stores that have been charged in the past, but stores that have the same recipient are displayed together (for example, , the store name associated with the store ID at the time of first charging is displayed), so it is essentially a list of virtual prepaid cards.

In this embodiment, the balance information file 35 records the store ID of the store where the store terminal 7 that sent the charge amount is installed. Since the store ID is overwritten each time the charge amount is transmitted, the store ID at the time of the most recent charge is retained.
The program implemented in the support server 1 to display the store list page shown in FIG. 21(2) opens the balance information file 35 of the customer according to the customer ID held at the time of login, and stores the store ID The program is programmed to acquire store names or store chain names (hereinafter collectively referred to as store names) according to the above information, and incorporate them into the store list page as shown in FIG. 21(2). In this embodiment, each record of the balance information file 35 has a field in which a name to be incorporated into the store list page is recorded. In the case of a recipient who manages only one store, the value in this field will be the store name, but in the case of a recipient who manages multiple stores, it will be the common store chain name.

Each store name shown in FIG. 21(2) is linked to a page for charging or using prepaid money at the store (hereinafter referred to as an individual card page). FIG. 21(3) is a schematic diagram showing an example of an individual card page.
As shown in FIG. 21(3), the individual card page is provided with an individual charge button 404 and an individual payment button 405. The individual charge button 405 is a button for paying (charging) prepaid money to the recipient associated with this store name. When this button is pressed, a two-dimensional charge code is displayed on the customer terminal 4 in the same manner as in FIG. 13(2), which is read by the store terminal 7 and the charge is performed. That is, the clerk receives the prepaid money, and the store terminal 7 transmits the charge amount.

The individual payment button 405 is a button for using prepaid money at a store managed by the recipient related to this store name. When the individual payment button is pressed, a two-dimensional code for payment is displayed on the customer terminal 4, as shown in FIG. 21(2), and the payment is made by reading it on the store terminal 7. The store clerk asks the customer for the usage amount, enters it on the store terminal 7, and sends it to complete the payment.

The physical store payment application of this embodiment virtually issues a plurality or a large number of different dedicated prepaid cards and provides charging and payment services. Although it has the same functionality and convenience as a dedicated prepaid card, customers do not need to carry the card in their wallet, but can select a virtual dedicated prepaid card on the customer terminal 4 and charge it or use it for payment. This app provides a simple and smart payment method.
Note that each virtual prepaid card may be charged not only with cash but also with a credit card or the like.

In addition, in the above-mentioned physical store, physical store payment support system, and physical store payment application, the physical store is described as a manned store, but implementation is possible even in an unmanned physical store. For unmanned physical stores, it is preferable that a prepaid charge machine is provided, and the exchange charge machine 13 provided in the embodiment of the coin laundry store may be suitably adopted. An example of an unmanned physical store is a game center.

11 Building 12 Laundry equipment 13 Money exchange charge machine 2 Support server 3 Storage unit 4 Customer terminal 5 Equipment operation central management unit 6 Recipient terminal 7 Store terminal 7
9 Internet

Claims (15)

It is a physical store, not a virtual store on the Internet,
A charge amount transmitter and a payment permission information receiver are provided.
The charge amount transmitter is equipped with a customer ID acquisition unit that acquires a customer ID that identifies a customer who pays and deposits prepaid money at the physical store from a customer terminal that is carried by the customer without using a card. Prepaid money is money that a customer pays and deposits in advance for future payments at the physical store or another store managed by the same manager as the physical store.
The charge amount transmitter includes an input section into which the charge amount, which is the amount of prepaid money paid and deposited by the customer at the physical store, is input.
The charge amount transmitter is connected to the support server via the network, and the customer ID acquisition unit acquires information that enables the acquisition of the recipient ID of the recipient who receives the prepaid money at the physical store. The customer ID and charge amount entered from the input section are sent to the support server, and the charge amount is added for the customer ID and the recipient ID in the balance information file stored in the storage section on the support server, and the prepaid amount is It is a transmitter that performs the process of updating the balance of money, and the recipient ID is information that identifies the manager of each physical store, and if the manager is the same in multiple physical stores, the same ID is used. is the identification information given,
The payment authorization information receiver is equipped with a display and is connected to the support server via a network.
The payment permission information receiver transmits the store ID that identifies the physical store, the customer ID, and the payment amount to the support server from a terminal installed at the physical store or a customer terminal , and receives the prepaid money at the physical store. When the support server sends payment permission information to the payment permission information receiver when the balance of prepaid money for the recipient ID of the recipient and the customer ID is greater than the payment amount, the payment permission information is received and displayed. A physical store characterized by being a receiver that displays on. 2. The physical store according to claim 1, wherein a store terminal, which is a PC or a smartphone, is provided as the charge amount transmitter and the payment permission information receiver. The physical store is equipped with a payment permission application transmitter,
The payment permission application transmitter allows input of the payment amount, and specifies the entered payment amount, the store ID that identifies the physical store, and the recipient ID of the recipient who will receive the prepaid money at the physical store. a transmitter that transmits information that can be used to make a payment and a customer ID to the support server via a network and executes a payment permission determination program on the support server ;
When the store ID that identifies the physical store, customer ID, and payment amount are sent, the payment permission determination program on the support server determines the recipient ID and customer ID of the recipient who receives the prepaid money at the physical store. A program that transmits payment permission information to the payment permission information receiver when the balance of prepaid money for is equal to or greater than the payment amount,
The payment permission application transmitter is equipped with a customer ID acquisition unit that acquires the customer ID from a customer terminal that is carried by the customer without using a card, and when executing the payment permission determination program, the customer ID is acquired from a customer terminal that is carried by the customer. 3. The physical store according to claim 1, wherein the acquisition unit is a transmitter that transmits the acquired customer ID to the support server. 4. The physical store according to claim 3, wherein a store terminal, which is a PC or a smartphone, is provided as the payment permission application transmitter. A physical store payment support system that supports payment at a physical store that is not a virtual store on the Internet,
Equipped with a support server and a storage unit,
In the memory section,
A store information file that records information including a store ID that identifies each physical store and a recipient ID that identifies the recipient who receives the prepaid money at each physical store;
A customer information file that records customer information including a customer ID that identifies the customer;
A balance information file that records the balance of prepaid money paid by each customer in advance is recorded.
The balance information file is a file that records the balance of prepaid money for each recipient ID in the store information file for each customer,
The support server has
A charge amount recording program, a payment permission information transmission program, and a balance reduction program are implemented.
The charge amount recording program is information that enables the acquisition of the recipient ID of the recipient who receives prepaid money at the physical store where the charge amount transmitter is installed, from the charge amount transmitter installed in the physical store. , When the customer ID that identifies the customer who paid the prepaid money and the charge amount, which is the amount of the paid prepaid money, are sent to the support server, the customer ID is stored in the balance information file stored in the storage unit on the support server. and a program that updates the balance of prepaid money by adding the charge amount for the recipient ID,
When the store ID, customer ID, and payment amount are sent, the payment permission information transmission program transmits the recipient ID of the recipient who receives the prepaid money at the physical store specified by the store ID and the prepaid money for the customer ID. This is a program that sends payment permission information when the balance is greater than or equal to the payment amount.
Each physical store is equipped with a payment permission information receiver that receives payment permission information and displays it on a display.
The payment permission information sending program is a program that sends payment permission information to a payment permission information receiver installed in a physical store identified by a store ID,
A physical store payment support system characterized in that the balance reduction program is a program that subtracts the payment amount from the balance and updates the balance information file when the payment permission information transmission program transmits the payment permission information. It is possible to enter the payment amount at each physical store, and it is possible to transmit the store ID that identifies the physical store, the customer ID, and the entered payment amount to the support server via the network. A payment permission application transmitter is installed,
6. The physical store payment support system according to claim 5, wherein the payment permission information transmission program is a program executed when the store ID, customer ID, and payment amount are transmitted from the payment permission application transmitter. A payment history information file is recorded in the storage unit,
The payment permission information includes a customer ID of a customer who is permitted to make a payment,
The support server is equipped with a payment history recording program that records the payment permission information in a payment history information file when the payment permission information transmission program transmits the payment permission information,
When the support server is accessed from a recipient terminal, which is a terminal operated by the recipient, information regarding the recipient ID of the recipient from among the payment permission information recorded in the payment history information file is sent to the support server. Claim 5 or 6, characterized in that a payment history viewing page display program is implemented for allowing payment permission information to be viewed on a recipient terminal when payment is permitted for recorded prepaid money. Physical store payment support system. A coin laundry store that has multiple laundry machines installed in the store and allows customers who visit the store to use each laundry machine for a fee,
The laundry equipment includes an access information providing unit that provides access information that is input to a customer terminal, which is a mobile terminal brought by the customer, to connect the customer terminal to the support server via the network. and
The access information provided by the access information providing unit includes a store ID for identifying the coin laundry store where the laundry equipment equipped with the access information providing unit is installed, and a store ID for identifying the laundry equipment equipped with the access information providing unit. It includes the device ID of
Each laundry device is equipped with a signal input section into which a use permission signal transmitted from the support server is input, and the use permission signal is a signal that can start the operation of the laundry device,
The usage permission signal is the prepaid money received by the coin laundry store manager identified by the store ID included in the transmitted access information when the access information provided by the access information provision department is transmitted from the mobile terminal to the support server. A coin laundry store characterized in that the signal is input to the signal input section when the balance of the laundry machine is equal to or more than the usage fee for the laundry machine associated with the machine ID. There is a prepaid charge machine installed in the store that accepts prepaid money to pay for the use of the laundry equipment in advance.
The prepaid charge machine has a customer ID acquisition unit that acquires a customer ID that identifies the customer who pays the prepaid money, a charge amount acquisition unit that acquires the charge amount that is the amount of prepaid money that has been inserted, and a support server that sends prepaid information to the support server. It is equipped with a prepaid information transmitting section to transmit ,
The customer ID acquisition unit is an acquisition unit that acquires a customer ID from a customer terminal that is a terminal carried by the customer without using a card,
The prepaid information transmission unit sends the store ID that identifies the coin laundry store where the prepaid charge machine is installed, the customer ID acquired by the customer ID acquisition unit, and the charge amount acquired by the charge amount acquisition unit to the support server as prepaid information. It is a transmitter that sends data to
The usage permission signal transmitted from the support server and input to the signal input unit is received by a prepaid charge machine installed at a coin laundry store specified by the store ID included in the access information provided by the access information providing unit. In addition to prepaid money received at a prepaid charge machine installed at another coin laundry store owned by the same operator, if the balance exceeds the usage fee, a signal is input to the signal input section. The coin laundry store according to claim 8, characterized in that: 10. The coin laundry store according to claim 9, wherein the prepaid charge machine is a device that also functions as a money exchange machine. The access information providing unit is a providing unit that provides a two-dimensional code obtained by two-dimensionalizing the execution code of the program on the support server as access information , and this execution code includes the device ID and the store ID as arguments. 11. A coin laundry store according to any one of claims 8 to 10. A coin laundry store payment support system that supports payment of usage fees for laundry equipment in a coin laundry store where multiple laundry equipment is installed in the store and customers who visit the store are allowed to use each laundry equipment for a fee,
Equipped with a support server and a storage unit,
In the memory section,
A store information file that records information about each coin laundry store, including a store ID that identifies each coin laundry store;
A device information file that records information on each laundry device including a device ID that identifies each laundry device installed at each coin laundry store;
A customer information file that records customer information including a customer ID that identifies registered customers;
A balance information file that records the balance of prepaid money paid by each customer in advance is recorded.
The store information file records a recipient ID that identifies the recipient of the equipment usage fee at the coin laundry store.
The balance information file is a file that records the balance of prepaid money for each recipient ID in the store information file for each customer,
The support server has
A charge amount recording program, a payment permission information transmission program, and a balance reduction program are implemented.
When the charge amount recording program receives the customer ID, the store ID of the coin laundry store or the recipient ID of the recipient who is the manager of the coin laundry store and receives the prepaid money, and the charge amount, the program records the charge amount. It is a program that updates the balance of Propaid money by adding the charge amount to the ID and the recipient ID of the recipient at the store,
When the payment permission information transmission program receives the customer ID, store ID, and device ID from the mobile terminal operated by the customer, it acquires the recipient ID from the store information file according to the store ID, and sends information about the customer ID and the recipient ID. This is a program that sends payment permission information to enable the laundry equipment associated with the equipment ID to operate when the balance of prepaid money recorded in the balance information file is greater than or equal to the usage fee for the laundry equipment associated with the equipment ID. can be,
The balance reduction program is a program that, when the payment permission information sending program sends payment permission information, deducts the usage fee from the prepaid money balance recorded for the customer ID and recipient ID and updates the balance. A coin laundry store payment support system characterized by: The charge amount recording program collects the customer ID from the prepaid charge machine installed at the coin laundry store, the store ID of the coin laundry store, or the recipient ID of the recipient who is the manager of the laundry store and receives the prepaid money. and the charge amount , the program adds the charge amount to the customer ID and the recipient ID of the recipient at the store to update the balance of the propaid money. Coin laundry store payment system. A payment history information file is recorded in the storage unit,
The payment permission information includes a customer ID of a customer who is permitted to make a payment,
The support server is equipped with a payment history recording program that records the payment permission information in a payment history information file when the payment permission information transmission program transmits the payment permission information,
When the support server is accessed from a recipient terminal which is a terminal operated by the recipient, the payment permission information recorded in the payment history information file is recorded regarding the recipient ID. 14. The coin laundry store payment support according to claim 12 or 13, further comprising a payment history viewing page display program for viewing payment permission information on a recipient terminal when payment is permitted for prepaid money. system. A physical store payment application program downloaded to a customer terminal, which is a terminal operated by a customer, for accessing the support server in the physical store payment support system according to any one of claims 5 to 7,
It has a function of displaying on the customer terminal a store list page that lists the names of stores or store chains related to each recipient whose recipient ID is recorded in the balance information file,
Command button to pay prepaid money to the recipient of the store or store chain selected on the store list page, and use the prepaid money at the store selected on the store list page or any store in the store chain. A physical store payment application program characterized by having a function of displaying command buttons on a customer terminal to perform the transaction.

Images