Car wash management system

Abstract

To provide a method of managing a car washing charge that has means useful for avoidance of expiration of a monetary value deposited from a user to a car washing station operator.SOLUTION: A method of managing a car washing charge includes the steps of: generating monetary value data to identify a monetary value by being tied to a user each time the monetary value is deposited from the user to a car washing station operator in accordance with one declaration of intention of the user; generating time limit data to identify an expiration date of the monetary value for each individual monetary value data and combining it with the monetary value data; generating charge data to identify a charge billed to the user upon provision of car washing; and, if charge data is generated, selecting monetary value data having an expiration date arriving the earliest based on the time limit data as to the user, appropriating a charge identified by the charge data from a monetary value identified by selected monetary value data, and calculating a remaining amount of the monetary value and generating remaining value data to identify the remaining amount.SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] The present invention relates to a method for managing car wash fees, in which the fee charged to a user for providing a car wash is based on the monetary value deposited by the user with a car wash operator. [Background technology]

[0002] Patent Document 1 discloses a car wash reception system that uses a mobile phone terminal. Each time the electronic money in the mobile phone terminal is charged, a monetary value is deposited by the customer with the car wash operator. The charged amount is recorded in the mobile phone terminal. When performing a car wash, the mobile phone terminal is held up to a car wash reception device. The car wash reception device deducts the cost of the car wash from the electronic money in the mobile phone terminal. In this way, the cost of the car wash can be settled at the time of reception for the car wash. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent No. 5130124 Summary of the Invention [Problem to be solved by the invention]

[0004] In Patent Document 1, no expiration date is set for the electronic money in the mobile phone terminal. If an expiration date is set for the electronic money, which is a deposit, the obligation to make a deposit as stipulated in the Law on Settlement of Funds is waived, so that, for example, even if the asset size of the car wash operator is small, the car wash operator can introduce the car wash reception system described in Patent Document 1. In this way, the convenience for users can be improved by introducing electronic money. On the other hand, car wash operators are required to have a way to avoid the expiration of electronic money as much as possible. Otherwise, car wash users will feel a strong disadvantage of the loss of monetary value due to expiration, and will hesitate to use the car wash reception system.

[0005] The present invention aims to provide a method for managing car wash fees that is useful in avoiding the expiration of the monetary value deposited by a customer with a car wash operator. [Means for solving the problem]

[0006] According to a first aspect of the present invention, the present invention includes a step of generating monetary value data that is associated with a user and identifies the monetary value each time a monetary value is deposited by the user to a car wash operator in response to an expression of intent by the user, a step of generating expiration date data that identifies an expiration date of the monetary value for each of the monetary value data and combining the expiration date data with the monetary value data, a step of generating fee data that identifies a fee to be charged to the user for providing a car wash, and a step of selecting the monetary value data with the earliest expiration date for the user based on the expiration date data and calculating the amount of the fee data based on the amount of the fee data selected. A method for managing car wash fees is provided, comprising the steps of: allocating a fee specified by the fee data from the monetary value specified by the monetary value data, calculating a remaining amount of the monetary value, and generating first residual value data specifying the remaining amount; and, when the monetary value falls below the fee when allocating the fee, selecting the monetary value data for the expiration date that comes next for the user after the expiration date, allocating the shortfall in the fee specified by the fee data from the monetary value specified by the selected monetary value data, calculating the remaining amount of the monetary value, and generating second residual value data specifying the remaining amount.

[0007] According to a second aspect, in addition to the configuration of the first aspect, the method for managing car wash fees includes a step of comparing the expiration date specified in the expiration data with a predetermined expiration date to detect the expiration of the monetary value data, and a step of generating expired data that identifies the expired monetary value based on the monetary value contained in the expired monetary value data.

[0008] According to a third aspect, in addition to the configuration of the second aspect, the method of managing car wash fees includes a step of comparing the expiration date specified in the expiration data with a predetermined expiration date and excluding the expired monetary value data from the selection targets when applying the fee.

[0009] According to a fourth aspect, in addition to the configuration of any of the first to third aspects, the method of managing car wash fees includes a step of transmitting notification data to the user's terminal, the notification data identifying the earliest expiration date identified by the expiration date data and the numerical value of the monetary value linked to that expiration date and identified by the monetary value data. Effect of the Invention

[0010] According to the first aspect, the car wash operator can receive in advance from the user the monetary value to be applied to the car wash fee. Since the monetary value is applied to the car wash fee according to the chronological order of the expiration date, the deposited monetary value can be used as soon as possible before the expiration date. The expiration date of the monetary value can be avoided as much as possible.

[0011] According to the second aspect, out-of-date monetary values ​​can be easily calculated based on the out-of-date data.

[0012] According to the third aspect, when monetary value data is extracted for appropriation of a payment, the monetary value data to be searched can be narrowed down. The processing load on the processor during extraction can be reduced. Extraction can be performed quickly.

[0013] According to the fourth aspect, the expiration date and the value of the deposited monetary value can be displayed on the user's terminal based on the notification data. In this way, the user can be aware of the next expiration date and the value of the monetary value. The user can be aware of the expiration of the monetary value. [Brief description of the drawings]

[0014] [Figure 1]1 is a block diagram illustrating a schematic configuration of a car wash system according to a first embodiment of the present invention. [Diagram 2] FIG. 2 is a schematic diagram illustrating the structure of a prepaid payment database. [Diagram 3] 13 is an image showing a specific example of a QR code displayed on a display panel of a smartphone terminal. [Figure 4] 1A is a specific example of a guide image, (b) an image of options for deposit amounts, and (c) a “deposit confirmation” image, all of which are displayed on a display panel of a smartphone terminal. [Diagram 5] FIG. 13 is a conceptual diagram showing a specific example of value management data including rewritten “usage amount” data and “balance” data. [Figure 6] FIG. 13 is a conceptual diagram showing a specific example of value management data including "usage amount" data and "balance" data rewritten in ascending order of validity period. [Figure 7] FIG. 13 is a conceptual diagram showing a specific example of value management data including rewritten "expired amount" data. [Figure 8] 11 is an image showing a specific example of a transaction history displayed on a display panel of a smartphone terminal. [Figure 9] FIG. 6 is a block diagram illustrating a schematic configuration of a car wash system according to a second embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0015] Hereinafter, an embodiment of the present invention will be described with reference to the accompanying drawings.

[0016] FIG. 1 shows a schematic configuration of a car wash system 11 according to a first embodiment of the present invention. The car wash system 11 includes an ASP server 13 connected to the Internet 12 and operated by an ASP (Application Service Provider), an Internet terminal (hereinafter referred to as an "operator terminal") 15 connected to the Internet 12 and owned by an operator of car washes 14A, 14B, and 14C, an Internet terminal (user terminal) 16 connected to the Internet 12 and owned by a customer of the car wash, and a smartphone terminal (user terminal) 18 connected to a mobile phone communication network 17 and owned by a customer of the car wash. The operator terminal 15 is connected to the ASP server 13 via the Internet 12, for example, in response to the execution of an application program. The Internet terminal 16 is connected to the ASP server 13 via the Internet 12, for example, in response to the execution of an application program. The mobile phone communication network 17 is connected to the Internet 12, for example, through a gateway. The smartphone terminal 18 is connected to the ASP server 13 via the mobile phone communication network 17 and the Internet 12, for example, in response to the execution of a mobile application program. The ASP server 13 can issue a QR code that specifies the car wash operation for each of the car washes 19Aa, 19Ab, 19Ac, 19Ba, 19Bb, and 19Ca in response to a request provided by the Internet terminal 16 or the smartphone terminal 18. Each of the car washes 19Aa, 19Ab, 19Ac, 19Ba, 19Bb, and 19Ca performs the car wash according to the operation decoded from the QR code. The three car washes 19Aa, 19Ab, and 19Ac are installed, for example, in the AA car wash 14A. The two car washes 19Ba and 19Bb are installed, for example, in the BB car wash 14B. The one car wash 19Ca is installed, for example, in the CC car wash 14C. Here, the AA car wash 14A and the CC car wash 14C are operated by the XX company. The BB car wash 14B is operated by the YY company.

[0017] The ASP server 13 comprises a processor (CPU) 24 that functions as a reception means 21, a QR code issuing means 22, and a payment means 23, and a storage means 33 that is connected to the processor 24 and stores a server application program 25, a car wash reservation database 26, a car wash machine database 27, a membership database 28, a spot payment database 29, a prepaid payment database 31, and a monthly payment database 32. The storage means 33 can be formed from a large-capacity storage device such as a disk array device.

[0018] Event data specifying one car wash event (one car wash) to be performed at car washes 19Aa, 19Ab, 19Ac, 19Ba, 19Bb, and 19Ca is registered in car wash reservation database 26. As described below, one event data includes "operator ID" data, "store ID" data, "model ID" data, "car wash machine ID" data, "car wash course ID" data, "option ID" data, "equipment ID" data, "payment amount" data, "issue date and time" data, "issue serial ID" data, "member ID" data, and "member type" data.

[0019] The "operator ID" data identifies the operator (e.g., a corporation) that operates each individual car wash. The "operator ID" can be composed of, for example, alphanumeric characters. The "operator ID" can be assigned by the ASP to each operator. Each individual operator can be identified based on the "operator ID."

[0020] The "Store ID" data identifies each car wash (including gas stations). The "Store ID" can be composed of alphanumeric characters, for example. The "Store ID" can be assigned by the ASP to each store. Each car wash can be identified based on the "Store ID".

[0021] The "Model ID" data identifies the model of the car wash machine. The "Model ID" can be composed of, for example, alphanumeric characters. The "Model ID" can be assigned by the ASP for each model of car wash machine. Individual models can be identified based on the "Model ID".

[0022] The "Car Wash Machine ID" data specifies the machine number for each individual car wash machine. The "Car Wash Machine ID" can be composed of alphanumeric characters, for example. The "Car Wash Machine ID" can be assigned by the manufacturer of the car wash machine. A consecutive number may be assigned for each model identified by the "Model ID". In this case, the car wash identifier is formed by the combination of the "Model ID" and the "Car Wash Machine ID". Individual car washes can be identified based on the "Car Wash Machine ID".

[0023] The "Car Wash Course ID" data identifies the car wash courses that can be performed for each individual car wash machine. The "Car Wash Course ID" can be composed of a hexadecimal number, for example. Car wash courses are set uniquely for each individual car wash machine (or each model). Car wash operations are specified for each car wash course. Individual car wash courses can be identified based on the "Car Wash Course ID".

[0024] "Option ID" data is added to a car wash program for each individual car wash to identify the options that can be implemented. The "Option ID" can be configured, for example, as a hexadecimal number. Options are set, for example, uniquely for each individual car wash (or for each model). Additional actions are specified for each option. Individual options can be identified based on the "Option ID".

[0025] The "Equipment ID" data specifies whether or not a specified piece of equipment is equipped. The "Equipment ID" can be composed of, for example, hexadecimal numbers. Based on the "Equipment ID", it is possible to specify whether or not the vehicle has a "non-foldable door mirror", a "fender pole", a "roof protrusion" such as a carrier, a "front protrusion" such as a large fog lamp, a "rear protrusion" such as a rear mirror, or a "number plate offset to the left or right".

[0026] The "payment amount" data specifies the amount charged to the customer for the car wash. The "payment amount" may be composed of numbers, for example.

[0027] The "issue date and time" data specifies the issue date and time of the QR code. The "issue date and time" can be composed of half-width numbers that represent, for example, the four-digit year "YYYY", the four-digit month and day "MMDD", and the six-digit time "hhmmss".

[0028] The "Issued Serial ID" data identifies one car wash. The "Issued Serial ID" can be composed of a sequence number of a set number of digits. Individual car washes (car wash events) can be identified based on the "Issued Serial ID".

[0029] The "member ID" data identifies a user registered in the car wash system. The "member ID" can be composed of, for example, alphanumeric characters. The "member ID" can be assigned to each user by the ASP. Individual users can be identified based on the "member ID."

[0030] The "membership type" data specifies the type of user. The type of user can be classified, for example, into "spot member," "prepaid member," and "monthly member." Spot members pay for each car wash. Prepaid members deposit a specific amount of monetary value with the operator in advance. The cost of the car wash is deducted from the deposited monetary value each time the car is washed. Here, a prepaid member can purchase points worth 1,000 yen by paying, for example, 950 yen, points worth 2,000 yen by paying 1,800 yen, and points worth 5,000 yen by paying 4,250 yen. Monthly members can wash their cars an unlimited number of times by paying a set amount each month.

[0031] The car wash database 27 stores "store ID" data, "model ID" data, "car wash ID" data, "car wash course ID" data, "option ID" data, and "accessory ID" data for each car wash. The member database 28 stores "member ID" data and "member type" data for each user. The spot payment database 29 stores, for example, "member ID" data, "operator ID" data, "payment amount" data, and "issue date and time" data for each payment of a spot member. The "issue date and time" data corresponds to payment date and time data that specifies the date and time of payment. The prepaid payment database 31 stores value management data that specifies the balance of the monetary value deposited by the prepaid member to the operator for each deposit of monetary value. The value management data will be described in detail later. The monthly payment database 32 stores, for example, "member ID" data, "operator ID" data, and "registration date and time" data for each monthly member. The "registration date and time" data specifies the date and time when the monthly membership qualification was acquired. Monthly membership status can be automatically renewed every month based on the date and time of the "Registration Date and Time" data.

[0032] As shown in FIG. 2, each value management data 34 includes "number" data 34a, "member ID" data 34b, "operator ID" data 34c, "charge amount" data (monetary value data) 34d, "usage amount" data 34e, "balance" data (residual value data) 34f, "expired amount" data 34g, "reception number" data 34h, and "charge date and time" data 34j. "Number" data 34a specifies a management number for each deposit. "Number" can be composed of half-width alphanumeric characters, for example. "Number" can be assigned in sequence in the order of deposit. Here, "member ID" data 34b specifies the user who deposited the monetary value. "Member ID" data 34b can link the value management data 34 to corresponding data in the member database 28. Based on "member ID" data 34b, the value management data 34 can be sorted by user. "Operator ID" data 34c specifies the operator to which the deposit is made. The value management data 34 can be sorted by administrator based on the "administrator ID" data 34c.

[0033] The "charge amount" data 34d is associated with a user and specifies a monetary value (amount) each time the user deposits a monetary value to the operator in response to one of the user's expressions of intent. The "charge amount" can be composed of, for example, half-width numbers.

[0034] The "amount used" data 34e specifies the monetary value (amount) used to pay for the car wash within the monetary value specified by the "charge amount" data 34d. The "amount used" can be composed of, for example, half-width numbers.

[0035] The "balance" data 34f specifies the monetary value (amount) remaining after payment for the car wash within the monetary value specified by the "charge amount" data 34d. The "balance (residual value)" can be calculated for each individual value management data 34 by subtracting the "usage amount" data 34e from the "charge amount" data 34d. The "balance" can be composed of, for example, half-width numbers.

[0036] The "expired amount" data 34g specifies the monetary value (amount) after a predetermined period has elapsed since the date and time of deposit, within the monetary value specified by the "charge amount" data 34d. The "expired amount" corresponds to the "balance" specified when a predetermined period has elapsed since the date and time of deposit. The "expired amount" can be composed of, for example, half-width numbers.

[0037] The "receipt number" data 34h specifies a receipt number for each deposit. The "receipt number" can be composed of, for example, 10 half-width digits. The "receipt number" may be assigned randomly, regardless of the order of deposits.

[0038] The "charge date and time" data 34j specifies the date and time of the deposit. The "charge date and time" can be composed of half-width numbers expressing, for example, a four-digit year "YYYY", a two-digit month "MM", a two-digit day "DD", a two-digit hour "hh", and a two-digit minute "mm". The expiration date of the monetary value is calculated from the "charge date and time". The expiration date of the monetary value can be specified by adding a predetermined period to the "charge date and time". Here, for example, the predetermined period is set to "3 months". In this way, the "charge date and time" data 34j functions as expiration data.

[0039] When the server application program 25 is executed on the ASP server 13, a car wash management application runs on the ASP server 13. The car wash management application establishes the reception means 21, the QR code issuing means 22, and the payment means 23 in the processor 24. The reception means 21 is connected to the Internet terminal 16 and the smartphone terminal 18 via the Internet 12, and transmits and receives text data and image data between the Internet terminal 16 and the smartphone terminal 18. The QR code issuing means 22 generates event data based on the text data received by the reception means 21 and the car wash machine database 27 and the member database 28 stored in the storage means 33. The payment means 23 executes payment between the user and the operator for each individual car wash (car wash event). The payment means 23 accesses the spot payment database 29, the prepaid payment database 31, or the monthly payment database 32 to execute payment.

[0040] The QR code issuing means 22 issues one QR code for one piece of event data. Here, the following strings are encrypted into the QR code in the order of the number of characters determined for each: "operator ID", "store ID", "model ID", "car wash machine ID", "car wash course ID", "option ID", "accessory ID", "payment amount", "issue date and time", "issue serial ID", "member ID", and "member type". Thus, the QR code includes an identifier that identifies one car wash and specifies the car wash operation.

[0041] The operator terminal 15 comprises a processor (CPU) 36 that functions as a sales management means 35, a storage means 37 connected to the processor 36 for storing a sales management application program and other programs and data, a display panel 38 connected to the processor 36 for displaying images on a screen, and a user interface 39 connected to the processor 36 for inputting instructions and data from the operator to the processor 36. Here, the user interface 39 has a keyboard and a mouse. The processor 36 can be connected to the Internet 12 via a LAN board. The processor 36 is connected to the processor 24 of the ASP server 13 and transmits and receives data to and from the processor 24.

[0042] When the sales management application program is executed on operator terminal 15, a sales management application runs on operator terminal 15. The sales management application establishes sales management means 35 in processor 36. Sales management means 35 is connected to processor 24 of ASP server 13 via Internet 12, and transmits and receives text data and image data to and from processor 24. The operator can manage car wash sales based on spot payment database 29, prepaid payment database 31 and monthly payment database 32.

[0043] The smartphone terminal 18 includes a processor (arithmetic processing unit) 41 connected to the processor 24 of the ASP server 13 for transmitting and receiving data to and from the processor 24, a memory 44 connected to the processor 41 for storing a car wash reservation application program (mobile app program) 42, QR code image data 43, and other programs and data, a display panel 45 connected to the processor 41 for displaying images on a screen, and a user interface 46 connected to the processor 41 for inputting user instructions and data to the processor 41. Here, the user interface 46 has a touch screen panel that identifies the coordinate values ​​of a contact detected on the screen for each image. The touch screen panel inputs user instructions and data to the processor 41 based on the image displayed on the screen and the coordinate values ​​of a contact detected on the screen. The processor 41 can be wirelessly connected to the mobile phone communication network 17 via a communication circuit 47. In addition, the processor 41 can be wirelessly connected to a WiFi router via a WiFi (registered trademark) circuit (not shown). The WiFi router connects the WiFi circuit to the Internet 12.

[0044] Similarly, the Internet terminal 16 may include a CPU (Central Processing Unit) connected to the processor 24 of the ASP server 13 for transmitting and receiving data to and from the processor 24, a storage means connected to the CPU for storing the car wash reservation application program, image data of the QR code, and other programs and data, a display panel connected to the CPU for displaying images on a screen, and a user interface connected to the CPU for inputting user instructions and data to the CPU. Here, the user interface includes a keyboard and a mouse. The CPU can be connected to the Internet 12 via a LAN board.

[0045] A printer 48 can be connected to the Internet terminal 16. The printer 48 can print character strings and images on the surface of printing paper based on text data and image data. The text data and image data can be supplied to the printer 48 from the CPU, for example.

[0046] Each of the car washes 19Aa, 19Ab, 19Ac, 19Ba, 19Bb, and 19Ca includes a washing device 51 that washes a vehicle with water, and a reception device 52 that is connected to the washing device 51 and specifies the operation of the washing device 51 according to input instructions. In the washing device 51, for example, a top brush that washes the front and top of the vehicle, left and right side brushes that wash the left and right side surfaces of the vehicle, a top nozzle that blows air onto the front and top surfaces of the vehicle, and a side nozzle that blows air onto the left and right side surfaces of the vehicle are supported on a gate-shaped frame that straddles the vehicle and moves in the front-rear direction relative to the vehicle. Here, the structure of the washing device 51 is similar to that of a general car wash, and detailed description thereof will be omitted.

[0047] The reception device 52 includes a processor (MPU) 56 that functions as a reading means 53, a matching means 54, and a determination means 55, an imaging device (camera) 57 that is connected to the processor 56 and outputs an imaging signal based on an image formed on an imaging element, a storage means 62 that is connected to the processor 56 and stores a car wash reception program 58, a car wash reception database 59, and a car wash history database 61, a display panel 63 that is connected to the processor 56 and displays an image on a screen, and a user interface 64 that is connected to the processor 56 and inputs a user's instructions to the processor 56. An identifier that identifies one car wash is registered in the car wash reception database 59. Here, the "issued serial ID" data is used as the identifier. The "issued serial ID" data is extracted from event data that has been accepted for past car washes. The car wash history database 61 is registered with car wash history data that specifies the operation of the car wash machine for each car wash. The car wash history data can be created based on control signals for the top brush, side brush, top nozzle, and side nozzle, for example. The car wash history data is linked to a corresponding identifier in the car wash reception database 59.

[0048] When the car wash reception program 58 is executed in the reception device 52, a car wash reception application runs in the reception device 52. The car wash reception application operates to establish the reading means 53, the matching means 54, and the determination means 55 in the processor 56. The reading means 53 decodes the QR code based on the image capture signal output from the imaging device 57. The event data acquired by the decoding is temporarily stored in, for example, a memory (not shown).

[0049] The collation means 54 compares the "model ID" and "car wash machine ID" acquired by decrypting the QR code with the "model ID" and "car wash machine ID" stored in the machine. If the decrypted "model ID" and "car wash machine ID" match the "model ID" and "car wash machine ID" that identify the machine, the determination means 55 allows the car to be washed. If they do not match, the determination means 55 avoids the car wash. The determination means 55 displays a character string such as "This car wash machine cannot be used" on the screen of the display panel 63.

[0050] Next, the operation of the car wash system 11 will be described. When a user launches a car wash reservation application (hereinafter referred to as the "mobile app") by executing the car wash reservation application program 42 on the smartphone terminal 18, the user is prompted to enter a login ID and password. The mobile app is installed in the smartphone terminal 18 in advance. When the login ID and password are approved, the mobile app of the smartphone terminal 18 is connected to the car wash management application of the ASP server 13. In this way, encrypted communication is realized between the processor 41 of the smartphone terminal 18 and the processor 24 of the ASP server 13.

[0051] Depending on the member authentication, the QR code issuing means 22 of the ASP server 13 can recognize the "member ID" and "member type" based on the member database 28. Here, a mobile app is provided for each car wash 14A, 14B, 14C. The mobile app displays an image unique to each car wash 14A, 14B, 14C on the screen of the display panel 45. The mobile app transmits "store ID" data from the smartphone terminal 18 to the ASP server 13. Therefore, the QR code issuing means 22 of the ASP server 13 can identify the "operator ID" and "store ID" based on the car wash database 27. The target car washes can be narrowed down based on the "store ID".

[0052] The user is prompted to select a car wash machine. The reception means 21 transmits image data (and text data) identifying the selected car wash machine to the processor 41. Images of the options are displayed on the screen of the display panel 45. The user selects one car wash machine based on the image. The selection is input based on the operation of the user interface 46. The selection of the car wash machine is transmitted to the reception means 21 of the ASP server 13. Based on the selection, the QR code issuing means 22 of the ASP server 13 can identify the "model ID" and "car wash ID".

[0053] Once the car wash machine is decided, the reception means 21 identifies the "car wash course ID" and "option ID" assigned to the car wash machine based on the car wash machine database 27. The reception means 21 transmits image data (and text data) identifying the selected car wash course and image data (and text data) identifying the selected option to the processor 41. The "car wash course" options and "option" options are displayed on the screen of the display panel 45. The user selects one "car wash course" and "option" based on the image. The selection is input based on the operation of the user interface 46. In this way, the QR code issuing means 22 of the ASP server 13 can identify the "car wash course ID" and "option ID".

[0054] The reception means 21 identifies the "equipment ID" associated with the car wash machine based on the car wash machine database 27. The reception means 21 transmits image data (and text data) identifying the equipment to the processor 41. An option of equipment is displayed on the screen of the display panel 45. The user selects the relevant equipment based on the image. The selection is input based on the operation of the user interface 46. In this way, the QR code issuing means 22 of the ASP server 13 can identify the "equipment ID".

[0055] The reception means 21 transmits image data specifying a confirmation screen for the car wash event to the processor 41. An image of "Content confirmation" is displayed on the screen of the display panel 45. When the car wash event is approved based on the operation of the user interface 46, the reception means 21 executes the payment procedure. When the payment is completed, the QR code issuing means 22 registers the event data in the car wash reservation database 26. In response to the establishment of the event data, the QR code issuing means 22 issues a QR code. The image data of the issued QR code is transmitted to the processor 41. The image data 43 of the QR code is stored in the memory 44 of the smartphone terminal 18. Here, the image data 43 of the QR code is overwritten. When a new QR code is issued on one smartphone terminal 18, the old QR code is erased. As shown in FIG. 3, the QR code 65 can be displayed on the screen of the display panel 45.

[0056] To have the car washed, the user drives up to the designated car wash. At this time, the user brings the smartphone terminal 18 with them. If a reservation for a car wash has been made via the internet terminal 16, the user simply brings with them a QR code printed out by the printer 48. The QR code 65 displayed on the screen is held up to the imaging device 57 of the reception device 52. The reading means 53 decodes the QR code 65 from the image signal from the imaging device 57. The event data is restored. The event data is temporarily stored in memory.

[0057] The matching means 54 compares the "model ID" and "car wash ID" (car wash identifier) ​​acquired by decryption with the machine's own "model ID" and "car wash ID" (car wash identifier that identifies the machine). If the car wash identifier acquired by decryption matches the car wash identifier that identifies the machine, the determination means 55 allows the car to be washed. If they do not match, the reception device 52 notifies the user that the car cannot be washed. The display panel 63 of the reception device 52 displays the text "This car wash cannot be used" on the screen.

[0058] When the car wash is permitted, the reception device 52 displays a "content confirmation" image on the screen of the display panel 63. When the contents of the car wash event are approved in response to the operation of the user interface 64, the car wash begins. The reception device 52 extracts the "issued serial ID" from the event data. The "issued serial ID" is registered in the car wash reception database 59. The operation of the car wash machine 19Aa is registered in the car wash history database 61 as car wash history data. Here, the car wash history data is linked to the registered "issued serial ID". In this way, the event data can be verified based on the actual car wash history. If the car wash is stopped midway, the corresponding "issued serial ID" is deleted from the car wash reception database 59. In this way, the same QR code 65 can be used again if the car wash is incomplete.

[0059] Users are classified into "spot members," "prepaid members," and "monthly members" based on the "membership type" data in the member database. Spot members can use a credit card, for example, to make payments. The screen of display panel 45 prompts the user to enter "card number," "expiration date," "name," and "security code." Using user interface 46, spot members can send the text data of "card number," "expiration date," "name," and "security code" to the payment company. The text data of "card number," "expiration date," "name," and "security code" may be registered in advance in member database 28 as member information. With approval from the payment company, spot members can pay for the car wash.

[0060] A prepaid member deposits a predetermined amount of monetary value with the operator in advance. When the mobile application is started, the payment means 23 of the ASP server 13 identifies the value management data 34 specific to the "member ID" from the prepaid payment database 31 based on the "member ID" data 34b in response to the member's authentication. The reception means 21 generates image data (and text data) specifying a guide for the prepaid member based on the identified value management data 34. The generated image data (and text data) is transmitted to the processor 41 of the smartphone terminal 18 as notification data. The image data (and text data) includes "total balance" data specifying the total balance, "expiration" data specifying the earliest expiration date among the value management data specific to the "member ID", "expiration balance" data linked to the expiration date and specifying the "balance" data, image data specifying a "charge +" button, and image data specifying a "charge transaction history" button. As shown in FIG. 4(a), a guide image 66 is displayed on the screen of the display panel 45. The guide image 66 includes a character string 67 specifying the numerical value of the “Total Balance”, a character string 68 specifying the date of the “Expiration Date”, a character string 69 specifying the numerical value of the “Expiration Balance”, a “Charge +” button 71, and a “Charge Transaction History” button 72.

[0061] When calculating the "total balance" data, the payment means 23 identifies the value management data 34 that is within the expiration date based on the "charge date and time" data 34j. For example, when prepaid member "taro_1357" logs in on June 1, 2020, the payment means 23 calculates the "total balance" data based on the "balance" data 34f of "000000002" and the "balance" data 34f of "000000004". The "balance" data 34f of "000000001", which is three months after the "charge date and time" data 34j, is not included. "4,000 yen" is identified as the "total balance" data.

[0062] At this time, the payment means 23 extracts the "expiration date" data 34j that identifies the earliest expiration date from the value management data 34 that is within the expiration date. If the prepaid member "taro_1357" logs in on June 1, 2020, the payment means 23 can identify the "balance" data 34f of "000000002". In this way, the "expiration date" data and the "expiration balance" data can be obtained.

[0063] To deposit monetary value, the prepaid member taps, for example, the "Charge +" button 71 on the guide image 66. When the "Charge +" button 71 is tapped, a request signal is sent from the processor 41 of the smartphone terminal 18 to the reception means 21 of the ASP server 13. The reception means 21 transmits image data (and text data) specifying options for the amount to be deposited to the processor 41. As shown in FIG. 4(b), images of the options are displayed on the screen of the display panel 45. Here, the images of the options include a "1000 yen" button 73a, a "2000 yen" button 73b, a "3000 yen" button 73c, and a "5000 yen" button 73d.

[0064] Based on the image, the user selects one of the amount buttons (for example, the "5000 yen" button 73d). The selection is input based on the operation of the user interface 46. The selection of the amount button is sent to the reception means 21 of the ASP server 13. The reception means 21 generates image data specifying a deposit confirmation screen in response to the selection of the amount button. The image data of the confirmation screen is sent from the reception means 21 to the processor 41. As shown in Figure 4 (c), an image 74 of "deposit confirmation" is displayed on the screen of the display panel 45. When the "charge" button 75 is tapped and the deposit is approved, the payment means 23 carries out the payment. A prepaid member can use, for example, a credit card to make the payment.

[0065] At this time, the payment means 23 generates one piece of value management data 34 in the prepaid payment database 31 according to the selected amount. For example, as identified by the number "000000006" in Fig. 2, the selected amount is registered in the "charge amount" data 34d in the generated value management data 34. Since the "usage amount" data 34e is "0 (zero)", the amount of the "charge amount" data 34d is reflected as is in the "balance" data 34f. When generating the value management data 34, the payment means 23 combines the "charge amount" data 34d with the "charge date and time" data 34j.

[0066] When issuing the QR code, the payment means 23 generates payment data specifying the fee to be charged to the user. The payment data can be calculated, for example, based on the "car wash course ID" data and the "option ID" data. For example, when the prepaid member "tanatana" pays a fee of 2000 yen, as shown in FIG. 5, the payment means 23 rewrites the "usage amount" data 34e to "2000" in the value management data 34 with the number "000000006". The "balance" data 34f is rewritten to "3000". In this way, the prepaid member can pay for the car wash.

[0067] When the prepaid member "takashi" pays the charge of 2000 yen, the settlement means 23 selects the value management data 34 with the earliest expiration date for the prepaid member "takashi" based on the expiration date data, appropriates the charge specified by the charge data from the "charge amount" specified by the selected value management data 34, calculates the remaining amount of the "charge amount", and generates "balance" data 34f that specifies the remaining amount. In the value management data 34, "2000" is added to the "usage amount" data 34e. Here, although the value management data 34 of "000000003" is selected based on the expiration date data, the "usage amount" data 34e exceeds the "charge amount" data 34d. In other words, the "balance" data 34f is less than the charge when the charge is appropriated, so there is a shortage in the "charge amount". As shown in FIG. 6, the "usage amount" data 34e of "000000003" is rewritten to "3000". The "Balance" data 34f of "000000003" is rewritten to "0 (zero)."

[0068] When a shortfall occurs in this way, the settlement means 23 selects the value management data 34 with the expiration date that comes next after the expiration date of the selected value management data 34, applies the shortfall in the price specified by the price data from the "charge amount" specified by the selected value management data 34, calculates the remaining "charge amount", and generates "balance" data 34f that specifies the remaining amount. Here, as shown in Figure 6, the "usage amount" data 34e of "000000005" is rewritten to the shortfall in the price, "1000". The "balance" data 34f of "000000005" is rewritten to "2000".

[0069] The payment means 23 checks the expiration date specified by the expiration data against a predetermined expiration date to detect the expiration of the "charge amount" data 34d. In the detection, the value management data 34 is extracted based on the "charge date and time" data 34j. When expired "charge amount" data 34d is detected, the payment means 23 generates expiration data that specifies the expired monetary value. The expiration data corresponds to "balance" data 34f that is specified by the expiration date and time. The payment means 23 transcribes the "balance" data 34f to "expiration amount" data 34g, as shown in FIG. 7.

[0070] A prepaid member can check the transaction history on the smartphone terminal 18. To check the history, the prepaid member taps, for example, the "charge transaction history" button 72 on the guide image 66. When the "charge transaction history" button 72 is tapped, a request signal is sent from the processor 41 of the smartphone terminal 18 to the reception means 21 of the ASP server 13. The reception means 21 sends image data (and text data) specifying the transaction history to the processor 41. As shown in FIG. 8, an image 76 of the transaction history is displayed on the screen of the display panel 45. The image can include, like the guide image 66, a character string 77 specifying the numerical value of the "total balance", a character string 78 specifying the date of the "expiration date", a character string 79 specifying the numerical value of the "expiration balance", and a "charge" button 81. The "charge" button 81 can function like the "charge +" button 71 on the guide image 66.

[0071] The transaction history image 76 includes a character string 82 that identifies the "transaction name" and a character string 83 that identifies the numerical value of the "transaction amount" according to a predetermined composition. The image is set according to the "transaction name." Here, the "transaction name" is classified, for example, into "charge," "payment," and "expiration." A character string 84 that identifies the charge date and time and a character string 85 that identifies the expiration date are added to "charge." A character string 86 that identifies the payment date and time are added to "payment." A character string 87 that identifies the expiration date and time are added to "expiration." In the case of an increase, the character string "+" is added to the beginning of the "transaction amount." In the case of a decrease, the character string "-" is added to the beginning of the "transaction amount."

[0072] Monthly members can use, for example, a credit card to make payments. The screen of display panel 45 prompts them to enter their "card number," "expiration date," "name," and "security code." Using user interface 46, monthly members can send text data of "card number," "expiration date," "name," and "security code" to the payment company. The text data of "card number," "expiration date," "name," and "security code" may be registered in advance in member database 28 as member information. With approval from the payment company, monthly members can pay their monthly membership fee. Membership fee payments may be automatically renewed every month.

[0073] In this embodiment, the operator of the car wash can receive in advance from the user (prepaid member) the monetary value to be used for the car wash fee. Since the monetary value is appropriated for the car wash fee according to the chronological order of the expiration date, the deposited monetary value can be used as soon as possible before the expiration date. The expiration date of the monetary value can be avoided as much as possible.

[0074] The payment means 23 according to this embodiment checks the expiration date and time specified in the "charge date and time" data 34j against a predetermined expiration date and detects the expiration of the "balance" data 34f. When the expiration is detected, the payment means 23 generates "expired amount" data 34g that specifies the expired monetary value based on the monetary value included in the expired "charge amount" data 34d (monetary value specified in the "balance" data 34f). The expired monetary value can be easily calculated based on the "expired amount" data 34g.

[0075] The settlement means 23 checks the expiration date specified by the "charge date and time" data 34j against a predetermined expiration date, and excludes expired "balance" data 34f from the selection targets when applying the payment. When value management data 34 is extracted when applying the payment, the value management data 34 to be searched can be narrowed down. The processing load on the processor 24 during extraction can be reduced. Extraction can be speeded up.

[0076] In this embodiment, the reception means 21 transmits notification data to the smartphone terminal 18, which specifies the earliest expiration date specified by the "charge date and time" data 34j, and the numerical value of the monetary value linked to the expiration date and specified by the "balance" data 34f. The expiration date and numerical value of the deposited monetary value can be displayed on the user's terminal based on the notification data. In this way, the user can be aware of the next expiration date and the numerical value of the monetary value. The user can be aware of the expiration of the monetary value.

[0077] In addition, when generating the fee data, the payment means 23 can set the unit price of the "car wash course" and "option" for each "spot member", "prepaid member" and "monthly member". Here, a unit price table is stored in the storage means 38. The unit price table is linked to the car wash machine database 27 for each individual car wash machine, for example. In the unit price table, the unit price of the "car wash course" and "option" are described for each "spot member", "prepaid member" and "monthly member". When the "model ID", "car wash machine ID", "car wash course ID", "option ID" and "membership type" are specified in the event data, the "payment amount" can be specified for each event data. By setting the unit price for each "membership type" in this way, the unit price of the "car wash course" and "option" for the "spot member" can be set higher than that for the "prepaid member".

[0078] In this embodiment, "expiration date" data may be further set (added) to the event data. The "expiration date" data specifies the expiration date of the QR code. The "expiration date" may be composed of half-width numbers expressing, for example, the four-digit year "YYYY", the four-digit month and day "MMDD", and the six-digit time "hhmmss". The "expiration date" may be arbitrarily set, for example, between 1 and 30 days from the "issue date and time". In addition, when the "expiration date" is set to inactive, the "expiration date" data may be set to a value of "0 (zero)".

[0079] The event data may further include "unsettled flag" data. The "unsettled flag" data specifies whether or not the payment has been completed. For example, if the payment has been completed, a "0 (zero)" value is written to the "unsettled flag" data. If the payment has not been completed, a "1" value is written to the "unsettled flag" data. When issuing a QR code, the QR code issuing means 22 of the ASP server 13 determines whether or not the payment procedure has been completed. When the "unsettled flag" is established, an image for selecting whether or not the payment has been made may be displayed on the screen of the display panel 45 of the smartphone terminal 18 of the spot member in response to the operation of the mobile app. Payment or unsettled can be selected in response to the operation of the user interface 46. When the reception device 52 of the car wash confirms "payment" in the event data in response to decoding the QR code 65, the car wash starts as is. When the event data confirms "unsettled", the reception device 52 displays an image on the screen of the display panel 63 that prompts the user to make a cash payment. The user can make the payment by inserting cash into the reception device 52. Once the cash payment is confirmed by the reception device 52, the car wash begins.

[0080] A mobile app may be provided for each individual operator (XX Company or YY Company). In this case, the mobile app, for example, prompts the user to select a car wash before selecting a car wash machine. The reception means 21 of the ASP server 13 transmits image data (and text data) identifying the selected car washes to the processor 41. Images of the options are displayed on the screen of the display panel 45. The user selects one car wash based on the image. The selection is input based on the operation of the user interface 46. The selection of the car wash is transmitted to the reception means 21. Based on the selection, the QR code issuing means 22 of the ASP server 13 can identify the "operator ID" and "store ID". The target car washes can be narrowed down based on the "store ID".

[0081] FIG. 9 shows a schematic configuration of the car wash system 11a according to the second embodiment of the present invention. Here, each reception device 52 is connected to the ASP server 13 via the Internet 12. The reception device 52 is supplied with event data registered in the car wash reservation database 26 from the ASP server 13. In response to the supply of the event data, at least the "issued serial ID" data is stored in the storage means 62. The reception device 52 only needs to be supplied with the event data corresponding to the "model ID" and the "car wash machine ID". The reception device 52 checks the "issued serial ID" data supplied from the ASP server 13 against the "issued serial ID" data obtained by decoding the QR code. If any one of the "issued serial ID" data supplied from the ASP server 13 matches the "issued serial ID" data obtained by decoding the QR code, the determination means 45 permits the car wash. At this time, the reception device 52 can erase the "issued serial ID" data supplied from the ASP server 13. When the car wash is completed, the reception device 52 can notify the ASP server 13 of the completion of the car wash. In this way, the ASP server 13 can carry out the payment process after the car wash is completed.

[0082] If the "issued serial ID" data obtained by decoding the QR code does not match any one of the "issued serial ID" data supplied from the ASP server 13, the determination means 45 will avoid washing the car. The determination means 45 will display a character string such as "This car wash machine cannot handle this product" on the screen of the display panel 53. [Explanation of symbols]

[0083] 34d...monetary value data ("charge amount" data), 34f...first residual value data and second residual value data ("balance" data), 34g...expiration data ("expiration amount" data), 34j...expiration data ("charge date and time" data).

Claims

[Claim 1] generating monetary value data that is associated with the user and identifies the monetary value each time the user deposits a monetary value to the car wash operator in response to an expression of intent by the user; generating expiration data for each of the monetary value data, the expiration data specifying an expiration date of the monetary value, and combining the expiration data with the monetary value data; generating fee data specifying a fee to be charged to the user for providing the car wash; When the payment data is generated, a step of selecting the monetary value data with the earliest expiration date based on the term data for the user, allocating the payment specified by the payment data from the monetary value specified by the selected monetary value data, calculating the remaining amount of the monetary value, and generating first remaining value data specifying the remaining amount; a step of, when the monetary value falls below the price at the time of appropriation of the price, selecting the monetary value data of the expiration date coming next after the said expiration date for the user, appropriating the shortfall of the price specified by the price data from the monetary value specified by the selected monetary value data, calculating the remaining amount of the monetary value, and generating second remaining value data specifying the remaining amount; A method for managing car wash fees, comprising:

Images