GSP
Quick Navigator

Search Site

Unix VPS
A - Starter
B - Basic
C - Preferred
D - Commercial
MPS - Dedicated
Previous VPSs
* Sign Up! *

Support
Contact Us
Online Help
Handbooks
Domain Status
Man Pages

FAQ
Virtual Servers
Pricing
Billing
Technical

Network
Facilities
Connectivity
Topology Map

Miscellaneous
Server Agreement
Year 2038
Credits
 

USA Flag

 

 

Man Pages
Vend::Payment::EFSNet(3) User Contributed Perl Documentation Vend::Payment::EFSNet(3)
 

Vend::Payment::EFSNet - Interchange EFSNet Support

    &charge=efsnet
 
        or
 
    [charge mode=efsnet param1=value1 param2=value2]

  Net::SSLeay
 
    or
  
  LWP::UserAgent and Crypt::SSLeay
Only one of these need be present and working.

The Vend::Payment::EFSNet module implements the efsnet() 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 EFSNet with a few configuration file changes.
To enable this module, place this directive in "interchange.cfg":
    Require module Vend::Payment::EFSNet
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 "efsnet". 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  efsnet
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=efsnet id=YourEFSNetID]
or
    Route efsnet id YourEFSNetID
or
    Variable MV_PAYMENT_ID      YourEFSNetID
The active settings are:
id
Your EFSNet Store ID, which you can get from the Merchant Services panel after logging in with the username and password supplied to you by Concord when you signed up.
http://www.concordefsnet.com/Developers/MerchantLogin.asp
(Check the "Credentials" page after login)
Global parameter is MV_PAYMENT_ID.
secret
Your EFSNet Store Key, which you can get from the Merchant Services panel. Global parameter is MV_PAYMENT_SECRET.
transaction
The type of transaction to be run. Valid values are:
    Interchange         EFSNet
    ----------------    -----------------
        auth            CreditCardAuthorize
        return          CreditCardRefund
        reverse         CreditCardRefund
        sale            CreditCardCharge
        settle          CreditCardSettle
        void            VoidTransaction
    
remap
This remaps the form variable names to the ones needed by EFSNet. See the "Payment Settings" heading in the Interchange documentation for use.

Try the instructions above, then switch to the test servers. A test order should complete with this test card number: 4111 1111 1111 1111
Enabling the test servers:
MV_PAYMENT_HOST testefsnet.concordebiz.com
If nothing works:
Make sure you "Require"d the module in interchange.cfg:
    Require module Vend::Payment::EFSNet
    
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 -e 'print "It works\n"'
    
or
    perl -MLWP::UserAgent -MCrypt::SSLeay -e 'print "It works\n"'
    
If either one prints "It works." and returns to the prompt you should be OK (presuming they are in working order otherwise).
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:
    <XMP>
    [calc]
        my $string = $Tag->uneval( { ref => $Session->{payment_result} });
        $string =~ s/{/{\n/;
        $string =~ s/,/,\n/g;
        return $string;
    [/calc]
    </XMP>
    
That should show what happened.
If all else fails, consultants are available to help with integration for a fee. See http://www.icdevgroup.org/ for mailing lists and other information.

CreditCardCredit transactions (where you apply a credit on a card without the transaction ID of a previous charge) are supported by this module, but disabled by default in new EFSNet accounts. If you need to use this function, call EFSNet.
This module supports partial returns, but EFSNet needs to know what the original transaction amount was. You can provide this by passing the value in the original_amount parameter.

Concord EFSNet requires all interface code to be certified by them. If you make a change to this module, please contact EFSNet for re-certification. More information at: http://www.concordefsnet.com/Developers/Documentation.asp

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

Chris Wenham <cwenham@synesmedia.com>. Based on code by Mark Stosberg <mark@summersault.com> and Mike Heins <mike@perusion.com>.

    Jeff Nappi <brage@cyberhighway.net>
    Paul Delys <paul@gi.alaska.edu>
    webmaster@nameastar.net
    Ray Desjardins <ray@dfwmicrotech.com>
    Nelson H. Ferrari <nferrari@ccsc.com>
2010-03-25 perl v5.28.1

Search for    or go to Top of page |  Section 3 |  Main Index

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