For more information... RTFM!
NAVIGATION
ACCOUNT LOGIN

You are not logged in

Powered by Interchange version 5.7.0

AuthorizeNet

Interchange's support for the Authorize.net Link to an external page Payment Services Provider.

Synopsis

&charge = authorizenet

or

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

Prerequisites

Net::SSLeay

or

LWP::UserAgent and Crypt::SSLeay

Only one of the above options needs be present and working.

Description

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

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

Require  module  Vend::Payment::AuthorizeNet

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 "authorizenet".  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  authorizenet

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=authorizenet id=YourAuthorizeNetID]

or

Route  authorizenet  id  YourAuthorizeNetID

or

Variable  MV_PAYMENT_ID  YourAuthorizeNetID

Settings

Name Description
id Your Authorize.net account ID, as supplied by Authorize.net when you sign up.  The variable is MV_PAYMENT_ID.
secret Your Authorize.net account password, as supplied by Authorize.net when you sign up.  The variable is MV_PAYMENT_SECRET.  This may not be needed for actual charges.
referer A valid referring URI.  Match this with your setting on secure.authorize.net.  The variable is MV_PAYMENT_REFERER.
transaction The type of transaction to be run.  Valid values are as follows:

Interchange AuthorizeNet
auth AUTH_ONLY
return CREDIT
reverse PRIOR_AUTH_CAPTURE
sale AUTH_CAPTURE
settle CAPTURE_ONLY
void VOID
remap This remaps the form variable names to the ones needed by Authorize.net.
test

Set this to TRUE if you want to operate in test mode.  This sets the Authorize.net "x_Test_Request" query parameter to TRUE.

Examples:

Route   authorizenet  test  TRUE

or

Variable  MV_PAYMENT_TEST  TRUE

or

[charge route=authorizenet test=TRUE]

Troubleshooting

Try the instructions above, then enable test mode.  A test order should complete.

Disable test mode and then test in various Authorize.net error modes by using the credit card number "4222 2222 2222 2222".

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

  • 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, consultants are available to help with integration for a fee.

Notes

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

Authors

Credits

Category:  Interchange payment modules
Last modified by: Kevin Walsh
Modification date: Tuesday 19 September 2006 at 9:20 AM (EDT)
Home  |  Legal nonsense  |  Privacy policy  |  Contact us