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::MCVE (3)

.ds Aq ’


Vend::Payment::MCVE - Interchange MCVE support





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


    mcve($mode, $opt);


The MCVE libraries are available free at


MCVE, Mainstreet Credit Verification Engine is a high performance software application designed to provide quality, in-house, Credit Card processing FROM Linux, FreeBSD, OpenBSD, IBM AIX, Sun Solaris, SCO OpenServer/UnixWare, and Mac OS X platforms to established clearing houses. The MCVE C & Perl library software can be downloaded free of charge from This module was developed and tested with the server software installed on ( Hot Connect, Inc. is an Interchange friendly Web Hosting, E-Commerce, and Internet Services company.

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

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

    Require module Vend::Payment::MCVE

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 mcve. 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  mcve

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=mcve name=mcve_configname]


    Route mcve name mcve_configname


    Variable MV_PAYMENT_NAME      mcve_configname

The active settings are:

    Variable   MV_PAYMENT_MODE mcve
    Variable   MV_PAYMENT_NAME mcve_username
    Variable   MV_PAYMENT_PASSWD mcve_password
    Variable   MV_PAYMENT_HOST
    Variable   MV_PAYMENT_PORT 8333
    Variable   MV_PAYMENT_COUNTER etc/mcve_id.counter
    Variable   MV_PAYMENT_SALE_ON_AUTH 1
    Variable   MV_PAYMENT_NO_SALE_BAD_CVV2 0

name Your MCVE configuration username, set up when MCVE was configured/installed on the machine. Global parameter is MV_PAYMENT_NAME.
no_sale_bad_avs Normally Interchange charge modules do an authorization, and if successful, do a sale. This module is configurable for a different models, where transactions are not automatically saled.
sale_on_auth The storekeeper may not wish to sale a transaction if the AVS is bad.
success_on_any Alternatively the storekeeper may wish to cause any transaction to appear to be a successful sale. The storekeeper would have to contact buyers with bad credit card information and manually redo the sale. The motivation is to make sure no one attempts a sale and gives up for any reason. This mode of operation, set with MV_PAYMENT_SUCCESS_ON_ANY is not commonly used.
transaction The type of transaction to be run. Valid values are:

    Interchange mode    MCVE mode
    ----------------    -----------------
    auth                auth
    sale                sale

Not supported yet:

    return              return
    reverse             reverse
    void                void

counter, counter_start Currently this is not being used, and Interchange is generating id’s.

    Route   mcve  counter        etc/mcve_id.counter
    Route   mcve  counter_start  100


Try the instructions above, with a test credit card number from your payment processor.

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

Make sure you Required the module in interchange.cfg:

    Require module Vend::Payment::MCVE

Make sure MCVE is installed and working.

Check the error logs, both catalog and global.

Make sure you set your payment parameters properly.

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

        $Tag->uneval( { ref => $Session->{payment_result} );

That should show what happened.


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


MCVE modifications by for Carlc Internet Services


Derived from template, and others.
Search for    or go to Top of page |  Section 3 |  Main Index

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

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