Systems and methods for managing a payment terminal via a web browser
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.
1. A method, comprising:
receiving, from a payment terminal, an IP address, a port, and an identifier associated with the payment terminal at an IP registry service;
receiving, from a merchant browser, the identifier associated with the payment terminal;
in response to receiving the identifier from the merchant browser, transmitting the IP address and the port of the payment terminal to the merchant browser to facilitate communication of the merchant browser with the payment terminal using a TCP/IP protocol;
receiving, from the payment terminal, an updated IP address and the identifier associated with the payment terminal;
receiving, from the merchant browser, the identifier associated with the payment terminal; and
in response to receiving the identifier, transmitting the updated IP address of the payment terminal to the merchant browser to facilitate communication of the merchant browser with the payment terminal using the TCP/IP protocol.
2. The method of claim 1 , further comprising computing a spoofed domain name for connecting to the payment terminal based on the IP address.
3. The method of claim 2 , further comprising computing a second spoofed domain name for connecting to the payment terminal based on the updated IP address.
4. The method of claim 1 , further comprising dynamically assigning, via a dynamic host configuration protocol (DHCP), the updated IP address to the payment terminal.
5. The method of claim 1 , further comprising:
receiving, from the merchant browser, a first DNS lookup request for a first web address comprising the IP address of the payment terminal and a root domain name;
transmitting, to the merchant browser, the IP address of the payment terminal;
receiving, from the merchant browser, a second DNS lookup request for a second web address comprising the updated IP address of the payment terminal and the root domain name; and
transmitting, to the merchant browser, the updated IP address of the payment terminal.
6. The method of claim 5 , further comprising translating the second web address into the updated IP address of the payment terminal by removing the root domain name.
7. The method of claim 5 , wherein the first web address comprising the IP address omitting any decimal points or colons.
8. A system comprising:
a memory; and
at least one computing device in communication with the memory, the at least one computing device being configured to:
receive, from a first client, a first IP address and an identifier associated with the first client at an IP registry service;
receive, from a second client, the identifier associated with the first client;
in response to receiving the identifier from the second client, transmit the first IP address of the first client to the second client to facilitate communication between the first client and the second client over a network;
subsequent to the first client dynamically changing from the first IP address to a second IP address, receive, from the first client, the second IP address and the identifier associated with the first client;
receive, from the second client, the identifier associated with the first client; and
in response to receiving the identifier, transmit the second IP address of the first client to the second client to facilitate communication between the first client and the second client over the network.
9. The system of claim 8 , wherein the first client comprises a payment terminal and the second client comprises a merchant browser.
10. The system of claim 8 , wherein the at least one computing device is further configured to match the identifier to a row in a table of payment terminals.
11. The system of claim 8 , wherein the at least one computing device is further configured to compute an adjusted IP address based on the first IP address, wherein the first IP address is transmitted to the second client as the adjusted IP address.
12. The system of claim 8 , wherein the at least one computing device is further configured to receive configuration information for the first client comprising a MAC address.
13. The system of claim 8 , wherein the at least one computing device comprises a first computing device configured to execute the IP registry service and a second computing device configured to execute a DNS service.