Parallels H-Sphere Documentation Administrator Guide Merchant Gateway Manager

 

IonGate Configuration

(Out of support)
 
 

Related Docs:   Merchant Gateway Manager Supported Merchant Gateway Providers

Last modified: 31 Oct 2006

 

WARNING: This documentation covers Parallels H-Sphere versions up to 3.1. For the latest up-to-date Parallels H-Sphere documentation, please proceed to the official Parallels site.

 

Preparation

IonGate certificate is trusted by Equifax and provided by GeoTrust. In Java 1.3.x and older the standard java cartcerts file doesn't include GeoTrust root Certificates and therefore H-Sphere returns 'Connect error, untrusted server cert chain' when trying to connect to the merchant gateway. That's why GeoTrust Root certificates should be imported into cacerts file.

So, if you have Java 1.3 and older, you have the following solutions:
A. If you have got the default java cacerts file and you have never changed it, you can simply replace it with the cacerts file offered by psoft:
/usr/java/<java home>/jre/lib/security/cacerts

B. Upgrade Java to 1.4 by following our documentation.

Note: If your certificate is already imported into cacerts, but Java still generates 'Connect error, untrusted server cert chain', please check the connection to your payment server from your control panel server by running the following command from the control panel server console to check connection:
telnet [server.name] [port]

 

Configuration

  1. Select IonGate in the Add New Gateway box.
  2. Click the Add button.
  3. Fill out the form that appears:

    • Title: give a name to this IonGate connection
    • Server: the name of the IonGate server
    • Port: the port of the IonGate server
    • Path: the path to the server side handler file. This can be a script or a binary file that is launched with an http request.
    • Login: your IonGate login
    • Problem Notification Email: enter your email address to receive notifications about:
      - AVS problems. AVS stands for Address Verification Service. It can be used as an additional layer of protection for merchants who wish to verify that the purchaser knows the billing address of the cardholder (in case these are two different people). This is not a very serious form of risk mitigation or fraud prevention, and yet it does give some assurance that a hacker isn't simply generating a list of valid credit card numbers and purchasing product at will. AVS simply matches the numeric portion of the cardholder's street billing address and the 5 or 9-digit zip code of the cardholder's billing address. The AVS request parameters are STREET and ZIP. The processing network verifies the AVS information, comparing a portion of the billing address from the request message with address data on file at the VIC or the issuer's center. Based on the comparison, a response will be returned which confirms whether the information matches or not. Banks do not decline transactions based on the AVS check. The AVS response is returned as two single tab-delimited characters: YY, NN, YN, NY (Y-'matches', N for 'does not match'). This information is just an advice. However, the H-Sphere system will either allow or decline the transaction depending on the selected AVS status. AVS is available only for US cardholders.
      Important: To provide non US cardholders CC processing, disable AVS check-up in the merchant gateway configuration.
      - H-Sphere signup error: user's signup failure for unknown reasons after credit card is charged.
      When either of the problems occurs, H-Sphere sends a message to this address with the recommendation to void the transaction in merchant's gateway account due to AVS problems or system faults. To cancel the transaction, the owner of H-Sphere should enter the merchant account and cancel the transaction manually.
  4. Click Submit Query

Related Docs:   Merchant Gateway Manager Supported Merchant Gateway Providers



© Copyright 2017. Parallels Holdings. All rights reserved.