I have a client who is currently implementing a billing / scheduling system (they are in the medical field). The system they are implementing has an API, so they want to eventually hook in and provide online payments and perhaps online appointments as well.

With that said - is there a case I can make for Authorize.net merchant accounts as they relate to the development scenario described above? They currently have a merchant account with a bank - the first argument is obviously the auth.net one will most likely be cheaper, but I am looking for a backup like the development integration is better, or something along those lines.

Thoughts?

Authorize.Net is only a payment gateway. They actually do not do the credit card processing. You need a merchant account to go with Authorize.Net.

Having said that, Authorize.Net doesn't really provide any kind of billing or scheduling system. All they really do is act as a middle man between a billing / scheduling system and the merchant account. A separate piece of software would do all of the work and then connect to Authorize.Net to process and credit card sales. So if they would want to leave their current provider they would need a new system, an Authorize.Net account, and a merchant account. Although it is possible they may find this to be cheaper in the long run (they also may not) it is a lot of work.

Now if they plan on doing a lot of recurring billing Authorize.Net is good for that and easy to work with thanks to their API. Their Advanced API also is easy to work with so if you have to do the integration you won't find it time consuming or maddening.

Right - I guess I wasn't being clear. I know what authorize.net is - what I am looking for is another argument I can make to persuade a client that wants to do the development described, to go with my merchant account / payment gateway that is auth.net based...

Right - I guess I wasn't being clear. I know what authorize.net is - what I am looking for is another argument I can make to persuade a client that wants to do the development described, to go with my merchant account / payment gateway that is auth.net based...
The only way I see of you making a case is by developing a software that does what they need and uses Authorize.net and your merchat provider. Otherwise they won't be able to do much with your gateway and merchant account if there is no software that can handle the transactions, recuring billing and appointments.

Right - I guess I wasn't being clear. I know what authorize.net is - what I am looking for is another argument I can make to persuade a client that wants to do the development described, to go with my merchant account / payment gateway that is auth.net based...
In that case it is the usual case of convincing them you offer more. Authorize.Net itself (w/a merchant account) won't be much of a selling point unless the costs are significantly lower then their current provider unless your software will utilize a feature of Authorize.Net to offer your client something they really need or want. Since Authorize.Net serves a very well defined role I am not sure what that would be.

I think your selling points will come from what your software can offer more then what Authorize.Net can offer.

Hi Nieme,

Here is one idea for you... with Authorize.Net you could offer your client a true "all in one" solution for both their online payments AND their card present payments since Authorize.Net does also provide a Card Present option. (this is also true for some other gateway as well)

So here is one possible approach... you could provide software that helps increase their efficiency, allows them to process both their card present payments and then also ties in their online payments through one centralized software system that you develop.

This in turn could lead to cost & time reductions on the accounting side because you could consolidate their merchant account & payments all under one roof and allow them to get consistent reports and nicely structured reports & charts if they wanted.

Thus, not only could you save them money but you could also make their operations potentially more efficient and eliminate some headaches. Remember - depending on who you are pitching this too - see what "pains" they deal with each day and see if you can help them avoid, mitigate or eliminate some of them and you'll then have a very interested and motivated buyer. :)