The EPI - E-Payment Interface

 

Overview | Concept | Licensing | Download | Installation | Sample Code | FAQ
Products | Scripts | Services | Tutorials | Books | Links | Contact | Bulletin Board

Please follow the links below to read the documentation specific to your gateway:

AuthorizeNet | BluePay | CyberCash | Echo Inc. | ESec | FirePay | GO Software(PCCharge)

iBill | Innovative Gateway | IntelliPay | Iongate | IPayment | LinkPoint | NovaInfo | PayBill

PayPal | PaySystems | Plug-n-Pay | Qenta | Skipjack | TeleCash | VeriSign | WorldPay

LinkPoint

LinkPoint is an US based company. As of this writing, LinkPoint only supports transactions in US dollars.

 

What you need to start

You receive from LinkPoint the following:

Old version:

  • Packaged binaries for your platform
  • Merchant Key File
  • Merchant ID

New version:

  • Merchant Key File
  • Merchant ID

The new version is not uploaded in any package yet, since it requires further testing.

 

Gateway Configuration Data

The LinkPoint product homepage is under: http://www.linkpoint.com/

The variables are matching both the 2001 version of the gateway and the new version (2003).

This package uses an additional binary, which is distributed by Linkpoint, for a fee. We programmed the module to interface with the LinkPoint wrapper, which sets up the environment for the binary.

Old Version

You will have to purchase the Linkpoint package and install it in the same directory as the EPI.pm, then flag the binary as executable if you are on an Unix system.

Be aware that the package is made up of TWO items, a binary and a perl wrapper, named lperl.pm. You will need to provide a path to the binaries, using the key -BINARY_FILE_PATH

LPERL uses temp files for data exchange. Please provide in the setup hash a writable path for the temp files (usually the system log path).

You will also get a certificate from Linkpoint, a file with the extension ".pem". Copy the certificate
to a directory specific to the shop, then provide the path to it, in the merchant setup hash.

IMPORTANT ! You will need to modify the lperl.pm to define a temporary folder for transaction data.

 

New Version (DEFAULT)

LPERL uses both OpenSSL and cURL installed on your secure Web server for data exchange. Please edit the lperl.pm and enter the correct path to curl, and make sure you install OpenSSL..

You will also get a certificate from Linkpoint, a file with the extension ".pem". Copy the certificate
to a directory specific to the shop, then provide the path to it, in the merchant setup hash.

IMPORTANT ! You will need to modify the lperl.pm to define the curl path!.

 

 

 

Payment Methods

The Supported payment methods are CreditCard, PurchaseCard and ECheck.

Valid values for -ACTION

For CreditCard and PurchaseCard:

  • TEST
  • AUTH_CAPTURE
  • AUTH_CAPTURE_PERIODIC
  • CAPTURE_ONLY
  • PRIOR_AUTH_CAPTURE
  • CREDIT

For ECheck:

  • TEST
  • AUTH_CAPTURE
  • VOID

 

Code to use for The CITY Shop

Old Version
$MerchantData = {
  -GATEWAY_NAME           => 'linkpoint',
  -GATEWAY_VERSION        => 1,
  -MERCHANT_ID            => '123456', 
  -MERCHANT_KEY_FILE      => '/var/www/cgi-bin/store/shops/city/123456.pem',
  -BINARY_FILE_PATH       => '/var/www/cgi-bin/store/Library/lbin',
};
New Version (DEFAULT)
$MerchantData = {
  -GATEWAY_NAME           => 'linkpoint',
  -GATEWAY_VERSION        => 2,
  -MERCHANT_ID            => '123456', 
  -MERCHANT_KEY_FILE      => '/var/www/cgi-bin/store/shops/city/123456.pem',
};

 

If you configure this for The CITY Shop, that is all you need to know, and you can return to the installation instructions.

 

Description of the used parameters:

-MERCHANT_ID
This is the Merchant ID provided to you by LinkPoint, same thing as the "store name"

-MERCHANT_KEY_FILE
a path to the key file provided by Linkpoint

-BINARY_FILE_PATH
the path to the binaries provided by Linkpoint

-LOG_ACTIVITY
This is a flag that you can set on "1" if you want to log the gateway activity

-LOG_FILE_PATH
This is the path where the log file will be created. Note that this is a path only, and the script will create there a file named "LINKPOINT.log"

 

Used fields

Depending on the payment mode, here are the specific required fields:

For the CreditCard method:

Required Fields:

-ORDER_NUMBER (not required by the AUTH_CAPTURE_PERIODIC)
-ORDER_AMOUNT
-CARD_NUMBER
-CARD_EXPIRES
-USER_FULL_NAME (or -USER_FIRST_NAME/-USER_LAST_NAME)
-USER_ADDRESS
-USER_CITY
-USER_STATE
-USER_ZIP
-USER_COUNTRY

Optional Fields (not used by CREDIT and VOID):

-ORDER_TAX
-ORDER_VAT_TAX
-ORDER_SUBTOTAL
-ORDER_SHIPPING
-ORDER_COMMENTS
-SHIP_FULL_NAME
-SHIP_COMPANY
-SHIP_ADDRESS
-SHIP_CITY
-SHIP_COUNTRY
-SHIP_STATE
-SHIP_ZIP
-USER_EMAIL
-USER_PHONE

This gateway supports also Credit Card Periodic Billing, using the AUTH_CAPTURE_PERIODIC action. Here are the fields associated with this option:

-PERIODIC_BILLING_START_DATE
-PERIODIC_BILLING_CYCLE
-PERIODIC_BILLING_INSTALLMENTS
-PERIODIC_BILLING_THRESHOLD
-PERIODIC_BILLING_COMMENTS (optional)

 

For the ECheck method:

Required Fields:

-ORDER_NUMBER
-CHECK_NUMBER
-CHECK_MICR_NUMBER
-BANK_ABA_CODE
-USER_FULL_NAME (or -USER_FIRST_NAME/-USER_LAST_NAME)
-USER_ADDRESS
-USER_CITY
-USER_STATE
-USER_ZIP
-USER_COUNTRY

Optional Fields:

-ORDER_TAX
-ORDER_VAT_TAX
-ORDER_SUBTOTAL
-ORDER_SHIPPING
-ORDER_COMMENTS
-SHIP_FULL_NAME
-SHIP_COMPANY
-SHIP_ADDRESS
-SHIP_CITY
-SHIP_COUNTRY
-SHIP_STATE
-SHIP_ZIP
-USER_EMAIL
-USER_PHONE


Look in the main install documentation for examples of passing the data to perform a transaction.