![]() |
| > Home > Documentation > Latest documentation > Interchange payment modules > ECHO |
|
ECHO
Interchange's support for the OpenECHO Synopsis
or
Prerequisites
If you have not done so already, you will need to sign up for an ECHO account.
You will be provided an ID and a PIN (also known as "secret").
You may also
sign up for a test account This module makes use of the OpenECHO module. You will need to make sure that OpenECHO.pm is in your Perl module path (@INC). The OpenEcho.pm file is available for download from the following locations: The OpenECHO.pm module itself has some additional prerequisites:
or
Only one of these needs be present and working. Net::SSLeay is preferred, as some have reported problems using LWP::UserAgent and Crypt::SSLeay.
The URL::Escape module is used to write some of the URIs used by the OpenECHO module. It is recommended that you read the documentation for the OpenECHO module itself in addition to this document. DescriptionThe Vend::Payment::ECHO module implements the echo() 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 ECHO 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 "echo". 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
Settings
Other variables
Example ConfigurationThis is an example configuration that one would add to catalog.cfg:
TroubleshootingThen 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:
Security considerationsBecause this library calls an executable, you should ensure that no untrusted users have write permission on any of the system directories or Interchange software directories. NotesThere is actually nothing in Vend::Payment::ECHO; This module changes its package name to Vend::Payment and places things there. Authors
Special thanks
DonationsPlease contact us if you have a HOWTO-style document, or anything else you'd like to share with other Interchange users and developers. Go on - you know you want to. |
| Home | Legal nonsense | Privacy policy | Contact us |