MCVE

Interchange's support for the Mainstreet Credit Verification Engine  Payment Services Provider.

Synopsis

or

Prerequisites

• MCVE.pm

Description

The Vend::Payment::MCVE module implements the mcve() 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 MCVE 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 "mcve".  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

A full setup would look like the following:

Settings

Name	Description
name	Your MCVE configuration username, set up when MCVE was configured/installed on the machine.  The variable is MV_PAYMENT_NAME
sale_on_auth	Normally Interchange charge modules do an authorisation and, if successful, do a sale.  This module is configurable for a different model, where transactions are not automatically committed.  The variable is MV_PAYMENT_SALE_ON_AUTH
no_sale_bad_avs	You may not wish to commit a transaction if the AVS is bad.  The variable is MV_PAYMENT_NO_SALE_BAD_AVS
no_sale_bad_cvv2	You may not wish to commit a transaction if the CVV2 is bad.  The variable is MV_PAYMENT_NO_SALE_BAD_CVV2
transaction	The type of transaction to be run.  Valid values are as follows: Interchange MCVE auth auth sale sale return return (not supported at this time) reverse reverse (not supported at this time) void void (not supported at this time)
counter	Not implemented.
counter_start	Not implemented.

Troubleshooting

Try the instructions, above, using a test credit card number provided by your payment processor.

Then 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::MCVE

• Make sure that the MCVE.pm Perl module is installed and working.
  
  
• 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::MCVE;  This module changes its package name to Vend::Payment and places things there.

Author

• MCVE modifications by tom@readyink.com  for Carlc Internet Services

Credits

• Derived from the CCVS.pm template, and others

Category:  Interchange payment modules

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