Parallels H-Sphere Documentation Administrator Guide Merchant Gateway Manager


AuthorizeNet (Relay Response) Configuration


Related Docs:   Merchant Gateway Manager Supported Merchant Gateway Providers

Last modified: 26 Dec 2007


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.

30 October 2002 Authorize.Net introduced a new connection method (SIM) to provide both an increased level of security and intermediate integration. SIM is a superior alternative to the WebLink and Relay Response connection methods. In 2004, WebLink and Relay Response will be discontinued and transactions will no longer be accepted using these methods. Merchants using WebLink or Relay Response are encouraged to plan and prepare for migration to SIM.



AuthorizeNet certificate is trusted by VeriSign Trust Network. In Java 1.3.x and older the standard java cartcerts file doesn't include VeriSign Trust Network public certificate and therefore H-Sphere returns 'Connect error, untrusted server cert chain' when trying to connect ito the merchant gateway. That's why VeriSign Trust Network 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. You can update your cacerts file using the keytool feature available in the standard Java installation.

C. 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 [] [port]



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

    • Title: give a name to this AuthorizeNet connection
    • Server: the name of the AuthorizeNet server
    • Port: the port of the AuthorizeNet 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 AuthorizeNet login
    • Password: the password which comes with login/username
    • Referrer URL: the URL of the page that requests the payment. It's required as in some cases requests can be canceled without this information. Referrer URL can be your control panel URL, e.g: http://cp.your_domain ( Make sure to enter the same Referrer URL in settings -> response/receipt URLs in your AuthorizeNet interface, otherwise the request will be denied.
    • Test Mode:
      - FALSE: credit card transactions will be completed and credit cards will be charged;
      - TRUE: authorization requests will be sent for verification without settlement requests and credit cards won't be charged.
      * In Test Mode, all transactions appear to be processed as real transactions. The gateway accepts the transactions, but does not pass them on to the financial institutions. Accordingly, all transactions will be approved by the gateway when Test Mode is turned on.
  4. Click Submit Query

Please make sure to disable Require Password in the AuthorizeNet interface.

Related Docs:   Merchant Gateway Manager Supported Merchant Gateway Providers

© Copyright 2018. Parallels Holdings. All rights reserved.