iPOSS Requirements

iPOSS requirements vary depending on the method through which a merchant chooses to interface.

For Remote Mode Because a transaction in Remote Mode takes place on our secure servers, there are only two requirements: Merchant must have a Merchant Account Merchant must have access to HTML code For Local Mode Interfacing with iPOSS in Local Mode carries the following requirements: Merchant must have a Merchant Account Merchant must have access to HTML code Site must be hosted on Solaris, Windows NT, AIX, HP-UX or Linux server * Merchant site must support Secure Sockets Layer (SSL) Commercial version of Pretty Good Privacy (PGP)

For All Merchants Before merchants can accept credit card payments in the physical world or on the Internet they must have a merchant account with a merchant bank. Such an account is required in order to process credit card transactions. In order to integrate successfully with iPOSS the merchant account must be set up on the FDR Omaha platform. If you or your clients are in need of a merchant account, we will provide you with the documents and application form needed to obtain such an account. During the signup procedure you will have the opportunity to indicate whether or not you need a merchant account.

* The limitation in web server platforms is not dictated by iPOSS, but by PGP. The commercial version of PGP required to interface in Local Mode is currently only available for Solaris, Windows NT, AIX, HP-UX and Linux platforms. Other platforms will be supported in future versions of PGP. When these become available, iPOSS Local Mode will support them as well.