iTransact

Interchange's support for the iTransact  Payment Services Provider.

Synopsis

or

Prerequisites

or

Only one of the above options needs be present and working.

Description

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

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

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

Make sure CreditCardAuto is off, which is the default in the Standard ecommerce demo.

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 website, you can set the following in catalog.cfg:

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 after the mode, then finally a default global payment Variable.  For example, the id parameter would be specified by:

or

or

Settings

Name	Description
id	Your iTransact account ID supplied by iTransact when you sign up.  The variable is MV_PAYMENT_ID.
home_page	The address of your website.  Defaults to "http://__SERVER_NAME__" if not set.  The variable is MV_PAYMENT_HOME_PAGE.
remap	This remaps the form variable names to the ones needed by iTransact.

Troubleshooting

Try the instructions above, then enable test mode in the online account manager.  A test order should complete.

Then move to live mode and try a sale with 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:

• Make sure you Required the module in interchange.cfg:

  Require module Vend::Payment::iTransact

• 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 -le 'print "Available"'

  or

  perl -MLWP::UserAgent -MCrypt::SSLeay -le 'print "Available"'

  If either of the above prints "Available", and returns to the shell prompt, then you should be OK (presuming they are in working order otherwise).

  
  
• Check the local and global error log files.
  
  
• Make sure you set your payment parameters properly.
  
  

• Try an order, then put this code in a page:

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

  That should show what happened.

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

Notes

There is actually nothing in Vend::Payment::iTransact;  This module changes its package name to Vend::Payment and places things there.

Authors

• Mark Johnson and Cameron Prince
• Based on original code by Mike Heins 

Category:  Interchange payment modules

Last modified by: Kevin Walsh Modification date: Tuesday 19 September 2006 at 9:30 AM (EDT)