TestPayment

Interchange's "payment test" module.

Synopsis

&charge = testpayment

[charge route="testpayment" param1="value1" param2="value2"]

Description

The Vend::Payment::TestPayment module implements the testpayment() 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 TestPayment with a few configuration file changes.

This module will perform one of the following actions:

If the card number is "4111 1111 1111 1111" then the transaction will be approved.
If the card number is "4111 1111 1111 1129" then the transaction will be declined.
Any other card number will raise an error and the transaction will be declined.

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

Require module Vend::Payment::TestPayment

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 "testpayment". To make it the default payment gateway for all credit card transactions in a specific website, you can set the following in catalog.cfg:

Variable MV_PAYMENT_MODE testpayment

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:

[charge route=testpayment id=testing]

Route testpayment id testing

Variable MV_PAYMENT_ID testing

Settings

Name	Description
id	A test account ID, which can be any value you like. The variable is MV_PAYMENT_ID.
secret	A test account password, which can be any value you like. The variable is MV_PAYMENT_HOME_PAGE. This is not needed for test charges, using this module, but you might as well set it up anyway.
transaction	The type of transaction to be run. Valid values are: auth return reverse sale settle void The transaction type is ignored in this version, but you may as well set it anyway.
remap	This remaps the form variable names to the ones needed by TestPayment.

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::TestPayment
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, Cursor Software , and other consultants, are available to help with integration for a fee.

Notes

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

Authors

Kevin Walsh
Based on original code by Mike Heins