Last modified: 16 Oct 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.
LinkPoint deprecated support for its old API. It may cause problems with signup and billing.
To update API to v3.01, users should convert the certificate from PEM to P12 format
FreeBSD Note: LinkPoint API uses java 1.4. It can't be configured for FreeBSD
that doesn't support the required Java version (in H-Sphere versions 2.4.3 RC 1 and earlier).
Please update your H-Sphere to latest stable version where
Java 1.4.2 is included for CP server under FreeBSD 4.x.
Make sure that the JLinkPointTxn.jar file is present in the
If it's not there:
When your linkpoint account is created you receive linkpoint welcome
email which contains username, password and the certificate in the PEM
format. You need to convert this certificate from PEM to P12 format. One
way to do this is to run the following from a command prompt:
- Contact LinkPoint (API) and obtain the JLinkPointTxn.jar file.
- Put the lib file into in the directory ~cpanel/java_rt/.
- Restart H-Sphere.
openssl pkcs12 -export -in YOURPEM.pem -inkey YOURPEM.pem -out
YOURPEM.p12 -passout pass:YOURPASS -name "YOURNAME"
- q YOURPEM - the name of your PEM file;
- q YOURPASS - your merchant password (the password you specified in merchant gateway settings);
- q YOURNAME - any arbitrary name.
openssl pkcs12 -export -in cert.pem -inkey key.pem -out
-passout pass:987654321 -name "LinkPoint"
PEM files example:
-----BEGIN RSA PRIVATE KEY-----
-----END RSA PRIVATE KEY-----
- Select Link Point (API v3.01) in the Add New Gateway box.
- Click the Add button.
- Fill out the form that appears:
- Title: give a name to this LinkPoint (API) connection
- Store Name: Your LinkPoint (API) unique ID, sometimes also referred to as Config File
- Server: the name of the LinkPoint (API) server
- Port: the port of the LinkPoint (API) server
- Password: the password which comes with login/username
- AVS: 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.
To provide non US cardholders CC processing, disable AVS check-up in the merchant gateway configuration.
- 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.
- Click Submit Query
- In Edit Gateway, select the newly created connection and press Edit.
- Note the two new parameters that appeared on the gateway configuration page, Key File, and Certificate File.
Put the key and certificate files on the control panel server to the locations suggested here.