[ic] Concord EFSNet payment gateway

[Kevin Walsh]

> >
> > If anyone has then they haven't contributed it for inclusion with
> > future Interchange releases.
> >
> I did what was perhaps the easiest hack in the world, eprocessingnetwork.com
> emulates the authorize.net API, so it simply was changing the servername and
> path in authorizenet.pm  Do you want such simple changes?
> 
Yes please; It'll save someone else from having to look up the details
of the change.

If it's just a matter of using the Concord EFSnet server, instead of
secure.authorize.net, you should set the following, rather than directly
editing the module:

    Route authorizenet host   whatever.eprocessingnetwork.com
    Route authorizenet script /path/to/script

It would still be useful to know the connection details you discovered
so that they could be added to the POD documentation in AuthorizeNet.pm.

-- 
   _/   _/  _/_/_/_/  _/    _/  _/_/_/  _/    _/
  _/_/_/   _/_/      _/    _/    _/    _/_/  _/   K e v i n   W a l s h
 _/ _/    _/          _/ _/     _/    _/  _/_/    kevin@cursor.biz
_/   _/  _/_/_/_/      _/    _/_/_/  _/    _/