Quick Navigator

Search Site

Unix VPS
A - Starter
B - Basic
C - Preferred
D - Commercial
MPS - Dedicated
Previous VPSs
* Sign Up! *

Contact Us
Online Help
Domain Status
Man Pages

Virtual Servers

Topology Map

Server Agreement
Year 2038

USA Flag



Man Pages

Manual Reference Pages  -  VEND::PAYMENT::ITRANSACT (3)

.ds Aq ’


Vend::Payment::iTransact - Interchange iTransact Support





    [charge mode=itransact param1=value1 param2=value2]



  LWP::UserAgent and Crypt::SSLeay

Only one of these need be present and working.


The Vend::Payment::iTransact module implements the itransact() routine for use with Interchange. It is compatible on a call level with the other Interchange payment modules — in theory (and even usually in practice) you could switch from CyberCash to iTransact with a few configuration file changes.

To enable this module, place this directive in interchange.cfg:

    Require module Vend::Payment::iTransact

This must be in interchange.cfg or a file included from it.

Make sure CreditCardAuto is off (default in Interchange demos).

The mode can be named anything, but the gateway parameter must be set to itransact. To make it the default payment gateway for all credit card transactions in a specific catalog, you can set in catalog.cfg:

    Variable   MV_PAYMENT_MODE  itransact

It uses several of the standard settings from Interchange payment. Any time we speak of a setting, it is obtained either first from the tag/call options, then from an Interchange order Route named for the mode, then finally a default global payment variable, For example, the id parameter would be specified by:

    [charge mode=itransact id=YouriTransact]


    Route itransact id YouriTransactID


    Variable MV_PAYMENT_ID      YouriTransactID

The active settings are:
id Your iTransact account ID, supplied by iTransact when you sign up. Global parameter is MV_PAYMENT_ID.
home_page The internet address of your site. Defaults to http://__SERVER_NAME__ if not set. Global parameter is MV_PAYMENT_HOME_PAGE.
remap This remaps the form variable names to the ones needed by iTransact. See the Payment Settings heading in the Interchange documentation for use.


Try the instructions above, then enable test mode. A test order should complete.

Then move to live mode and try a sale with the card number 4111 1111 1111 1111 and a valid expiration date. The sale should be denied, and the reason should be in [data session payment_error].

If nothing works:
o Make sure you Required the module in interchange.cfg:

    Require module Vend::Payment::iTransact

o Make sure either Net::SSLeay or Crypt::SSLeay and LWP::UserAgent are installed and working. You can test to see whether your Perl thinks they are:

    perl -MNet::SSLeay -e print "It works\n"


    perl -MLWP::UserAgent -MCrypt::SSLeay -e print "It works\n"

If either one prints It works. and returns to the prompt you should be OK (presuming they are in working order otherwise).

o Check the error logs, both catalog and global.
o Make sure you set your account ID properly.
o Try an order, then put this code in a page:

        my $string = $Tag->uneval( { ref => $Session->{payment_result} });
        $string =~ s/{/{\n/;
        $string =~ s/,/,\n/g;
        return $string;

That should show what happened.

o If all else fails, consultants are available to help with integration for a fee. See


There is actually nothing *in* Vend::Payment::iTransact. It changes packages to Vend::Payment and places things there.


Mark Johnson and Cameron Prince, based on original code by Mike Heins.
Search for    or go to Top of page |  Section 3 |  Main Index

perl v5.20.3 VEND::PAYMENT::ITRANSACT (3) 2010-03-25

Powered by GSP Visit the GSP FreeBSD Man Page Interface.
Output converted with manServer 1.07.