Remote Mode
Remote Mode is the more transparent and easier method to implement, as it requires only HTML code. Merchant's can use our Setup Wizard to generate the necessary HTML code based on the merchant's answers to a few simple questions.
After an order is submitted in Remote Mode, the customer is transferred to a transaction result page hosted on a VERIFY ONLINE secure server. The URL will change to indicate the new location.
If approved, the customer sees a confirmation message and is redirected back to the merchant's site. If the transaction fails, a denial message is broadcast and the customer is returned to the
merchant's order form or home page.
 |
Advantages |
|
| - | No setup required |
| - | Compatible with all web servers |
| - | Requires only HTML code |
| |
Disadvantages |
|
| - | URL changes for transaction results |
|
 |
Local Mode
In local mode, all aspects of the purchase process take place on the merchant's end (except the credit card transaction). The URL never changes and the customer never leaves the site.
Before iPOSS can accept the transaction request, it must be encrypted on the merchant side using the commercial version of PGP. Upon receipt,
iPOSS decodes the encrypted packet and processes the credit card transaction.
Once the transaction is complete, iPOSS transmits an approval/denial message back to the customer. A copy of the transaction result is also emailed to both customer and merchant.
| |
Advantages |
|
| - | Customer never leaves merchant site |
| - | Additional security layer through PGP |
| |
Disadvantages |
|
| - | Available for Solaris, Linux and NT only |
| - | Requires some familiarity with Unix |
|
Integration
integration can be as easy as
copying & pasting HTML code. There are two modes in which merchants can integrate their online stores with iPOSS processing services:
Remote Mode and Local Mode (as seen from the merchant's point of view.) The differences between these modes is illustrated below.
