On 7/23/07, schof <sean.schofi...
> The plan is to use ActiveMerchant for the payment gateway stuff.
> I've already used it in some tests with Authorize.net and it works
> great. No sense in reinventing this part IMO.
I think maybe there is a misunderstanding. What I'm working is a
payment gateway itself, not a connector to existing gateways. Payment
gateways connect to processing networks such as Firstdata and Vital.
What I have connects directly to the processing networks and
eliminates the need to use a payment gateway at all. You would still
use activemerchant, there would just be another adapter added to it
for what I am creating.
Why do this? Two main reasons. First, what people really want is a
complete solution, not a shopping cart + payment gateway where they
have to use two different interfaces to manage their business. It's
an unnatural separation. A lot of commercial solutions know this and
have implemented the payment gateway features into their core
applications so they can give people a unified UI. Mercantec,
MonsterCommerce, Netsuite, and several others have moved in this
Second, most payment gateways suck. Their UI's suck and their
features suck. And unless you pull the payment gateway into your
application, there is nothing you can do about this. Your application
and your users just have to deal with it.
Now all that said, I realize that this is most likely not something
you are interested in. There is still a need for a good stand alone
shopping cart system in rails. Being that what you are doing is bsd
licensed I'm still interested in working on this project also and
possibly incorporating some of it back into what I am doing. The main
difference would be that some functionality which you leave to a
payment gateway would be built into the system I am creating. Things
like recurring billing and detailed transaction reports for example.