I need to give my client a comparison of what it will cost if instead he keeps and uses his Authorize.net account. I know the fees he pays for Authorize.net - is there anything else he will need besides that? I have been doing shopping carts for years, and I STILL get confused by all of the terminology surrounding merchant accounts and gateways. The article you linked to says they need a "merchant bank account, and another gateway provider." Authorize.net is the gateway provider, right? or would they need to sign up with something else to make it all work?
For his demographic, offering Paypal as an option is not really going to be a big selling point - hence why we were trying to avoid anyone ever having to go to Paypal or seeing Paypal anywhere. So I need to figure out if there is any reason (beyond not offering Paypal) to not use Authorize.net and if one option is going to end up being significantly more expensive than the other.
Are there any PCI compliance issues with using Authorize.net in conjunction with this plugin?
After having paid $40 for another plugin, plus $20 for their support to talk to me, I need to go into this with much more open eyes. Statistics: Posted by websydaisy — April 15th, 2011, 8:14 am
]]>