Overview of the SecureTable product
SecureTable is a universal middleware platform that provides an EMV-Compliant, Pay at the Table (PATT) processing solution that can be connected to a POS (Point of Sale) system. The solution can work in standalone mode as well as integrated to a Point of Sale (POS) system such as Maitre’D, Veloce, Squirrel, Aloha and Micros among other.
SecureTable uses a “Pull” architecture. This means that a payment terminal using SecureTable can initiate the transaction process by Pulling information from the POS system. In other words, after the guest checks are printed, there is no need for the server to walk back to the POS workstation to apply payments and close guest checks. All payments, including credit, debit and cash, can be applied and checks closed directly at the table side.
The integration of SecureTable with various POS systems allows the payment terminal to retrieve guest check data from the POS System. Once a payment has been processed by the payment terminal, SecureTable sends the payment data back to the POS System for reporting purposes. Payment amounts, tip amounts and card brand used are all automatically transmitted to the POS system to allow for accurate reporting.
If an EMV solution with tethered (wired) EMV payment terminals is already in place and integrated to the POS system, SecureTable can still be used without worry. A configurable table-locking or invoice-locking mechanism prevents accidentally accessing guest checks that are being processed by a payment terminal through SecureTable. This means that establishments can, for example, use wireless payment terminals with SecureTable in the dining room while using tethered payment terminals for the cashier station, bar, pickup counter and drive-through windows.
With a direct integration, Maitre’D communicates directly with SecureTable’s STPI client through a secure socket connection without using drop-files. This allows Maitre’D to take advantage of all the features offered by SecureTable, without the limitations imposed by using the former TPI client middleware.