In 6.4, if using a Radiant 1520, 1220, etc pos terminal, part of PCI compliance is the change type type of your credit card reader in terminal settings. It must be set to OPOS with the name of the Radiant OPOS reader. If you do not, Aloha Manager will generate a verify report telling you the...
Based on feedback through the reseller channels it appears that any 6.x version prior to 6.4.14 has more than its share of issues and 6.4.14 thus far (after 2 years of controlled deployment) does not. If you have a Radiant subscription on your license I would suggest opting out of the 6.1, 6.2...
You didn't mention what Aloha Version you are on.
If you are on any of the 6.x versions, fields were added to programming of a payment key to ask for zip code and/or security code.
The problem with this is in the early version so fo 6.x Aloha didn't really DO ANYTHINH with this...
Aloha 6.4 is the current version release and 6.5 and 6.6 are in controlled deployment.
Aloha, unlike some other POS product is tied closely to the OS. This has been a blessing and a curse.
For example, unannounced changed in IE7 way back when effective Aloha EDC, and thus an Aloha system...
Rosemary
There is no reason FB/Delvery should not work when upgrading to Aloha 6.x. It is considered a "legacy" product by Radiant, but if you have been using it, it should continue working. There was a version update for FB/Delivery that needs to be in place for it to work. If the other...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.