JP6781659B2 - Payment system and information management device - Google Patents

Description

The present invention relates to a payment system and an information management device.

In recent years, in retail stores, restaurants, etc., a plurality of processing processes of payment processing have been distributed to payment terminals that accept payments, payment servers that execute payment processing, and the like to reduce the cost of the entire system. (See, for example, Patent Document 1).

For example, when making a payment at a restaurant, a clerk goes to a table seat with a payment terminal and receives a payment amount or the like from a customer on the spot. When the clerk inputs the payment amount and the like into the payment terminal, the payment terminal communicates with the payment server, and the payment server performs the payment processing in the payment. When the payment server properly completes the payment process, it notifies the payment terminal of the end of payment. The clerk can confirm the end of payment through the payment terminal.

Japanese Unexamined Patent Publication No. 2003-233874

However, if a plurality of processing processes of payment processing are dispersed in this way, for example, even a clerk who has the authority to use the payment terminal moves the payment terminal to a place out of the eyes of the supervisor and illegally moves it. It becomes possible to make a payment.

The present invention has been made in view of such a point, and provides a payment system and an information management device capable of performing payment processing from a payment terminal only when the payment terminal exists within a predetermined area. The purpose is to do.

According to one aspect of the present invention, a first storage unit is attached with a wireless tag in which the first identification information is stored, receives payment information, and stores the payment information and the second identification information which is its own identification information. A payment processing device having a payment receiving device, a second storage unit for storing the payment information and the second identification information notified from the payment receiving device, and a payment processing unit for executing payment processing, and a predetermined area. Indicates whether or not the reader device that reads the first identification information from the wireless tag, the reader device, the wireless tag, the payment receiving device, and the wireless tag are detected within the reading range of the reader device. A third storage unit that holds management information associated with the detection information, and a tag information update unit that updates the detection information corresponding to the wireless tag identified by the first identification information acquired from the reader device. When a payment acceptance / rejection request is received from the payment processing device, the management information is referred to, and based on the detection information corresponding to the payment receiving device identified by the second identification information acquired from the payment processing device. A payment system including a payment availability notification unit for notifying the payment processing device of the availability of payment based on the payment information, and an information management device including the payment processing device is provided.

Further, according to one aspect of the present invention, the information management device of the payment system is provided.

According to the disclosed technology, it is possible to prevent fraudulent payment by performing the payment processing from the payment terminal only when the payment terminal exists in the predetermined area.

It is a figure explaining the payment system of 1st Embodiment. It is a figure which shows the payment system of the 2nd Embodiment. It is a figure which shows an example of the hardware composition of the RFID control device of 2nd Embodiment. It is a figure which shows an example of the tag information held by the RFID control device of the 2nd Embodiment. It is a figure which shows an example of the management information held by the management server of the 2nd Embodiment. It is a figure which shows an example of the hardware configuration of the payment terminal of the 2nd Embodiment. It is a sequence diagram which shows the payment process executed by the payment system of the 2nd Embodiment. It is a flowchart which shows the detection information update process executed by the management server of the 2nd Embodiment. It is a flowchart which shows the payment terminal confirmation process executed by the management server of the 2nd Embodiment. It is a sequence diagram which shows the payment process executed by the payment system of 3rd Embodiment.

Hereinafter, embodiments will be described with reference to the drawings.
[First Embodiment]
The payment system of the first embodiment will be described with reference to FIG.

FIG. 1 is a diagram illustrating a payment system according to the first embodiment.
The payment system 5 includes a payment receiving device 1, a payment processing device 2, a reader device 3, and an information management device 4.

The payment receiving device 1 is, for example, a payment terminal that receives payment information such as a payment amount and card information in response to an operation input by a clerk at a retail store, a restaurant, or the like. Such a payment receiving device 1 is attached with a wireless tag 1a in which the first identification information 1a1 is stored, receives the payment information 1b1 and stores the payment information 1b1 and the second identification information 1b2 which is its own identification information. It has a first storage unit 1b.

The payment processing device 2 is, for example, a payment server, a second storage unit 2a that stores payment information 1b1 and a second identification information 1b2 notified from the payment reception device 1, and a payment processing unit 2b that executes payment processing. Has.

The reader device 3 reads the first identification information 1a1 from the wireless tag 1a in the predetermined area. An antenna (not shown) is connected to the reader device 3, and the reading range by the antenna is set within a predetermined area. The reader device 3 outputs a predetermined radio wave from the antenna, communicates with the wireless tag 1a, and reads the first identification information 1a1.

The information management device 4 is communicably connected to the payment processing device 2 and the reader device 3. Such an information management device 4 has a third storage unit 4a, a tag information update unit 4b, and a settlement availability notification unit 4c.

The third storage unit 4a is a management information 4a1 in which the reader device 3, the wireless tag 1a, the payment receiving device 1, and the wireless tag 1a are associated with detection information indicating whether or not the reader device 3 is detected within the reading range of the reader device 3. To hold.

The tag information updating unit 4b updates the detection information corresponding to the wireless tag 1a identified by the first identification information 1a1 acquired from the reader device 3.
When the settlement acceptance / rejection notification unit 4c receives the settlement acceptance / rejection request from the settlement processing device 2, the settlement acceptance / rejection notification unit 4c corresponds to the settlement acceptance device 1 identified by the second identification information 1b2 acquired from the settlement processing device 2 with reference to the management information 4a1. Based on the detection information, the payment processing device 2 is notified whether or not the payment is possible based on the payment information 1b1.

Next, a payment method executed by such a payment system 5 will be described.
First, the information management device 4 holds the management information 4a1 in advance. The management information 4a1 includes, for example, a "reader device (" No. 1 ")", a "wireless tag (" aaa (first identification information 1a1) ")", and a "payment reception device (" bbb (second identification information 1b2)). ")" Is associated with it, and further, "detection information" is associated with it. The "detection information" is set to "undetected" as an initial value.

The reader device 3 (“No. 1”) is the first from the wireless tag 1a attached to the payment receiving device 1 (“bbb”) in the area where the payment is permitted, for example, at a predetermined timing. The identification information 1a1 (“aaa”) is read.

In the information management device 4, the tag information updating unit 4b acquires the first identification information 1a1 (“aaa”) of the wireless tag 1a from the reader device 3 (“No. 1”), and in the management information 4a1, the first The detection information corresponding to the identification information 1a1 (“aaa”) is updated to “detecting” (see FIG. 1). Therefore, the payment receiving device 1 (“bbb”) to which the wireless tag 1a for storing the first identification information 1a1 (“aaa”) is attached exists in the area where the payment is permitted. I understand.

Then, when the payment receiving device 1 receives the payment information 1b1 based on the operation input from the clerk, the payment receiving device 1 notifies the payment processing device 2 of the payment information 1b1 and the second identification information 1b2 (“bbb”). The payment processing device 2 notifies the information management device 4 of a payment approval / disapproval request together with the second identification information 1b2 (“bbbb”) before performing the payment processing based on the received payment information 1b1.

In the information management device 4, the settlement acceptance / rejection notification unit 4c executes the following processing when receiving the settlement acceptance / rejection request from the settlement processing device 2. That is, in the case of FIG. 1, the settlement acceptance / rejection notification unit 4c refers to the management information 4a1, and the detection information corresponding to the second identification information 1b2 (“bbbb”) acquired from the settlement processing device 2 is “detecting”. To determine that.

It can be seen that this is because the payment receiving device 1 (the second identification information 1b2 is "bbbb") existing in the area where the payment is allowed to be executed causes the payment processing device 2 to execute the payment processing. ..

As a result, the settlement acceptance / rejection notification unit 4c notifies the settlement processing device 2 of the permission of settlement based on the settlement information 1b1 based on such a determination.
The payment processing device 2 is located in the reading area of the reader device 3 (No. 1), and the payment receiving device 1 (the second identification information 1b2 is “bbb”” to which the first identification information 1a1 (“aaa”) is attached. ) Performs payment processing based on the payment information notified.

When the settlement processing is completed, the settlement processing device 2 notifies the settlement receiving device 1 to that effect. The clerk can confirm the completion of the payment process by using the payment receiving device 1.
In the payment system 5, the information management device 4 updates the detection information (of the management information 4a1) corresponding to the wireless tag 1a identified by the first identification information 1a1 acquired from the reader device 3. When the information management device 4 receives the payment approval / disapproval request from the payment processing device 2, the information management device 4 refers to the management information 4a1 and detects the payment reception device 1 identified by the second identification information 1b2 acquired from the payment processing device 2. Based on the information, the payment processing device 2 is notified whether or not the payment is possible based on the payment information 1b1.

As a result, the payment processing device 2 normally performs the payment processing from the payment receiving device 1 that exists only in the predetermined area. Therefore, it is possible to prevent the payment receiving device 1 from being taken out of the predetermined area and being illegally settled by the payment receiving device 1.

[Second Embodiment]
In the second embodiment, the payment system of the first embodiment will be described more specifically.
The payment system of the second embodiment will be described with reference to FIG.

FIG. 2 is a diagram showing a payment system according to the second embodiment.
The payment system 80 is applied to stores such as restaurants, and has an RFID (Radio Frequency IDentifier) control device 10, a payment terminal 40, a payment server 50, and a management server 60.

The RFID control device 10 is installed, for example, in the backyard of a store. The RFID control device 10 is connected to a first RFID reader 20 (reader device) installed in room A of the store and a second RFID reader 30 (reader device) installed in room B of the store. The range of the radio wave generated from the antenna 21 of the first RFID reader 20 is in the A room. Further, the range of the radio wave generated from the antenna 31 of the second RFID reader 30 is in the B room.

The RFID control device 10 controls such a first RFID reader 20 to cause the first RFID reader 20 to read the tag ID (first identification information) from the RFID tag in the room A. Similarly, the RFID control device 10 controls the second RFID reader 30 to cause the second RFID reader 30 to read the tag ID from the RFID tag in the room B. The RFID control device 10 holds the tag ID read by the first RFID reader 20 for each first RFID reader 20, and holds the tag ID read by the second RFID reader 30 for each second RFID reader 30. Further, when the RFID control device 10 acquires the tag IDs from the first and second RFID readers 20 and 30, it notifies the management server 60 of those tag IDs.

In addition, the RFID control device 10 causes the first and second RFID readers 20 and 30 to read the tag ID of the RFID tag in response to the tag ID reading request from the management server 60, and acquires the read tag ID. Is also possible.

The payment terminal 40 (payment reception device) is, for example, a handy type terminal that can wirelessly communicate with the payment server 50 and can be carried by a clerk. Such a payment terminal 40 receives payment information such as a payment amount and card information in response to an operation input by a clerk. The payment terminal 40 is provided with, for example, a reading device for reading a magnetic stripe or an IC chip attached to a card. Further, the payment terminal 40 notifies the payment server 50 of the payment information and the terminal ID (second identification information) that identifies the payment terminal 40, and causes the payment server 50 to execute the payment process based on the payment information. Further, FIG. 2 shows a case where an RFID tag 47 in which a tag ID is stored is attached to the surface of the payment terminal 40.

The payment server 50 is communicably connected to the payment terminal 40 and the management server 60. The payment server 50 (payment processing device) may be wirelessly connected to the management server 60 in the same manner as the payment terminal 40. The payment server 50 is notified of payment information and the terminal ID of the payment terminal 40 from the payment terminal 40. The payment server 50 executes the payment process based on the notified payment information, and notifies the payment terminal 40 of the payment completion notification when the payment is completed. Further, the payment server 50 notifies the management server 60 of the terminal ID of the payment terminal 40 together with the payment approval / disapproval request.

The management server 60 (information management device) is communicably connected to the RFID control device 10 via the network 70, and is also communicably connected to the payment server 50. The management server 60 uses the tag ID notified from the RFID control device 10, the information between the first and second RFID readers 20 and 30 that read the tag ID, the terminal ID of the payment terminal 40 notified from the payment server 50, and the like. Therefore, it is detected that the payment terminal 40 exists in the payment allowable area. The management server 60 determines whether or not the payment process by the payment terminal 40 is possible, and notifies the payment server 50 of the determination result. Details of the processing executed by the management server 60 will be described later. In some cases, the management server 60 can directly perform wireless communication with the payment terminal 40.

Next, the hardware configuration of each configuration included in the payment system 80 will be described.
First, a hardware configuration example of the RFID control device 10 will be described with reference to FIG.
FIG. 3 is a diagram showing an example of the hardware configuration of the RFID control device according to the second embodiment.

The RFID control device 10 has a control unit 11, a display 12 and an input unit 13 connected to the control unit 11, respectively.
The entire device of the control unit 11 is controlled by the CPU (Central Processing Unit) 11a. A RAM (Random Access Memory) 11b, an HDD (Hard Disk Drive) 11c, a graphic processing unit 11d, an input / output interface 11e, and a communication control unit 11f are connected to the CPU 11a via a bus 11g, respectively. There is.

The RAM 11b temporarily stores at least a part of an OS (Operating System) program to be executed by the CPU 11a and an application program for executing the RFID control device 10. Further, the RAM 11b stores various data required for processing by the CPU 11a, data generated by the processing, and the like.

The OS and application programs are stored in the HDD 11c.
A display 12 is connected to the graphic processing unit 11d. The graphic processing unit 11d causes the image to be displayed on the screen of the display 12 in accordance with the instruction from the CPU 11a.

An input unit 13 is connected to the input / output interface 11e. The input unit 13 inputs to a control unit 11 such as a keyboard, a mouse, or a touch panel attached to the display 12. Further, the input / output interface 11e can be connected to a portable recording medium interface capable of writing information to the portable recording medium 14 and reading information from the portable recording medium 14. The input / output interface 11e transmits the signal sent from the input unit 13 to the CPU 11a via the bus 11g. Further, the input / output interface 11e transmits a control signal from the CPU 11a to the input unit 13 via the bus 11g.

The communication control unit 11f is connected to the first RFID reader 20 and the second RFID reader 30 in a connection format of RS-232C (Recommended Standard 232 version C), USB (Universal Serial Bus), or LAN (Local Area Network), for example. There is. The communication control unit 11f transmits / receives data to / from the first RFID reader 20 and the second RFID reader 30. Further, the communication control unit 11f is communicably connected to the management server 60 via the network 70.

The control unit 11 may be configured to include a module including an FPGA (Field Programmable Gate Array), a DSP (Digital Signal Processer), or the like, or may not have the CPU 11a. In that case, each of the control units 11 includes a non-volatile memory (for example, EEPROM (Electrically Erasable and Programmable Read Only Memory), a flash memory, a flash memory type memory card, etc.) and stores the firmware of the module. The non-volatile memory can write firmware via the portable recording medium 14 or the communication control unit 11f. In this way, the control unit 11 can also update the firmware by rewriting the firmware stored in the non-volatile memory.

With the hardware configuration as described above, the processing function of the second embodiment can be realized.
The payment server 50 and the management server 60 also have at least the same hardware configuration as the control unit 11 of the RFID control device 10. Therefore, the description of the hardware configuration of the payment server 50 and the management server 60 will be omitted.

Next, the tag information held by such an RFID control device 10 will be described with reference to FIG.
FIG. 4 is a diagram showing an example of tag information held by the RFID control device of the second embodiment.

The RFID control device 10 includes, for example, a tag information holding unit that holds the tag ID 11c1 of the tag ID read from the first RFID reader 20 and the tag ID read from the second RFID reader 30 in the HDD 11c.

The tag information holding unit holds each RFID reader that has read the tag information 11c1. For example, as shown in FIG. 4, "001", "003", and "011" are held as the tag IDs read by the first RFID reader 20. Further, "005", "006", and "012" are held as the tag IDs read by the second RFID reader 30.

Next, the management information held by the management server 60 will be described with reference to FIG.
FIG. 5 is a diagram showing an example of management information held by the management server of the second embodiment.
The management server 60 includes, for example, a management information holding unit that holds the management information 61c1 in advance in the HDD.

The management information 61c1 indicates, for example, whether or not a payment terminal 40 that is permitted to be used in a predetermined room in the store exists in the room. Such management information 61c1 is within the reading range of the terminal ID that identifies the first and second RFID readers 20 and 30 and the payment terminal 40, the tag ID that identifies the RFID tag 47, and the first and second RFID readers 20 and 30. The RFID tag 47 is associated with the detection information indicating whether or not the RFID tag 47 is detected in advance. As described above, "not detected" is set as the initial value of the detection information.

For example, in the second embodiment, the first RFID reader 20 whose reading range is the A room is supported in the A room of the store. In the case shown in FIG. 5, in the room A to which the first RFID reader 20 is applied, the payment terminal 40 (terminal ID (“aa”)) to which the RFID tag 47 (tag ID “001”) is attached. Usage is set. Similarly, in room A, the use of the payment terminal 40 (terminal ID (“ab”)) to which the RFID tag 47 (tag ID “004”) is attached is set. In Room B, the use of a payment terminal 40 (terminal ID (“bd”, “bf”)) to which an RFID tag 47 (tag IDs “005” and “0012”) is attached is set.

Further, in the case of FIG. 5, the "detection information" corresponding to the payment terminal 40 (terminal ID ("ac")) to which the RFID tag 47 (tag ID "011") is attached is "detecting". Therefore, it can be seen that the payment terminal 40 (terminal ID (“ac”)) to which the RFID tag 47 (tag ID “011”) is attached exists in the room A. Further, since the other "detection information" is "undetected", it can be seen that the other payment terminal 40 does not exist in the room A.

Similarly, in the case of FIG. 5, the “detection information” corresponding to the payment terminal 40 (terminal ID (“bd”)) to which the RFID tag 47 (tag ID “005”) is attached is “detecting”. Therefore, it can be seen that the payment terminal 40 (terminal ID (“bd”)) to which the RFID tag 47 (tag ID “005”) is attached exists in the room B. Further, since the other "detection information" is "undetected", it can be seen that the other payment terminal 40 does not exist in the room B.

Further, in the case of FIG. 5, the payment terminal 40 (terminal ID (“ac”)) to which the RFID tag 47 (tag ID “011”) is attached is attached to the second RFID reader 30 in addition to the first RFID reader 20. It is set. Therefore, the payment terminal 40 (terminal ID (“ac”)) is set to be used in both rooms A and B.

The "detection information" shown in FIG. 5 is an example. The "detection information" is appropriately updated by the management server 60 based on the reading status of the first RFID reader 20 and the second RFID reader 30. Details of such updates will be described later.

Next, the hardware configuration of the payment terminal 40 will be described with reference to FIG.
FIG. 6 is a diagram showing an example of the hardware configuration of the payment terminal according to the second embodiment.
The description of the same configuration as the RFID control device 10 will be simplified (or omitted in some cases).

The payment terminal 40 has a control unit 41, a display 42 connected to the control unit 41, a touch panel 43, a numeric keypad 44, a card processing unit 45, and a printer unit 46, respectively. Further, the payment terminal 40 has an RFID tag 47.

The entire device of the control unit 41 is controlled by the CPU 41a. The RAM 41b, the flash memory 41c, the graphic processing unit 41d, the input / output interface 41e, and the communication control unit 41f are connected to the CPU 41a via the bus 41g, respectively.

The OS and application programs are stored in the flash memory 41c.
The communication control unit 41f wirelessly connects to the payment server 50 so as to be able to communicate with each other. Further, the communication control unit 41f also wirelessly connects to the management server 60, if necessary.

The touch panel 43 is associated with the display 42, detects a touch operation by the user, and notifies the CPU 41a of the detected signal.
The numeric keypad 44 includes buttons for execution keys and the like, as well as buttons for numbers from 0 to 9.

The card processing unit 45 is controlled by the control unit 41 to read or write information to a medium attached to the card. For example, if a magnetic stripe is added to the card, the card processing unit 45 reads the information stored in the magnetic stripe and writes the information to the magnetic stripe. If an IC chip is attached to the card, the card processing unit 45 reads the information from the IC chip and writes the information to the IC chip.

The printer unit 46 is controlled by the control unit 41 and outputs a receipt printed with the payment details.
The RFID tag 47 is attached to the surface of the housing of the payment terminal 40 or is held inside the payment terminal 40. In such an RFID tag 47, a tag ID which is an identification number for identifying the RFID tag 47 is recorded. The tag ID is a number that identifies the RFID tag 47, and is, for example, “001”, “003”, “011”, etc., as illustrated in FIGS. 4 and 5.

Next, the payment process executed by the payment system 80 will be described with reference to FIG. 7.
FIG. 7 is a sequence diagram showing a payment process executed by the payment system of the second embodiment.

The following payment processing is executed by each control unit (CPU) of the payment terminal 40, the payment server 50, and the management server 60.
[Step S20] The payment terminal 40 receives payment information such as a payment amount and card information based on an operation input from a clerk.

Then, the payment terminal 40 notifies the payment server 50 of the payment request message and the terminal ID together with the payment information.
[Step S21] When the payment server 50 receives the payment request message and the terminal ID together with the payment information in step S20, the payment server 50 notifies the management server 60 of the terminal ID received in step S20 and the payment terminal confirmation request message.

[Step S22] The management server 60 (tag information update unit) executes the detection information update process, receives the tag information from the RFID control device 10 (not shown), and receives the tag information in the management information 61c1. The detection information corresponding to the tag ID included in is updated.

The details of the detection information update process in step S22 will be described later.
[Step S23] The management server 60 (payment availability notification unit) refers to the management information 61c1 and confirms the detection information corresponding to the terminal ID received from the payment server 50. The management server 60 determines that the detection information is "detecting".

The details of the payment terminal confirmation process in step S23 will be described later.
[Step S24] Based on the process of step 23, the management server 60 (payment availability notification unit) normally determines whether or not the payment terminal 40 identified by the terminal ID notified from the payment server 50 exists in the predetermined area. To determine.

The next process proceeds to the process of step S25 when the payment terminal 40 identified by the terminal ID notified from the payment server 50 normally exists in the predetermined area, and is notified by the payment server 50. If the payment terminal 40 identified by the terminal ID does not normally exist in the predetermined area (there is an abnormality), the process proceeds to step S28.

[Step S25] The management server 60 (payment approval / disapproval notification unit) indicates that the payment terminal 40 identified by the terminal ID notified from the payment server 50 normally exists in the predetermined area on the payment server 50. Notify the normal confirmation telegram (permission of payment).

[Step S26] When the normal confirmation telegram is notified, the payment server 50 performs payment processing based on the payment information notified in step S20.
[Step S27] When the payment process is properly completed, the payment server 50 notifies the payment terminal 40 of the payment completion message.

From the above, the clerk recognizes that the payment process has been completed by the payment terminal 40.
[Step S28] The management server 60 (payment approval / disapproval notification unit) indicates that the payment server 50 has not detected the payment terminal 40 identified by the terminal ID notified from the payment server 50. Not permitted).

[Step S29] When the payment server 50 is notified of the abnormality confirmation message, the payment server 50 notifies the payment terminal 40 of the error message.
As described above, the clerk is prevented from performing the payment processing by the payment terminal 40.

Based on the above sequence, the payment process by the payment system 80 is executed.
Next, the detection information update process in step S22 in the sequence diagram of FIG. 7 will be described with reference to FIG.

FIG. 8 is a flowchart showing the detection information update process executed by the management server of the second embodiment.
The control unit (CPU) of the management server 60 executes the following processing each time tag information is received from the RFID control device 10.

[Step S22a] The management server 60 receives the tag information (for example, see FIG. 4) held by the RFID control device 10 from the RFID control device 10.
When the RFID control device 10 reads the tag ID of the RFID tag 47 by the first RFID reader 20 and the second RFID reader 30, the tag information including the read tag ID together with the first RFID reader 20 and the second RFID reader 30 (for example, FIG. 4) is notified to the management server 60.

Alternatively, the RFID control device 10 reads the tag ID of the RFID tag 47 by the first RFID reader 20 and the second RFID reader 30 in response to a request from the management server 60, and holds the tag information (for example, FIG. 4).

[Step S22b] The management server 60 selects the first and second RFID readers 20 and 30 from the management information 61c1 and the tag IDs associated with the first and second RFID readers 20 and 30.

For example, the "first RFID reader" and the "tag ID (" 001 ")" are selected from the management information 61c1 shown in FIG.
[Step S22c] The management server 60 includes the first and second RFID readers 20 and 30 selected in step S22b and the tag IDs associated with the first and second RFID readers 20 and 30 in the tag information. Judge whether or not.

The next process proceeds to the process of step S22d when the tag IDs for the selected first and second RFID readers 20 and 30 are included in the tag information, and the first and second RFIDs selected in the tag information are processed. If the tag IDs for the readers 20 and 30 are not included, the process proceeds to step S22e.

For example, since the tag information shown in FIG. 4 includes the "first RFID reader" and the "tag ID (" 001 ")" selected in step S22b, the process proceeds to step S22d.

[Step S22d] In the management information 61c1, the management server 60 updates the detection information associated with the first and second RFID readers 20 and 30 and the tag ID selected in step S22b to "detecting".

For example, in the management information 61c1 of FIG. 5, the detection information corresponding to the "first RFID reader" and the "tag ID (" 001 ")" included in the tag information shown in FIG. 4 is updated to "detecting".

[Step S22e] In the management information 61c1, the management server 60 updates the detection information associated with the first and second RFID readers 20 and 30 and the tag ID selected in step S22b to "not detected".

In this case, if the detection information remains "undetected", it is maintained without being updated.
For example, when the "first RFID reader" and the "tag ID (004)" are selected in step S22b, this combination is not included in the tag information of FIG. Therefore, in the management information 61c1 of FIG. 5, the detection information corresponding to the "first RFID reader" and the "tag ID (004)" is updated to "not detected".

[Step S22f] The management server 60 determines whether or not all the tag IDs in the management information 61c1 have been selected.
The next process proceeds to step S11 again when all the tag IDs in the management information 61c1 have not been selected, and when all the tag IDs in the management information 61c1 have been selected, the detection information End the update process.

As described above, the management server 60 performs the detection information update process.
That is, when the detection information is "detecting" in the management information 61c1, the RFID tag 47 corresponding to the detection information exists in a predetermined area which is the reading range of the first and second RFID readers 20 and 30. Is shown.

Next, the payment terminal confirmation process in step S23 in the sequence diagram of FIG. 7 will be described with reference to FIG.
FIG. 9 is a flowchart showing a payment terminal confirmation process executed by the management server of the second embodiment.

The control unit (CPU) of the management server 60 executes the following processing after step S22.
[Step S23a] The management server 60 receives the terminal ID from the payment server 50 (corresponding to step S21 in FIG. 6).

[Step S23b] The management server 60 (settlement possibility notification unit) determines whether or not the terminal ID received in step S23a is included in the management information 61c1.
The next process proceeds to step S23c when the terminal ID received in step S23a is included in the management information 61c1, and when the terminal ID received in step S23a is not included in the management information 61c1. The process proceeds to step S23e.

[Step S23c] The management server 60 (settlement possibility notification unit) determines whether or not the detection information corresponding to the terminal ID received in step S23a is being detected.
The next process proceeds to step S23d when the detection information corresponding to the terminal ID received in step S23a is being detected, and the detection information corresponding to the terminal ID received in step S23a is not being detected ( If it has not been detected), the process proceeds to step S23e.

[Step S23d] The management server 60 (settlement acceptance / rejection notification unit) determines that the payment terminal 40 identified by the terminal ID notified from the payment server 50 normally exists in the predetermined area on the payment server 50. To do.

[Step S23e] The management server 60 (payment availability notification unit) does not detect the payment terminal 40 identified by the terminal ID notified from the payment server 50 on the payment server 50 (the payment terminal 40 is abnormal). That) is judged.

As described above, the management server 60 can be identified by the terminal ID notified from the payment server 50, and can determine whether or not the payment terminal 40 for which the payment processing is to be executed exists in the predetermined area.

In the payment system 80, the management server 60 reads the terminal ID that identifies the first and second RFID readers 20 and 30 and the payment terminal 40, the tag ID that identifies the RFID tag 47, and the first and second RFID readers 20 and 30. It holds management information 61c1 that is previously associated with detection information indicating whether or not the RFID tag 47 is detected in the range. The management server 60 updates the detection information corresponding to the tag ID of the RFID tag 47 acquired from the RFID control device 10. When the management server 60 receives the payment terminal confirmation request from the payment server 50, the management server 60 refers to the management information 61c1 and makes a payment to the payment server 50 based on the detection information corresponding to the terminal ID of the payment terminal 40 acquired from the payment server 50. Notify whether the terminal is normal or not.

As a result, the payment server 50 can normally perform the payment processing from the payment terminal 40 that exists only in the predetermined area corresponding to the reading range of the first and second RFID readers 20 and 30. Therefore, it is possible to prevent the payment terminal 40 from being taken out of the predetermined area and being illegally settled by the payment terminal 40.

[Third Embodiment]
In the third embodiment, a case where the management server 60 executes another process when an abnormality is determined in the payment terminal confirmation process of the management server 60 in the payment process of the second embodiment will be described. ..

In the third embodiment, the same payment system 80 as in the second embodiment is used. Therefore, the description of the payment system 80 will be omitted.
Next, the payment process executed by the payment system 80 will be described with reference to FIG.

FIG. 10 is a sequence diagram showing a payment process executed by the payment system of the third embodiment.
In the process shown in the sequence diagram of FIG. 10, the management server 60 executes the detection information update process (FIG. 8) and the payment terminal confirmation process (FIG. 9), respectively, as in the second embodiment.

Further, in the sequence diagram of FIG. 10, the processes of steps S20 to S27 are executed in the same manner as in the sequence diagram of FIG. Therefore, the description of these processes will be omitted.
[Step S28a] In step S24, the management server 60 (payment approval / disapproval notification unit) does not normally have the payment terminal 40 identified by the terminal ID notified from the payment server 50 in the predetermined area (there is an abnormality). ), The following processing is executed. That is, the management server 60 notifies the payment terminal 40 of a stop request confirmation message for stopping the use of the payment terminal 40.

As a result, the payment terminal 40 stops processing the payment, and the clerk cannot perform the payment processing by the payment terminal 40.
In the payment system 80, when the management server 60 receives the payment terminal confirmation request from the payment server 50, the management server 60 refers to the management information 61c1 and detects the detection information corresponding to the terminal ID of the payment terminal 40 acquired from the payment server 50. If is not detected, the payment terminal 40 is notified of a stop request message to stop the payment by the payment terminal 40.

Unlike the second embodiment, the suspension of the use of the payment terminal 40 does not go through the payment server 50, so that the processing load of the payment server 50 can be reduced. Further, since the stop request message is directly notified to the payment terminal 40 without going through the payment server 50, the use of the payment terminal 40 can be stopped quickly.

The above processing function can be realized by a computer. In that case, a program that describes the processing content of the function that the computer should have is provided. By executing the program on a computer, the above processing function is realized on the computer.

The program describing the processing content can be recorded on a computer-readable recording medium. Computer-readable recording media include magnetic storage devices, optical disks, opto-magnetic storage media, semiconductor memories, and the like. Magnetic storage devices include HDDs, flexible disks (FD), magnetic tapes (MT), and the like. Optical discs include DVD (Digital Versatile Disc), DVD-RAM, CD (Compact Disc) -ROM, CD-R (Recordable) / RW (ReWritable), and the like. The magneto-optical storage medium includes MO (Magneto --Optical disk) and the like. The semiconductor memory includes a flash memory such as a USB (Universal Serial Bus) memory.

When the above program is distributed, for example, a portable recording medium such as a DVD or a CD-ROM on which the program is recorded is sold. It is also possible to store the program in the server computer and transfer the program from the server computer to another computer via the network.

A computer that executes the above program stores, for example, a program recorded on a portable recording medium or a program transferred from a server computer in its own storage device. Then, the computer reads the program from its own storage device and executes the processing according to the program. The computer can also read the program directly from the portable recording medium and execute the processing according to the program. In addition, the computer can sequentially execute processing according to the received program each time the program is transferred from the server computer.

Further, it is possible to replace a part or all of the processing described in the program with an electronic circuit. For example, at least a part of the above processing functions may be realized by an electronic circuit such as a DSP, an ASIC (Application Specific Integrated Circuit), or a PLD (Programmable Logic Device).

1 Payment receiving device 1a Wireless tag 1a1 1st identification information 1b 1st storage unit 1b1 Payment information 1b2 2nd identification information 2 Payment processing device 2a 2nd storage unit 2b Payment processing unit 3 Reader device 4 Information management device 4a 3rd storage unit 4a1 Management information 4b Tag information update unit 4c Payment availability notification unit 5 Payment system

Claims (6)

A payment receiving device to which a wireless tag in which the first identification information is stored is attached, and which has a first storage unit that receives the payment information and stores the payment information and the second identification information that is its own identification information.
A payment processing device having a second storage unit for storing the payment information and the second identification information notified from the payment reception device and a payment processing unit for executing payment processing, and a payment processing device.
A reader device that reads the first identification information from the wireless tag in a predetermined area, and
A third storage unit that holds management information associated with the reader device, the wireless tag, the payment receiving device, and detection information indicating whether or not the wireless tag is detected within the reading range of the reader device. When the tag information update unit that updates the detection information corresponding to the wireless tag identified by the first identification information acquired from the reader device and the payment processing device receives a payment approval / disapproval request, the management information is transmitted. With reference to the payment processing device, the payment processing device is notified of the possibility of payment based on the payment information based on the detection information corresponding to the payment receiving device identified by the second identification information acquired from the payment processing device. An information management device having a pass / fail notification unit,
Payment system with. When the detection information indicates that the wireless tag is detected within the reading range of the reader device, the payment acceptance / rejection notification unit notifies the payment processing device of the permission of the payment.
The payment system according to claim 1. When the detection information indicates that the wireless tag is not detected within the reading range of the reader device, the payment acceptance / rejection notification unit notifies the payment processing device of the disapproval of the payment.
The payment system according to claim 1. When the payment acceptance / rejection notification unit does not include the payment receiving device identified by the second identification information acquired from the payment processing device with reference to the management information, the payment processing device is charged with the payment. Notify the disapproval of
The payment system according to claim 1. When the detection information indicates that the wireless tag is not detected within the reading range of the reader device, the payment acceptance / rejection notification unit notifies the payment receiving device of the suspension of the payment.
The payment system according to claim 1. A payment receiving device and the wireless tag having a first storage unit to which a wireless tag in which the first identification information is stored is attached and which receives the payment information and stores the payment information and the second identification information which is its own identification information. Holds detection information indicating whether or not is detected within the reading range of the reader device that reads the first identification information from the wireless tag in a predetermined area, and management information in which the wireless tag and the reader device are associated with each other. 3rd storage unit and
A tag information update unit that updates the detection information corresponding to the wireless tag identified by the first identification information acquired from the reader device, and a tag information update unit.
When a payment approval / disapproval request is received from a payment processing device having a second storage unit that stores the payment information and the second identification information notified from the payment reception device and a payment processing unit that executes payment processing, the management information Refers to, and notifies the payment processing device of the possibility of payment based on the payment information based on the detection information corresponding to the payment receiving device identified by the second identification information acquired from the payment processing device. Settlement availability notification section and
Information management device with.

Images