Systems and methods for managing a payment terminal via a web browser

• US 10,311,421 B2
• Filed: 06/04/2018
• Issued: 06/04/2019
• Est. Priority Date: 06/02/2017
• Status: Active Grant

• Current Assignee: Bluefin Payment Systems LLC
• Original Assignee: Bluefin Payment Systems LLC
• Inventors: Barnett, Timothy William, McCarthy, Donal
• Primary Examiner(s): Coppola, Jacob C.
• Application Number:
  US15/997,269
• Publication Number:
  US 20180349875A1
• Time in Patent Office: 365 Days
• CPC Class Codes: G06Q 20/202 Interconnection or interaction of plural electronic cash registers [ECR] or to host computer, e.g. network details, transfer of information from host to ECR or from ECR to ECR
• CPC Class Codes: G07G 1/0009 Details of the software in the checkout register, electronic cash register [ECR] or point of sale terminal [POS]
• CPC Class Codes: H04L 2101/33 containing protocol addresses or telephone numbers
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 61/5014 using dynamic host configuration protocol [DHCP] or bootstrap protocol [BOOTP]
• CPC Class Codes: H04L 67/12 specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
• CPC Class Codes: H04L 69/169 Special adaptations of TCP, UDP or IP for interworking of IP based networks with other networks protocols for interworking, protocol conversion H04L69/08

Abstract

The present disclosure relates generally to communication with payment terminals via TCP/IP protocol. Using network technology and novel processes, in particular embodiments, the present systems and methods facilitate local network discovery and communication between a payment terminal and an electronic cash register (“ECR”) via a browser. For example, in certain embodiments, the present systems and methods leverage TCP/IP network technology to securely facilitate communications between SaaS ECR software running in a browser environment and one or more payment terminals.

Claims

1. A TCP/IP architecture for enabling secure communication, the TCP/IP architecture comprising:

an IP registry service, including one or more processors, the IP registry service in operative communication with a HTTPS/TLS enabled device and a software component via a network, wherein the software component is associated with a browser running on a computing device and wherein the IP registry service;

receives, from the HTTPS/TLS enabled device, an IP address, port, and unique identifier associated with the HTTPS/TLS enabled device;

receives, from the software component, the unique identifier of the HTTPS/TLS enabled device; and

in response to receiving the unique identifier, transmits the IP address and port of the HTTPS/TLS enabled device to the software component such that the browser running on the computing device can communicate with the HTTPS/TLS enabled device over TCP/IP protocol via the IP address and the port; and

a domain name system (DNS), wherein the DNS;

receives a DNS lookup request from the browser for a web address, the web address comprising the IP address of the HTTPS/TLS enabled device and a root domain name; and

in response to receiving the DNS lookup request for the web address;

translates the web address into the IP address of the HTTPS/TLS enabled device by removing the root domain name from the web address; and

transmits the IP address of the HTTPS/TLS enabled device to the browser, such that the browser can communicate with the HTTPS/TLS enabled device via HTTPS protocol.

2. The TCP/IP architecture of claim 1, wherein the software component is middleware in communication with the browser.

3. The TCP/IP architecture of claim 1, wherein the software component is a JavaScript SDK installed as a plug-in on the browser.

4. The TCP/IP architecture of claim 1, wherein the software component is third-party software for connecting with one or more Internet of Things devices.

5. The TCP/IP architecture of claim 1, wherein the HTTPS/TLS enabled device is a payment terminal.

6. A method comprising:

receiving, from a HTTPS/TLS enabled device, an IP address, port, and unique identifier associated with the HTTPS/TLS enabled device;

receiving, from a software component, the unique identifier of the HTTPS/TLS enabled device, wherein the software component is associated with a browser running on a computing device; and

in response to receiving the unique identifier, transmitting the IP address and port of the HTTPS/TLS enabled device to the software component such that the browser running on the computing device can communicate with the HTTPS/TLS enabled device over TCP/IP protocol via the IP address and the port;

receiving a DNS lookup request from the browser for a web address, the web address comprising the IP address of the HTTPS/TLS enabled device and a root domain name; and

in response to receiving the DNS lookup request for the web address;

translating the web address into the IP address of the HTTPS/TLS enabled device by removing the root domain name from the web address; and

transmitting the IP address of the HTTPS/TLS enabled device to the browser, such that the software component can communicate with the HTTPS/TLS enabled device via HTTPS protocol.

7. The method of claim 6, wherein the software component is middleware in communication with the browser.

8. The method of claim 6, wherein the software component is a JavaScript SDK installed as a plug-in on the browser.

9. The method of claim 6, wherein the software component is third-party software for connecting with one or more Internet of Things devices.

10. The method of claim 6, wherein the HTTPS/TLS enabled device is a payment terminal.