Patent Grant
12099982
The present systems and methods relate generally to communication over TCP/IP protocol.
As computer technology continues to become more pervasive, businesses are all but required to implement computer software into some aspect of their operations. However, installing and managing software can be an expensive undertaking that requires an expertise that many businesses do not have, and do not desire to obtain. As a mechanism for servicing businesses in need of software, but have no desire to install or manage it, software as a service (“SaaS”) was developed. SaaS is a software distribution model where a third-party provider hosts applications and makes them available to customers over the Internet through a web browser. SaaS may remove the need for businesses to install and manage applications on their own computers or in their own data centers.
Businesses that use electronic cash registers (“ECR”) often use SaaS applications to interface with their ECRs. Additionally, businesses that use ECRs often accept check and credit card payments from customers by using an electronic payment terminal to process those types of payments. Data collection and other communication issues may occur when businesses use SaaS applications and ECRs to manage their payment terminals, because SaaS applications for ECRs, and the web browsers they employ, are typically not designed to communicate directly with payment terminals. In such situations, businesses are limited to either using a payment terminal specifically designed to work with an ECR's software, or face the inefficient and cumbersome task of gathering and reconciling data from multiple sources. Therefore, there is a long-felt but unresolved need for a system or method that can control, update, and communicate with payment terminals via a web browser.
As discussed above, SaaS systems typically operate in a browser-based environment. Further, some payment terminals may upload information to an ECR via a hard-wired universal serial bus (“USB”) connection (e.g., at the end of the day, end of a shift, or the like). As will be understood by one of ordinary skill in the art, a traditional browser cannot communicate through USB connections (for security purposes). Thus, any SaaS system operating in a browser-based environment normally cannot communicate with an ECR via a typical USB connection.
Some payment terminals include the ability to communicate with an ECR wirelessly. In these scenarios, the ECR may be programmed to communicate with the payment terminals over Wi-Fi or the like, eliminating the need for USB connections for uploading data to a SaaS system. However, for enhanced security, some systems include dynamically updated IP addresses for ECRs and/or payment terminals. For an ECR browser to communicate with a payment terminal with a dynamically-updated IP address, a user would need to re-configure the connection between the ECR and the payment terminal each time the payment terminal's IP address is updated (which may be periodically, and, in some embodiments, daily). Re-configuring the connection between the ECR and the payment terminal presents additional issues when a system includes multiple payment terminals (e.g., 2, 5, 20, 100, etc.).
Accordingly, and in various embodiments, the present systems and methods allows for continuous, secured connectivity of a payment terminal to an ECR loaded with a SaaS system via TCP/IP protocol, despite the payment terminal having a dynamically updated IP address.
Briefly described, and according to one embodiment, aspects of the present disclosure generally relate to systems and methods for controlling, updating, and communicating with payment terminals via a web browser over TCP/IP protocol. The systems and methods herein further relate to automatically updating a computing system communicating with a payment terminal over TCP/IP protocol with the payment terminal's IP address through an IP registry service (e.g., when the payment terminal's IP address is dynamically updated, the computing system will automatically be updated with the new IP address). The systems and methods herein still further relate to overcoming potential secure socket layer (“SSL”) security issues between web browser and payment terminal communication over TCP/IP protocol. As will be understood from discussions herein, various combinations of the payment terminal, the web browser, the IP registry service, and a custom domain name system (“DNS”) perform the functions described herein.
These and other aspects, features, and benefits of the claimed system(s) will become apparent from the following detailed written description of the preferred embodiments and aspects taken in conjunction with the following drawings, although variations and modifications thereto may be effected without departing from the spirit and scope of the novel concepts of the disclosure.
The accompanying drawings illustrate one or more embodiments and/or aspects of the disclosure and, together with the written description, serve to explain the principles of the disclosure. Wherever possible, the same reference numbers are used throughout the drawings to refer to the same or like elements of an embodiment, and wherein:
For the purpose of promoting an understanding of the principles of the present disclosure, reference will now be made to the embodiments illustrated in the drawings and specific language will be used to describe the same. It will, nevertheless, be understood that no limitation of the scope of the disclosure is thereby intended; any alterations and further modifications of the described or illustrated embodiments and any further applications of the principles of the disclosure as illustrated therein are contemplated as would normally occur to one skilled in the art to which the disclosure relates. All limitations of scope should be determined in accordance with and as expressed in the claims.
Whether a term is capitalized is not considered definitive or limiting of the meaning of a term. As used in this document, a capitalized term shall have the same meaning as an uncapitalized term, unless the context of the usage specifically indicates that a more restrictive meaning for the capitalized term is intended. However, the capitalization or lack thereof within the remainder of this document is not intended to be necessarily limiting unless the context clearly indicates that such limitation is intended.
The systems and methods disclosed herein relate to controlling, updating, and communicating with browser-enabled payment terminals via a web browser over TCP/IP protocol. The systems and methods herein further relate to automatically updating a computing system communicating with a payment terminal over TCP/IP protocol with the payment terminal's IP address through an IP registry service (e.g., when the payment terminal's IP address is dynamically updated, the computing system will automatically be updated with the new IP address). The systems and methods herein still further relate to overcoming potential SSL security issues between web browser and payment terminal communication over TCP/IP protocol. For purposes of this discussion, TCP/IP protocol refers to the suite of communication protocols used to interconnect network devices over both the internet and private networks.
In one embodiment, the system includes a payment terminal that supports communication over a network, for example, a PAX® Technology Limited terminal (although any terminal that supports communication over a network is contemplated as part of this system). According to particular embodiments, the system includes a payment terminal that exposes an HTTPS API or is otherwise configured to communicate over HTTPS protocol. In particular embodiments, the system includes a payment terminal that is configured to communicate via one or more other network protocols.
In some embodiments, the systems described herein include a browser plug-in or other software executable by a browser to be included in a merchant browser for communicating with the payment terminal that supports communication over a network, and other components of the system. In various embodiments, the merchant browser is configured for communicating with an IP registry service and a custom DNS. As will be understood from discussions herein, various combinations of the payment terminal, the merchant browser, a browser plug-in (e.g., JavaScript SDK), the IP registry service, and the custom DNS perform the functions described herein.
As discussed herein, in various embodiments, the system assigns a payment terminal a domain name based at least in part on the payment terminal's IP address and a root domain name. To overcome potential SSL security issues, in some embodiments, the systems discussed herein ensure that the payment terminal domain name matches a root domain name assigned to the SSL certificate (which is a prerequisite for establishing a secure connection via SSL). In one embodiment, the browser plug-in is enabled to use an IP address assigned to the payment terminal and designate a temporary, or “spoof” name, i.e., web address, for the payment terminal that includes the IP address and the root domain name assigned to the SSL certificate, thus linking the web address of the payment terminal with the SSL certificate of the payment terminal.
In various embodiments, upon a secured connection request by the merchant browser to the payment terminal via the spoof domain name, or web address of the payment terminal, the merchant browser is routed to the custom DNS service, such that the custom DNS service may translate the web address into the IP address of the payment terminal, allowing the merchant browser to initiate a secured connection to the payment terminal. Once a secured connection is initiated, the payment terminal presents the merchant browser with a copy of its SSL certificate, such that the merchant browser may authenticate the SSL certificate via a certificate authority, and verify the identity of the payment terminal (e.g., because the root domain name matches the domain name on the SSL certificate, the SSL certificate can be authenticated by the certificate authority). The secured connection is completed once the certificate authority authenticates or verifies the authenticity of the payment terminal's SSL certificate.
As will also be understood, the system may execute various functionalities described herein via a single component or more than one component of the system. For example, as further discussed below, the system may be configured to compute a “spoof” domain name. The system, in one embodiment, computes the spoof domain name via a JavaScript SDK installed on a browser. In at least one embodiment, the system computes the spoof domain name via the IP registry service (or a combination of the JavaScript SDK and the IP registry service).
As another example, the system, in the embodiment shown in the figures, includes several different components, such as an IP registry service and a DNS server. In one or more embodiments, the IP registry service and DNS server may be one system or one server.
These components and processes will be described herein.
Referring now to the figures, for the purposes of example and explanation of the processes and components of the disclosed systems and methods, reference is made to
As an example, and as shown in
Additionally, in some embodiments, the exemplary system environment 100 includes a merchant browser 106 and a SaaS vendor 108. In particular embodiments, the merchant browser 106 may operate on an ECR (e.g., a desktop computer, a tablet computer, a mobile device, or any other suitable ECR). In various embodiments, the SaaS vendor 108 provides software to facilitate use of the ECR. In at least one embodiment, the merchant browser 106 is configured to interface with the SaaS vendor 108.
In some embodiments, the exemplary system environment 100 includes a certificate authority 120 for providing secure communication between the merchant browser 106 and the payment terminal 102. For purposes of this discussion, a certificate authority 120 issues digital certificates, which are verifiable data files that contain credentials to help websites, people, and devices, represent their authentic online identity, as verified by the certificate authority 120.
In at least one embodiment, a user downloads and installs a JavaScript Software Development Kit (“SDK”) 205 on the merchant browser 106, or otherwise interfaces with the merchant browser 106, such that the JavaScript SDK 205 facilitates communication between the SaaS software loaded on the merchant browser 106 and the payment terminal 102.
Continuing with
In particular embodiments, the exemplary system environment 100 includes an IP registry service 116 for recording IP addresses and other information of various devices. In various embodiments, the IP registry service 116 may record payment terminal 102's terminal identification number and other identifying information (e.g., version number, MAC address, device type, serial number, etc.). In some embodiments, the IP registry service 116 may transmit IP addresses of payment terminals 102 to a merchant browser 106. In one or more embodiments, and as will be discussed herein, the IP registry service 116 may be responsible for creating a “spoof,” or temporary domain name of the payment terminal 102. As will be understood from discussions herein, the IP registry service 116 may record terminal identification numbers and IP addresses of any number of payment terminals and/or devices.
In at least one embodiment, the exemplary system environment 100 includes a custom DNS service 118 for providing identification services based on device domain names. For purposes of this discussion, a DNS service provides a naming system for computers, services, or other devices or resources connected to a network. In one or more embodiments, a DNS service translates a domain name into an IP address needed for identifying a device or service. For example, the domain name assigned to the payment terminal 102 (paymentterminal.com), would translate into the IP address of the payment terminal 102 (e.g., 192.168.1.100), which was assigned by the DHCP server 104.
In at least one embodiment, the various components of this exemplary system environment 100 are operatively connected via one or more networks 112. In one embodiment, the network 112 may be, but is not limited to, the Internet, and may involve the usage of one or more services (e.g., a web-deployed service with client/service architecture, a corporate local area network (“LAN”) or wide area network (“WAN”), a cellular data network, or through a cloud-based system). Moreover, as will be understood and appreciated by one having ordinary skill in the art, various networking components like routers, switches, hosts, etc. are typically involved in these communications. Although not shown in
Turning to
As shown in
Turning now to
In one or more embodiments, the IP registry service 116 may be configured to adjust the received IP address to a standard/normalized format. In one embodiment, if the received IP address is in IPv4 format, but does not include 12 integers, with a decimal placed after every third integer (e.g., the received IP address is “192.168.1.100”), the IP registry service 116 adjusts the received IP address by appending zeroes such that three integers (including placed zeros) are included between each decimal point. As will be understood, the system will append zeros between decimal points to the left of any existing integers (e.g., if a terminal IP address is “192.168.1.100,” the system may add two zeros to the left of the third “1”). For example, an IP address of 192.168.1.100 would be adjusted to 192.168.001.100. The system, in particular embodiments, may then utilize this standardized IP address format (e.g., with 12 integers) for creating a “spoof” domain name.
According to various embodiments, and as shown in
Now turning to
In at least one embodiment, and as will be discussed herein, the JavaScript SDK 205 may be responsible for creating a spoof, or temporary domain name of the payment terminal 102. In these embodiments, the merchant browser 106 loads the terminal identification number (e.g., 123555000) of the payment terminal 102 onto the JavaScript SDK 205. In various embodiments, the terminal identification number of the payment terminal 102 was previously provided to the SaaS vendor 108 and/or merchant browser 106 when the merchant initially setup the payment terminal 102.
In one or more embodiments, upon sending the IP registry service 116 the terminal identification number of the payment terminal 102, the JavaScript SDK 205 receives the corresponding adjusted address of the payment terminal 102 in return. In these embodiments, the JavaScript SDK 205 computes the spoof domain name for the payment terminal 102 by combining the root of the domain name assigned to the payment terminal 102, with the adjusted IP address of the payment terminal 102 stripped of all decimal points (e.g., the JavaScript SDK 205 may convert an adjusted IP address of 192.168.001.100 and a root domain name of paymentterminal.com to 192168001100.paymentterminal.com), such that the spoof domain name matches the SSL certificate assigned to the payment terminal. As will be understood, in various embodiments, the JavaScript SDK may be configured to receive the IP address of the payment terminal (e.g., 192.168.1.100) and convert the IP address to an adjusted IP address by appending zeros between decimals to create a 12 integer IP address, with three integers between each decimal point (e.g., 192.168.001.100).
Additionally, in various embodiments, the spoof domain name may be created using Internet protocol version 6 (“IPv6”) structure. For example, an IP address of 2001:db8::ff00:42:8329, in particular embodiments, would first be converted to a 32 integer format by appending zeros between each colon, e.g., 2001:0db8:0000:0042:0000:8a2e:0370:7334. Continuing with this example, the colons may then be removed from the expanded IPv6 representation, and the resulting spoof domain name would be 20010db80000004200008a2e03707334.paymentterminal.com.
Turning now to
Referring now to
In various embodiments, and as shown in
In various embodiments, the payment terminal 102 responds to the HTTPS connection request by sending the merchant browser 106 a copy of the payment terminal's 102 SSL certification, which matches the domain name of the payment terminal 102 known to the merchant browser 106 (paymentterminal.com) such that a successful SSL “handshake” may occur between the payment terminal 102 and the merchant browser 106. In various embodiments, upon obtaining a successful SSL handshake with the payment terminal 102, the merchant browser 106 verifies the payment terminal's 102 SSL certificate with the certificate authority 120 prior to completing the connection. At this point, in one or more embodiments, the system is configured to process a payment transaction.
For example, and as shown in
Turning now to
In particular embodiment, the system also includes a merchant's local area network (“LAN”), which facilitates an interconnected network of devices maintained by a merchant. In certain embodiments, the merchant's LAN 201 includes a payment terminal 102 and a merchant browser 106. In various embodiments, the merchant's LAN 201 may be connected to the custom TCP/IP payment architecture via a hardwired (e.g., Ethernet, USB, etc.) or wireless (e.g., Wi-Fi, Bluetooth, etc.) connection. In one or more embodiments, the merchant's LAN 201 may also be connected to the SaaS vendor 108 and/or the TMS 110 via a hardwired (e.g., Ethernet, USB, etc.) or wireless (e.g., Wi-Fi, Bluetooth, etc.) connection. In particular embodiments, one or more components of the merchant's LAN 203 may include processors, databases, servers, and other computational elements. In at least one embodiment, and as described above, the merchant browser 106 includes a JavaScript SDK 205.
According to various embodiments, the JavaScript SDK 205 may be responsible for communicating with the ECR API endpoints of the payment terminal 102 and computing the spoof domain name of the payment terminal 102. In one embodiment, the JavaScript SDK 205 includes a self-sufficient library such that all functions and objects are contained within the JavaScript SDK 205. In particular embodiments, the JavaScript SDK 205 supports fluent function calls, such that functions may return an object that can have success and failure callbacks attached to it. In at least one embodiment, the JavaScript SDK 205 may support multiple payment terminals 102 on the same HTML page. In various embodiments, the JavaScript SDK 205 may work with any suitable web browser (e.g., Google Chrome®, Internet Explorer®, Microsoft Edge®, Firefox®, Safari®, etc.). In some embodiments, the functionality of the JavaScript SDK may be executed/completed by a standalone application (e.g., a standalone application interfacing with a merchant browser and an IP registry service and/or DNS server). In further embodiments, the functionality of the JavaScript SDK may be execute/completed in one or more run-time environments, such as, for example Node.js.
From the foregoing, it will be understood that various aspects of the processes described herein are software processes that execute on computer systems that form parts of the system. Accordingly, it will be understood that various embodiments of the system described herein are generally implemented as specially-configured computers including various computer hardware components and, in many cases, significant additional features as compared to conventional or known computers, processes, or the like, as discussed in greater detail herein. Embodiments within the scope of the present disclosure also include computer-readable media for carrying or having computer-executable instructions or data structures stored thereon. Such computer-readable media can be any available media which can be accessed by a computer, or downloadable through communication networks. By way of example, and not limitation, such computer-readable media can comprise various forms of data storage devices or media such as RAM, ROM, flash memory, EEPROM, CD-ROM, DVD, or other optical disk storage, magnetic disk storage, solid state drives (SSDs) or other data storage devices, any type of removable non-volatile memories such as secure digital (SD), flash memory, memory stick, etc., or any other medium which can be used to carry or store computer program code in the form of computer-executable instructions or data structures and which can be accessed by a computer.
When information is transferred or provided over a network or another communications connection (either hardwired, wireless, or a combination of hardwired or wireless) to a computer, the computer properly views the connection as a computer-readable medium. Thus, any such a connection is properly termed and considered a computer-readable medium. Combinations of the above should also be included within the scope of computer-readable media. Computer-executable instructions comprise, for example, instructions and data which cause a computer to perform one specific function or a group of functions.
Those skilled in the art will understand the features and aspects of a suitable computing environment in which aspects of the disclosure may be implemented. Although not required, some of the embodiments of the claimed systems may be described in the context of computer-executable instructions, such as program modules or engines, as described earlier, being executed by computers in networked environments. Such program modules are often reflected and illustrated by flow charts, sequence diagrams, exemplary screen displays, and other techniques used by those skilled in the art to communicate how to make and use such computer program modules. Generally, program modules include routines, programs, functions, objects, components, data structures, application programming interface (API) calls to other computers whether local or remote, etc. that perform particular tasks or implement particular defined data types, within the computer. Computer-executable instructions, associated data structures and/or schemas, and program modules represent examples of the program code for executing steps of the methods disclosed herein. The particular sequence of such executable instructions or associated data structures represent examples of corresponding acts for implementing the functions described in such steps.
Those skilled in the art will also appreciate that the claimed and/or described systems and methods may be practiced in network computing environments with many types of computer system configurations, including personal computers, smartphones, tablets, hand-held devices, multi-processor systems, microprocessor-based or programmable consumer electronics, networked PCs, minicomputers, mainframe computers, and the like. Embodiments of the claimed system are practiced in distributed computing environments where tasks are performed by local and remote processing devices that are linked (either by hardwired links, wireless links, or by a combination of hardwired or wireless links) through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.
An exemplary system for implementing various aspects of the described operations, which is not illustrated, includes a computing device including a processing unit, a system memory, and a system bus that couples various system components including the system memory to the processing unit. The computer will typically include one or more data storage devices for reading data from and writing data to. The data storage devices provide nonvolatile storage of computer-executable instructions, data structures, program modules, and other data for the computer.
Computer program code that implements the functionality described herein typically comprises one or more program modules that may be stored on a data storage device. This program code, as is known to those skilled in the art, usually includes an operating system, one or more application programs, other program modules, and program data. A user may enter commands and information into the computer through keyboard, touch screen, pointing device, a script containing computer program code written in a scripting language or other input devices (not shown), such as a microphone, etc. These and other input devices are often connected to the processing unit through known electrical, optical, or wireless connections.
The computer that affects many aspects of the described processes will typically operate in a networked environment using logical connections to one or more remote computers or data sources, which are described further below. Remote computers may be another personal computer, a server, a router, a network PC, a peer device or other common network node, and typically include many or all of the elements described above relative to the main computer system in which the systems are embodied. The logical connections between computers include a local area network (LAN), a wide area network (WAN), virtual networks (WAN or LAN), and wireless LANs (WLAN) that are presented here by way of example and not limitation. Such networking environments are commonplace in office-wide or enterprise-wide computer networks, intranets, and the Internet.
When used in a LAN or WLAN networking environment, a computer system implementing aspects of the system is connected to the local network through a network interface or adapter. When used in a WAN or WLAN networking environment, the computer may include a modem, a wireless link, or other mechanisms for establishing communications over the wide area network, such as the Internet. In a networked environment, program modules depicted relative to the computer, or portions thereof, may be stored in a remote data storage device. It will be appreciated that the network connections described or shown are exemplary and other mechanisms of establishing communications over wide area networks or the Internet may be used.
While various aspects have been described in the context of a preferred embodiment, additional aspects, features, and methodologies of the claimed systems will be readily discernible from the description herein, by those of ordinary skill in the art. Many embodiments and adaptations of the disclosure and claimed systems other than those herein described, as well as many variations, modifications, and equivalent arrangements and methodologies, will be apparent from or reasonably suggested by the disclosure and the foregoing description thereof, without departing from the substance or scope of the claims. Furthermore, any sequence(s) and/or temporal order of steps of various processes described and claimed herein are those considered to be the best mode contemplated for carrying out the claimed systems. It should also be understood that, although steps of various processes may be shown and described as being in a preferred sequence or temporal order, the steps of any such processes are not limited to being carried out in any particular sequence or order, absent a specific indication of such to achieve a particular intended result. In most cases, the steps of such processes may be carried out in a variety of different sequences and orders, while still falling within the scope of the claimed systems. In addition, some steps may be carried out simultaneously, contemporaneously, or in synchronization with other steps.
In one embodiment, and as shown in
At step 304, the JavaScript SDK receives a unique identifier, such as a terminal identification number of a payment terminal from the merchant browser or other system component. In one embodiment, the system is configured to retrieve the unique identifier from the SaaS vendor. In various embodiments, the unique identifier of the payment terminal may be stored on the ECR and accessible via the merchant browser. In particular embodiments, the unique identifier of the payment terminal may be stored in a remote database.
Turning now to step 306, the JavaScript SDK sends the unique identifier of the payment terminal to an IP registry service and requests the IP address and listening port of the payment terminal from the IP registry service in return. At step 308, the system receives the adjusted IP address and listening port of the payment terminal from the IP registry service.
At step 310, the JavaScript SDK is configured to compute a spoof domain name of the payment terminal, such that the domain name of the payment terminal matches a domain name of a SSL certificate assigned to the payment terminal. In one embodiment, after receiving the adjusted IP address and listening port of the payment terminal, the system may compute the spoof domain name of the payment terminal by combining the root of the domain name assigned to the payment terminal, with the adjusted IP address of the payment terminal stripped of all decimal points (e.g., an IP address of 192.168.1.100 and a root domain name of paymentterminal.com, may be converted to 192168001100.paymentterminal.com). In particular embodiments, the system may compute the spoof domain name of the payment terminal by using any suitable combination of alphanumeric characters.
At step 312, the JavaScript SDK initiates a secured connection request with the payment terminal using the spoof domain name computed above in step 310. In various embodiments, the secured connection request is initiated over TCP/IP protocol. In at least one embodiment, the secured connection request is an HTTPS request. As will be understood, the secured connection request initiated in step 312 will be routed to the domain registry company (e.g., GoDaddy.com®) of the root domain name (e.g. paymentterminal.com). In various embodiments, the domain registry company will then route the request to the custom DNS service based on the merchant having previously created an A name server record that points to the custom DNS service, as will be further described herein. For the purposes of this discussion, an A name server record is used to delegate a subdomain to a set of name servers, which specialize in mapping domain names to their respective IP addresses. Thus, in this example, any web address containing the root domain “paymentterminal.com” is routed to the custom DNS service, such that the IP address corresponding to the web address may be retrieved.
At step 314, the JavaScript SDK receives the IP address of the payment terminal from the custom DNS service (e.g., the custom DNS service receives 192168001100.paymentterminal.com and returns 192.168.1.100). In one embodiment, the system is configured to store the IP address of the payment terminal in a temporary memory location (e.g. cache).
At step 316, the JavaScript SDK is configured to route the secured connection request initiated in step 312, directly to the payment terminal using the IP address of the payment terminal.
In various embodiments, at step 318, the merchant browser, (in some embodiments, via the JavaScript SDK), verifies the security certificate of the payment terminal by matching the domain name of the payment terminal with the domain name assigned to an SSL certificate. In particular embodiments, if the domain name of the payment terminal matches the domain name assigned to the SSL certificate, then a secure SSL “handshake” occurs, and an encrypted channel of communication is opened between the merchant browser and the payment terminal. In various embodiments, upon obtaining a secure SSL handshake, the system verifies the security certificate of the payment terminal using a preauthorized authority, which checks the SSL certificate as presented and validates its authenticity.
At step 404, the IP registry is configured to receive configuration information for the payment terminal. In one or more embodiments, the system may receive the configuration information from the merchant. In various embodiments, the system may receive the configuration information from the payment terminal, the terminal management software, the merchant browser, on any other component. In particular embodiments, configuration information may include a terminal identification number, serial number, other unique identifier, MAC address, version number, device type, and other like information. In one or more embodiments, the configuration information may be stored in a local database and/or a remote database.
At step 406, the IP registry receives the IP address and listening port of the payment terminal from the payment terminal, such that the IP address and listening port may be stored with, or otherwise matched to the registration information of the payment terminal. In one or more embodiments, the system receives the IP address and listening port from the payment terminal. In one embodiment, the system receives the IP address from the payment terminal after authenticating with the security token obtained in step 402. In particular embodiments, the system may receive the IP address and listening port from the TMS, the merchant browser, or any other suitable component. In one embodiment, the IP address and listening port may be stored in a local database. In another embodiment, the IP address and listening port may be stored in a remote database.
At step 408 the IP registry service is configured to compute an adjusted IP address of the payment terminal based on the IP address of the payment terminal received at step 406. In one or more embodiments, if the IP address received at step 406 does not include 12 integers, such that three integers are included in each part before and after each decimal point in the IP address, the IP registry service adjusts the received IP address. In various embodiments, the IP registry service is configured to adjust the received IP address by appending zeroes from left to right in each part that does not contain three integers, until three integers are included in each part (e.g., an IP address of 192.168.1.100 would be adjusted to 192.168.001.100).
At step 410, the IP registry is configured to receive a terminal identification number (or other unique identifier) of a payment terminal from a JavaScript SDK and/or a merchant browser. In various embodiments, at step 412, the IP registry is configured to match the received terminal identification number, to the payment terminal associated with the terminal identification number received. In particular embodiments, the terminal identification number is stored in a table with the IP address, MAC address, and listening port of the corresponding payment terminal. In one or more embodiments, the system may perform a database query, or other suitable search method, to identify the IP address and listening port associated with the received terminal identification number.
In response to receiving the terminal identification number at step 410, and upon locating the associated IP address and listening port at step 412, in various embodiments, at step 414, the IP registry sends the adjusted IP address computed at step 408, and the listening port of the payment terminal back to the JavaScript SDK and/or merchant browser.
Turning now to
In various embodiments, the exemplary process begins at step 502, where the DNS service is configured to receive a spoof domain name of the payment terminal from the JavaScript SDK. In various embodiments, the spoof domain name may contain letters, numbers, or symbols. In certain embodiments, the spoof domain name may include a pattern that resembles the IP address of the payment terminal.
At step 504, the DNS service converts the spoof domain name of the payment terminal into the IP address of the payment terminal, based on the name server of the system, which maps the payment terminal's domain name back to the IP address of the payment terminal as described above. As discussed herein, the IP address of the payment terminal may be included in the spoof domain name. For example, the IP address may be xxx and the spoof domain name may be xxx.yyy.com. Continuing with this example, the system converts the spoof domain name (e.g., xxx.yyy.com) to the IP address (e.g., xxx) by removing the root domain name (e.g., yyy.com). In particular embodiments, the system may add punctuation (e.g., decimals, periods, colons, semi-colons, etc.) at particular intervals, such as after every third or fourth integer.
At step 508 the DNS service is configured to send the IP address of the payment terminal back to the JavaScript SDK.
The DNS service process 500, in various embodiments, provides a mechanism that allows a merchant browser to locate a payment terminal via the spoof domain name assigned to the payment terminal. In particular embodiments, the DNS service process 500 facilitates a secured TCP/IP connection between the merchant browser running SaaS vendor software, and the payment terminal via a spoof domain name that matches the SSL certificate of the payment terminal and still maps back to the payment terminal.
In one or more embodiments, the DNS service calculates the IP address of the payment terminal as discussed above (e.g., the DNS service does not look up the IP address in any databases or the like). In at least one embodiment, the DNS service functionality is combined with the IP registry service described herein. As will be understood, in embodiments where the DNS service and IP registry service functionalities are combined, the system may be able to look up a payment terminal's IP address based on any pre-configured value added to a domain name (e.g., because the preconfigured value and the IP address are stored in a database as part of the IP registry service). In these embodiments, a spoof domain name for a payment terminal could include any suitable values attached to a domain name (e.g., unique identifier+domain name) and the system could return the IP address of a payment terminal upon receiving the spoof domain name by looking up the corresponding IP address of the payment terminal.
Alternative embodiments of the system may comprise features that are, in some respects, similar to the various components described above. Selected distinguishing features of these alternative embodiments are discussed below.
In addition to SaaS applications for electronic cash registers, this disclosure contemplates other SaaS applications that may require a secured connection to otherwise incompatible hardware devices, including but not limited to: customer relationship management applications, file and data sharing applications, financial management applications, messaging applications, and other like software applications.
Additionally, in one or more embodiments, the system may include a software component and/or middleware, e.g., software that acts as a bridge between an operating system or database and applications. In these embodiments, the software component and/or middleware may communicate with the systems described herein (e.g., IP registry service and/or DNS service) to create secure connections over TCP/IP protocol with various devices, including, but not limited to payment terminals and other Internet of Things (“IoT”) devices. Examples of middleware include, but are not limited to: transaction processing monitors, remote call procedures, message queues, automated backup systems, etc.
This disclosure is not limited to payment terminals. Other hardware components or devices that may use dynamic IP addresses, and require secured connection over TCP/IP protocol to otherwise incompatible SaaS applications are contemplated, including but not limited to: barcode scanners, smartphones and other smart devices, tablet computers, desktop computers, wearable devices, data acquisition devices, servers on internal networks, and any other browser-enabled and/or Internet of Things (“IoT”) devices. As will be understood, the system may function with any devices that are network connected, and, in particular embodiments, expose an HTTPS API.
Furthermore, this disclosure contemplates device discovery and secured connectivity between multiple browser-enabled and/or IoT devices. In these embodiments, the IP registry service and the DNS service may be installed on a local network to facilitate such device-to-device connectivity.
Various aspects of the present systems and methods will now be described. It will be understood by one of ordinary skill in the art that any of the aspects below may incorporate and include any other aspects mentioned below or features described herein. Therefore, the aspects below should be understood to include any combination of aspects and should not be limited to the combinations presented below. For example, although the second aspect includes the IP registry service of the first aspect, it may also include features of the sixteenth aspect, the first aspect, or the forty-second aspect.
According to a first aspect, the present systems and methods, in various embodiments, may include a TCP/IP architecture for enabling secure communication between a payment terminal and a merchant computing system, the TCP/IP architecture including: A) 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: 1) receives, from the payment terminal, an IP address, port, and unique identifier associated with the payment terminal; 2) receives, from the merchant browser, the unique identifier of the payment terminal; and 3) 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 B) a domain name system (DNS), wherein the DNS: 1) receives a DNS lookup request from the merchant browser for a web address including the IP address of the payment terminal and a root domain name; and 2) in response to receiving the DNS lookup request for the web address: i) translates the web address into the IP address of the payment terminal by removing the root domain name; and ii) 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.
According to a second aspect, the TCP/IP architecture or a method of the first aspect or any other aspect, wherein the DNS translates the web address into the IP address of the payment terminal by removing the root domain name and reformatting the IP address.
According to a third aspect, the TCP/IP architecture or a method of the second aspect, or any other aspect, wherein the DNS reformats the IP address by inserting decimals into the IP address.
According to a fourth aspect, the TCP/IP architecture or a method of the third aspect or any other aspect, wherein the web address includes the IP address in an adjusted format.
According to a fifth aspect, the TCP/IP architecture or a method of the fourth aspect or any other aspect, wherein the adjusted format of the IP address includes the IP address without any decimal points.
According to a sixth aspect, the TCP/IP architecture or a method of the fifth aspect or any other aspect, wherein the IP registry service creates the web address by combining the IP address of the payment terminal with the root domain name.
According to a seventh aspect, the TCP/IP architecture or a method of the sixth aspect or any other aspect, wherein the merchant browser requests verification of the authenticity of a security certificate associated with the payment terminal and the web address from a certificate authority.
According to an eighth aspect, the TCP/IP architecture or a method of the seventh aspect or any other aspect, wherein the merchant browser, upon receiving verification of the authenticity of the security certificate, communicates with the payment terminal via HTTPS protocol.
According to a ninth aspect, the TCP/IP architecture or a method of the eighth aspect or any other aspect, wherein the IP registry service and the DNS are operatively connected.
According to a tenth aspect, the TCP/IP architecture or a method of the ninth aspect or any other aspect, further including a payment processing system.
According to an eleventh aspect, the TCP/IP architecture or a method of the tenth aspect or any other aspect, wherein the payment processing system: A) receives an encrypted payment payload from the payment terminal; B) determines whether the encrypted payment payload has been compromised; and C) upon determining that the payment payload has not been compromised, facilitates decryption of the encrypted payment payload.
According to a twelfth aspect, the present systems and methods may include, in various embodiments, a computer-implemented method including: A) receiving, from a payment terminal, an IP address, port, and unique identifier associated with the payment terminal at an IP registry service; B) receiving, from a merchant browser, the unique identifier associated with the payment terminal at the IP registry service; C) 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; D) receiving, at a custom domain name system (DNS), a DNS lookup request from the merchant browser for a web address including the IP address of the payment terminal and a root domain name; and E) in response to receiving the DNS lookup request for the web address: 1) translating, at the DNS, the web address into the IP address of the payment terminal by removing the root domain name; and 2) 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.
According to a thirteenth aspect, the method or system of the twelfth aspect or any other aspect, wherein the DNS translates the web address into the IP address of the payment terminal by removing the root domain name and reformatting the IP address.
According to a fourteenth aspect, the method or system of the thirteenth aspect or any other aspect, wherein the DNS reformats the IP address by inserting decimals or colons into the IP address.
According to a fifteenth aspect, the method or system of the fourteenth aspect or any other aspect, wherein the web address includes the IP address in an adjusted format.
According to a sixteenth aspect, the method or system of the fifteenth aspect or any other aspect, wherein the adjusted format of the IP address includes the IP address without any decimal points or colons.
According to a seventeenth aspect, the method or system of the sixteenth aspect or any other aspect, wherein the IP registry service creates the web address by combining the IP address of the payment terminal with the root domain name.
According to a eighteenth aspect, the method or system of the seventeenth aspect or any other aspect, wherein the merchant browser requests verification of authenticity of a security certificate associated with the payment terminal and the web address from a certificate authority.
According to a nineteenth aspect, the method or system of the eighteenth aspect or any other aspect, wherein the merchant browser, upon receiving verification of the authenticity of the security certificate, communicates with the payment terminal via HTTPS protocol.
According to a twentieth aspect, the method or system of the nineteenth aspect or any other aspect, wherein the IP registry service and the DNS are operatively connected.
According to a twenty-first aspect, the present systems and methods may include, in various embodiments, a TCP/IP architecture for enabling secure communication between a HTTPS/TLS enabled device and a software component within a local network, the TCP/IP architecture including: A) 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 IP registry service: 1) receives, from the HTTPS/TLS enabled device, an IP address, port, and unique identifier associated with the HTTPS/TLS enabled device; 2) receives, from the software component, the unique identifier of the HTTPS/TLS enabled device; and 3) 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 software component can communicate with the HTTPS/TLS enabled device over TCP/IP protocol via the IP address and the port; and B) a domain name system (DNS), wherein the DNS: 1) receives a DNS lookup request from the software component for a web address including the IP address of the HTTPS/TLS enabled device and a root domain name; and 2) in response to receiving the DNS lookup request for the web address: i) translates the web address into the IP address of the HTTPS/TLS enabled device by removing the root domain name; and ii) transmits the IP address of the HTTPS/TLS enabled device to the software component, such that the software component can communicate with the HTTPS/TLS enabled device via HTTPS protocol.
According to a twenty-second aspect, the TCP/IP architecture or a method of the twenty-first aspect or any other aspect, wherein the software component is middleware in communication with the browser.
According to a twenty-third aspect, the TCP/IP architecture or a method of the twenty-first aspect or any other aspect, wherein the software component is a JavaScript SDK installed as a plug-in on the browser.
According to a twenty-fourth aspect, the TCP/IP architecture or a method of the twenty-first aspect or any other aspect, wherein the software component is third-party software for connecting with one or more IoT devices.
According to a twenty-fifth aspect, the present systems and methods may include, in various embodiments, a method including: A) receiving, from the HTTPS/TLS enabled device, an IP address, port, and unique identifier associated with the HTTPS/TLS enabled device; B) receiving, from a software component, the unique identifier of the HTTPS/TLS enabled device; and C) 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 a browser can communicate with the HTTPS/TLS enabled device over TCP/IP protocol via the IP address and the port; D) receiving a DNS lookup request from a browser for a web address comprising the IP address of the HTTPS/TLS enabled device and a root domain name; and E) in response to receiving the DNS lookup request for the web address: 1) translating the web address into the IP address of the HTTPS/TLS enabled device by removing the root domain name; and 2) transmitting the IP address of the HTTPS/TLS enabled device to browser, such that the software component can communicate with the HTTPS/TLS enabled device via HTTPS protocol.
According to a twenty-sixth aspect, the method or system of the twenty-fifth aspect or any other aspect, wherein the software component is middleware in communication with the browser.
According to a twenty-seventh aspect, the method or system of the twenty-fifth aspect or any other aspect, wherein the software component is a JavaScript SDK installed as a plug-in on the browser.
According to a twenty-eighth aspect, the method or system of the twenty-fifth aspect or any other aspect, wherein the software component is third-party software for connecting with one or more IoT devices.
According to a twenty-ninth aspect, the present systems and methods may include, in various embodiments, a system including a computer server including an IP registry service, the IP registry service in operative communication with a browser-enabled payment terminal and a merchant browser, wherein the IP registry service is configured for: A) receiving, from the browser-enabled payment terminal, a local IP address, port, and serial number of the browser-enabled payment terminal; B) receiving, from the merchant browser, the serial number of the browser-enabled payment terminal; and C) in response to receiving the serial number, transmitting the IP address and port of the browser-enabled payment terminal to the merchant browser such that the merchant browser can communicate with the browser-enabled payment terminal over TCP/IP protocol via the IP address and the port.
According to a thirtieth aspect, the present systems and methods may include, in various embodiments, a server including: A) a domain name system (DNS) for: 1) receiving a DNS lookup request from a merchant browser for a web address including an IP address of a payment terminal, wherein the merchant browser translated the IP address of the payment terminal into the web address; and 2) in response to receiving the DNS lookup request for the web address: i) translating the web address into the IP address of the payment terminal; and ii) transmitting the IP address of the payment terminal to the merchant browser.
According to a thirty-first aspect, the present systems and methods may include, in various embodiments, a system including: A) a computer server including an IP registry service, the IP registry service in operative communication with a browser-enabled payment terminal and a merchant browser, wherein the IP registry service is configured for: 1) receiving, from the browser-enabled payment terminal, a local IP address, port, and serial number of the browser-enabled payment terminal; 2) receiving, from the merchant browser, the serial number of the browser-enabled payment terminal; and 3) in response to receiving the serial number, transmitting the IP address and port of the browser-enabled payment terminal to the merchant browser such that the merchant browser can communicate with the browser-enabled payment terminal over TCP/IP protocol via the IP address and the port; and B) a domain name system (DNS) for: 1) receiving a DNS lookup request from a merchant browser for a web address including an IP address of a payment terminal, wherein the merchant browser translated the IP address of the payment terminal into the web address; and 2) in response to receiving the DNS lookup request for the web address: i) translating the web address into the IP address of the payment terminal; and ii) transmitting the IP address of the payment terminal to the merchant browser.
According to a thirty-second aspect, the present systems and methods may include, in various embodiments, a system including an executable computer program operatively connected to a merchant browser and an IP registry service, a DNS service, and a payment terminal, wherein the executable computer program is configured for: A) receiving a unique identifier associated with a payment terminal; B) transmitting the unique identifier to an IP registry service; C) requesting the IP address and listening port of the payment terminal from the IP registry service; D) receiving the IP address and listening port of the payment terminal from the IP registry service; and E) upon receiving the IP address and listening port of the payment terminal from the IP registry service: 1) computing a spoof domain name of the payment terminal; 2) initiating a secured connection request to the payment terminal; 3) receiving the IP address of the payment terminal from a DNS Service; and 4) upon receiving the IP address of the payment terminal from the DNS Service: i) routing the secured connection request directly to the payment terminal; ii) verifying a security certificate of the payment terminal; and iii) connecting to the payment terminal.
According to a thirty-third aspect, the system or a method of the thirty-second aspect or any other aspect, wherein the merchant browser is an electronic cash register.
According to a thirty-fourth aspect, the system or a method of the thirty-third aspect or any other aspect, wherein the executable computer code is operatively connected to the payment terminal via a wireless radio.
According to a thirty-fifth aspect, the system or a method of the thirty-fourth aspect or any other aspect, wherein the wireless radio includes a Bluetooth device.
According to a thirty-sixth aspect, the system or a method of the thirty-fifth aspect or any other aspect, wherein the executable computer program is a JavaScript SDK installed as a plug-in to the merchant browser.
According to a thirty-seventh aspect, the system or a method of the thirty-fifth aspect or any other aspect, wherein the executable computer program is middleware communicably connected to the merchant browser, the IP registry service, the DNS service, and the payment terminal.
According to a thirty-eighth aspect, the system or a method of the thirty-seventh aspect or any other aspect, wherein the secured connection request to the payment terminal is initiated via transport layer security (“TLS”) protocol.
According to a thirty-ninth aspect, the present systems and methods may include, in various embodiments, a method including: A) receiving a unique identifier associated with a payment terminal; B) transmitting the unique identifier to an IP registry service; C) requesting the IP address and listening port of the payment terminal from the IP registry service; D) receiving the IP address and listening port of the payment terminal from the IP registry service; and E) upon receiving the IP address and listening port of the payment terminal from the IP registry service: 1) computing a spoof domain name of the payment terminal; 2) initiating a secured connection request to the payment terminal; 3) receiving the IP address of the payment terminal from a DNS Service; and F) upon receiving the IP address of the payment terminal from the DNS Service: 1) routing the secured connection request directly to the payment terminal; 2) verifying a security certificate of the payment terminal; and 3) connecting to the payment terminal.
According to a fortieth aspect, the present systems and methods may include, in various embodiments, a system including an executable computer program operatively connected to a merchant browser and an IP registry service, a DNS service, and a payment terminal, wherein the executable computer program is configured for: A) receiving a unique identifier associated with a payment terminal; B) transmitting the unique identifier to the IP registry service; C) requesting the IP address and listening port of the payment terminal from the IP registry service; D) receiving the IP address, listening port, and spoof domain address of the payment terminal from the IP registry service; E) initiating a secured connection request to the payment terminal; F) receiving the IP address of the payment terminal from a DNS Service; and G) upon receiving the IP address of the payment terminal from the DNS Service: 1) routing the secured connection request directly to the payment terminal; 2) verifying a security certificate of the payment terminal; and 3) connecting to the payment terminal.
According to a forty-first aspect, the present systems and methods may include, in various embodiments, a system including an executable computer program operatively connected to a merchant browser and an IP registry service, a DNS service, and a payment terminal, wherein the executable computer program is configured for: A) receiving a unique identifier associated with a payment terminal; B) transmitting the unique identifier to an IP registry service; C) requesting the IP address and listening port of the payment terminal from the IP registry service; D) receiving the IP address, listening port, and spoof domain name of the payment terminal from the IP registry service; and E) upon receiving the IP address and listening port of the payment terminal from the IP registry service, transmitting the IP address, listening port, and spoof domain name of the payment terminal to a merchant browser such that the merchant browser can connect to the payment terminal via the IP address, listening port, and spoof domain name via HTTPS protocol.
According to a forty-second aspect, the present systems and methods may include, in various embodiments, a method including: A) receiving a unique identifier associated with a payment terminal; B) transmitting the unique identifier to an IP registry service; C) requesting the IP address and listening port of the payment terminal from the IP registry service; D) receiving the IP address, listening port, and spoof domain name of the payment terminal from the IP registry service; and E) upon receiving the IP address and listening port of the payment terminal from the IP registry service, transmitting the IP address, listening port, and spoof domain name of the payment terminal to a merchant browser such that the merchant browser can connect to the payment terminal via the IP address, listening port, and spoof domain name via HTTPS protocol.
Aspects, features, and benefits of the present disclosure will become apparent from the information disclosed herein. Variations and modifications to the disclosed systems and methods may be effected without departing from the spirit and scope of the novel concepts of the disclosure.
It will, nevertheless, be understood that no limitation of the scope of the disclosure is intended by the information disclosed in the exhibits or the applications incorporated by reference; any alterations and further modifications of the described or illustrated embodiments, and any further applications of the principles of the disclosure as illustrated therein are contemplated as would normally occur to one skilled in the art to which the disclosure relates. Various brand names and devices produced by certain companies (e.g., PAX®) may be included in this application (including the exhibits). As will be understood, these devices are exemplary only and other devices with similar functionality are contemplated as part of the systems and methods disclosed herein.
The foregoing description of the exemplary embodiments has been presented only for the purposes of illustration and description and is not intended to be exhaustive or to limit the systems and methods to the precise forms disclosed. Many modifications and variations are possible in light of the above teaching.
The embodiments were chosen and described in order to explain the principles of the disclosure and their practical application so as to enable others skilled in the art to utilize the disclosure and various embodiments and with various modifications as are suited to the particular use contemplated. Alternative embodiments will become apparent to those skilled in the art to which the present disclosure pertains without departing from their spirit and scope. Accordingly, the scope of the present disclosure is defined by the appended claims rather than the foregoing description and the exemplary embodiments described therein.
This application is a continuation of U.S. patent application Ser. No. 16/400,359, filed May 1, 2019, entitled “SYSTEMS AND METHODS FOR MANAGING A PAYMENT TERMINAL VIA A WEB BROWSER”, which is a continuation of U.S. patent application Ser. No. 15/997,269, filed Jun. 4, 2018, now U.S. Pat. No. 10,311,421, entitled “SYSTEMS AND METHODS FOR MANAGING A PAYMENT TERMINAL VIA A WEB BROWSER”, which claims priority to and the benefit under 35 U.S.C. § 119 of U.S. Provisional Patent Application No. 62/514,308, filed Jun. 2, 2017, and entitled “SAASCONEX,” each of which are incorporated herein by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4926475 | Spiotta et al. | May 1990 | A |
| 6286099 | Kramer | Sep 2001 | B1 |
| 6446092 | Sutter | Sep 2002 | B1 |
| 6484260 | Scott et al. | Nov 2002 | B1 |
| 6523032 | Sunkara | Feb 2003 | B1 |
| 6934664 | Webb et al. | Aug 2005 | B1 |
| 7028014 | Naclerio | Apr 2006 | B1 |
| 7386471 | Nack | Jun 2008 | B1 |
| 7546465 | Kent, Jr. et al. | Jun 2009 | B2 |
| 7731435 | Piersol et al. | Jun 2010 | B2 |
| 7941673 | Trimberger | May 2011 | B1 |
| 8315948 | Walker et al. | Nov 2012 | B2 |
| 8429041 | Bonalle et al. | Apr 2013 | B2 |
| 8555083 | Nanda et al. | Oct 2013 | B1 |
| 8788428 | Weston et al. | Jul 2014 | B2 |
| 9280765 | Hammad | Mar 2016 | B2 |
| 9355374 | Barnett et al. | May 2016 | B2 |
| 9419842 | Galliher, III et al. | Aug 2016 | B1 |
| 9942043 | Palanisamy | Apr 2018 | B2 |
| 9953316 | Barnett et al. | Apr 2018 | B2 |
| 9996835 | Dill et al. | Jun 2018 | B2 |
| 10361856 | Cassin et al. | Jul 2019 | B2 |
| 10438198 | Griffin et al. | Oct 2019 | B1 |
| 20020082896 | Inagi | Jun 2002 | A1 |
| 20030035569 | Chau | Feb 2003 | A1 |
| 20030051150 | Jung | Mar 2003 | A1 |
| 20030177236 | Goto et al. | Sep 2003 | A1 |
| 20040247126 | McClellan | Dec 2004 | A1 |
| 20050108517 | Dillon et al. | May 2005 | A1 |
| 20050166082 | Williams et al. | Jul 2005 | A1 |
| 20060047786 | Doi | Mar 2006 | A1 |
| 20060049255 | Von Mueller et al. | Mar 2006 | A1 |
| 20060161750 | Perkins et al. | Jul 2006 | A1 |
| 20070005974 | Kudou | Jan 2007 | A1 |
| 20070067297 | Kublickis | Mar 2007 | A1 |
| 20070101123 | Kollmyer et al. | May 2007 | A1 |
| 20070217408 | Sahashi et al. | Sep 2007 | A1 |
| 20070246529 | Lalo et al. | Oct 2007 | A1 |
| 20080049644 | Halbert | Feb 2008 | A1 |
| 20080080713 | Cho et al. | Apr 2008 | A1 |
| 20080109372 | Bykov et al. | May 2008 | A1 |
| 20080201778 | Guo et al. | Aug 2008 | A1 |
| 20080320297 | Sabo et al. | Dec 2008 | A1 |
| 20080320317 | Funahashi et al. | Dec 2008 | A1 |
| 20090048971 | Hathaway et al. | Feb 2009 | A1 |
| 20090126017 | Chahal | May 2009 | A1 |
| 20090294527 | Brabson et al. | Dec 2009 | A1 |
| 20090327421 | Fu et al. | Dec 2009 | A1 |
| 20100094755 | Kloster | Apr 2010 | A1 |
| 20100107230 | Tyagi et al. | Apr 2010 | A1 |
| 20100151816 | Besehanic | Jun 2010 | A1 |
| 20100174626 | Stringfellow et al. | Jul 2010 | A1 |
| 20100306635 | Tang et al. | Dec 2010 | A1 |
| 20100325710 | Etchegoyen | Dec 2010 | A1 |
| 20100325734 | Etchegoyen | Dec 2010 | A1 |
| 20100332396 | Etchegoyen | Dec 2010 | A1 |
| 20100332400 | Etchegoyen | Dec 2010 | A1 |
| 20110035294 | Mizrah | Feb 2011 | A1 |
| 20110082798 | Michaud et al. | Apr 2011 | A1 |
| 20110093503 | Etchegoyen | Apr 2011 | A1 |
| 20110093703 | Etchegoyen | Apr 2011 | A1 |
| 20110179271 | Orsini et al. | Jul 2011 | A1 |
| 20110196754 | Proud et al. | Aug 2011 | A1 |
| 20110258272 | Drako et al. | Oct 2011 | A1 |
| 20110307710 | McGuire et al. | Dec 2011 | A1 |
| 20120018511 | Hammad | Jan 2012 | A1 |
| 20120030209 | Bause et al. | Feb 2012 | A1 |
| 20120054050 | Ziegler et al. | Mar 2012 | A1 |
| 20120054493 | Bradley | Mar 2012 | A1 |
| 20120066769 | Latchem et al. | Mar 2012 | A1 |
| 20120084206 | Mehew et al. | Apr 2012 | A1 |
| 20120150742 | Poon et al. | Jun 2012 | A1 |
| 20120210421 | Ormazabal et al. | Aug 2012 | A1 |
| 20120255034 | Orsini et al. | Oct 2012 | A1 |
| 20120278335 | Bentkofsky et al. | Nov 2012 | A1 |
| 20120317036 | Bower et al. | Dec 2012 | A1 |
| 20120324242 | Kirsch | Dec 2012 | A1 |
| 20130036098 | Mutalik et al. | Feb 2013 | A1 |
| 20130097081 | Leavitt et al. | Apr 2013 | A1 |
| 20130160038 | Slaney et al. | Jun 2013 | A1 |
| 20130191887 | Davis et al. | Jul 2013 | A1 |
| 20130212666 | Mattsson et al. | Aug 2013 | A1 |
| 20130225213 | Antypas, III | Aug 2013 | A1 |
| 20130242795 | Heen et al. | Sep 2013 | A1 |
| 20130254117 | Von Mueller et al. | Sep 2013 | A1 |
| 20130297579 | Andrew et al. | Nov 2013 | A1 |
| 20130311434 | Jones | Nov 2013 | A1 |
| 20130346302 | Purves et al. | Dec 2013 | A1 |
| 20140013452 | Aissi et al. | Jan 2014 | A1 |
| 20140025948 | Bestler et al. | Jan 2014 | A1 |
| 20140032418 | Weber | Jan 2014 | A1 |
| 20140052553 | Uzo | Feb 2014 | A1 |
| 20140072188 | Liu et al. | Mar 2014 | A1 |
| 20140173686 | Kgil et al. | Jun 2014 | A1 |
| 20140197234 | Hammad | Jul 2014 | A1 |
| 20140323166 | Zhang et al. | Oct 2014 | A1 |
| 20140344921 | Hamlin et al. | Nov 2014 | A1 |
| 20150150110 | Canning et al. | May 2015 | A1 |
| 20150178819 | Kassemi et al. | Jun 2015 | A1 |
| 20150199682 | Kalgi et al. | Jul 2015 | A1 |
| 20150220635 | Deen et al. | Aug 2015 | A1 |
| 20150220636 | Deen et al. | Aug 2015 | A1 |
| 20150221336 | Deen et al. | Aug 2015 | A1 |
| 20150229613 | Baum et al. | Aug 2015 | A1 |
| 20150271150 | Barnett et al. | Sep 2015 | A1 |
| 20150381582 | O'Hare et al. | Dec 2015 | A1 |
| 20160087933 | Johnson et al. | Mar 2016 | A1 |
| 20160148197 | Dimmick | May 2016 | A1 |
| 20160189126 | Cheng et al. | Jun 2016 | A1 |
| 20160219024 | Verzun | Jul 2016 | A1 |
| 20160241528 | Kulkarni et al. | Aug 2016 | A1 |
| 20160342997 | De Tella et al. | Nov 2016 | A1 |
| 20170017939 | Killoran, Jr. et al. | Jan 2017 | A1 |
| 20170032361 | Purves et al. | Feb 2017 | A1 |
| 20170053139 | Schenk et al. | Feb 2017 | A1 |
| 20170063798 | Lapidous | Mar 2017 | A1 |
| 20170104731 | Baudoin et al. | Apr 2017 | A1 |
| 20170200150 | Cohn et al. | Jul 2017 | A1 |
| 20170201498 | Baig et al. | Jul 2017 | A1 |
| 20170300918 | Bernstein et al. | Oct 2017 | A1 |
| 20170310709 | Foxhoven et al. | Oct 2017 | A1 |
| 20180062832 | Hatcher | Mar 2018 | A1 |
| 20180189502 | Kumar et al. | Jul 2018 | A1 |
| 20180191735 | Lahoz et al. | Jul 2018 | A1 |
| 20180198607 | Punekar et al. | Jul 2018 | A1 |
| 20180309741 | Neafsey et al. | Oct 2018 | A1 |
| 20180336366 | Scheiblauer | Nov 2018 | A1 |
| 20180349875 | Barnett et al. | Dec 2018 | A1 |
| 20180349891 | Putre et al. | Dec 2018 | A1 |
| 20190207754 | Iyer | Jul 2019 | A1 |
| 20190342295 | Peterson | Nov 2019 | A1 |
| Number | Date | Country |
|---|---|---|
| 102387501 | Mar 2012 | CN |
| 105024980 | Nov 2015 | CN |
| 1482404 | Dec 2004 | EP |
| 2001067324 | Mar 2001 | JP |
| 2003050681 | Feb 2003 | JP |
| 2003273896 | Feb 2004 | JP |
| 2005533416 | Nov 2005 | JP |
| 2005333374 | Dec 2005 | JP |
| 2006039631 | Feb 2006 | JP |
| 2006053599 | Feb 2006 | JP |
| 2006203610 | Sep 2006 | JP |
| 2008166894 | Jul 2008 | JP |
| 2009282525 | Dec 2009 | JP |
| 2011511510 | Apr 2011 | JP |
| 2011244460 | Dec 2011 | JP |
| 2013201618 | Apr 2013 | JP |
| 2013545411 | Dec 2013 | JP |
| 2016510468 | Apr 2016 | JP |
| 2020522933 | Jun 2018 | JP |
| 20090039301 | Apr 2009 | KR |
| 2005079023 | Aug 2005 | WO |
| Entry |
|---|
| International Search Report and Written Opinion mailed Apr. 13, 2015 for related PCT application No. PCT/US2015/10405. |
| International Search Report and Written Opinion mailed Sep. 4, 2015 for related PCT application No. PCT/US2015/21595. |
| Common Approval Scheme, Point of Interaction Protection Profile, Nov. 26, 2010 Version: 2.0, 161 pages. |
| Security Standards Council, Payment Card Industry (PCI) PIN Transaction Security (PTS) Point of Interaction (POI), Modular Security Requirements, Version 4.0 Jun. 2013, 59 pages. |
| European Search Report dated Jul. 19, 2017 in related European Patent Application No. 15765006. |
| European Search Report and European Search Opinion dated Oct. 13, 2017 in related European patent application No. 15765781.8. |
| Matt, Susan: “P2P Encryption”, Jun. 23, 2011 (Jun. 23, 2011). XP055412989. Retrieved from the Internet: URL: http://www.elementps.com/Portals/0/P2P-Encryption-White-Paper.pdf. |
| First Data: “EMV and Encryption+Tokenization: A Layered Approach to Security” Jun. 1, 2012 (Jun. 1, 2012). XP055413104. Retrieved from the Internet: URL: https://www.firstdata.com/downloads/thought-leadership/EMV-Encrypt-TokenizationWP.pdf. |
| International Search Report and Written Opinion dated Aug. 31, 2018 in International Patent Application No. PCT/US18/35850. |
| International Search Report and Written Opinion dated Aug. 23, 2018 in International Patent Application No. PCT/US18/35858. |
| International Search Report and Written Opinion mailed Jan. 22, 2019 in related international patent application No. PCT/US18/55690. |
| Introducing JSON, (http://www.json.org/json-en.html). (Year: 2021). |
| Extended European Search Report dated Dec. 8, 2020 for European Patent Application No. 18809547.5. |
| Dicky: “15 Really Usefull Web-based HTML Editors”, WebDesignBooth, Jul. 17, 2009 (Jul. 17, 2009), XP055047393, Retrieved from the Internet: URL:http//www.webdesignbooth.com/15-really-usefull-web-based-html-editors/. |
| Extended European Search Report dated Jan. 29, 2021 for European Application No. 18809760. |
| Ogigau-Neamtiu. “Tokenization as a data security technique.” In: Zeszyty Naukowe AON. Jan. 26, 2016 (2016) Retrieved on Jul. 3, 2020 (Jul. 3, 2020) https://yadda.icm.edu.pl/baztech/element/bwmeta1.element.baztech-7680b362-6a77-420a-aff6-9409bfb9efe6/c/OGIGAU-NEAMTIU-Tokenization-as-a-data-security-technique.pdf. |
| International Search Report & Written Opinion mailed Jul. 24, 2020 in international PCT application No. PCT/US2020/032734. |
| Haoka, Sayaka, Fourth Examination Division Japanese Patent Office, “Notification of Reasons for Rejection,” Japanese Patent Application No. 2022-093697, Drafted Date: Aug. 22, 2023. |
| Number | Date | Country | |
|---|---|---|---|
| 20220101293 A1 | Mar 2022 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62514308 | Jun 2017 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16400359 | May 2019 | US |
| Child | 17400670 | US | |
| Parent | 15997269 | Jun 2018 | US |
| Child | 16400359 | US |
