The first step is to fulfil the prerequisites of the payment module
(listed in the individual module documentation below) and enable the module
in the global configuration file with the Require
directive:
require Vend::Payment::NetBilling
If we are using only one gateway in a catalog, setting up
MV_PAYMENT
variables is sufficient.
Variable | Purpose | Notes |
---|---|---|
MV_PAYMENT_MODE | gateway mode name | |
MV_PAYMENT_HOST | gateway host name | optional (predefined in module) |
MV_PAYMENT_ID | merchant identifier | |
MV_PAYMENT_SECRET | secret part of credentials | password or certificate |
MV_PAYMENT_REFERER | referring URL | |
| currency | three-letter currency code according to ISO 4217 |
MV_PAYMENT_TEST | test mode |
An example configuration looks like:
Variable MV_PAYMENT_MODE signio Variable MV_PAYMENT_PARTNER verisign Variable MV_PAYMENT_ID nevairbe Variable MV_PAYMENT_SECRET foobar
With the Route
directive it is possible to specify payment gateways
for special purposes. The payment route should set all relevant payment
parameters for the gateway, otherwise the settings from the MV_PAYMENT_* may
leak into the route.
Route signio partner verisign Route signio id nevairbe Route signio secret foobar
The following payment gateway transactions are known by Interchange:
Transaction | Description |
---|---|
avs | Address verification (AVS) |
auth | Payment authorization (Charge) |
return | Credit |
reverse | Reverse former transaction |
sale | Charge and capture |
settle | Capture of an authorized charge |
void | Cancel or refund payment |
abort | Abort pending capture. |
Modules for the following payment gateways are included in the Interchange source code:
Module | Name | Mode | Description |
---|---|---|---|
AuthorizeNet | AuthorizeNet | authorizenet | |
BoA | Bank of America | boa | |
BusinessOnlinePayment | Business::OnlinePayment | onlinepayment | wrapper for Business::OnlinePayment |
Cybercash | Cybercash | cybercash | |
ECHO | Electronic Clearing House, Inc. | echo | |
EFSNet | Concord EFSNet | echo | |
Ezic | EziC | ezic | |
Getitcard | Getitcard | getitcard | Prepaid cards from Getitcard. |
ICS | Cybersource ICS | ICS | |
iTransact | iTransact | itransact | |
Linkpoint | LinkPoint | linkpoint | |
MCVE | Mainstreet Credit Verification Engine | mcve | |
NetBilling | NetBilling | netbilling | |
PRI | Payment Resources International | PRI | |
PSiGate | PSiGate | psigate | |
Sage | Sage Payment | sage | |
Signio | Payflow Pro | signio | |
Skipjack | Skipjack | skipjack | |
TCLink | TrustCommerce | trustcommerce | |
TestPayment | Payment Test | testpayment | for test purposes |
The AuthorizeNet module implements the ADC Direct Response method for AuthorizeNet version 3.
OpenECHO module from http://www.openecho.com/.
The Getitcard payment module is used for purchases with prepaid cards issued by GetitcardŽ (http://www.getitcard.com/).
Required parameters are id
and keyfile
.
The domain name of the LinkPoint Secure Payment Gateway (LSPG). Default is
secure.linkpt.net
for production and
staging.linkpt.net
for testing.
File name of the merchant security certificate. This file should contain the RSA private key and the certificate, otherwise you get an error like "Unable to open/parse client certificate file."
The Netbilling module implements the Netbilling Direct Mode 2.1.
This is your account and sitetag separated by a colon (ACCOUNT:SITETAG). ACCOUNT is the number of your Netbilling merchant or agent account, as a 12-character string. Required for ALL transactions. SITETAG is the site tag of your website configured in the Netbilling system. Required for membership transactions, optional for others.
Net::TCLink module from http://www.trustcommerce.com/tclink.html or CPAN.
This module can be used for test purposes.