![]() |
![]()
| ![]() |
![]()
NAMEVend::Payment::iTransact - Interchange iTransact SupportSYNOPSIS&charge=itransact or [charge mode=itransact param1=value1 param2=value2] PREREQUISITESNet::SSLeay or LWP::UserAgent and Crypt::SSLeay Only one of these need be present and working. DESCRIPTIONThe 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] or Route itransact id YouriTransactID or Variable MV_PAYMENT_ID YouriTransactID The active settings are:
TroubleshootingTry 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:
BUGSThere is actually nothing *in* Vend::Payment::iTransact. It changes packages to Vend::Payment and places things there.AUTHORSMark Johnson and Cameron Prince, based on original code by Mike Heins.
|