Settlement device and transaction management system using the same

Abstract

To provide a settlement device capable of reducing development costs and maintenance costs of application software, and to provide a transaction management system using the settlement device.SOLUTION: A settlement device 2 comprises: at least one hardware unit 10 to be used in settlement processing: and a computer 20 for controlling the hardware unit and for processing transaction information. The computer 20 comprises: a hardware gateway 23 having a web socket server function 23a, and a function for controlling the hardware unit 10: and a web browser 24 having a web socket client function and constituting a front end 24a of an operation system. The hardware gateway 23 is provided independently of the front end 24a, and performs control of the hardware unit 10 and transmission of transaction information by performing web socket communication with the front end 24a.SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] The present invention relates to a payment device for performing payments using cash, electronic money, barcodes, etc., and a transaction management system using the same. [Background technology]

[0002] 2. Description of the Related Art Payment devices that accept payments using cash, electronic money, bar codes, etc., such as food ticket machines, ticket vending machines, various payment machines, and various document issuing machines, are widely used.

[0003] Fig. 4 is a block diagram showing the schematic configuration of a conventional transaction management system using a payment device. As shown in the figure, a payment device 2 installed in each store is connected to a cloud server 4 via the Internet 3. An operation application 31 that runs on an OS (Operation System) 21 such as Windows (registered trademark) is implemented in the payment device 2, and controls the entire payment device 2. In addition, in the payment device 2, hardware control middleware 32 such as ActiveX (registered trademark) or DLL (Dynamic Linking Library) runs together with the operation application 31 to control hardware units 10 such as a cash processing unit and a printer unit.

[0004] 4, a user of the payment device 2 purchases tickets and performs settlement processing using the operation application 31. The following describes the operation procedure when performing settlement processing with cash.

[0005] For example, when a user deposits one 1,000 yen note into the banknote unit following instructions on the screen, the hardware control middleware 32 instantly receives the deposit information from the unit control firmware 22, and the operation application 31 reflects the deposited amount on the screen. When the deposit is completed, the operation application 31 sends a change dispensing instruction to the unit control firmware 22 via the hardware control middleware 32. Every time a withdrawal operation is performed, the hardware control middleware 32 receives withdrawal information from the unit control firmware 22, and the operation application 31 reflects the withdrawal amount on the screen. When all change has been withdrawn, the transaction is complete, and the transaction data required for sales management is uploaded to the cloud server 4.

[0006] The transaction data is transmitted each time a transaction is completed using a unique protocol that matches the transaction data receiving program 51 on the cloud server 4 side. Alternatively, the transaction data is stored and transmitted collectively as a transaction data file at the end of the day or when a specified operation is performed on the operation application. The transaction data is stored in a database 52.

[0007] Regarding transaction management systems, for example, Patent Document 1 describes a receipt issuing device that constitutes a POS system by being connected to a POS terminal device that performs payment processing and an output device that performs output based on data. This receipt issuing device includes a server with a communication unit that communicates with the POS terminal device and the output device, and a printer unit that issues receipts, and the communication unit is connected to the output device via a web socket. The server receives a document that includes information about the receipt from the POS terminal device, and causes the printer unit to issue a receipt based on the document. [Prior art documents] [Patent documents]

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

[0009] The operation application 31 implemented in the conventional payment device 2 shown in Fig. 4 is an OS-native program that integrates the operation system and the hardware unit control system, so it was difficult to separate the two. Therefore, when the design of the payment device itself is changed, the functions implemented in the operating OS change, or the OS itself is changed, the operation application must be changed, resulting in a problem of poor software maintainability.

[0010] Furthermore, when building a cloud-linked system that collectively manages multiple payment devices, the sales management program and the operation application 31 are completely independent, so a unique mechanism for transmitting transaction information to the sales management program is required, which can easily increase development costs. In particular, when adopting a method of transmitting transaction data each time a transaction is completed, a communication function that follows the unique procedures and protocols of the transaction data receiving program 51 must be implemented on the operation application 31 side, which tends to increase the development costs of the operation application 31.

[0011] Furthermore, when upgrading the operation application 31, it is necessary to perform the upgrade for each payment device installed in each store, or to have a special mechanism for automatically switching programs at a specified time. This makes it difficult to upgrade the program on the payment device side, and increases maintenance costs.

[0012] The present invention has been made in consideration of the above circumstances, and an object of the present invention is to provide a payment device and a transaction management system using the same that can reduce the development costs and maintenance costs of application software. [Means for solving the problem]

[0013] In order to solve the above problems, a payment device according to the present invention is a device for processing cash or electronic money, and comprises at least one hardware unit used for payment processing, and a computer for controlling the hardware unit and processing transaction information, the computer comprises a hardware gateway having a WebSocket server function and a function for controlling the hardware unit, and a web browser having a WebSocket client function and constituting a front end of the operation system, the hardware gateway being provided independently of the front end, and controlling the hardware unit and transmitting transaction information by performing WebSocket communication with the web browser.

[0014] According to the present invention, the hardware unit control system and the operation system of the payment device can be completely separated, and the operation system can be placed on a cloud server. Therefore, even if software upgrade is required due to the addition of functions, the upgrade can be completed by simply replacing the software placed on the cloud server, and software maintenance costs can be saved. In addition, even if the OS function of the payment device is changed due to a design change or the OS itself is upgraded, there is no need to change the program of the operation system. In addition, general IT development methods can be used to develop the operation system, and there is no need for a development environment or development method that is dependent on the OS, which leads to savings in application development costs.

[0015] In the present invention, the hardware unit is preferably a cash processing unit, an electronic money settlement unit, an IC card reader, a barcode reader or a ticket printer.

[0016] In the present invention, it is preferable that the computer includes a main computer that manages the hardware unit and a user terminal connected to the main computer via a communication network, the user terminal having a touch panel display, the hardware gateway being implemented in the main computer, and the web browser being implemented in the user terminal.

[0017] In addition, a transaction management system according to the present invention comprises the above-mentioned payment device according to the present invention and a cloud server capable of data communication with the payment device via the Internet, and the cloud server includes a group of back-end programs that process transaction information sent from the payment device, and a database that stores the transaction information processed by the group of back-end programs.

[0018] In the present invention, it is preferable that the cloud server has a web server function, and the web content constituting the front end is placed on the cloud server. Effect of the Invention

[0019] According to the present invention, it is possible to provide a settlement device and a transaction management system using the same that can reduce the development costs and maintenance costs of application software. [Brief description of the drawings]

[0020] [Figure 1] FIG. 1 is a block diagram showing a schematic configuration of a transaction management system according to a first embodiment of the present invention. [Diagram 2] FIG. 2 is a block diagram showing a schematic configuration of a transaction management system according to a first embodiment of the present invention. [Diagram 3] FIG. 3 is a block diagram showing a schematic configuration of a transaction management system according to a second embodiment of the present invention. [Figure 4]FIG. 4 is a block diagram showing a schematic configuration of a conventional transaction management system using a settlement device. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0021] Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings.

[0022] 1 and 2 are block diagrams showing the schematic configuration of a transaction management system according to an embodiment of the present invention.

[0023] As shown in FIGS. 1 and 2, a transaction management system 1 includes a payment device 2 installed in each store, and a cloud server 4 capable of data communication with the payment device 2 via the Internet 3.

[0024] The payment device 2 is, for example, a ticket vending machine, and has a function of issuing meal tickets, facility use tickets, etc., when a predetermined amount is deposited. For this purpose, the payment device 2 includes a plurality of hardware units 10 used for payment processing, and a computer 20 that controls each hardware unit 10. The hardware units 10 are, for example, a cash processing unit (banknote unit, coin unit), an electronic money payment unit, an IC card reader, a barcode reader, a ticket printer, a receipt printer, etc. The computer 20 has a well-known configuration including a CPU (Central Processing Unit), memory, a GPU (Graphics Processing Unit), and a NIC (Network Interface Controller). A touch panel display 25 is connected to the computer 20.

[0025] In addition to an OS 21, various device drivers and application programs are installed in the computer 20. In particular, in this embodiment, a hardware gateway 23 having a WebSocket server function and controlling each hardware unit 10 via unit control firmware 22, and a Web browser 24 having a WebSocket client function and constituting a front end 24a of an operation system are implemented.

[0026] The unit control firmware 22 is a control program pre-installed in each hardware unit 10 that performs settlement processing, etc. For example, a coin unit is equipped with a coin storage and dispensing mechanism, an electronic circuit (hardware) for electronic control, and a control program written in the electronic circuit. The unit control firmware 22 corresponds to this control program, and performs functions such as controlling the hardware to dispense the required number of coins when it receives a coin dispensing instruction signal from the computer, and sending a completion signal to the computer when dispensing is completed.

[0027] The hardware gateway 23 is an application program that controls each hardware unit 10 via the unit control firmware 12. For example, when cash is deposited in the cash processing unit, the hardware gateway 23 receives deposit information, and when change is dispensed, outputs withdrawal information to the cash processing unit. The unit control firmware 12 is a control program for each hardware unit 10 that performs settlement processing and the like.

[0028] The hardware gateway 23 includes various middleware. In particular, the hardware gateway 23 according to this embodiment has a WebSocket server 23a for performing WebSocket communication with the front end, and a unit manager 23b for exchanging instructions and information with the hardware unit 10. That is, the hardware gateway 23 can perform WebSocket communication with a WebSocket client. WebSocket is one of computer communication protocols that provides a bidirectional communication channel on a single TCP connection. The WebSocket protocol is a protocol different from HTTP, and has been standardized by the IETF as RFC 6455. The hardware gateway 23 has the WebSocket server 23a, and thus can perform real-time communication with the web browser 24.

[0029] The web browser 24 is software for connecting to a web server to obtain and display web content, and is capable of web socket communication. Examples of the web browser 24 include Firefox (registered trademark) and Microsoft Edge (registered trademark). Generally, the latest general-purpose web browsers have a web socket client function, and therefore can perform web socket communication with the web socket server 23a.

[0030] The web browser 24 constitutes the front end of the operation system of the payment device 2. The front end of the operation system is web content that uses various JavaScript frameworks and libraries, and runs on the web browser 24 on the payment device 2.

[0031] On the other hand, the cloud server 4 is equipped with a group of back-end programs 41 for operation and a database 42 for sales management. The group of back-end programs 41 are various web application frameworks, etc. The operation screen and transaction screen displayed on the touch panel display 25 of the payment device 2 are composed of content (web content) written in HTML, CSS, JavaScript, etc., and the web content is placed on the cloud server 4 equipped with a web server function. In other words, the transaction screen, etc. are not stored on the payment device 2 side (except for the cache function of the web browser), but are dynamically generated through interactions with the cloud server 4 or downloaded each time.

[0032] The display operation of the transaction screen, etc. by the payment device 2 is similar to the series of display operations of the transaction screen that a web browser performs from accessing an online shopping website from a personal computer to purchasing a product. The personal computer only has a web browser installed, and all information required for online shopping can be obtained by downloading it from the website. As a result, even if an operation system needs to be upgraded to add new functions, the upgrade can be completed simply by replacing the program on the website. Similarly, the display operation of the transaction screen, etc. of the payment device 2 can be performed by simply updating the software (web content) on the cloud server 4 side, thereby reducing maintenance costs.

[0033] Furthermore, with the above configuration, even if the functions of the OS 21 of the payment device 2 change or the OS 21 itself is upgraded, the front-end and back-end program group 41 are not affected, so there is no need to change the programs of each payment device 2. Furthermore, since all general IT development methods can be used, this contributes greatly to reducing application development costs.

[0034] Next, the operation of the payment device 2 will be described. In Fig. 2, a user of the payment device 2 purchases tickets and performs settlement processing by operating a transaction screen provided on the web browser 24 by the front end 24a of the operation system. The operation procedure when making a payment by cash will be described below.

[0035] For example, when a user follows the instructions on the screen to select a 600 yen note, performs a touch operation, and then deposits one 1000 yen note into the bill unit, the deposit information is instantly transmitted in this order to the unit control firmware 12 implemented in the bill unit, the hardware gateway 23, and the front end 24a of the operation application running on the web browser 24, and is reflected as the deposit amount on the screen of the web browser 24. Two-way communication is always performed between the hardware gateway 23 and the front end 24a via web sockets.

[0036] When the deposit is completed, a change dispensing instruction for 400 yen is sent from the front end 24a to the hardware gateway 23, and the change dispensing instruction is further transmitted from the hardware gateway 23 to the unit control firmware 12 implemented in the change unit, and the coin unit dispenses four 100 yen coins.

[0037] The front-end 24a receives withdrawal information for each withdrawal operation via the same route as for deposit operations, and reflects the withdrawal amount on the screen. When all change has been dispensed, the transaction is complete, and the front-end 24a sends an http request (or an https request using SSL) to the back-end program group 41 on the cloud server 4. Sending transaction information to the back-end program group 41 can generally be completed with one round-trip http communication to a specified URL, so there is no need to implement a special communication procedure.

[0038] As described above, in the transaction management system 1 according to this embodiment, the hardware gateway 23 is disposed in the settlement device 2, and the hardware gateway 23 has a WebSocket server 23a, so that the hardware control system can be completely separated from the operation system. Here, the operation system is managed by the front end 24a, which runs on the web browser 24. Although the hardware gateway 23 is not integrated with the operation system, by using WebSocket, it can be operated without the user feeling a time lag even in situations that require real-time performance, such as the transmission of deposit information to the operation system.

[0039] FIG. 3 is a block diagram showing the configuration of a transaction management system according to the second embodiment of the present invention.

[0040] As shown in Fig. 3, the transaction management system 1 according to this embodiment is characterized in that the settlement device 2 in Fig. 1 is physically separated into a hardware unit control system device and an operation system device. The main computer 20A constituting the hardware unit control system device and the user terminal 20B constituting the operation system device are connected via a communication network 30 such as a wireless LAN, and the two perform WebSocket communication. In addition to the OS 21A, application programs such as a hardware gateway 23 having a WebSocket server 23a are installed in the main computer 20A. In addition to the OS 21B, application programs such as a web browser 24 having a WebSocket client function are installed in the user terminal 20B. The other configurations are the same as those of the first embodiment.

[0041] In addition to the effects of the invention according to the first embodiment, the transaction management system 1 according to this embodiment can use general-purpose user terminals such as tablet terminals as operation devices, thereby reducing system costs and improving convenience.

[0042] Although a preferred embodiment of the present invention has been described above, the present invention is not limited to the above embodiment, and various modifications are possible without departing from the spirit of the present invention, and it goes without saying that these modifications are also included within the scope of the present invention. [Explanation of symbols]

[0043] 1. Transaction Management System 2. Payment Device 3. Internet 4. Cloud Server 10 Hardware Units 12 Unit Control Firmware 20. Computers 20A Main Computer 20B User terminal 21, 21A, 21B OS (operating system) 22 Unit Control Firmware 23 Hardware Gateway 23a WebSocket Server 23b Unit Manager 24 Web Browser 24a Front End 25 Touch Panel Display 30 Communication Network 31 Operation Application 32 Hardware Control Middleware 41 Back-end programs 42 Database 51 Transaction data receiving program 52 Database

Claims

1. A payment device that processes cash or electronic money, At least one hardware unit used for payment processing; a computer for controlling the hardware unit and processing transaction information; The computer includes: a hardware gateway having a web socket server function and a function for controlling the hardware unit; A web browser having a web socket client function and constituting a front end of an operation system; A payment device characterized in that the hardware gateway is provided independently of the front end and controls the hardware unit and transmits transaction information by performing WebSocket communication with the web browser.

2. The payment device according to claim 1 , wherein the hardware unit is a cash processing unit, an electronic money payment unit, an IC card reader, a barcode reader or a ticket printer.

3. The computer includes a main computer that manages the hardware unit, and a user terminal that is connected to the main computer via a communication network; the user terminal has a touch panel display; the hardware gateway is implemented in the main computer; The payment device according to claim 1 , wherein the web browser is implemented in the user terminal.

4. A payment device according to any one of claims 1 to 3, a cloud server capable of data communication with the payment device via the Internet; The cloud server includes: A back-end program group for processing transaction information sent from the payment device; A transaction management system comprising a database for storing transaction information processed by the back-end programs.

5. The transaction management system according to claim 4 , wherein the cloud server has a web server function, and web content constituting the front end is placed on the cloud server.

Images