Hacker News Reader

Comment by hex1848 | Hacker News Reader

Authorize.Net is what we've used for online payments and our internal subscription processing for over a decade. API is easy to use. Never really had any downtime. Rates are competitive. No one has come along and given us much of a reason to change.

View on HN

Everyone else is dumping on authorize.net, but they're willing to work with industries that PayPal and friends won't touch.

Have they added support for the Visa stored credential framework [1]?

Last I saw on their forums, a few months ago, a few people has asked about it but Authorize.Net didn't have anything yet. (Support has been kind of spotty in general among payment processors [2]).

I was going to check their forums again to see if anything has changed, but the forum link on their developer site is giving me a 404 right not.

[1] https://usa.visa.com/dam/VCOM/global/support-legal/documents...

[2] https://3dmerchant.com/blog/cenpos/which-payment-gateways-su...

They could really use someone who gives a damn to focus on their official libraries. They seem to have tried to make them function similar no matter which language you use. Not the smartest move, they end up being sort of convoluted in languages like Python. Which lead to many people starting a client library, but probably moving on from using them and the libs go unmaintained.

That brings me back. I remember Authorize.net before there was the ActiveMerchant gem (ruby).

Have you used Stripe as well? Authorize.net always got the job done. Then Stripe came along. I was honestly surprised of its success at the time. It was mainly just more of a joy to use - not cheaper or much easier. Just 'fun' as I remember it.

Authorize.net is OLLLLLLLLD school. Its the primary merchant service that is recommended/resold by banks.

I ended up choosing stripe but only because Stripe has better branding and was 'cooler' to use.

I worked with authorize.net in 2006/7 for a php driven lead gen site... that brings me back...

When stripe first came out my initial thought on the API was “these guys got tired of Authorize.Net”

Reply on news.ycombinator.com