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.
Claims20
A TCP/IP architecture for enabling secure communication between a payment terminal and a merchant computing system, the TCP/IP architecture comprising:
- an IP registry service, including one or more processors, the IP registry service in operative communication with a payment terminal and a merchant browser via a network, wherein the IP registry service:
- receives, from the payment terminal, an IP address, port, and unique identifier associated with the payment terminal;
- receives, from the merchant browser, the unique identifier of the payment terminal;
- and
- in response to receiving the unique identifier, transmits the IP address and port of the payment terminal to the merchant browser such that the merchant browser can communicate with the payment terminal 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 merchant browser for a web address comprising the IP address of the payment terminal 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 payment terminal by removing the root domain name;
- and
- transmits the IP address of the payment terminal to the merchant browser, such that the merchant browser can communicate with the payment terminal via HTTPS protocol.
A computer-implemented method comprising:
- receiving, from a payment terminal, an IP address, port, and unique identifier associated with the payment terminal at an IP registry service;
- receiving, from a merchant browser, the unique identifier associated with the payment terminal at the IP registry service;
- in response to receiving the unique identifier, transmitting the IP address and port of the payment terminal to the merchant browser such that the merchant browser can communicate with the payment terminal over TCP/IP protocol via the IP address and the port;
- receiving, at a custom domain name system (DNS), a DNS lookup request from the merchant browser for a web address comprising the IP address of the payment terminal and a root domain name;
- and
- in response to receiving the DNS lookup request for the web address:
- translating, at the DNS, the web address into the IP address of the payment terminal by removing the root domain name;
- and
- transmitting, by the DNS, the IP address of the payment terminal to the merchant browser, such that the merchant browser can communicate with the payment terminal via HTTPS protocol.
Dependencies are inferred from the claim text.