[bop-devel] Authorize.net Direct Post Method

[Ivan Kohler]

On Tue, Dec 13, 2011 at 05:01:12PM -0600, Bob McClure Jr wrote:
> Hi Ivan,
> 
> My client has been using Business::OnlinePayment::AuthorizeNet for
> some time to handle Auth.net's AIM process.  Now they want to change
> to their Direct Post Method to get out from under some PCI
> requirements.

>  Auth.net has no support for Perl.  I suspect that
> Business::OnlinePayment::AuthorizeNet::AIM could be hacked into
> Business::OnlinePayment::AuthorizeNet::DPM, but thought I should first
> check to see if someone has already invented that wheel.

I'm not aware of anyone currently working on this with Authorize.net.

Third-party "browser redirect" systems like direct post are outside the 
scope of the framework that Business::OnlinePayment provides, so I don't 
think "hacking ::AIM into ::DPM" is any sort of reasonable way forward.

We've been working on a prototype framework for third-party services 
like PayPal and Google Checkout, called 
Business::OnlineThirdPartyPayment.  Personally I think we should rename 
before uploading to CPAN.  :)

The base module, a dummy processor module and two real processor modules 
are available from http://freeside.biz/cgi-bin/viewvc.cgi/

> Failing that, I'd like to find someone who could give me some tips on 
> what I'd need to change.
> 
> Any ideas?

Subscribe to bop-devel and ask if anyone's interested in working with 
you on Business::OnlineThirdPartyPayment::AuthorizeNet ?  And be 
prepared to take it on yourself if not.
:)

-- 
_ivan