Systems and methods for managing a payment terminal via a web browser
AssigneeBluefin Payment Systems LLC
InventorsTimothy William Barnett, Donal McCarthy
Life of this patent
Estimating the term…
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.
Claims10
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.
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.
Dependencies are inferred from the claim text.