Customer terminal and computer program

Abstract

To provide a technique for guiding a customer who uses either a store tag 13 or a two-dimensional bar code 11 to make an electronic payment to a payment using the store tag 13.SOLUTION: A store ID tag 1 including a two-dimensional barcode 11 and a store tag 13 is placed in a store. When making a payment to the store, a customer captures an image of the two-dimensional barcode 11 with a customer terminal 2, or brings the customer terminal 2 close to the store tag 13. According to the former case, the customer terminal 2 acquires store ID data embedded in the two-dimensional barcode 11. According to the latter case, the store tag 13 and the customer terminal 2 perform RFID communication with each other, and the store ID data is transmitted to the customer terminal 2. The customer terminal 2 transmits route data indicating a route through which the store ID was obtained to a payment device to make the payment.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to electronic payment technology.

Background Art

[0002] Although various electronic payment technologies as technologies for settling payments from customers to stores have been widespread for a long time, there is a payment system using barcodes such as QR codes (trademark) and other two-dimensional barcodes or one-dimensional barcodes among them. Among the payment systems using barcodes, there are a type in which the store side reads the barcode displayed on the display of the customer's smartphone and conducts payment, and a type in which the user's smartphone reads the barcode posted in the store and conducts payment. In the present application, the following discussion will focus on the latter.

[0003] The payment system as described above is generally configured as follows. The payment system includes a payment device. The payment device is generally constituted by a server device. Payment data described later is sent from the customer's smartphone to the payment device. The payment data is data including three pieces of data for specifying who pays, to whom, and how much. By receiving the payment data, the payment device settles the payment from the customer to the store. The payment method executed by the payment device can be appropriately selected. For example, it is possible to adopt a prepayment payment means premised on the prepayment of the customer stipulated by the law regarding the settlement of funds in Japan, a debit settlement premised on immediate settlement, or a credit settlement premised on post-payment. The following description will proceed by taking the case where the payment device is a prepayment payment means payment device as an example. As described above, the payment device is generally composed of a server device. The payment device includes a balance database which is a database. In the balance database, a store ID which is information for identifying an account (an account in the context of a bank) for a store to receive payments, and a customer ID which is information for identifying a customer (or an account (an account in the context of a bank) for a customer to make payments) are recorded. In the balance database, information on the balance of the account associated with the store ID, and information on the balance of the customer associated with the customer ID are also recorded. The payment device also includes a balance section having a function of updating data on the balance database. Payment data is sent to the payment device from a customer, more specifically from a customer terminal (mostly a smartphone in most cases) that the customer possesses. As described above, the payment data is data for identifying who pays how much to whom. The payment data includes customer ID data which is data of the customer ID for identifying the payer, store ID data which is data of the store ID for identifying the payee, and amount data for identifying the payment amount. When these three pieces of data are complete, the details of the payment can be determined. When receiving the payment data, the balance section decreases the balance associated with the customer ID specified by the customer ID data included in the payment data by the payment amount specified by the amount data in the balance database, and increases the balance associated with the store ID specified by the store ID data included in the payment data by the payment amount specified by the amount data in the balance database. In this way, by balancing the balance of the customer and the balance of the store, the payment device executes the payment.

[0004] In order for the customer to send payment data from the customer terminal, it is necessary to generate the payment data on the customer terminal. Currently, for example, it is executed as follows. Let's assume the customer terminal is a smartphone and continue the discussion. The store displays a barcode that contains the store ID as information. In many cases, the barcode is printed on paper and displayed near the register device where payment is made. The customer who wants to make a payment first touches the icon of the payment computer program (so-called app) displayed on the display of their smartphone. Then, a start image is displayed. The start image has a button for activating the camera. The customer touches the button to activate the camera installed in the smartphone. The customer takes a picture of the barcode displayed in the store with the smartphone camera. Then, image data for the image including the barcode is generated in the smartphone. The smartphone extracts the data about the store ID embedded in the barcode, that is, the store ID data, from the image data. When the customer takes a picture of the barcode with the smartphone camera, an amount input image, which is a screen prompting the customer to enter the payment amount, is displayed on the smartphone display. The amount input image is, for example, a screen that displays a horizontally long rectangular input frame under the text "Please enter the payment amount". The customer enters the payment amount in the frame. The customer shows the amount input image with the payment amount entered in the frame to the store clerk. If the payment amount displayed in the frame is incorrect, the clerk asks the customer to correct the input and conveys to the customer the intention that it is okay if it is correct. When it is determined that the amount entered in the frame of the amount input image is correct as the payment amount, the customer touches a button for indicating the intention to execute the payment displayed on the amount input image, for example, a button with text such as "Confirm" or "Pay". Then, payment data including customer ID data, store ID data, and amount data is generated. As described above, the smartphone extracts the store ID data from the barcode. The customer ID data is initially recorded in the recording device built into the smartphone. Also, the data regarding the amount entered in the amount input image becomes the amount data. Therefore, the smartphone can generate payment data by combining these three pieces of data. The payment data is sent from the customer's smartphone to the payment device via a network, such as the Internet or the carrier line of the mobile phone company that provides the smartphone. Thereby, the payment device that has received the payment data executes the payment as described above.

Summary of the Invention

Problems to be Solved by the Invention

[0005] The flow of payment executed using the electronic payment system using a barcode is as described above. The electronic payment system as described above is generally used conveniently by many customers. However, there are also points to be improved in the electronic payment system as described above. First, there are some inconveniences in the electronic payment system as described above. Customers who feel that the electronic payment system as described above is inconvenient are mainly elderly people, although not limited to this. Elderly people often have difficulty finding the icon of the payment computer program among the many icons displayed on the top screen of the smartphone. Also, even if they can find the icon and launch the payment computer program, many elderly people have difficulty launching the camera. Also, even if they succeed in launching the camera, when the customer is an elderly person, situations such as not being able to tell whether the front camera or the rear camera of the smartphone has been launched frequently occur. Even when the camera is turned on, some customers have difficulty getting the camera to capture the barcode by positioning the barcode within the camera's imaging range. There is also a high likelihood that barcode imaging will fail when customers are unable to determine whether the in-camera or out-camera is activated. Due to these various circumstances, customers who are not proficient in operating smartphones, typically older customers, often encounter difficulties in the process of reaching the money input image. This causes inconvenience in the operability of the electronic payment system.

[0006] In addition, electronic payment systems using barcodes also have security issues. The easiest fraud committed by a malicious third party against security issues is to place a fake barcode in the store. When committing fraud, the malicious third party posts a barcode containing an ID (fraudulent ID), which is information for identifying the account for receiving payment, near the store's register device. The barcode containing the fraudulent ID is usually printed on paper, but since printing a barcode on paper is possible without special equipment, it is easy to post a fake barcode in the store. Then, the payment made by a customer who has imaged the fake barcode with their smartphone camera will be made not to the store ID but to the fraudulent ID. As a result, the malicious third party can receive the money paid by the customer instead of the store. In addition, there are also prevalent tactics such as using fake barcodes to lure customers to illegal websites on the Internet, getting customers to input their personal information, or stealing personal information, financial institution IDs, and passwords recorded on smartphones.

[0007] In view of the above points, the above-described electronic payment system should be improved so as not to use barcodes. However, it would be too harsh on customers who are already accustomed to the electronic payment system using barcodes to suddenly stop using all such systems at a certain point in time and switch to an electronic payment system that does not use barcodes, and there is also a risk that it may not be accepted by customers. The main object of the present invention is to provide a technology for smoothly changing the system when replacing an electronic payment system using barcodes with an electronic payment system that does not use barcodes, and a further object is to provide a technology that enables customers to be encouraged to use an electronic payment system that does not use barcodes.

Means for Solving the Problems

[0008] The present invention is arranged in a store having a store ID for receiving payment, which conducts retail sales to customers having a customer ID for making payments, and includes a store tag including a memory recording store ID data which is data for specifying the store ID, and a transmitter for wirelessly transmitting the store ID data recorded in the memory to perform short-range communication, and a barcode enclosing information corresponding to the store ID specified by the store ID data recorded in the memory of the paired store tag, and a settlement device for settling the payment made by the customer to the store, and is a customer terminal which the customer is expected to possess. This customer terminal includes a recording device recording customer ID data which is data for specifying the customer ID, a receiver capable of receiving the store ID data from the transmitter of the store tag, a transceiver mechanism for transmitting data via a network, a display having a function of displaying an image, a camera for performing imaging and generating image data which is data about the imaged image, an input device into which amount data which is data for specifying the payment amount which is the amount the customer pays to the store can be input, and a control unit for executing information processing. When the customer brings the customer terminal closer to the store tag than a predetermined distance, the control unit receives the store ID data from the receiver that has received the store ID data from the transmitter of the store tag, and automatically, when the store ID data is received, causes the display to display a first amount input image, which is an image prompting the customer to input the payment amount. When the customer captures the barcode with the camera, the control unit receives image data of an image including the barcode generated by the camera from the camera, reads out the store ID data encapsulated in the barcode included in the image specified by the image data, and automatically, when the store ID data is read out, causes the display to display a second amount input image, which is an image prompting the customer to input the payment amount. When the control unit receives the amount data input by the customer by inputting the payment amount into the first amount input image or the second amount input image displayed on the display using the input device, the control unit associates the store ID data received from the store tag or read from the barcode, the customer ID data read from the recording device, the amount data input from the input device, and route data indicating whether the amount data is input from the first amount input image or the second amount input image with each other as payment data, which is information necessary to specify the payment from the customer to the store, and transmits the payment data from the transceiver to the settlement device via the network.

[0009] The settlement system described in the background art section was composed of a barcode arranged in a store, a customer terminal, and a settlement device. On the other hand, the settlement system including the customer terminal in the present invention includes a customer terminal and a settlement device, but what is arranged in the store is not only a barcode but also a barcode and a store tag. The customer terminal in the present invention is typically a smartphone held by a customer, similar to the case of the settlement system described in the background art section. Even in the payment system including the customer terminal in the present application, the customer terminal needs to obtain store ID data prior to generating payment data. The customer terminal described in the background art section obtained the store ID by imaging a barcode with a camera, but the customer terminal in the present application obtains the store ID data by wireless communication with a store tag or by imaging a barcode with a camera. As a result, the customer terminal in the present invention can generate payment data including the three data described in the background art section, namely, store ID data, customer ID data, and amount data, similar to the customer terminal (smartphone) described in the background art section. However, the payment data generated by the customer terminal according to the present application includes route data, as will be described later. Therefore, the payment data received by the payment device from the customer terminal includes route data (or route data is added) in addition to the store ID data, customer ID data, and amount data.

[0010] The customer terminal according to the present application includes a recording device that records customer ID data which is data for specifying customer ID data, a receiver that is capable of receiving store ID data from a transmitter of a store tag, a transceiver mechanism that transmits data via a network, a display having a function of displaying an image, a camera that performs imaging and generates image data which is data about the captured image, an input device into which amount data which is data for specifying the payment amount that the customer pays to the store can be input, and a control unit that executes information processing. All of these can be said to be what a general smartphone has. Examples of the recording device are a memory or a mass storage device. An example of the receiver is a device for performing short-range communication with the transmitter of the store tag. As technologies applicable to the store tag and the receiver, RFID (radio frequency identification) and NFC (near field communication) are known or well-known. A transmission / reception mechanism capable of communication via the Internet, a carrier line, or other networks is so well-known or well-known that there is no need to explain it in the field of smartphones applicable to customer terminals. An example of the display is a liquid crystal display or an organic EL (electro-luminescence) display. An example of the input device is, for example, a touch panel type display. An example of the control unit is an arithmetic unit. Examples of the arithmetic unit are a CPU (central processing unit), a GPU (graphics processing unit), and a GPGPU (general purpose computing on GPU). The control unit may be configured to exhibit the functions described below by the functions of a computer program described later recorded in the recording device.

[0011] When the customer brings the customer terminal closer to the store tag than a predetermined distance, the control unit receives store ID data from the receiver that has received the store ID data from the transmitter of the store tag, and automatically displays on the display a first amount input image, which is an image prompting the customer to input the payment amount. When the customer captures a barcode with the camera, the control unit receives image data of the image including the barcode generated by the camera, reads the store ID data encapsulated in the barcode included in the image specified by the image data, and automatically displays on the display a second amount input image, which is an image prompting the customer to input the payment amount. The customer terminal of the present invention obtains the store ID data by wireless communication with the store tag or by capturing a barcode with the camera. And regardless of which path is used to obtain the store ID data, the control unit causes the display to display either the first amount input image or the second amount input image, both of which are images prompting the customer to input the payment amount. The customer can arbitrarily select whether to use the store tag or the barcode to obtain the store ID data. According to the customer terminal of the present application, by giving the customer such freedom, when replacing an electronic payment system using a barcode with an electronic payment system not using a barcode (i.e., an electronic payment system using a store tag), it is possible to make the change of the system smooth. In particular, when using a store tag, the customer is liberated from the inconveniences described in the background art section. This is because, in the present invention, the store ID is automatically transmitted from the store tag to the customer terminal when the customer brings the customer terminal close to the store tag installed in the store. As a result, a first payment amount input image prompting the customer to input the payment amount is automatically displayed on the display of the customer terminal that has received the store ID. That is, the customer can actually reach the first payment amount input image just by performing the operation of bringing the customer terminal close to the store tag. In other words, when the customer brings the customer terminal close to the store tag, a payment amount input image is semi-forcibly displayed on the display of the customer terminal. Therefore, according to the customer terminal of the present invention, when making a payment to the store, the customer does not need to perform operations such as searching for an icon from the top screen of the customer terminal, activating the camera of the customer terminal, checking whether the state of the activated camera is the desired state, and imaging a barcode with the camera. Thus, according to the customer terminal of the present invention, even a person who is not familiar with operating a customer terminal, such as an elderly person, can easily make a payment at the store.

[0012] After the first amount input image or the second amount input image is displayed on the display, what the customer should do, the response of the store side, and the operation of the customer terminal are basically the same as those described in the background art. The customer inputs the payment amount into the first amount input image or the second amount input image and shows it to the store clerk. When the store clerk tells that the payment amount input into the amount input image is correct, the customer performs an operation corresponding to an indication of the intention to make a payment to the customer terminal. Then, payment data including customer ID data, store ID data, and amount data is generated. As described above, the customer terminal acquires the store ID data from the store tag or barcode. The customer ID is initially recorded in the recording device built into the customer terminal. Also, the data on the amount input into the first amount input image or the second amount input image becomes the amount data. Therefore, the customer terminal combines these three pieces of data to generate payment data. However, in the present invention, the control unit includes route data in the payment data. Then, the payment data is sent from the customer terminal to the settlement device, and in the settlement device, the settlement process for the payment from the customer to the store is executed in the same manner as described in the background art section. That is, the control unit is configured as described below. When the control unit receives the amount data input by the customer by inputting the payment amount into the first amount input image or the second amount input image displayed on the display using the input device, it associates the store ID data received from the store tag or read from the barcode, the customer ID data read from the recording device, the amount data input from the input device, and the route data indicating whether the amount data is input from the first amount input image or the second amount input image, as payment data that is information necessary to identify the payment from the customer to the store, and transmits it to the settlement device via the network from the transceiver mechanism. The route data is data indicating whether the amount data was input from the first amount input image or the second amount input image. The route data may be data directly indicating whether the amount data was input from the first amount input image or the second amount input image, or may be data indirectly indicating whether the amount data was input from the first amount input image or the second amount input image. For example, the route data may be data indicating that the receiver received the store ID data from the store tag (or that the receiver communicated with the store tag) in a predetermined time period before the payment data was generated. When the data indicating that the receiver received the store ID data from the store tag is used as the route data, since the first amount input image was displayed on the display of the customer terminal as long as the route data exists, the route data is data indirectly indicating that "the amount data was input from the first amount input image". In any case, payment data including route data is sent from the customer terminal to the settlement device. As a result, the settlement device can identify who pays how much to whom based on the store ID data, customer ID data, and amount data in the payment data. Therefore, using these data, the settlement device settles the payment from the customer to the store as described in the background art section. On the other hand, the settlement device can use the route data included in the payment data (for example, by recording the route data in a predetermined recording device) to determine at least to what extent among all customers use the store tag and to what extent use the barcode during settlement. Also, by associating and using the customer ID data and the route data, it becomes possible to determine which of the store tag and the barcode was used by the customer identified by the customer ID during settlement. Further, by associating and using the customer ID data, the amount data, and the route data, it becomes possible to determine which of the store tag and the barcode was used by the customer identified by the customer ID when making a payment for the amount specified by the amount data. Of course, when determining which of the store tag and the barcode was used when the customer made a settlement, other data can also be used, such as the store ID that identifies the store where the customer made a purchase, and data that identifies the date and time when the customer made a purchase (for example, data indicating the date and time when the settlement device received the payment data can be used as such data). In any case, if the payment data includes route data, the settlement device can determine which of the store tag and the barcode was used when a certain settlement was made. If a settlement device can determine whether a store tag or a barcode was used during a certain settlement, a store or a corporation that operates the store can encourage customers to use an electronic payment system that does not use barcodes (i.e., a settlement using a store tag) based on the information obtained above. For example, if a store or a corporation that operates the store implements measures such as providing benefits (e.g., discounts on the payment amount, free products or prizes) to customers who use the store tag under certain conditions and not to customers who use the barcode, customers will be induced to use the store tag instead of the barcode during settlement. When implementing such measures, the information obtained by the settlement device on whether a store tag or a barcode was used during a certain settlement is very useful.

[0013] The control unit may be configured to display the second amount input image on the display as visually distinguishable from the first amount input image displayed on the display when the second amount input image is displayed on the display. As described above, in the customer terminal of the present application, when a customer receives a store ID from a store before making a payment to the store and uses the store tag, a first amount input image is displayed on the display of the customer terminal, and when using the barcode in the same situation, a second amount input image is displayed on the display of the customer terminal, respectively. As described above, the customer inputs the payment amount into the first amount input image or the second amount input image and shows it to the store clerk. In the present invention, this essential process of "showing the display of the customer terminal to the store clerk" is utilized. If the first amount input image and the second amount input image are visually distinguishable images, the store clerk can visually distinguish whether the image displayed on the display is either the first amount input image or the second amount input image. And depending on whether the image shown by the customer to the store clerk is the first amount input image or the second amount input image, that is, based on whether the store tag or the barcode was used by the customer prior to making a payment to the store, the actions of the store clerk can be changed, such as the store clerk providing different benefits to the customer. For example, if the store clerk implements measures such as giving a privilege to a customer who uses the store tag under certain conditions and not giving it to a customer who uses the barcode, it becomes possible to induce the customer to use the store tag instead of the barcode during settlement. Various methods can be considered to make the first amount input image and the second amount input image visually distinguishable images. For example, it is conceivable to display a predetermined character, symbol, figure, etc. only on one of the first amount input image and the second amount input image, or to display different predetermined characters, symbols, figures, etc. on one and the other of them. Also, by the method of displaying a predetermined pattern only at a predetermined same position or range (for example, a part with a background) of one of the first amount input image and the second amount input image, or by displaying different patterns at the predetermined same position or range of one and the other of them, the first amount input image and the second amount input image can be made into visually distinguishable images. Furthermore, by the method of making the colors of a predetermined same position or range of the first amount input image and the second amount input image different, the first amount input image and the second amount input image can also be made into visually distinguishable images.

[0014] In the customer terminal according to the present invention, when the store ID data is sent from the store tag to the customer terminal, an amount input image is automatically displayed on the display. Any mechanism may be used as long as it can automatically display the amount input image on the display when the store ID data is sent from the store tag to the customer terminal. For example, in addition to the store ID data, instruction data for instructing the control unit to display the first amount input image on the display may be further recorded in the memory of the store tag. In this case, when the customer brings the customer terminal closer to the store tag than a predetermined distance, the control unit that has received the store ID data and the instruction data from the receiver that has received the store ID data and the instruction data from the transmitter of the store tag may automatically display the first amount input image on the display.

[0015] In addition, the control unit is configured to display an icon for starting a settlement computer program, which is a computer program for transmitting the payment data to the settlement device, on the display, and the control unit that has received the startup data generated by the customer inputting to the icon may start the settlement computer program. In this case, in addition to the store ID data, the instruction data and the startup data may be further recorded in the memory of the store tag. In this case, when the customer brings the customer terminal closer to the store tag than a predetermined distance, the control unit that has received the store ID data, the instruction data, and the startup data from the receiver that has received the store ID data, the instruction data, and the startup data from the transmitter of the store tag may automatically display the first amount input image on the display.

[0016] The store tag may be arranged near a barcode that includes the same store ID data as that recorded in the store tag. The barcode and the store tag can be provided on the same piece of paper or other sheet. By doing so, the paired barcode and store tag can be handled together, which is convenient for the store. For example, the store tag may be arranged on the back side of the portion where the barcode is printed on the paper on which the barcode is printed.

[0017] The inventor of the present application also proposes, as one aspect of the present invention, a computer program for causing a general mobile terminal to function as the customer terminal of the present invention. The effect of this computer program is, in addition to the effects of the customer terminal described above, that a general mobile terminal can be made to function as the customer terminal of the present invention. An example of the computer program is as follows. The computer program is arranged in a store having a store ID for receiving payment and conducting retail sales for a customer having a customer ID for making a payment. It includes a store tag including a memory recording store ID data which is data for specifying the store ID, and a transmitter for wirelessly transmitting the store ID data recorded in the memory to perform short-range communication, and a barcode arranged in the store in pair with the store tag and containing information corresponding to the store ID specified by the store ID data recorded in the memory of the paired store tag, and a settlement device for the customer to settle the payment to the store. It is a customer terminal that the customer is expected to possess, and includes a recording device recording customer ID data which is data for specifying the customer ID, a receiver capable of receiving the store ID data from the transmitter of the store tag, a transceiver mechanism for transmitting data via a network, a display having a function of displaying an image, a camera for imaging and generating image data which is data about the imaged image, an input device capable of inputting amount data which is data for specifying the payment amount which is the amount the customer pays to the store, and a control unit for executing information processing. It is a computer program for causing the control unit in the customer terminal to execute the following processing. This computer program causes the control unit to receive store ID data from the receiver that has received the store ID data from the transmitter of the store tag when the customer brings the customer terminal closer to the store tag than a predetermined distance, and automatically display, on the display, a first amount input image, which is an image prompting the customer to input the payment amount, when the store ID data is received. When the customer captures the barcode with the camera, the control unit receives image data of an image including the barcode generated by the camera from the camera, reads out the store ID data encapsulated in the barcode included in the image specified by the image data, and automatically displays, on the display, a second amount input image, which is an image prompting the customer to input the payment amount, when the store ID data is read out. When the control unit receives the amount data input by the customer by inputting the payment amount into the first amount input image or the second amount input image displayed on the display using the input device, it associates the store ID data received from the store tag or read from the barcode, the customer ID data read from the recording device, the amount data input from the input device, and the path data indicating whether the amount data was input from the first amount input image or the second amount input image as payment data, which is information necessary to identify the payment from the customer to the store, and transmits the payment data from the transceiver to the settlement device via the network.

Brief Description of the Drawings

[0018]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Embodiments for Carrying Out the Invention

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

[0020] FIG. 1 shows an overall view of a payment system according to an embodiment. As shown in FIG. 1, the payment system is composed of a store ID tag 1, a customer terminal 2, and a payment device 3. The customer terminal 2 and the payment device 3 can be connected via a predetermined network 4, and the customer terminal 2 and the payment device 3 can communicate with each other. The communication between the customer terminal 2 and the payment device 3 in this embodiment may be unidirectional from the customer terminal 2 to the payment device 3, but in this embodiment, it is not limited to this and is bidirectional. The network 4 is not particularly limited as long as it can realize such communication, and for example, it may be the Internet. Alternatively, the network 4 may be a carrier line provided by a mobile phone company that sells the customer terminal 2 which is a smart phone, and although it is not limited to this, in this embodiment, it is done as described later.

[0021] The store ID tag 1 is arranged in a store that conducts retail. The store has at least one store ID for receiving payments. The store ID tag 1 is arranged near the place where payments are made from customers to the store in the store, typically near the register device arranged in the store. The store ID is an identifier for specifying an account (for example, an account at a bank) for the store to receive payments. One store ID tag 1 corresponds to one store ID and contains information corresponding to the corresponding store ID. One store ID may be assigned to one store, or multiple store IDs may be assigned. For example, in the accounting area of a store that is a supermarket, the same store ID tag 1 may be arranged for all of a large number of arranged register devices. This is an example where one store ID is assigned to one store, but in this case, payments made by customers at any register device of that store will be received with a common or the same store ID. In addition, the store ID may be assigned, for example, for each sales floor within a store. This is an example where multiple store IDs are assigned to a single store. Each register device in the food section of a store is assigned a common store ID, and each register device in the clothing section of the same store is assigned a different common store ID from that assigned to the food section. In this case, any payment made by a customer at any register device in the food section of the store will be received with the common store ID for the food section, and any payment made by a customer at any register device in the clothing section of the store will be received with the common store ID for the clothing section. Similarly, the store ID may be assigned for each register device. In addition, the store ID may be common to multiple stores. For example, if a corporation desires to receive payments with a specific store ID regardless of which store and which sales floor a customer shops at within a chain of supermarkets under its umbrella, a common store ID will be assigned to the chain of supermarkets. For example, the store ID is assigned for each wallet used to receive the money paid by the customer. Since the store is naturally free to decide how to set the wallet for receiving payments, at least one store ID is assigned to each store, but the number is not limited to one, and in some cases, a common store ID may be assigned across stores. That is, the store ID assigned to each store ID tag 1 is not necessarily unique.

[0022] The store ID tag 1 holds information about the store ID in two forms. Except for the differences in the information held about the store ID, although this is not limited to this, the configurations of the multiple store ID tags 1 in this embodiment can be considered the same. The store ID tag 1 includes a piece of paper 12 printed with a two-dimensional barcode 11. The piece of paper 12 is made of paper in this embodiment, but is not limited thereto, and is rectangular, but is not limited thereto. Of course, the piece of paper may be made of other materials, such as resin, and its shape may be circular, elliptical, etc. other than rectangular. The two-dimensional barcode 11 contains at least the information of the store ID assigned to the store ID tag 1 including the two-dimensional barcode 11. An example of the two-dimensional barcode 11 is a QR code (trademark). Also, the two-dimensional barcode 11 does not necessarily have to be two-dimensional, and a barcode is sufficient. The two-dimensional barcode 11 may be a one-dimensional barcode. The store ID tag 1 also includes a store tag 13 (FIGS. 1 and 2). The store tag 13 and the two-dimensional barcode 11 included in the same store ID tag 1 are paired. The store tag 13 is thinly configured, but is not limited thereto, and is configured by an IC chip in this embodiment. The store tag 13 is rectangular, but is not limited thereto, and its size is slightly smaller than that of the piece of paper 12. The store tag 13 is attached in a state where it is overlapped with the piece of paper 12 printed with the two-dimensional barcode 11 on an appropriate plane X (for example, the outer surface of the case of the register device, a nearby wall, etc.) as shown in FIG. 2(B) so that the store tag 13 is located behind the piece of paper 12. If the piece of paper 12 printed with the two-dimensional barcode 11 and the store tag 13 are fixed to each other, it will be convenient for the store clerk who tries to attach the store ID tag 1 to a predetermined position in the store. However, the piece of paper 12 and the store tag 13 do not necessarily have to be arranged in an overlapped manner, and it is sufficient if both are arranged in the vicinity within the reach of the customer who makes a payment as described later. For example, the store ID tag 13 may be attached in the immediate vicinity of the portion where the two-dimensional barcode 11 is printed on the front side of the piece of paper 12 when the two-dimensional barcode 11 is printed at a certain position on the front side of the piece of paper 12. The store tag 13 includes a memory 14 and a transmitter 15 (Fig. 2). The memory 14 is a recording device capable of recording electronic data, and is constituted by, for example, a RAM (random access memory). The memory 14 stores at least store ID data which is data about the store ID assigned to the store ID tag 1 including the store tag 13. In this embodiment, but not limited thereto, the memory 14 stores, in addition to the store ID data, startup data and instruction data which will be described later. The store ID data recorded in the memory 14 of the store tag 13 is substantially the same as the information about the store ID included in the two-dimensional barcode 11 (that is, the two-dimensional barcode 11 paired with a certain store tag 13) included in the same store ID tag 1. The store tag 13 also includes a transmitter 15. The transmitter 15 has a function of reading the data recorded in the memory 14 and transmitting it to the customer terminal 2 when the customer's customer terminal 2 approaches within a predetermined distance. When the store tag 13 is an RFID tag as will be described later, the transmitter 15 is generally a simple coil wound along the periphery of the store tag 13. The data read from the memory 14 and sent from the transmitter 15 to the customer terminal 2 includes at least the store ID data. In this embodiment, in addition to the store ID data, the startup data and the instruction data are transmitted from the transmitter 15 to the customer terminal 2. As products having such a configuration and function, RFID tags and NFC tags are known. The store tag 13 can be configured using a known, well-known, or commercially available RFID tag or NFC tag. When the store tag 13 is an RFID tag or an NFC tag, the RFID tag or the NFC tag may be a passive tag, an active tag, or a semi-active tag. In this embodiment, but not limited thereto, the store tag 13 is created by writing the above-described data into the memory 14 of a known or well-known RFID tag.

[0023] Next, the configuration of the customer terminal 2 will be described. The customer terminal 2 is a portable communication terminal held by each customer. In terms of its relationship with the payment system, the configuration of each customer terminal 2 can be said to be the same. The customer terminal 2 includes a computer. More specifically, the customer terminal 2 in this embodiment is composed of a general-purpose computer when viewed as hardware, but due to the functions of the computer programs described later, it exhibits functions different from those of a general-purpose computer and performs operations different from those of a general-purpose computer. The customer terminal 2 is generally a smartphone or a tablet, typically a smartphone. All of them are capable of communicating via the network 4, and it is required that they can generate the function blocks described later inside by installing the computer programs described later and execute the information processing described later. The customer terminal 2 also requires a display 201 described later. In the context of the present invention, this is because the customer terminal 2 is required to be able to display both the first amount input image and the second amount input image described later on its display 201. In the customer terminal 2, other necessary functions are being able to communicate with the payment device 3 via the network 4 and being able to receive information (or data) about at least the store ID from the store ID tag 1. The customer terminal 2 in this embodiment is configured to receive store ID data (which may include other data) from the store ID tag 1 either via the two-dimensional barcode 11 or via the store tag 13. The customer terminal 2 has a camera 203 for imaging the two-dimensional barcode 11 in order to receive information about the store ID from the two-dimensional barcode 11. The customer terminal 2 also has a receiver for receiving the data transmitted by the transmitter 15 included in the store tag 13 in order to wirelessly receive the store ID data from the store tag 13. The customer terminal 2 having the functions and configurations described above is well-known or widely known and is also commercially available. For example, it has a recording device for recording in order to install a predetermined computer program, and has an arithmetic device for executing the installed computer program. It also has a transmission / reception mechanism for communicating via the network 4, a display 201 for displaying images, a camera 203 capable of taking pictures, and a receiver for wirelessly receiving store ID data from the store tag 13. All of these are configured using hardware, but all of the hardware necessary to configure them is installed in many currently commercially available smartphones. For example, when the customer terminal 2 is a smartphone or a tablet, the customer terminal 2 as a smartphone may be, for example, an iPhone (trademark) manufactured and sold by Apple Japan Co., Ltd., and the customer terminal 2 as a tablet may be, for example, an iPad (trademark) manufactured and sold by Apple Japan Co., Ltd. Hereinafter, although not limited to this, the discussion will proceed on the assumption that the customer terminal 2 is a smartphone.

[0024] An example of the appearance of the customer terminal 2 is shown in FIG. 1. The customer terminal 2 is provided with a display 201. The display 201 is for displaying still images or moving images, and a well-known or widely known one can be used. The display 201 is, for example, a liquid crystal display or an organic EL (electro-luminescence) display. The customer terminal 2 is also provided with an input device 202. The input device 202 is for the user to perform a desired input to the customer terminal 2. A well-known or widely known one can be used for the input device 202. The input device 202 of the customer terminal 2 in this embodiment is a button type, but it is not limited to this. When the display 201 is a touch panel, the display 201 also serves as the function of the input device 202, and although not limited to this, it is configured like this in this embodiment. The customer terminal 2 is also equipped with a camera 203. Although the symbol 203 is exactly the lens of the camera, as is well known, an image sensor is arranged on the rear side of the lens, and the combination with the lens constitutes a camera. What is shown in FIG. 1 is a so-called in-camera in a smartphone, but it is not limited to this. On the back of the customer terminal 2, a so-called out-camera (lens) is provided. The configurations of both the in-camera and the out-camera are well-known rather than just known, and since they are implemented in many commercially available smartphones, further explanation is omitted. The customer terminal 2 also has a receiver (not shown) capable of receiving data transmitted by the transmitter 15 in the store tag 13.

[0025] The hardware configuration of the customer terminal 2 is shown in FIG. 3. The hardware includes a CPU (central processing unit) 211, a ROM (read only memory) 212, a RAM (random access memory) 213, and an interface 214, which are interconnected by a bus 216. The CPU 211 is an arithmetic unit that performs calculations. The CPU 211 executes the processes described below, for example, by executing a computer program recorded in the ROM 212 or the RAM 213. Although not shown, the hardware may be provided with an HDD (hard disk drive), an SSD (solid state drive), or other large-capacity recording devices, and the computer program may be recorded in the large-capacity recording device. Also, the CPU 211 may be a GPU (graphics processing unit) or a GPGPU (general purpose computing on GPU) in consideration of future improvement in arithmetic processing capabilities. In this application, as an example of the embodiment, a so-called CPU is adopted for the CPU 211. The computer program mentioned here at least includes a computer program for causing the customer terminal 2 (hereinafter referred to as the processing, for example, the processing for causing the customer terminal 2 composed of a smartphone to function as the customer terminal in the present invention) to execute on the customer terminal 2. This computer program may be pre-installed on the customer terminal 2 or may be post-installed on the customer terminal 2. The installation of this computer program on the customer terminal 2 may be performed via a predetermined recording medium such as a memory card, or may be performed via a network such as a LAN or the Internet. It is natural that the computer program may include data used when the CPU 211 executes information processing according to instructions based on the computer program. The ROM 212 is a recording device for non-rewritable data, and records a computer program and data necessary for the CPU 211 to execute the processing described later. The computer program recorded in the ROM 212 is not limited to this. If the customer terminal 2 is a smartphone, for example, a computer program and data necessary for realizing functions such as calls and e-mails, which are necessary for the customer terminal 2 to function as a smartphone, are recorded. The customer terminal 2 is also enabled to browse a homepage based on the data received via the network 4, and a known web browser for enabling this is installed. The RAM 213 is a recording device for rewritable data, and provides a work area necessary for the CPU 211 to perform processing. In some cases, the above-mentioned computer program and data (a part thereof) may be temporarily recorded, for example. The interface 214 exchanges data between the CPU 211, the RAM 213, etc. connected by the bus 216 and the outside. The display 201, the input device 202, the camera 203, and the receiver mentioned above are connected to the interface 214. The operation content input from the input device 202 is input from the interface 214 to the bus 216. Also, as is well known, the image data for displaying an image on the display 201 is sent from the bus 216 to the interface 214 and output from the interface 214 to the display 201. The image data generated by the camera 203 performing imaging reaches from the camera 203 to the interface 214 and is sent from the interface 214 to the bus 216. The store ID data and other data received by the receiver from the store tag 13 reach from the receiver to the interface 214 and are sent from the interface 214 to the bus 216. The interface 214 is also connected to a transceiver mechanism (not shown), which is a known means for communicating with the outside via the network 4. Thereby, the customer terminal 2 can transmit data via the network 4 and receive data via the network 4. The transmission and reception of data via such a network 4 are performed wirelessly. As long as such communication is possible, the configuration of the transceiver mechanism can be known or well known. The data received by the transceiver mechanism from the network 4 is received by the interface 214, and the data passed from the interface 214 to the transceiver mechanism is sent by the transceiver mechanism to the outside via the network 4, for example, to the payment device 3.

[0026] When the CPU 211 executes a computer program, functional blocks as shown in FIG. 4 are generated inside the customer terminal 2. Note that the following functional blocks may be generated by the function of the above-described computer program alone for causing the customer terminal 2 to function as the customer terminal of the present invention, or may be generated by the cooperation of the above-described computer program and the OS and other computer programs installed in the customer terminal 2. Inside the customer terminal 2, an input unit 221, a control unit 222, an image recognition unit 223, a recording unit 225, and an output unit 226 are generated in relation to the functions of the present invention. Inside the control unit 222, an image generation unit 222A and a payment data generation unit 222B are generated. These, including the image generation unit 222A and the payment data generation unit 222B, are functional blocks and are all conceptual. Among these, functional blocks that execute information processing as described later, namely, the control unit 222 (including the image generation unit 222A and the payment data generation unit 222B), and the image recognition unit 223, correspond to an arithmetic device as hardware (in this embodiment, the CPU 211 is an example thereof), or are realized by the function of an arithmetic device that executes information processing according to the instructions of the above computer program. However, when each functional block temporarily holds data, a recording device (mainly the RAM 213) may be used for temporary recording of the data. When viewed as hardware, the input unit 221 and the output unit 226 correspond to the interface 214, or are realized by the function of the interface 214. More specifically, conceptually, the input unit 221 and the output unit 226 correspond to the connection part between the interface 214 and the bus 216. The functional block for recording data, namely, the recording unit 225 in this embodiment, is realized as a recording device for recording information as hardware, namely, the ROM 212, the RAM 213, or a mass storage device if it exists. When the information or data recorded in the recording device changes, the recording device will be composed of the RAM 213 or the mass storage device.

[0027] The input unit 221 receives the input from the interface 214. The input from the interface 214 to the input unit 221 includes the input from the input device 202. The input from the input device 202 includes, for example, although all will be described later, startup data and amount data. The inputs to the input unit 221 from the interface 214 include the input of image data from the camera 203. The inputs to the input unit 221 from the interface 214 also include the input of store ID data, startup data, and instruction data from the receiver. Also, the inputs to the input unit 221 from the interface 214 include the input of result data from the transceiver mechanism, which will be described later. When receiving the data described above, if the received data is image data from the camera 203, the input unit 221 sends it to the image recognition unit 223, and if it receives other data, it sends all the received data to the control unit 222.

[0028] The control unit 222 is configured to control the entire customer terminal 2 when the customer makes a payment at the store using the customer terminal 2. For example, the control unit 222 has a function of causing the display 201 to display an image for prompting the customer to make various inputs when the customer makes a payment using the customer terminal 2. In the control unit 222, the image generation unit 222A is responsible for the function of generating image data, which is the data for the image to be displayed on the display 201. When receiving the data described later, the image generation unit 222A within the control unit 222 generates image data and sends the generated image data to the output unit 226. For example, the control unit 222 may receive store ID data, startup data, instruction data, and result data from the input unit 221. When receiving them, the control unit 222 is configured to generate predetermined image data. The details of which data the control unit 222 receives and what kind of image data it generates will be described later. The control unit 222 may also receive store ID data, startup data, and instruction data from the image recognition unit 223. When it receives them, the control unit 222 is configured to generate predetermined image data. How the control unit 222 generates what kind of image data when it receives which data will be described later. What kind of image data is generated by the control unit 222 will be described later. The control unit 222 is configured to send the generated image data to the output unit 226. When the image generation unit 222A in the control unit 222 generates image data, the image generation unit 222A may use the data recorded in the recording unit 225. How the image generation unit 222A uses what kind of data recorded in the recording unit 225 when generating image data will be described later. As already described, there is a payment data generation unit 222B in the control unit 222. The payment data generation unit 222B has a function of generating payment data. Although the details of the payment data will be described later, briefly speaking, the payment data is data including customer ID data, store ID data, and amount data. As described above, the control unit 222 may receive store ID data from the input unit 221 or the image recognition unit 223. The control unit 222 may also receive amount data from the input unit 221. Further, customer ID data is recorded in the recording unit 225. The payment data generation unit 222B generates payment data using the store ID data, the amount data, and the customer ID data. The payment data generation unit 222B is configured to send the generated payment data to the output unit 226. Note that the payment data in this embodiment further includes route data in addition to the above three types of data. The payment data generation unit 222B existing in the control unit 222 generates payment data including route data. What kind of data the route data is and how the payment data generation unit 222B generates the payment data including the route data will be described later.

[0029] The control unit 222 may also generate camera activation data for activating the camera 203. The cases in which the control unit 222 generates the camera activation data will be described later. The control unit 222 is configured to send the generated camera activation data to the output unit 226.

[0030] The image recognition unit 223 may receive image data from the input unit 221. This image data is data generated by the camera 203 that has performed imaging. As will be described later, the image data sent from the camera 203 is image data regarding an image including the two-dimensional barcode 11 in the store ID tag 1. The image recognition unit 223 executes image recognition processing on the image data and reads the information contained in the two-dimensional barcode 11, that is, the information regarding the store ID. It will be obvious to those skilled in the art that the technology for reading the information contained in the two-dimensional barcode 11 is known or well-known. The technology for reading the information contained in the two-dimensional barcode 11 used in the image recognition unit 223 is sufficient with such known or well-known technology.

[0031] The recording unit 225 has a function of recording data. Although not limited to this, in this embodiment, the customer ID data of the customer who uses the customer terminal 2 is recorded in the recording unit 225. Also, in the recording unit 225 in this embodiment, the data of the image used by the image generation unit 222A in the control unit 222 to generate an image is recorded.

[0032] The output unit 226 may receive, from the control unit 222, the image data generated by the control unit 222, more specifically, the image data generated by the image generation unit 222A in the control unit 222. The output unit 226 sends the received image data to the display 201 via the interface 214. An image based on the image data is displayed on the display 201 that has received the image data. The output unit 226 may receive payment data from the payment data generation unit 222B. When receiving the payment data, the output unit 226 sends the payment data to the transceiver mechanism via the interface 214. The transceiver mechanism is configured to send the payment data to the settlement device 3 via the network 4. The output unit 226 may receive camera activation data. When receiving the camera activation data, the output unit 226 is configured to send the camera activation data to the camera 203 via the interface 214. When receiving the camera activation data, the camera 203 starts up and begins imaging.

[0033] Next, the configuration of the settlement device 3 will be described. The settlement device 3 is a device that receives payment data and performs settlement for the payment of an amount specified by the amount data from the account of the customer specified by the customer ID data included in the payment data to the account of the store specified by the store ID data included in the payment data. Since such a device is publicly known or well-known, such a device can be diverted and used as the settlement device 3. For example, the settlement device 3 may execute settlement as a prepaid payment means, or may execute debit settlement which is immediate settlement, or credit settlement which is postpaid settlement. Hereinafter, the description will proceed on the assumption that the settlement device 3 executes settlement as a prepaid payment means, although it is not limited thereto. The settlement device 3 has a function of managing the customer ID and the balance of the account specified by each customer ID associated with each customer ID, and also managing the store ID and the balance of the account specified by each store ID associated with each store ID. Since the settlement device 3 having such a function is publicly known or well-known in the electronic payment system technology, the settlement device 3 may be configured by following such a publicly known or well-known device. Hereinafter, the settlement device 3 will be briefly described.

[0034] The settlement device 3 is composed of a computer. In this embodiment, the settlement device 3 is composed of one computer, but it may be composed by combining a plurality of computers. The minimum functions required of the settlement device 3 are the ability to record data, perform information processing, and at least communicate with the customer terminal 2 via the network 4. The computer that constitutes the settlement device 3 may be a so-called server device that is known or well-known in terms of hardware, and may be a commercially available one. A known or well-known and commercially available server device usually has the above-mentioned minimum functions. The settlement device 3 in this embodiment is composed of a commercially available server device as hardware. However, the computer that constitutes the settlement device 3 exhibits functions different from those of a general-purpose server device and performs operations different from those of a general-purpose server device by means of a computer program described later.

[0035] The settlement device 3 may be provided with a display and an input device, but since this is not related to this embodiment, the description is omitted. The hardware configuration of the settlement device 3 will be described. The hardware configuration of the settlement device 3 is common in a computer and can follow the hardware configuration (Figure 3) of the customer terminal 2. The settlement device 3 of this embodiment includes a CPU, a ROM, a RAM, and an interface, which are interconnected by a bus. Further, the settlement device 3 includes a large-capacity recording device connected to the bus. The configurations and functions of the CPU, ROM, RAM, interface, and bus in the settlement device 3 may be the same as those of the CPU 211, ROM 212, RAM 213, interface 214, and bus 216 in the customer terminal 2, and this is the case in this embodiment. As already described, the large-capacity recording device is a recording device capable of recording a large amount of data. The interface is connected to a transceiver mechanism capable of communicating via network 4. The transceiver mechanism may be a known or well-known one, and at a minimum, it is required to be able to communicate with the customer terminal 2 via network 4. Payment data received by the transceiver mechanism may be input to the interface. The interface that has received the payment data is configured to send it to the bus. Also, the interface is configured to send the result data, which will be described later, sent from the bus to the transceiver mechanism.

[0036] By executing a computer program for causing the server device to function as the settlement device 3, which was recorded in at least one of the recording devices (mass storage device, ROM, RAM) of the settlement device 3, functional blocks as shown in FIG. 5 will be generated within the settlement device 3. The following functional blocks may be generated by the function of the above-mentioned computer program alone for causing the server device to function as the settlement device 3 in the present invention, or may be generated by the cooperation of the above-mentioned computer program and the OS and other computer programs installed in the settlement device 3. Within the settlement device 3, an input unit 321, a balance unit 322, a balance database 323, and an output unit 324 are generated in relation to the functions of the present invention. These are functional blocks and are conceptual. Among these, the functional block that executes information processing, namely, the balance unit 322, corresponds to an arithmetic unit (CPU in this embodiment) as hardware, or is realized by the function of an arithmetic unit that executes information processing according to the instructions of the above-mentioned computer program. However, when the balance unit 322 temporarily holds data, a recording device (mainly RAM) may be used for the temporary recording of the data. When viewed as hardware, the input unit 321 and the output unit 324 correspond to an interface or are realized by the functions of an interface. More specifically, conceptually, the input unit 321 and the output unit 324 correspond to the connection part between the interface and the bus. The functional block for recording data, that is, the balance database 323, is realized as a recording device for recording information as hardware, that is, a RAM or a mass storage device. In this embodiment, the balance database 323 is configured with the data recorded in the mass storage device. The balance database 323 may be configured across a plurality of mass storage devices.

[0037] The input unit 321 may receive payment data sent from the customer terminal 2 via the network 4 and received by the transceiver mechanism from the interface. The input unit 321 that has received the payment data is configured to send the payment data to the balance unit 322. The balance database 323 records the customer ID and the balance of the account specified by each customer ID associated with each customer ID, and also records the store ID and the balance of the account specified by each store ID associated with each store ID. An example of data regarding each customer ID and the balance associated therewith, and each store ID and the balance associated therewith, recorded in the balance database 323 is shown in FIG. 6(A). The customer IDs of each customer are listed vertically below the column of "Customer ID". Of course, this is not the only case, but in this embodiment, a serial number starting from "000001" with the letter "C" at the head is used as the customer ID of each customer. Also, vertically listed below "Customer Balance" is the current balance of the account specified by the customer ID in the left adjacent column. For example, the balance of the account specified by the customer ID "C000002" is "22500". The store IDs are listed vertically below the column of "Store ID". Of course, this is not the only case, but in this embodiment, a serial number starting from "000001" with the letter "S" at the head is used as the store ID of each store. Also, vertically listed below "Store Balance" is the current balance of the account specified by the store ID in the left adjacent column. For example, the balance of the account specified by the store ID "S000003" is "213879451".

[0038] The balance unit 322 has a function of updating the data shown in FIG. 6(A) recorded in the balance database 323. As described above, payment data may be sent from the input unit 321 to the balance unit 322. When the balance unit 322 receives the payment data, it updates the data shown in FIG. 6(A) recorded in the balance database 323. How the balance unit 322 updates the content of the data shown in FIG. 6(A) in the balance database 323 will be described later. After the balance unit 322 updates the content of the balance associated with the customer ID and the balance associated with the store ID shown in FIG. 6(A) in the balance database 323, it generates result data. The result data is sent from the balance unit 322 to the output unit 324 and then from the output unit 324 to the transceiver mechanism. The transceiver mechanism is configured to transmit the result data to the customer terminal 2 via the network 4. Note that the result data is generated not only in the case where the balance unit 322 fails to update the content of the balance database 323, but also in this embodiment. Although the content of the result data generated in that case is different from the content of the result data generated when the balance unit 322 updates the content of the balance database 323, the result data including this point will be described later.

[0039] The balance database 323 also records history data as shown in FIG. 6(B). As described above, payment data is sent to the balance unit 322. The payment data includes customer ID data, store ID data, amount data, and further includes route data. The history data includes, among these, at least route data that identifies whether the first amount input image or the second amount input image was used when the customer entered the amount data when making a payment. Although not limited to this, in this embodiment, as shown in FIG. 6(B), the history data includes, in addition to the route data, customer ID data, store ID data, amount data, and date / time data. In FIG. 6(B), the data written under the character "Date / Time" is the date / time data, the data written under the character "Customer ID" is the customer ID data, the data written under the character "Store ID" is the store ID data, the data written under the character "Route" is the route data, and the data written under the character "Amount" is the amount data. The horizontally written date / time data, customer ID data, store ID data, route data, and amount data are linked to each other. Among these linked data, each data except the date / time data can be recorded in the balance database 323 as it is, which is the same name data included in the payment data sent from the customer terminal 2 by the customer who attempted to make a payment to the store. The route data will be further described later. The date and time data is data that identifies the date and time when a customer attempts to make a payment at a store. This date and time data can be, for example, data (e.g., a timestamp indicating that time) that the payment device 3 or the balance database 323 of the payment device 3 identifies the time when payment data is received. A similar timestamp can of course also be generated by the customer terminal 2 instead of the payment device 3. For example, when the payment data generation unit 222B in the control unit 222 of the customer terminal 2 generates payment data, the payment data generation unit 222B can include a timestamp for the time when the payment data is generated in the payment data. Whether the timestamp is generated by the customer terminal 2 or the payment device 3, it should be obvious to at least those skilled in the art that it is possible to include the timestamp in the history data as shown in FIG. 6(B).

[0040] Hereinafter, the usage method and operation of the payment system configured as described above will be described. When the payment system is used, it is assumed that customer ID data is recorded in the recording unit 225 of the customer terminal 2. It is widely practiced for each customer to record the customer ID assigned to each customer in a recording device (e.g., RAM 213 or a large-capacity recording device) in their own customer terminal 2, which is a smartphone in this embodiment, and the technology for that is known or well-known. It is possible to record customer ID data in the recording unit 225 using such known or well-known technology. As a method when a customer who has shopped at a store makes a payment using the customer terminal 2 at the store, in this embodiment, the customer can select two methods. One is payment using the two-dimensional barcode 11, and the other is payment using the store tag 13. These will be described in order below.

[0041] (Payment using the two-dimensional barcode 11) The payment using the two-dimensional barcode 11 will be described with reference to FIG. 7. The store clerk requests payment from the customer who has shopped at the store. The customer performs an operation to start a computer program for payment and inputs start-up data in order to make a payment using the two-dimensional barcode 11. The customer causes the top screen to be displayed on the display 201 of the customer terminal 2. Usually, a plurality of icons for starting various computer programs (so-called apps) are displayed on the top screen (Fig. 8). In this embodiment, for example, the icon with a "￥" mark surrounded by a circle and labeled 501 in Fig. 8 is the icon for starting the above-described computer program. The image data for displaying the icon 501 on the top screen is generated by the control unit 222 using, for example, the data recorded in the recording unit 225. The control unit 222 sends the generated image data to the output unit 226. The image data is sent from the output unit 226 to the display 201 via the interface 214. As a result, the icon 501 is always displayed on the top screen displayed on the display 201, although not limited to this, in this embodiment. Of course, the functions of the OS or other computer programs may be used for the display of the icon 501. The customer makes an input to the icon 501. In this embodiment, the input to the icon 501 is made by the customer touching the position where the icon 501 is displayed on the display 201 which is a touch panel. Then, in this embodiment, the input device 202 which the display 201 also serves as generates start-up data, and the generated start-up data is input to the customer terminal 2.

[0042] When the start-up data is input, a computer program for causing the smartphone to function as the customer terminal 2 of the present invention associated with the icon 501 starts, and a start image is displayed on the display 201 (S1101). The start-up data reaches the control unit 222 of the customer terminal 2 from the input device 202 via the interface 214 and the input unit 221. The control unit 222 that has received the start-up data starts the above-described computer program and causes a start image to be displayed on the display 201. Specifically, the control unit 222 that has received the startup data, and more specifically, the image generation unit 222A in the control unit 222, generates image data for displaying a start image on the display 201. To generate this image data, the image generation unit 222A may read out image data and other appropriate data recorded in the recording unit 225 and use it. The generated image data is sent from the control unit 222 to the output unit 226 in the same manner as the image data for displaying the icon 501 on the display 201, and is then sent to the display 201 via the interface 214. A start image is displayed on the display 201. An example of the start image is shown in FIG. 9. On the start image, there are a button 502 labeled "Use 2D barcode" and a button 503 labeled "Use store tag". Since payment is to be made using the 2D barcode 11 this time, the customer inputs data regarding the intention to perform settlement using the 2D barcode 11 by touching the button 502. Then, the input device 202 generates data corresponding to the intention indication. That data follows the same path as the startup data and is sent from the input device 202 to the control unit 222 via the interface 214 and the input unit 221. Upon receiving that data, the control unit 222 generates camera activation data, which is data for activating the camera 203. The generated camera activation data is sent to the camera 203 via the output unit 226 and the interface 214. Upon receiving the camera activation data, the camera 203 is activated and starts imaging.

[0043] When the camera 203 is activated, the customer adjusts the position and orientation of the customer terminal 2 and images the 2D barcode 11 included in the store ID tag 1 near the register device with the camera 203 (S1102). When imaging is performed, the camera 203 generates image data regarding the image including the 2D barcode 11. The image data generated by the camera 203 is sent from the camera 203 to the input unit 221 via the interface 214, and further sent to the image recognition unit 223. The image recognition unit 223 performs image recognition on the two-dimensional barcode 11 reflected in the image specified by the image data, and reads out the store ID encapsulated as information in the two-dimensional barcode 11. The image recognition unit 223 generates store ID data corresponding to the read store ID. The image recognition unit 223 sends the store ID data to the control unit 222. The store ID data is received by the payment data generation unit 222B.

[0044] When the store ID data is sent to the payment data generation unit 222B, the customer then inputs the amount data. Before that, a second amount input image is displayed on the display 201 (S1103). When the store ID data is sent to the payment data generation unit 222B, the image generation unit 222A generates image data for displaying a second amount input image, which is a screen prompting the customer to input the payment amount. When generating the data of the second amount input image, the image generation unit 222A reads out the necessary data from the recording unit 225 and uses that data if necessary. The image data generated by the image generation unit 222A in the control unit 222 is sent to the display 201 through the same path as the image data generated by the image generation unit 222A so far. The second amount input image is displayed on the display 201 that has received the image data. An example of the second amount input image displayed on the display 201 is shown in FIG. 10(A). The character 504 "Please input the payment amount" is displayed on the second amount input image. Below the character 504, there is a frame 505 for amount input. By the combination of the character 504 and the frame 505, the customer who sees them understands that they should input the payment amount within the frame 505. The customer inputs the payment amount into the frame 505 (S1104). The input device 201 is used for the input. In this embodiment, the customer inputs the payment amount into the frame 505 by performing an operation for inputting numbers on the display 201 (FIG. 10(B)). In the example of FIG. 10(B), the payment amount is 1000 yen. After the customer inputs the payment amount into the frame 505 of the amount input image, the customer shows the amount to the store clerk. If the amount is incorrect, the clerk will point it out. Once pointed out, the customer will re-enter the payment amount in the amount input image and show the corrected amount input image to the clerk. If the payment amount is correct, the clerk will inform the customer to that effect. The customer finalizes the payment amount entered in the second amount input image (S1105). To finalize the payment amount, the customer touches the button 506 labeled "Finalize" displayed in the amount input image. The customer touches the button 506. Then, the payment amount displayed on the screen (1000 yen in this example) is finalized as the amount that allows the customer to make the payment. When the customer touches the button 506, the amount data, which is data identifying the amount written in the frame 505, is sent from the input device 202 to the control unit 222 along the same path as the startup data and received by the payment data generation unit 222B.

[0045] Upon receiving the amount data, the payment data generation unit 222B generates payment data (S1106). The payment data is a combination of customer ID data, which is data identifying the customer making the payment, store ID data, which is data identifying the store receiving the payment (accurately, the account or accounts used by the store), and amount data identifying the payment amount. When the payment data generation unit 222B receives the amount data, it reads out the customer ID data recorded in the recording unit 225 from the recording unit 225. The payment data generation unit 222B combines the previously received store ID data and amount data with the newly read customer ID data to generate payment data including customer ID data, store ID data, and amount data. Note that the reading of the customer ID data from the recording unit 225 by the payment data generation unit 222B may be performed at any timing before the generation of the payment data. For example, the payment data generation unit 222B may read the customer ID data from the recording unit 225 at the timing when the startup data is input to the control unit 222.

[0046] As described above, the payment data in this embodiment includes route data. The route data is data indicating whether the above-described amount data was input from the first amount input image (the "first amount input image" will be described later) or from the second amount input image. When "payment using the two-dimensional barcode 11" is selected, the customer inputs the amount data from the second amount input image shown in FIG. 10 as described above, although there are exceptions as will be described later. Therefore, the route data in this case is "data indicating that the amount data was input from the second amount input image". The route data may be data that directly indicates "the fact that the amount data was input from the second amount input image", or may be data that indirectly indicates it. This point will be described later. In any case, the payment data generation unit 222B generates payment data including the route data. The payment data generation unit 222B sends the generated payment data to the output unit 226.

[0047] The output unit 226 sends the payment data to the transceiver mechanism via the interface 214. The transceiver mechanism sends the payment data to the settlement device 3 via the network 4 (S1107). The customer terminal 2 automatically performs each process from when the customer touches the button 506 until the payment data is sent to the settlement device 3, for example, within several seconds. The settlement device 3 receives the payment data by its transceiver mechanism. Upon receiving the payment data, the settlement device 3 performs settlement processing (S1108). Specifically, the payment data received by the settlement device 3 is sent from the transceiver mechanism, through the input unit 321, to the balance unit 322. The balance unit 322 updates the content of the balance database 323 using the received payment data. As described above, the payment data includes customer ID data, store ID data, and amount data. The balance unit 322 reduces the data of the balance (customer balance) associated with the customer ID data included in the received payment data by the amount specified by the amount data among the data recorded in the balance database 323, and increases the data of the balance (store balance) associated with the store ID data included in the received payment data by the amount specified by the amount data. As a result, the balance of the customer specified by the customer ID decreases, and the balance of the store specified by the store ID increases, so it means that a payment of the amount specified by the amount data has been made from the customer specified by the customer ID to the store specified by the store ID. For example, if in the payment data, the customer ID is "C000001", the store ID is "S000004", and the amount data is "1000 (yen)", then the balance unit 322 updates the customer balance associated with the customer ID "C000001" from 6221 to 5221, and rewrites the store balance associated with the store ID "S000004" from 7452422 to 7453422 (see Fig. 6). Thereby, the settlement is completed normally. When the settlement is completed normally, the balance unit 322 generates result data indicating that the settlement has been completed normally. On the other hand, there may be cases where the settlement does not end normally. For example, it is the case when the balance of the account specified by the customer ID data is less than the amount specified by the amount data, that is, when there is an insufficient balance. For example, if in the payment data, the customer ID is "C000005", the store ID is "S000004", and the amount data is "1000 (yen)", then since the customer balance associated with the customer ID "C000005" is 324, the balance of the account specified by the customer ID data is less than the amount specified by the amount data. Of course, there will also be reasons other than insufficient balance, but if the balance unit 322 cannot perform the settlement, it generates result data indicating that the settlement has not ended normally. The result data is sent from the balance unit 322 to the output unit 324, and further sent to the transceiver mechanism via the interface. The result data is sent from the transceiver mechanism to the customer terminal 2 via the network 4 (S1109).

[0048] On the other hand, the balance unit 322 writes the history data into the balance database 323. Every time a payment is made by a customer to the store, the balance unit 322 writes a set of data arranged horizontally in FIG. 6(B) into the balance database 323. The writing of the history data into the balance database 323 by the balance unit 322 can be executed independently of the above-described settlement process performed by the balance unit 322. Therefore, the writing of the history data into the balance database 323 may be performed before, after, or in parallel with the settlement process. For example, a set of data including the date and time data of "2024 / 04 / 12 / 10:00.40" is written into the balance database 323 by the balance unit 322. The meaning of this data is that at "10:00:40 on April 12, 2024", when a payment of "5820" yen was made from a customer with customer ID "C001005" to a store with store ID "S000202", the amount data was input from the second amount input image. As is clear from FIG. 6(B), the path data written under the word "path" is either "1" or "0". In this embodiment, when the data is "1", it indicates that the amount data was input from the first amount input image, and when the data is "0", it indicates that the amount data was input from the second amount input image. Of course, the path data does not have to be data such as "0" and "1", and it is naturally possible to use other data such as "first amount input image" and "second amount input image". In any case, this route data is generated by the payment data generation unit 222B of the customer terminal 2, and more specifically, in this embodiment, although not limited thereto. The payment data generation unit 222B generates route data of "1" when any one of the following (1) to (3) "predetermined conditions" is satisfied, and generates route data of "0" when the predetermined condition is not satisfied. The following conditions (1) to (3) are all satisfied when the customer inputs the amount data from the first amount input image, but are not satisfied when the customer inputs the amount data from the second amount input image. Therefore, when any of the following conditions (1) to (3) is satisfied, it is guaranteed that the amount data has been input from the first amount input image. Thus, the route data is set to "1" indicating that the amount data has been input from the first amount input image. (1) When the payment data generation unit 222B detects that the image generation unit 222A has generated image data for displaying the first amount input image on the display 201 (2) When the payment data generation unit 222B detects that an amount for inputting amount data has been input into the first amount input image displayed on the display 201 (3) When the control unit 222 detects that data has been transmitted from the store tag 13 to the receiver within a predetermined time period before the amount data is input (for example, within 30 seconds before the amount data is input) Although not limited thereto, in this embodiment, it is assumed that the above (3) is adopted as the predetermined condition. Then, when the payment data generation unit 222B detects that data has been transmitted from the store tag 13 to the receiver within a predetermined time period before the amount data is input, the route data is set to "1", and when it does not detect that data has been transmitted from the store tag 13 to the receiver within a predetermined time period before the amount data is input, the route data is set to "0".

[0049] To get back to the story. The settlement device 3 sends the result data to the customer terminal 2 via the network 4 as described above. The customer terminal 2 receives the result data through the transceiver mechanism. The received result data is sent to the control unit 222 via the transceiver mechanism, the interface 214, and the input unit 221. The control unit 222 generates image data for displaying an image corresponding to the result data on the display 201. After generating the image data, the control unit 222 sends the image data to the display 201 via the output unit 226 and the interface 214. Thereby, an image corresponding to the image data is displayed on the display 201. If the result data indicates that the settlement has ended normally, the image will indicate that the settlement has ended normally. If the result data indicates that the settlement has not ended normally, the image will indicate that the settlement has not ended normally. The customer shows the image displayed on the display 201 of the customer terminal 2 to the store clerk. If the image indicates that the settlement has ended normally, the customer's payment to the store is completed (S1110). If the image does not indicate that the settlement has ended normally, the customer makes a payment to the store by other means.

[0050] (Payment using the store tag 13) The payment using the store tag 13 will be described with reference to FIG. 11. The store clerk requests payment from the customer who has made a purchase in the store. The customer inputs startup data to the customer terminal 2 by performing an operation to start a computer program for making a payment. First, the customer causes the top screen to be displayed on the display 201 of the customer terminal 2. The customer touches the icon 501 shown in FIG. 8 from among the icons on the top screen. Thereby, startup data is input from the input device 202.

[0051] When startup data is input, a computer program for causing a smartphone associated with the icon 501 to function as the customer terminal 2 of the present invention starts, and a start image is displayed on the display 201 (S1201). The processing up to this point is the same as in the case of (payment using the two-dimensional barcode 11). The start image is, for example, the one shown in FIG. 9.

[0052] This time, instead of payment using the two-dimensional barcode 11, payment using the store tag 13 is performed. Therefore, the customer inputs data regarding the intention to perform settlement using the store tag 13 by touching a button 503 labeled "Use Store Tag". Then, the input device 202 generates data regarding that intention.

[0053] That data follows the same path as the startup data and is input from the input device 202 to the control unit 222. Upon receiving the data, the control unit 222 generates image data indicating that payment using the store tag 13 has been selected. The image data is sent from the control unit 222 to the display 201 via the output unit 226 and the interface 214 in the same manner as before. An image based on the image data is displayed on the display 201. The image may include a message, such as "Bring the smartphone closer to the store tag", to inform the customer of the action to be taken. However, it is not always necessary to display any new image on the display 201 of the customer terminal 2 even if the customer touches the button 503. The customer brings the customer terminal 2 closer to the store ID tag 1 (S1202). When the customer terminal 2 is brought close enough to the store ID tag 1, the transmitter 15 included in the store tag 13 on the back side of the piece of paper 12 in the store ID tag 1 reads out the data recorded in the memory 14 included in the store tag 13, that is, the startup data, the instruction data, and the store ID data, from the memory 14 and transmits it toward the customer terminal 2. The receiver of the customer terminal 2 receives startup data, instruction data, and store ID data. The presence of the piece of paper 12 does not interfere with the above-described data transmission and reception performed between the transmitter 15 and the receiver. Although not limited to this, the data transmission and reception between the transmitter 15 included in the store tag 13 and the receiver included in the customer terminal 2 in this embodiment is executed as communication by RFID. The three pieces of data received by the receiver are sent from the receiver to the input unit 221 via the interface 214, and further sent to the control unit 222. The control unit 222 does not perform any particular processing upon receiving the startup data, that is, ignores the startup data. This is because the computer program according to the present invention for performing settlement installed in the customer terminal 2 has already started up. On the other hand, when the image generation unit 222A in the control unit 222 receives the instruction data, it generates image data for displaying a first amount input image on the display 201 based on the instruction data. That is, the instruction data is data regarding an instruction to "display the first amount input image on the display 201". Similar to the second amount input image, the first amount input image is an image that prompts the customer to input the payment amount. However, the first amount input image is different from the second amount input image. The first amount input image and the second amount input image are visually distinguishable from each other when they are displayed on the display 201. This will be described later. When the image generation unit 222A in the control unit 222 generates image data for displaying the first amount input image on the display 201, it sends the image data to the output unit 226. The image data is sent from the output unit 226 to the display 201 via the interface 214. As a result, the first amount input image will be displayed on the display 201 (S1203). Also, the store ID data received by the receiver from the store tag 13 is sent to the payment data generation unit 222B via the interface 214 and the input unit 221.

[0054] An example of the first amount input image displayed on the display 201 of the customer terminal 2 is shown in FIG. 12. As described above, the first amount input image is an image having the same purpose as the second amount input image, that is, an image for prompting the customer to input the payment amount. Therefore, the first amount input image is basically the same as the second amount input image shown in FIG. 10. That is, the first amount input image includes the character 504 of "Please enter the payment amount", the frame 505 for amount input displayed below the character 504, and the button 506 labeled "Confirm". However, the first amount input image is visually distinguishable from the second amount input image when it is displayed on the display 201. In this embodiment, the first amount input image shown in FIG. 12 has the character "Use Store ID" surrounded by an ellipse, while the second amount input image shown in FIG. 10 has neither an ellipse nor the character "Use Store ID". Thereby, a person who has seen either the first amount input image or the second amount input image, for example, a store clerk, can distinguish and recognize whether the image he / she has seen is the first amount input image or the second amount input image. In this embodiment, as described above, in order to visually distinguish the first amount input image from the second amount input image, only the former includes the characters "Store ID Utilization" enclosed by an ellipse. Of course, other means may be used to visually distinguish the first amount input image from the second amount input image. For example, only one of the first amount input image and the second amount input image may display a predetermined character, symbol, figure, etc. (The examples described with reference to FIGS. 10 and 12 are examples where a predetermined character and figure are displayed only in the first amount input image.), or different predetermined characters, symbols, figures, etc. may be displayed on one and the other of them, respectively, so that the first amount input image and the second amount input image can be visually distinguished. Also, by a method of displaying a predetermined pattern only at a predetermined same position or range (for example, a part with a background) of only one of the first amount input image and the second amount input image, or by displaying different patterns at a predetermined same position or range of one and the other of them, the first amount input image and the second amount input image can be made into visually distinguishable images. Furthermore, by a method of making the colors of a predetermined same position or range of the first amount input image and the second amount input image different, the first amount input image and the second amount input image can be made into visually distinguishable images. For example, FIGS. 13(A) and (B) show examples in which the backgrounds (or the colors of the backgrounds) of the first amount input image and the second amount input image are made different. Whichever is the first amount input image does not matter, but for example, let FIG. 13(A) be the first amount input image and FIG. 13(B) be the second amount input image. It will be obvious that the two are visually distinguishable.

[0055] Even when the first amount input image is displayed on the display 201, the customer inputs the payment amount into the frame 505 in the same manner as when the second amount input image is displayed on the display 201 (S1204). Similar to when inputting the payment amount into the second amount input image, the display 201 as the input device 202 is used for the input. In the example of FIG. 12(B), the payment amount is 1000 yen.

[0056] The processing from here is the same as the processing from (S1104) to (S1110) in the case of (payment using the two-dimensional barcode 11). When the customer has entered the payment amount within the frame 505 of the amount input image, the customer shows that amount to the store clerk. If the amount is incorrect, the clerk points it out. If pointed out, the customer re-enters the payment amount in the first amount input image and shows the corrected first amount input image to the clerk. If the payment amount is correct, the clerk notifies the customer to that effect. The customer finalizes the payment amount entered in the first amount input image (S1205). Then, the amount data is sent to the payment data generation unit 222B.

[0057] Upon receiving the amount data, the payment data generation unit 222B generates payment data (S1206). The payment data, similar to the case of (payment using the two-dimensional barcode 11), is a combination of customer ID data, which is data for identifying the customer who makes the payment, store ID data, which is data for identifying the store (precisely, the account or accounts used by the store) that receives the payment, and amount data for identifying the payment amount. The payment data also includes route data. As described above, in this embodiment, the above-mentioned condition (3) is adopted as a predetermined condition. Thereby, when the payment data generation unit 222B detects that data has been transmitted from the store tag 13 to the receiver during a predetermined time period before the amount data is input, the route data is set to "1", and when it does not detect that data has been transmitted from the store tag 13 to the receiver during a predetermined time period before the amount data is input, the route data is set to "0". In this example, before the above-described processing of S1204 and S1205 for inputting the amount data is executed, since the store ID data and the like have been transmitted from the store tag 13 to the receiver of the customer terminal 2, the control unit 222 or the payment data generation unit 222B in the control unit 222 that detected this generates route data of "1" and includes it in the payment data.

[0058] Payment data is sent from the payment data generation unit 222B to the output unit 226. The payment data is further sent from the output unit 226 to the transceiver mechanism and then sent to the settlement device 3 via the network 4. That is, the payment data is sent from the customer terminal 2 to the settlement device 3 (S1207). After the customer touches the button 506, the customer terminal 2 automatically performs each process from that point until the payment data is sent to the settlement device 3, for example, within several seconds. The settlement device 3 receives the payment data by its transceiver mechanism. Upon receiving the payment data, the settlement device 3 performs settlement processing (S1208). The settlement processing is the same as in the case of (payment using the two-dimensional barcode 11). Thereafter, the result data is sent from the settlement device 3 to the customer terminal 2 via the network 4 (S1209).

[0059] The customer terminal 2 receives the result data by its transceiver mechanism. An image corresponding to the content of the result data is displayed on the display 201 of the customer terminal 2. If the image indicates that the settlement has been completed normally, the payment by the customer to the store is completed (S1210). If the image does not indicate that the settlement has been completed normally, the customer makes a payment to the store by another method.

[0060] On the other hand, the settlement device 3 that has received the payment data writes the history data to the balance database 323 in the same manner as in the case of (payment using the two-dimensional barcode 11). The process of writing the history data to the balance database 323 in the settlement device 3 is performed by the balance unit 322 recording the same type of data as in the case of (payment using the two-dimensional barcode 11) to the balance database 323. Therefore, in this embodiment, the balance unit 322 records the route data, customer ID data, store ID data, amount data, and date / time data in a linked state with each other in the balance database 323. As a result, in the balance database 323 of the settlement device 3, history data will be accumulated whether the customer makes a payment using the two-dimensional barcode 11 or using the store tag 13.

[0061] By the way, in the payment using the store tag 13 described above, after the customer starts the computer program according to the present invention for making a payment by operating the icon 501 displayed on the top screen of the display 201 of the customer terminal 2, or after the start image is displayed on the display 201, the customer terminal 2 is brought closer to the store ID tag 1 including the store tag 13. However, the customer may omit the process of displaying the start image on the customer terminal 2 (S1201). In this settlement system, in a state where the above-described computer program has not started or the start image is not displayed on the display 201, the customer can execute the process of S1202 described above, that is, bring the customer terminal 2 closer to the store ID tag 1. When the customer takes such an action, the transmitter 15 included in the store tag 13 on the back side of the piece of paper 12 in the store ID tag 1 reads out the data recorded in the memory 14 included in the store tag 13, that is, the startup data, the instruction data, and the store ID data from the memory 14, and transmits it toward the customer terminal 2. The receiver of the customer terminal 2 receives the startup data, the instruction data, and the store ID data by the receiver. The three pieces of data received by the receiver are sent from the receiver to the input unit 221 via the interface 214, and further sent to the control unit 222. When the control unit 222 receives the startup data, it starts the computer program according to the present invention for performing settlement. Further, when the image generation unit 222A in the control unit 222 receives the instruction data, it generates, based on the instruction data, image data for displaying a first amount input image on the display 201, for example, using the data recorded in the recording unit 225 as needed. As a result, a first amount input image will be displayed on the display 201 as in the case described above (S1203). At this time, the control unit 222 that has received the startup data may display the start image and the first amount input image on the display 201 in that order, or may omit the start image and display the first amount input image from the beginning. Also in this case, the payment data generation unit 222B in the control unit 222 receives the store ID data from the receiver via the interface 214 and the input unit 221.

[0062] That is, in this embodiment, even when the computer program according to the present invention for performing settlement is not started on the customer terminal 2, the customer can display a first amount input image on the display 201 of the customer terminal 2 simply by bringing the customer terminal 2 close to the store ID tag 1 or the store tag 13 included therein. The customer can display the first amount input image on the display 201 of the customer terminal 2 without searching for the icon 501 or touching the icon 501. The processing after the first amount input image is displayed is as already described. Also, when the customer terminal 2 is brought close to the store ID tag 1 or the store tag 13 included therein in a state where the computer program according to the present invention for performing settlement is not started on the customer terminal 2 and a first amount input image is displayed on the display 201 of the customer terminal 2, the above-described route data becomes "1" indicating that the payment data was input from the first amount input image. This is because, also in this case, the payment data generation unit 222B detects that data was transmitted from the store tag 13 to the receiver during a predetermined time period before the amount data was input. Therefore, the route data (or payment data including the route data) generated in this case is the same as the data generated by the payment data generation unit 222B when the process of displaying the start image on the customer terminal 2 (S1201) is not omitted. As a result, the content of the history data accumulated in the balance database 323 of the payment device 3 each time a settlement is made is also the same as the content of the history data accumulated in the balance database 323 when the process of displaying the start image on the customer terminal 2 (S1201) is not omitted.

[0063] As described above, history data is accumulated in the balance database 323 of the payment device 3. The history data includes at least route data. Other data can be arbitrarily included in the history data. In this embodiment, in addition to the route data, customer ID data, store ID data, amount data, and date / time data are recorded in the balance database 323 in a state where they are associated with each other. The history data is subsequently used by the payment device 3 or another device outside the payment device 3. When using the history data in a device outside the payment device 3, the history data shown in FIG. 6(B) recorded in the balance database 323 is sent to another device via the network 4 or other networks, or sent to another device via a recording medium, and thus used in another device. Using the history data, a store or a person who manages the store (hereinafter, this person is referred to as the "manager") can grasp the following. As described above, the history data includes at least route data. Therefore, the manager can grasp to what extent among all customers use the store tag 13 during settlement and to what extent use the two-dimensional barcode 11 during settlement. If the route data is recorded by associating the date and time data, the operator can grasp the proportion of customers who used the store tag 13 and the proportion of customers who used the two-dimensional barcode 11 when making settlements during a certain period. Also, if the customer ID data is recorded in addition to the route data, the operator can grasp which of the settlements using the store tag 13 and the settlements using the two-dimensional barcode 11 each customer used. Furthermore, if the amount data is associated and recorded in addition to the route data, the operator can grasp the relationship between the amount of money paid by the customer to the store and whether the store tag 13 or the two-dimensional barcode 11 is used during the settlement. In this way, the operator records the necessary data among the customer ID data, store ID data, amount data, and date and time data (or other data) in addition to or instead of the route data, and appropriately uses the recorded data, so that it becomes possible to analyze whether the customer used the store tag 13 or the two-dimensional barcode 11 in the settlement. Of course, depending on the type of data recorded, the operator can analyze whether the customer used the store tag 13 or the two-dimensional barcode 11 in the settlement in relation to the date and time and the payment amount. The operator can use such analysis results as information for developing appropriate measures to guide the behavior of customers to use the store tag 13 instead of the two-dimensional barcode 11 during the settlement.

[0064] Also, in the settlement system described in this embodiment, it is possible to guide the customer to use the store tag 13 instead of the two-dimensional barcode 11 during the settlement as follows. As described above, when the customer selects (payment using the store tag 13), the customer inputs the payment amount into the first amount input image (S1204), and shows the display 201 on which the first amount input image with the payment amount input is displayed to the store clerk of the store. Similarly, when the customer selects (payment using the two-dimensional barcode 11), the customer enters the payment amount in the second amount input image (S1104), and shows the display 201 on which the second amount input image with the payment amount entered is displayed, to the store clerk of the store. That is, regardless of whether the customer selects (payment using the store tag 13) or (payment using the two-dimensional barcode 11), the customer needs to show the first amount input image or the second amount input image to the store clerk of the store. And as already described, the first amount input image and the second amount input image are different from each other and are visually distinguishable images. Therefore, the store clerk who is shown the first amount input image or the second amount input image can distinguish whether the shown image is the first amount input image or the second amount input image. More specifically, in the payment to that store that the customer is currently about to make, the store clerk can distinguish whether the store tag 13 is being used or the two-dimensional barcode 11 is being used. Using this, the store clerk can give different benefits to the customer depending on whether the image shown by the customer to the clerk is the first amount input image or the second amount input image, or whether the store tag 13 or the two-dimensional barcode 11 is being used for the payment to that store that the customer is currently about to make. For example, the store management etc. can make the store clerk execute measures such as giving discounts on the price, or providing free products or prizes only to customers who use the store tag 13 for the payment to the store, when the image shown to the clerk is the first amount input image. By doing so, it becomes possible to guide the customer to use the store tag 13 instead of the two-dimensional barcode 11 when the customer makes a payment.

Explanation of Signs

[0065] 1 Store ID Tag 2 Customer Terminal 3 Payment Device 11 Two-dimensional Barcode 12 Piece of Paper 13 Store Tag 14 Memory 15 Transmitter 201 Display 202 Input device 203 Camera 221 Input section 222 Control section 222B Payment data generation section 223 Image recognition section 225 Recording section 226 Output section

Claims

1. a store tag that is disposed in a store having a store ID for receiving payments and that retails to customers having a customer ID for making payments, the store tag including a memory that records store ID data that identifies the store ID, and a transmitter that wirelessly transmits the store ID data recorded in the memory for short-distance communication; a barcode that is placed in the store in pair with the store tag and contains information corresponding to the store ID identified by the store ID data recorded in the memory of the paired store tag; a payment device for making a payment of money made by the customer to the store; A customer terminal which is to be possessed by the customer and which constitutes a settlement system by a combination of the above. a recording device that records customer ID data that is data that identifies the customer ID; a receiver capable of receiving the store ID data from the transmitter of the store tag; a transmitting / receiving mechanism for transmitting data over a network; A display having a function of displaying an image; a camera that captures an image and generates image data relating to the captured image; an input device capable of inputting amount data which is data specifying a payment amount which is an amount to be paid by the customer to the store; A control unit that executes information processing; It is equipped with The control unit is When the customer brings the customer terminal closer to the store tag than a predetermined distance, the store ID data is received from the receiver that has received the store ID data from the transmitter of the store tag, and when the store ID data is received, a first amount input image that prompts the customer to input the payment amount is automatically displayed on the display; When the customer photographs the barcode with the camera, image data of the image including the barcode generated by the camera is received from the camera, the store ID data included in the barcode included in the image specified by the image data is read, and when the store ID data has been read, a second amount input image, which is an image that prompts the customer to input the payment amount, is automatically displayed on the display, and, When the customer receives the amount data input by inputting the payment amount into the first amount input image or the second amount input image displayed on the display using the input device, the store ID data received from the store tag or read from the barcode, the customer ID data read from the recording device, the amount data input from the input device, and route data indicating whether the amount data was input from the first amount input image or the second amount input image are linked to each other as payment data, which is information necessary to identify a payment from the customer to the store, and are transmitted from the transmission / reception mechanism to the payment device via the network. Customer terminal.

2. The control unit is configured to display the second amount input image on the display as a visually distinguishable image from the first amount input image displayed on the display when the second amount input image is displayed on the display. The customer terminal according to claim 1.

3. In addition to the store ID data, the memory further stores instruction data that instructs the control unit to display the first amount input information on the display, When the customer brings the customer terminal closer to the store tag than a predetermined distance, the control unit, which receives the store ID data and the instruction data from the receiver that receives the store ID data and the instruction data from the transmitter of the store tag, automatically causes the first amount input image to be displayed on the display. The customer terminal according to claim 1.

4. the control unit is adapted to display, on the display, an icon for launching a payment computer program, which is a computer program for transmitting the payment data to the payment device, and the control unit is adapted to launch the payment computer program upon receiving launch data generated by a customer making an input to the icon; In addition to the store ID data, the instruction data and the start-up data are further recorded in the memory, and when the customer brings the customer terminal closer to the store tag than a predetermined distance, the control unit, which receives the store ID data, the instruction data, and the start-up data from the receiver that has received the store ID data, the instruction data, and the start-up data from the transmitter of the store tag, automatically causes the display to display the first amount input image. The customer terminal according to claim 3.

5. a store tag that is disposed in a store having a store ID for receiving payments and that retails to customers having a customer ID for making payments, the store tag including a memory that records store ID data that identifies the store ID, and a transmitter that wirelessly transmits the store ID data recorded in the memory for short-distance communication; a barcode that is placed in the store in pair with the store tag and contains information corresponding to the store ID identified by the store ID data recorded in the memory of the paired store tag; a payment device for making a payment of money made by the customer to the store; A customer terminal which is to be possessed by the customer and which constitutes a settlement system by a combination of the above. A recording device that records customer ID data that is data that identifies the customer ID; a receiver capable of receiving the store ID data from the transmitter of the store tag; a transmitting / receiving mechanism for transmitting data over a network; A display having a function of displaying an image; a camera that captures an image and generates image data relating to the captured image; an input device capable of inputting amount data which is data specifying a payment amount which is an amount to be paid by the customer to the store; A control unit that executes information processing; The control unit in the customer terminal includes: a process for receiving the store ID data from the receiver that has received the store ID data from the transmitter of the store tag when the customer brings the customer terminal closer to the store tag than a predetermined distance, and automatically displaying on the display a first amount input image that prompts the customer to input the payment amount when the store ID data has been received; or a process for receiving, when the customer takes an image of the barcode with the camera, receiving from the camera image data of an image including the barcode generated by the camera, reading out the store ID data contained in the barcode included in the image specified by the image data, and automatically displaying on the display a second amount input image that prompts the customer to input the payment amount when the store ID data has been read out; a process of, when the customer receives the amount data input by inputting the payment amount into the first amount input image or the second amount input image displayed on the display using the input device, linking the store ID data received from the store tag or read from the barcode, the customer ID data read from the recording device, the amount data input from the input device, and route data indicating whether the amount data was input from the first amount input image or the second amount input image as payment data, which is information necessary to identify a payment from the customer to the store, and transmitting the data from the transmission / reception mechanism to the payment device via the network; A computer program for executing the following:

Images