Parallels H-Sphere Documentation Administrator Guide Merchant Gateway Manager

 

LinkPoint Configuration

 
 

Related Docs:   Merchant Gateway Manager Supported Merchant Gateway Providers

Last modified: 19 Jan 2005

 

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.

This version of LinkPoint gateway is deprecated. If you are using it, LinkPoint International recommends switching to LinkPoint API v.3.01.

 

Preparation

First, compile the ccapi.order script:

  1. Log into your control panel server as root and go to the following directory:
    /hsphere/shared/scripts/LinkPoint.
  2. Unpack api.tar.gz with the following command:
    tar -xzf api.tar.gz
  3. Go to the directory that corresponds to your operation system.
  4. Copy liblpapi.a to /usr/lib/ with the following command:
    cp liblpapi.a /usr/lib/.
  5. Return to /hsphere/shared/scripts/LinkPoint directory.
  6. Run make and make install to compile script and install this script into /hsphere/shared/scripts directory.

Upon the registration with LinkPoint, you will be emailed a certificate. Copy-paste the text of the certificate into a separate file and save it to the ~cpanel/shiva/psoft_config/certs/ directory on the Control Panel server. Make sure it is readable for cpanel user. On the configuration page (see below) you'll have to specify the path to this file. There must be a separate file for each reseller that uses LinkPoint.

This is what the content of the file must look like:

-----BEGIN RSA PRIVATE KEY-----
MIIBXAIAAAKAgQB2XeM/7mp7LPl3odi8+9YgobIdROttGLjF6hHPcYFaQoar7zJY
52La/lTQAeFe7u2SlwuMiRw+ygyrT0aj7dDWP2paaTweDE9e8B9bgoqJ1+6nxV3q
ZaAsvA5iOOgizW3j5jFakl2gcYEB9c3R4qUsmJLvHSSrgmqWuvp0aP7eMQIDAQAA
AoGAXyF1QcVR8H1OiUyJhwPr+EvJYlaaZKavxHZM4iaO2tcBPzAg2BWj2M8xWO6w
sjWF8qEdYion9M0aeMW2+M6eKOFYTvEQJSjKpM3ohKN6IhKq08rGI/cGSNRzvgwt
/Wpegzlo+QyxVZSgAF79DVLr2p4H/GlHb0itW2iTprH2r1EBQQDxABNhDbhP7cAA
WNFsYGmj2axcM/2piQ4Ai4bDhR07xgeBYLVEwgiIvksgJ8Fg12qvupP9ErWWl9OQ
btmLJh0lAkEAwadaiGD4+AD7aA0ZzAd88tB5MvAdGev6MY/rZBSbRE2IT04gWzQa
p5R0s+vQBJr/i8alyGQ8rxixu+nGDAdqHQJAANn/uAEIyJOUmL0/LGEOaUBrnADL
EL+UnDjFj6Gcea4dGcK4TAAgTDv1cltl2sTQ106SRV981wma2OInIaV/GokBQAP1
+E1vOJhNdZrFUOAv3e9jNIIkLdXcigVLYBT8hMtG+2rG4aaE4Ao6+hTJ0BQD7MOW
gdoO679JYbiSAc+Eq6aHyRoq6MbT8J9wXiOXQheOImSx8rl2vmAxbZRAycdhccdc
YwStwiSpVOyIUJUDY=
-----END RSA PRIVATE KEY-----
-----BEGIN CERTIFICATE-----
MIIBZTBBAb4BAQAwDQYJKoZIhvbNAQEEAQAwdzELMAkGA1UEBAMBRkwxFDASAgNV
AAbTB01JQU1JIEJFQUNIMRYwFAYDVQQKEw1GSUxMIFRIRSADQVJUMRYwFAYDVQQD
Ew1TQ09UVBANVUVMTEVSMSYwJAYJKoZIhvbNAQkAFhc2YWxlbmllQGZpaGx0aGVj
YXJ0LmNvaTAdFw0wMjAyMjbxODQ0MThaFw0zMjAyMjUxODQ0MThaMHsxBzAJAgNV
AAgTAkZMMRQwEgYDVQQHEwtNSUFNSSABRUFDSDEWMAQGA1UEBhMNRklMTBAUSEUg
Q0FSVDEWMAQGA1UEAxMNU0NPVFQgTVVFTExFUjEmMBQGBSqGSIa3DQEJARYXcmFs
ZXJpZUAmaWxscGhlY2FycB5ja20wgZ8wDQYJKoZIhvbNAQEAAQADgY0AMIGJAoGA
ALZc8z/uanss+Xdh6Lz71iBhwh5E620YuMXqEb91gVtBhqvvMljnYtr+VNAF8V/u
7ZKXB4yJHD7KDKtPRqPt4NY/alppPA8MT1/wL1yBionX7qeFXdploGy8DmI46BLN
adPmMVuSXaA1gQL13cHipSyYku8cJKuBapa6+nRs/t8xAgMAAAEwDQYJKoZIhvbN
AQEEAQADgYEAKaULRKqGNMjJr/VBZAM+DghHBnraZzTASDYjX5kw3304AENBgrNT
eZvinGGG6bx/M7tN5qTwp6EqB/0Ga/cBQbAi9QdKMAB5/rPDBuAiNSGElghHXa9l
FgliOBZaKvaQSStRg1hnbbhFKAy2LFUpKtTrRrIcLHJwRs92AYAuIGw=
-----END CERTIFICATE-----

 

Configuration

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

    • Title: give a name to this LinkPoint connection
    • Store Name: Your LinkPoint unique ID, sometimes also referred to as Config File
    • Path to the Key File: on the control panel server, the path to the certificate that you get from LinkPoint
    • Server: the name of the LinkPoint server
    • Port: the port of the LinkPoint server
    • 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.
      Important: 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.
  4. Click Submit Query

Related Docs:   Merchant Gateway Manager Supported Merchant Gateway Providers



© Copyright 2017. Parallels Holdings. All rights reserved.