Core Product: Aloha Takeout
Complimentary Products: Aloha Quick Service, Aloha Table Service
Separate License Required? An Aloha Takeout and Delivery license is required. The Delivery component of Aloha Takeout requires a separate license from Aloha Delivery/Frequent Buyer (D/FB), and is included as part of the Aloha Takeout license. It is not necessary to actually install D/FB.
Other References: Aloha Takeout Reference Guide, Aloha Takeout Implementation Guide
To collect and store sensitive cardholder information, the Aloha Takeout application requires the presence of a site key. The process uses the site key to encrypt the sensitive data before storing the data in the database or transmitting it between client terminals and the server. When a customer wants to pay for a transaction with a stored payment card, Aloha Takeout retrieves this information, unencrypts it in the background, and passes it to the Aloha POS for use with Aloha EDC in the normal payment process. The system also requires the site key for online orders with credit card payments, even though the site may not be storing credit card information with their customers. Until you establish a site key in the system, you cannot enter cardholder information using the ATO application.
Because the site key encrypts sensitive cardholder information, it is necessary to regularly rotate the site key. We suggest rotating the site key every ninety days, and the system allows a maximum of three hundred and sixty-five days between site key rotations. Once you establish your site key, you can configure the system to automatically rotate your site key, or you can manually rotate your site key. If you choose to allow the system to automatically rotate your site key, you will no longer know your site key. If you choose to manually rotate your site key and you lose the site key, you can reset the key; however, doing so requires you to clear your stored credit card data and you cannot retrieve this data.
Reference: Refer to the Aloha Takeout Site Key Feature Focus Guide - HKS485.
This section demonstrates how to establish a site key, how to rotate your site, automatically or manually, and if necessary, how to reset your site key, which clears all of your stored credit card data.
How the system stores and rotates a site key
The system stores site key information in the %ATOPATH%\DATA directory in an encrypted file called ATO_SK.dat. When you or the system change the site key, the system changes the name of the existing ATO_SK.dat to ATO_SK1.dat and stores the new site key in ATO_SK.dat. When ATO needs to decrypt credit card information, it attempts to use ATO_SK.dat. If this fails, it tries ATO_SK1.dat, ATO_SK2.dat, etc. until it either decrypts or runs out of site key archives.
In most cases the %ATOPATH%\DATA directory should only contain one ATO_SK.dat file. When you restart the Radiant Takeout and Delivery service, it goes through the stored credit cards in the SQL database and re-encrypts them with the new key. When complete, the system will delete ATO_SK1.dat and any other archives during the ATO EOD process.