[ic] checking Vend::Payment::BusinessOnlinePayment into CVS?

Ethan Rowe ethan at endpoint.com
Mon Oct 18 10:28:27 EDT 2004

Ethan Rowe wrote:

> ivan-interchange-users at 420.am wrote:
>> Hi,
>> Earlier this year I posted Vend::Payment::BusinessOnlinePayment, a
>> wrapper that allows the use of Business::OnlinePayment payment modules
>> with Interchange.
>> Business::OnlinePayment is a set of related CPAN perl modules for
>> processing payments with different online gateways:
>> http://420.am/business-onlinepayment
>> The module can be downloaded from
>> http://420.am/cgi-bin/viewcvs.cgi/Vend-Payment-BusinessOnlinePayment/Vend-Payment-BusinessOnlinePayment.tar.gz?tarball=1 
>> What would be necessary to have a developer check this into
>> Interchange CVS, or get access to do so myself?
>> The license is GPL/Artistic and I would be happy to assign copyright to
>> the Interchange Development Group if desired.
> Hi.
> This sounds interesting and promising. I'll try to take a look at this 
> within the next week or so; I should be able to do some testing 
> against Verisign and Authorize.Net at least. I'll report back here 
> with what I find.
> Thanks.
I've done some exploration of this module and was pleased with the 
result.  My testing only included Authorize Net; however, setting things 
up to work with the payment gateway were really quite simple.  
Essentially, once you have the Business::OnlinePayment module and the 
associated gateway-specific module(s) in place, and successfully tested 
independently of Interchange, getting Interchange to operate with the 
BusinessOnlinePayment.pm module was really quite simple.  I've never 
never used the Business::OnlinePayment modules before, incidentally.

The only extra bit of configuration required for this module is the need 
to specify the particular processor in the payment route, charge 
operation, etc.  With most Interchange payment modules, the module is 
specific to the processor; obviously part of the point of this module is 
to eliminate that specificity.  Therefore, it necessitates an extra line 
in your configuration.  For instance:
Route  onlinepayment  id           "__MV_PAYMENT_ID__"
Route  onlinepayment  secret       "__MV_PAYMENT_SECRET__"
Route  onlinepayment  processor    AuthorizeNet

The "processor" setting gets passed along to Business::OnlinePayment and 
must match up with a Business::OnlinePayment::xxxx gateway-specific 
module to use for the actual transaction.

My tests were not exhaustive by any means, but I was able to handle 
successful and unsuccessful transactions gracefully, and the setup was 
quite easy.  Therefore, I believe this module is worth a look, as it 
effectively pulls out the responsibility of communicating with a gateway 
from Interchange's core.  In my humble, very-possibly-insignificant 
opinion. :)


Ethan Rowe
End Point Corporation
ethan at endpoint.com

More information about the interchange-users mailing list