The only thing going for Authorize.net is that it is supported everywhere in every language and every framework. And, of course, they aren't actually a merchant services provider. They are just a gateway service. You need both to accept credit card payments (if I could find a company that did both really well, I'd switch to them).
Authorize.net is a bit pricey and a bit difficult to use. But, it is the gateway service that we currently use...and when I switched to another shopping cart, we didn't have to change gateway providers or write new processing code. Which was nice.
When we write our own shopping cart (which seems impossible to avoid, because everything we've tried is such a poor fit for the way we sell our software), it won't tie into Authorize.net. It'll use PayPal, Google Checkout, and some other payment gateway (whichever one works with the cheapest merchant services provider, while still offering recurring payment support, probably).
Comments
The only thing going for Authorize.net is that it is supported everywhere in every language and every framework. And, of course, they aren't actually a merchant services provider. They are just a gateway service. You need both to accept credit card payments (if I could find a company that did both really well, I'd switch to them).
Authorize.net is a bit pricey and a bit difficult to use. But, it is the gateway service that we currently use...and when I switched to another shopping cart, we didn't have to change gateway providers or write new processing code. Which was nice.
When we write our own shopping cart (which seems impossible to avoid, because everything we've tried is such a poor fit for the way we sell our software), it won't tie into Authorize.net. It'll use PayPal, Google Checkout, and some other payment gateway (whichever one works with the cheapest merchant services provider, while still offering recurring payment support, probably).