Overall Satisfaction with Authorize.net
Our company currently uses Authorize.net as one of a host of pay gateways whose implementation we offer to our client base. It is integrated into our contribution collection engine used across many of our clients' projects. It fits the needs of organizations looking for a simple way to link bank accounts to their web properties.
- Easy to connect to merchant accounts via plugin or API.
- Existing libraries make it fairly easy to plug and play with a variety of coding languages.
- Consistency in the API. As with any mature product, different areas of the API are at different stages. This can make integration of different features or products somewhat confusing.
- SSL protected/hosted JS library to offload any need for PCI compliance from the end user.
- It has allowed our client base to increase their reach when soliciting donations from potential supporters.
- Paypal and Stripe
The Authorize.net API is more robust than the competitors' that we tested. The one drawback is that there is no hosted SSL protected JS library, which is a great feature that Stripe offers. We chose Authorize.net for situations where the solution needed a very customizable experience with a server side hosted code.
Authorize.net is very well suited for any scenario that requires linking merchant accounts to a website that is on PCI compliant servers. It is easy to add to any custom integration or plugin, regardless of coding language. It is also very well suited for creating subscription based payments. Finally, it offers a more robust set of functions for verification of credit cards/bank accounts, particularly when needing to verify the legitimacy of a card/account while delaying the capture of the funds.