JP6194731B2 - Payment system - Google Patents

Description

  The technology disclosed in this specification relates to a payment system.

  A system for providing software to a terminal device by communication is known. For example, the software providing system disclosed in Patent Document 1 includes an intermediary terminal that mediates sales of software, a software management device that provides software to an information terminal, and an information terminal that uses software. When sales information including software information representing sold software and identification information for identifying the information terminal is input, the mediation terminal transmits the input sales information to the software management apparatus. When receiving the sales information, the software management apparatus stores the sales information. When the identification information is input by the user, the information terminal transmits transmission information including the input identification information to the software management apparatus. The software management device identifies sales information from the identification information included in the received transmission information, identifies software based on the identified sales information, and transmits the identified software to the information terminal.

JP 2005-32183 A

  By the way, a payment system for performing payment using electronic money is installed for each payment area, a payment terminal for payment, a relay device installed in the usage area where the payment terminal is installed, and each usage area. And a plurality of money management devices installed for each type of electronic money. When payment using electronic money is performed at the payment terminal, the payment terminal transmits information related to the executed payment to the money management device via the relay device. The money management device transmits the information after settlement to the settlement terminal via the relay device. In such a payment system, in order to actually perform payment using a payment terminal, payment software needs to be stored in the payment terminal.

  The conventional technology adopts the following configuration in order to provide payment software to a payment terminal. That is, the payment terminal connects a software provision request for providing software for payment of electronic money of a type desired to be used at the payment terminal via the relay device and the money management device so as to communicate with the money management device. To the installed software management device. The software management apparatus stores settlement software for performing settlement using the electronic money for each type of electronic money. When the software management device receives the software provision request via the relay device and the money management device, the software management device specifies the type of electronic money payment software that the payment terminal desires to use via the money management device and the relay device. Send the payment software to the payment terminal.

  In the system described above, the money management device communicates information related to the payment executed at the payment terminal via the relay device with the payment terminal. In addition, the money management device must send and receive software provision requests and payment software. Therefore, in the above-described system, particularly when the number of payment terminals increases, the processing load on the money management apparatus may become excessive.

  The present specification provides a technique capable of suppressing an excessive processing load on the money management apparatus as compared with the conventional technique.

  The payment system disclosed in this specification is installed in each usage area with one or a plurality of payment terminals for performing payment using at least one type of electronic money selected from a plurality of types of electronic money. A relay device that is communicably connected to one or a plurality of settlement terminals installed in the area, and is installed for each type of electronic money, and is communicably connected to a relay device that is installed for each use area. A money management device capable of transmitting and receiving information relating to payment using electronic money performed at a payment terminal via a relay device in a use area where the payment terminal is installed, and a money management device Payments for different software management devices that are communicably connected to a relay device installed in each usage area and perform payment using the electronic money for each type of electronic money And a, a software management unit that stores the software. The settlement terminal transmits a software provision request for requesting provision of settlement software for electronic money of the type desired to be used at the settlement terminal to the relay device in the use area where the settlement terminal is installed. When the relay device receives a software provision request from the settlement terminal, the relay device transmits information regarding the type of settlement software requested by the received software provision request to the software management device, while the software for the settlement software Is received, the received settlement software is transmitted to the settlement terminal that requested the provision of the settlement software. When the software management device receives information about the type of payment software from the relay device, the software management device sends the payment software corresponding to the information about the type of payment software to the relay device that has transmitted the information about the type of payment software. Send.

  In the payment system described above, when the relay apparatus receives a software provision request from the payment terminal, the relay apparatus transmits information regarding the type of payment software requested by the received software provision request to the software management apparatus. When the software management device receives information about the type of payment software from the relay device, the software management device sends the payment software corresponding to the information about the type of payment software to the relay device that has transmitted the information about the type of payment software. Send. The relay device transmits payment software to the payment terminal. That is, in the payment system described above, the money management apparatus does not need to send / receive software provision requests and payment software. Compared to a conventional system in which the money management device needs to send and receive software provision requests and payment software, it is possible to suppress an excessive processing load on the money management device.

The figure which shows typically the structure of the payment system of an Example. The flowchart which shows the process which the control part of a payment terminal performs. The flowchart which shows the process which the control part of a relay apparatus performs. The flowchart which shows the process which the control part of a software management apparatus performs. The sequence chart which shows the specific example of the process which a payment system performs.

  The main features of the embodiments described below are listed. In addition, the technical elements shown below are independent technical elements and exhibit technical usefulness alone or in various combinations, and are not limited to the combinations described in the claims at the time of filing. .

(Characteristic 1) The payment software is used for executing communication related to payment using electronic money between the payment terminal and the electronic money software necessary for the payment terminal to handle electronic money. And necessary communication software. When receiving information related to the type of payment software from the relay device, the software management device may transmit electronic money software and communication software corresponding to the information related to the type of payment software to the relay device.

  According to this configuration, software necessary for the payment terminal to perform payment using electronic money can be appropriately provided to the payment terminal.

(Characteristic 2) The payment terminal may further transmit version information regarding the version of the payment software currently stored in the payment terminal to a relay device in the use area where the payment terminal is installed. When receiving the version information from the payment terminal, the relay device transmits the received version information to the software management device. On the other hand, when receiving the latest version of the payment software from the software management device, the relay device receives the latest version. The payment software may be transmitted to the payment terminal that has transmitted version information relating to the previous version of the payment software. When the software management apparatus receives version information from the relay apparatus and the settlement software related to the version information is updated to a new version, the software management apparatus uses the new version for settlement to the relay apparatus that transmitted the version information. Software may be sent.

  According to this configuration, the latest version of payment software can be provided to the payment terminal.

(Characteristic 3) When the settlement terminal is instructed to transmit a software provision request, the settlement terminal may not transmit the software provision request to the relay device while the settlement terminal is communicating with the relay device.

  While the payment terminal is communicating with the relay device (for example, communication related to payment), the communication load between the payment terminal and the relay device is large. According to the configuration described above, the payment terminal can transmit a software provision request to the relay device while avoiding an increase in communication load between the payment terminal and the relay device. Therefore, it can suppress that the communication load between a payment terminal and a relay apparatus becomes large too much.

(Configuration of payment system 2; Fig. 1)
A payment system 2 shown in FIG. 1 is a system for performing payment using electronic money. The payment system 2 includes a payment terminal 10, relay devices 20, 30 and 40, money management devices 50, 60 and 70, and a software management device 80.

(Payment terminal 10)
The payment terminal 10 is a terminal for performing payment using at least one type of electronic money among a plurality of types of electronic money (electronic money M1, M2, M3, etc. in FIG. 1). The settlement terminal 10 is installed in a store by a store manager, for example. In the example of FIG. 1, the payment terminal 10 is a terminal for performing payment using electronic money M1. The payment terminal 10 is installed within the area A1. In FIG. 1, only the payment terminal 10 is illustrated, but the payment system 2 includes one or more other payment terminals (not shown) in addition to the payment terminal 10.

  The payment terminal 10 includes a control unit 12 and a memory 14. The control unit 12 executes various processes according to programs in the memory 14. The contents of the process executed by the control unit 12 will be described in detail later. The memory 14 stores various programs. The memory 14 also has an area for storing (that is, installing) payment software necessary for making payment using the electronic money M1. The memory 14 also has an area for storing version information indicating the version of the settlement software (see versions X1 and Y1 in FIG. 4). Here, the payment software executes communication related to the payment using the electronic money M1 between the payment terminal 10 and the relay device 20 between the electronic money software necessary for the payment terminal 10 to handle the electronic money M1. This includes two types of software required for communication. Therefore, the settlement software version includes electronic money software version X1 and communication software version Y1. The electronic money software version X1 and the communication software version Y1 are represented by numbers such as “1.01”, and a larger number means a newer version.

  Furthermore, the memory 14 also has an area for storing information related to the settlement executed using the electronic money M1. The memory 14 also includes various information (a user ID, type information indicating the type (M1) of electronic money to be used) input when the user of the payment terminal 10 performs a request operation (described later), and the payment terminal. 10 also has an area for storing an area (area information indicating an area (A1) using 10).

  Although not shown in FIG. 1, the payment terminal 10 is a short-range wireless communication with an IC card that can use the electronic money M1, a mobile terminal with a built-in IC chip, or the like (hereinafter referred to as “payment medium”). A short-range wireless communication interface for communication is also provided. The control unit 12 of the payment terminal 10 communicates information related to payment using the electronic money M1 with the payment medium by performing short-range wireless communication with the payment medium via the short-range wireless communication interface.

  Although not shown in FIG. 1, the payment terminal 10 also includes a communication interface for performing communication (see arrow 100 in FIG. 1) with the relay device 20 installed in the usage area A1. . The control unit 12 of the payment terminal 10 executes the payment terminal 10 with the money management device 50 via the relay device 20 at every predetermined timing (for example, every time a predetermined time of the day arrives). Communication related to payment using the received electronic money M1 is executed. The payment terminal 10 does not communicate with the relay devices 30 and 40 installed outside the use area A1.

  Although not shown in FIG. 1, the payment terminal 10 also includes a connection unit for connecting to a POS (Point Of Sales) terminal (not shown) so as to be communicable. The payment terminal 10 is used by being connected to a POS terminal installed in the store via a connection unit so as to be communicable.

  In the payment system 2 of the present embodiment, the payment terminal 10 performs payment using the electronic money M1 with the payment medium, and further receives the electronic money M1 with the money management device 50 via the relay device 20. In order to execute the communication related to the payment used, the payment software (software for electronic money and communication software) needs to be stored in the memory 14 of the payment terminal 10. Processing for providing the payment software to the payment terminal 10 will be described in detail later.

(Relay device 20, 30, 40)
The relay devices 20, 30, and 40 relay communication between a payment terminal (the payment terminal 10 and the like in FIG. 1) and the money management devices 50, 60, and 70, and communication between the payment terminal and the software management device 80. Device. The relay apparatuses 20, 30, and 40 are installed for each use area (areas A1, A2, A3, etc. in FIG. 1), and are communicably connected to a payment terminal installed in the use area. The relay apparatuses 20, 30, and 40 are installed by a communication company for each usage area. In the example of FIG. 1, the relay apparatuses 20, 30, and 40 are installed in the use areas A1, A2, and A3, respectively. Further, in FIG. 1, only the relay devices 20, 30, and 40 are illustrated, but in another example, the settlement system 2 has one or more other relay devices (in addition to the relay devices 20, 30, and 40). (Not shown). The relay apparatuses 20, 30, and 40 can communicate with a payment terminal installed in the usage area regardless of the type of electronic money. For example, the relay device 20 can communicate with the payment terminal 10 installed in the usage area A1. The relay apparatuses 20, 30, and 40 have the same configuration. Below, the structure of the relay apparatus 20 is demonstrated.

  As illustrated in FIG. 1, the relay device 20 includes a control unit 22. The control unit 22 executes various processes according to a program in a memory (not shown). The contents of the process executed by the control unit 22 will be described in detail later. The relay device 20 communicates with the payment terminal 10 in the use area A1 (see arrow 100 in FIG. 1), and communicates with the money management devices 50, 60, and 70 (see arrow 300 in FIG. 1). It has a communication interface.

(Money management devices 50, 60, 70)
The money management devices 50, 60, and 70 are devices that manage various types of information related to settlement using electronic money for each type of electronic money (M1, M2, M3, etc.). Each of the money management devices 50, 60, and 70 has the same configuration. The money management devices 50, 60, and 70 are installed for each type of electronic money (M1, M2, M3, etc.) and are communicably connected to the relay devices 20, 30, and 40, respectively. In the example of FIG. 1, the money management devices 50, 60, and 70 correspond to electronic money types M1, M2, and M3, respectively. The money management device 50 or the like is installed by an electronic money provider that provides various types of electronic money. In addition, in the example of FIG. 1, only the money management devices 50, 60, and 70 are illustrated, but in another example, the payment system 2 includes one or more other than the money management devices 50, 60, and 70. Of money management apparatus (not shown). The money management devices 50, 60, and 70 can communicate with the relay devices 20, 30, and 40, respectively, regardless of the usage area. That is, for example, the money management device 50 can transmit and receive information regarding payment using the electronic money M1 performed at the payment terminal 10 to and from the payment terminal 10 via the relay device 20.

(Software management device 80)
The software management device 80 is a device that stores payment software for performing payment using the electronic money for each type of electronic money, and provides the payment software to the payment terminal in response to a request. The software management device 80 does not have a function of transmitting / receiving information related to payment with a payment terminal, unlike the money management device 50 or the like. The software management device 80 is installed by a software provider that provides settlement software corresponding to various electronic money. The software management device 80 is communicably connected to each of the relay devices 20, 30, and 40 (see arrow 200 in FIG. 2). In this embodiment, the software management device 80 is not connected to the money management device 50 or the like so as to be communicable.

  The software management device 80 includes a control unit 82 and a memory 84. The control unit 82 executes various processes according to programs in the memory 84. The contents of the process executed by the control unit 82 will be described in detail later. The memory 84 stores various programs. In addition, the memory 84 stores settlement software for performing settlement using the electronic money for each type of electronic money. Specifically, the memory 84 includes, for each of a plurality of types of electronic money, software 86 for electronic money necessary for the payment terminal to handle the electronic money, and the payment terminal is installed in the use area of the payment terminal. The communication software 88 necessary for executing communication related to the settlement using the electronic money with the relay device is stored. The electronic money software 86 and the communication software 88 are respectively associated with version information indicating the version of the software. Whenever the latest version of each electronic money software and each communication software can be provided, the software provider updates each electronic money software and each communication software in the memory 84 to the latest version. Therefore, the latest version of electronic money software 86 and communication software 88 are always stored in the memory 84.

  Further, the memory 84 has an area for storing application information related to the application for use of the electronic money M1 by the user of the payment terminal 10. The user of the payment terminal 10 gives application information to the provider of the electronic money M1 and applies for the use of the electronic money M1. The application information includes a user ID for identifying the user of the payment terminal 10 and type information indicating information indicating the type (M1) of electronic money scheduled to be used. The provider of the electronic money M1 that has received an application for use of the electronic money M1 from the user of the payment terminal 10 accesses the software management device 80 and stores the application information (user ID, type information (M1)) in the memory 84. Let

  Although not shown in FIG. 1, the software management apparatus 80 also includes a communication interface for communicating with the relay apparatuses 20, 30, and 40.

  2 to 4, in order to install the payment software in the payment terminal 10, the control unit 12 of the payment terminal 10, the control unit 22 of the relay device 20, and the control unit of the software management device 80. The content of the process which each of 82 performs is demonstrated. Hereinafter, a case where payment software necessary for the payment terminal 10 to use the electronic money M1 is installed in the payment terminal 10 will be described as an example.

(Processing executed by the control unit 12 of the payment terminal 10; FIG. 2)
With reference to FIG. 2, the contents of processing executed by the control unit 12 of the payment terminal 10 in order to install payment software in the payment terminal 10 will be described. The user of the payment terminal 10 makes an application for use of the electronic money M1 in advance to the provider of the electronic money M1. The provider of the electronic money M1 that has accepted the use application accesses the software management device 80 and stores the application information in the memory 84.

  When the payment terminal 10 is turned on with the application completed, the control unit 12 starts the process of FIG. In S10, the control unit 12 monitors whether a predetermined request condition for requesting transmission of the settlement software is satisfied. The user of the payment terminal 10 can operate the POS terminal connected to the payment terminal 10 to perform a predetermined request operation for requesting transmission of payment software. For example, immediately after purchasing the payment terminal 10 or when enabling payment of new electronic money, payment software for performing payment using electronic money is not stored in the memory 14. In such a case, the user of the payment terminal 10 operates the POS terminal and performs the above request operation. The request operation indicates a user ID for identifying a user of the payment terminal 10, type information indicating the type of electronic money (for example, M1) used in the payment terminal 10, and an installation area (A1) of the payment terminal 10. Includes operations for entering area information. When a requested operation is performed at the POS terminal, the control unit 12 detects that the requested operation has been performed via a connection unit (not shown). When the request operation is performed, the control unit 12 stores the input user ID, type information (for example, M1), and area information (A1) in the memory 14. In this case, the control unit 12 determines YES in S10 and proceeds to S12.

  Further, as in the case where the process of FIG. 2 has been performed once or more in the past, the payment software for the electronic money M1 is already stored in the memory 14 of the payment terminal 10 at the time of S10. In some cases. In that case, when a predetermined request timing (for example, a predetermined time of the day) has arrived, the control unit 12 determines YES in S10 and proceeds to S12. That is, the above request timing means a timing for updating the settlement software already stored in the memory 14.

  In S12, the control unit 12 determines whether communication is being performed with the relay device 20 installed in the use area A1. For example, when the payment software for the electronic money M1 is already stored in the memory 14 of the payment terminal 10, the control unit 12 of the payment terminal 10 performs the predetermined timing (for example, within one day). Every time a predetermined time arrives, communication related to the payment performed at the payment terminal 10 is executed with the money management device 50 via the relay device 20. While communication is performed, the communication load between the payment terminal 10 and the relay device 20 is high. Therefore, it is determined whether or not the payment terminal 10 is communicating with the money management device 50 via the relay device 20 before the payment software installation process is started. When payment terminal 10 is not executing communication with relay device 20, control unit 12 determines NO in S12, and proceeds to S14. On the other hand, when the settlement terminal 10 is executing communication with the relay device 20, the control unit 12 determines YES in S12, and proceeds to S13. In S13, the control unit 12 waits for a predetermined time (for example, 1 minute). Thereafter, the control unit 12 returns to S12 and determines again whether or not communication with the relay device 20 is being performed. If the communication between the payment terminal 10 and the relay device 20 has been completed, the control unit 12 determines NO in S12 and proceeds to S14.

  In S <b> 14, the control unit 12 transmits a software provision request to the relay device 20. The software provision request includes the user ID of the user of the payment terminal 10, type information indicating the type (M1) of electronic money to be used, version information of payment software for the electronic money M1, and the installation area of the payment terminal 10. The area information indicating (A1) is included. The user ID, type information (M1), and area information (A1) are stored in the memory 14 when the above request operation is performed. When the payment software for the electronic money M1 is already stored in the memory 14 at the time of S14, the version information indicates the version of the payment software stored in the memory 14. The settlement software version mentioned here includes electronic money software version X1 (for example, “1.01”) and communication software version Y1 (for example, “1.02”). On the other hand, if payment software (electronic money software and communication software) for performing payment using the electronic money M1 is not stored in the memory 14 at the time of S14, the version X1 included in the software provision request And Y1 represents “0.00”.

  Next, in S <b> 16, the control unit 12 determines whether or not payment software for the electronic money M <b> 1 has been received from the relay device 20. When the settlement software is received from the relay device 20 before a predetermined waiting time (for example, 5 minutes) elapses, the control unit 12 determines YES in S16, and proceeds to S18. On the other hand, when the predetermined waiting time elapses before receiving the settlement software from the relay device 20, the control unit 12 determines NO in S16 and ends the process of FIG.

  In S18, the control unit 12 installs the received settlement software. That is, the control unit 12 stores the received payment software in the memory 14. When the received payment software is the latest version of the payment software already stored in the memory 14, in S18, the control unit 12 changes the payment software stored in the memory 14 to the latest version. Update to payment software. When S18 ends, the control unit 12 ends the process of FIG.

  When the payment software is installed in the memory 14, the control unit 12 performs short-range wireless communication with the payment medium that can use the electronic money M1, and between the payment medium and the payment medium. Thus, it becomes possible to communicate information relating to payment using the electronic money M1. Further, the control unit 12 is performed at the settlement terminal 10 with the money management device 50 via the relay device 20 at every predetermined timing (for example, every time a predetermined time of the day arrives). Communication related to settlement can be executed.

(Processing executed by the control unit 22 of the relay device 20; FIG. 3)
With reference to FIG. 3, contents of processing executed by the control unit 22 of the relay device 20 in order to provide payment software to the payment terminal 10 will be described. While the relay device 20 is operating, the control unit 22 performs the monitoring of S30 in FIG.

  In S30, the control unit 22 monitors whether a software provision request is received. As described above, when the settlement terminal 10 existing in the area A1 transmits a software provision request to the relay device 20 (see S14 in FIG. 2), the control unit 22 receives the software provision request. In this case, the control unit 22 determines YES in S30, and proceeds to S32.

  In S <b> 32, the control unit 22 transmits the user ID, type information, and version information included in the received software provision request to the software management apparatus 80. At this time, the control unit 22 does not transmit the area information included in the received software provision request to the software management apparatus 80. For this reason, the communication load is slightly reduced as compared with the case where the entire received software provision request is transmitted to the software management apparatus 80.

  Next, in S <b> 34, the control unit 22 determines whether payment software has been received from the software management device 80. When the settlement software is received from the software management device 80 before a predetermined waiting time (for example, 5 minutes) elapses, the control unit 22 determines YES in S34 and proceeds to S36. On the other hand, when the predetermined waiting time elapses before receiving the settlement software from the software management device 80, the control unit 22 determines NO in S34 and ends the process of FIG.

  In S <b> 36, the control unit 22 transmits the received payment software to the payment terminal 10. When S36 ends, the control unit 22 ends the process of FIG.

(Processing executed by the control unit 82 of the software management device 80; FIG. 4)
With reference to FIG. 4, the contents of processing executed by the control unit 82 of the software management device 80 in order to provide payment software to the payment terminal 10 will be described. While the software management device 80 is operating, the control unit 82 executes the monitoring of S50 in FIG.

  In S50, the control unit 82 monitors reception of the user ID, type information, and version information. As described above, when the relay device 20 transmits the user ID, type information (M1), and version information (see S32 in FIG. 3), the control unit 82 receives the user ID, type information, and version information. . At this time, the control unit 82 also knows that the transmission source such as the user ID is the relay device 20 based on information (for example, IP address) indicating the transmission source of the user ID, type information, and version information. Can do. In this case, the control unit 82 determines YES in S50, and proceeds to S52.

  In S52, the control unit 82 determines whether or not the received user ID and type information (M1) have been registered. Specifically, in S52, the control unit 82 determines whether or not application information (that is, user ID and type information) that matches the received user ID and type information (M1) exists in the memory 84. to decide. When application information that matches the received user ID and type information (M1) is stored in the memory 84, the control unit 82 determines YES in S52, and proceeds to S54. On the other hand, when application information that matches the received user ID and type information (M1) is not stored in the memory 84 (that is, application information is not stored at the time of S52), the control unit 82 It is determined NO in S52, and the process of FIG. In this case, the control unit 82 does not transmit the settlement software to the relay device 20.

  In S54, the control unit 82 specifies the electronic money software necessary for the payment terminal 10 to handle the electronic money M1 from the memory 84 based on the received type information (M1).

  Next, in S56, the control unit 82 specifies the version X1 of the electronic money software stored in the memory 14 of the payment terminal 10 based on the received version information.

  Next, in S58, the control unit 82 determines whether or not the version X2 of the electronic money software specified in S54 is newer than the version X1 specified in S56. When the version X2 is newer than the version X1, the control unit 82 determines YES in S58, and proceeds to S60. Also, when the version X1 specified in S56 is “0.00”, the control unit 82 determines YES in S58, and proceeds to S60. On the other hand, when the version X2 is the same as the version X1 (that is, when the latest version of electronic money software is stored in the memory 14 of the payment terminal 10), the control unit 82 determines NO in S58. Then, skip S60 and proceed to S62.

  In S60, the control unit 82 adds the electronic money software specified in S54 to the distribution list. Specifically, in S60, the control unit 82 adds the program data of the electronic money software specified in S54 to a distribution list that is a specific area secured in the memory 84.

  In S62, the control unit 82, based on the received type information (M1) and the transmission source (relay device 20) of the type information and the like, the payment terminal 10 connects the relay device 20 and the electronic money M1 from the memory 84. Identify the communication software necessary for communication related to payment using.

  Next, in S64, the control unit 82 specifies the version Y1 of the communication software stored in the memory 14 of the payment terminal 10 based on the received version information.

  Next, in S66, the control unit 82 determines whether or not the communication software version Y2 specified in S62 is newer than the version Y1 specified in S64. If the version Y2 is newer than the version Y1, the control unit 82 determines YES in S66, and proceeds to S68. Also, when the version Y1 specified in S64 is “0.00”, the control unit 82 determines YES in S66, and proceeds to S68. On the other hand, when the version Y2 is the same as the version Y1 (that is, when the latest version of communication software is stored in the memory 14 of the payment terminal 10), the control unit 82 determines NO in S66. , S68 is skipped and the process proceeds to S70.

  In S68, the control unit 82 adds the program data of the communication software specified in S62 to the distribution list secured in the memory 84.

  Next, in S <b> 70, the control unit 82 transmits settlement software (at least one of electronic money software and communication software) in the distribution list to the relay device 20. If there is no software in the distribution list at S70 (NO in S58 and NO in S66), the control unit 82 does not transmit the settlement software to the relay device 20 in S70. . When S70 ends, the controller 82 ends the process of FIG.

(Specific example: FIG. 5)
With reference to FIG. 5, the operation of each device when providing payment software for payment using the electronic money M1 to the payment terminal 10 will be described. In the example of FIG. 5, when the payment terminal 10 is turned on, the payment software for making payment using the electronic money M1 is not stored in the memory 14 of the payment terminal 10.

  The user of the payment terminal 10 makes an application for use of the electronic money M1 in advance to the provider of the electronic money M1. The provider of the electronic money M1 that has accepted the use application accesses the software management apparatus 80 and stores application information (user ID, type information (M1)) in the memory 84. A user of the payment terminal 10 performs a predetermined request operation using a POS terminal (not shown) connected to the payment terminal 10. The request operation includes a user ID for identifying the user of the payment terminal 10, type information indicating the type (M1) of electronic money used in the payment terminal 10, and area information indicating the installation area (A1) of the payment terminal 10. Includes input operations.

  When the request operation is performed (YES in S10 of FIG. 2), the settlement terminal 10 transmits a software provision request to the relay device 20 existing in the area A1 (S14 of FIG. 2). The software provision request includes a user ID, type information (M1), version information (0.00), and area information (A1). At this time, the payment software (software for electronic money and software for communication) is not stored in the memory 14 of the payment terminal 10. Therefore, the version information included in the software provision request indicates “0.00” for both the electronic money software version X1 and the communication software version Y1. When payment terminal 10 transmits a software provision request, relay device 20 receives the software provision request (YES in S30 of FIG. 3).

  When the relay device 20 receives the software provision request, the relay device 20 transmits the user ID, type information, and version information included in the received software provision request to the software management device 80 (S32 in FIG. 3). The relay device 20 does not transmit the area information to the software management device 80. The software management device 80 receives the user ID, type information, and version information (YES in S50 of FIG. 4).

  As described above, the application information indicating the combination of the user ID of the user of the payment terminal 10 and the type information (M1) is stored in advance in the memory 84 of the software management device 80 (YES in S52 of FIG. 4). ). Therefore, the software management device 80 specifies electronic money software necessary for the payment terminal 10 to handle the electronic money M1 from the memory 84 based on the received type information (M1) (S54 in FIG. 4). ). In the example of FIG. 5, payment software is not stored in the memory 14 of the payment terminal 10. Therefore, the electronic money software version X2 in the software management apparatus 80 is newer than the version X1 (“0.00”) indicated by the version information (YES in S58 of FIG. 4). Therefore, the software management apparatus 80 adds the specified electronic money software to the distribution list (S60 in FIG. 4).

  Next, based on the received type information (M1) and the transmission source of the type information (relay device 20), the software management device 80 causes the payment terminal 10 to connect the relay device 20 and the electronic money M1 from the memory 84. The communication software necessary for performing communication related to the payment using is specified (S62 in FIG. 4). The version Y2 of the communication software in the software management apparatus 80 is also newer than the version Y1 (“0.00”) indicated by the version information (YES in S66 of FIG. 4). The software management device 80 adds the specified communication software to the distribution list (S68 in FIG. 4).

  The software management device 80 transmits the settlement software (electronic money software and communication software) in the distribution list to the relay device 20 (S70 in FIG. 4). The relay device 20 receives the settlement software (YES in S34 of FIG. 3). When receiving the payment software, the relay device 20 transmits the received payment software to the payment terminal 10 (S36 in FIG. 3). The payment terminal 10 receives the payment software (YES in S16 of FIG. 2). When receiving the payment software, the payment terminal 10 installs the received payment software (S18 in FIG. 2).

  When the payment software is installed in the payment terminal 10, the payment terminal 10 performs the short-range wireless communication with the payment medium that can use the electronic money M1, thereby transferring the electronic money M1 to and from the payment medium. Information on the settlement used can be communicated. In addition, the payment terminal 10 is connected to the money management device 50 via the relay device 20 at every predetermined timing (for example, every time a predetermined time of the day arrives). It is possible to execute communication related to the settlement.

  The payment system 2 of the present embodiment has been described above. As described above, in the payment system 2 of the present embodiment, when the relay device 20 receives the software provision request from the payment terminal 10, the user ID, the type information (M1), and the version information included in the software provision request are The data is transmitted to the software management device 80 (S32 in FIG. 3). When receiving the type information from the relay device 20, the software management device 80 transmits the settlement software corresponding to the type information to the transmission source relay device 20 (S70 in FIG. 4). The relay device 20 transmits the payment software to the payment terminal 10 (S36 in FIG. 3). That is, in the payment system 2 of the present embodiment, the money management devices 50, 60, and 70 do not need to send and receive software provision requests and payment software. Compared to a conventional system in which the money management device needs to send and receive software provision requests and settlement software, it is possible to suppress an excessive processing load on the money management devices 50, 60, and 70.

  The payment software for the payment terminal 10 for the electronic money M1 uses the electronic money M1 between the payment terminal 10 and the relay device 20 and the electronic money software necessary for the payment terminal 10 to handle the electronic money M1. Communication software related to settlement. The software management device 80 transmits the electronic money software and the communication software to the relay device 20 (S70 in FIG. 4). Therefore, in the payment system 2 of this embodiment, the payment terminal 10 can provide the payment terminal 10 with two types of software necessary for the payment terminal 10 to make payment using the electronic money M1. In the settlement system 2 of the present embodiment, the electronic money software and the communication software can be individually updated.

  As described above, in this embodiment, the software management device 80 uses the electronic money software stored in the memory 84 of the software management device 80 rather than the electronic money software version X1 already stored in the payment terminal 10. When the version X2 is new, the electronic money software stored in the memory 84 is added to the distribution list (YES in S58 of FIG. 4, S60). Similarly, the software management device 80, when the communication software version Y2 stored in the memory 84 of the software management device 80 is newer than the communication software version Y1 already stored in the payment terminal 10, The communication software stored in the memory 84 is added to the distribution list (YES in S66, S68). The software management device 80 transmits the settlement software in the distribution list to the relay device 20 (S70). In other words, in this embodiment, the payment terminal 10 can be provided with the latest version (version X2, Y2) of payment software.

  In the present embodiment, the settlement terminal 10 does not transmit a software provision request to the relay device 20 while communicating with the relay device 20 (NO in S12 of FIG. 2), and communicates with the relay device 20. If not, a software provision request is transmitted to the relay device 20 (YES in S12, S14). For this reason, in the payment system 2 of the present embodiment, the payment terminal 10 transmits a software provision request to the relay device 20 while avoiding the increase in the communication load between the payment terminal 10 and the relay device 20. can do. Therefore, it can suppress that the communication load between the payment terminal 10 and the relay apparatus 20 becomes large too much.

  As mentioned above, although one Example of the technique disclosed by this specification was described in detail, these are only illustrations and do not limit a claim. The technology described in the claims includes various modifications and changes of the specific examples illustrated above. For example, the following modifications may be included.

(Modification 1) In the above embodiment, the software provision request transmitted to the relay device 20 by the control unit 12 of the payment terminal 10 includes a user ID, type information, version information, and area information (see FIG. 4). . However, the present invention is not limited to this, and the software provision request includes only the user ID, type information, and version information, and may not include area information. Even when the software provision request does not include area information, when the relay apparatus 20 receives the software provision request, the settlement terminal in which the received software provision request exists in the use area (A1) of the relay apparatus 20 Can be identified.

  The technical elements described in this specification or the drawings exhibit technical usefulness alone or in various combinations, and are not limited to the combinations described in the claims at the time of filing. In addition, the technology illustrated in the present specification or the drawings achieves a plurality of objects at the same time, and has technical utility by achieving one of the objects.

2: Payment system 10: Payment terminal 12: Control unit 14: Memory 20, 30, 40: Relay device 22: Control unit 50, 60, 70: Money management device 80: Software management device 82: Control unit 84: Memory 86: Electronic money software 88: communication software

Claims (4)

One or a plurality of payment terminals for performing payment using at least one type of electronic money selected from a plurality of types of electronic money;
A relay device installed for each use area and connected to be communicable with one or a plurality of payment terminals installed in the use area;
Installed for each type of electronic money, communicably connected to a relay device installed for each usage area, and settled with a payment terminal via a relay device in the usage area where the payment terminal is installed A money management device capable of transmitting and receiving information relating to payment using electronic money performed at a terminal;
A software management device different from the money management device, which is communicably connected to a relay device installed in each usage area, and for which payment software for performing payment using the electronic money for each type of electronic money A software management device for storing,
The payment terminal sends a software provision request for requesting the provision of electronic money payment software of the type desired to be used at the payment terminal to the relay device in the use area where the payment terminal is installed,
When the relay device receives a software provision request from the settlement terminal, the relay device transmits information regarding the type of settlement software requested by the received software provision request to the software management device, while the software for the settlement software , Send the received payment software to the payment terminal that requested the provision of the payment software,
When the software management device receives information about the type of payment software from the relay device, the software management device sends the payment software corresponding to the information about the type of payment software to the relay device that has transmitted the information about the type of payment software. Send,
Payment system. The payment software is software necessary for the payment terminal to execute communication related to payment using the electronic money between the payment software and the electronic money software required for the payment terminal to handle the electronic money. Including software,
The software management device, when receiving information about the type of payment software from the relay device, transmits electronic money software and communication software corresponding to the information about the type of payment software to the relay device. The payment system described in 1. The payment terminal further transmits version information regarding the version of the payment software currently stored in the payment terminal to the relay device in the use area where the payment terminal is installed,
The relay device further transmits the received version information to the software management device when receiving version information from the payment terminal, while receiving the latest version of payment software from the software management device. Send the latest version of the payment software to the payment terminal that sent the version information related to the previous version of the payment software,
When the software management apparatus receives version information from the relay apparatus and the settlement software related to the version information is updated to a new version, the software management apparatus uses the new version for settlement to the relay apparatus that transmitted the version information. The payment system according to claim 1 or 2, wherein the software is transmitted.   The payment terminal, when instructed to transmit a software provision request, does not transmit the software provision request to the relay apparatus while the payment terminal is communicating with the relay apparatus. The payment system according to item.

Images