The uniPAY POS client component resides in the Point-of-Sale hardware accepting the transactions at a retailer. The client application is integrated with the retailer's billing system. When a consumer chooses to pay by credit/debit card option the billing software passes the control over to the uniPAY payment client. The payment client activates the card reader for acceptance of card data and then creates the required transaction and communicates it over to uniPAY server. A card reader maybe integrated as a part of the billing system or can be added externally (Innoviti can provide the same) to the billing hardware for acceptance of a card transaction. The uniPAY client also accepts loyalty, gift, pre-paid, staff and discount card transactions.
| Programs Supported: | Credit/Debit Cards, Gift Vouchers, Gift Cards, Staff Discount, Pre-Paid, Mobile Loyalty, Loyalty, Discount Card, Other custom marketing programs | |
| Credit/Debit Cards: | All VISA, MasterCard, AMEX, and JCB | |
| Hardware Platforms: | PCs, Embedded Digital Terminals, POS Systems | |
| Operating Systems: | Windows 3.1, 98, 2000, XP, Embedded XP, Vista, 7, Linux, Embedded OS, Windows CE, DOS 6.22 | |
| Billing Software: | Retalix, TPLinux, TP.net, Orion, LS Retail, E-Retail, Triversity, NAVision, Shawman, Amadeus, Showbiz, Vista, Other proprietary billing software | |
| Billing Integration Interface: | Windows DLLs, Web services, Socket calls, Linux static library | |
| Billing POS Program Languages Supported: | Visual Basic, NAVision Dynamics, .NET, C/C++, JAVA | |
| Minimum System RAM Requirement: | >64MB | |
| Connectivity Requirement: | Any always-on connectivity (dial-up, LAN, GPRS, VSAT, Leased line) | |
| Security: | SSL, 128-bit using 3DES | |
| Hardware Peripherals: | Magnetic swipe reader, keyboard | |
| Diagnostics: | Error logs on client reported to uniPAY Host for centralized viewing. System health status reporting. Software version reporting | |