Today I received an email from someone wanting to use my services but doesn't want to use Paypal. All I want to do is set up a payment processor for credit cards where: Credit card info is stored on the processor's servers The processor use IPN or XML-RPC to create the account in Amember - instead of creating the account then accepting payments, for better conversions, the account is created with payment. Payments are recurring (subscriptions) Fees are reasonable (Remember, I currently use paypal). I'm looking at the supported payment systems page and it has good amount of information. So I've narrowed it down to: 1ShoppingCart/MCSSL http://www.1shoppingcart.com/ 2Checkout http://www.2checkout.com/ ccBill http://www.ccbill.com/ YowCow http://www.yowcow.com/ (seems to be down) 1ShoppingCart has more than I need. 2Checkout seems most reasonable but doesn't warn of cancellations. ccBill sounds good but charges 14.5%. Any advice?
If you want to pay $30/mo you can upgrade your PayPal account to Pro(website payments pro) and use the paypal_pro plugin which gives you both the option for paypal payments and cc via PayPal....as long as you have ssl enabled the cc page of the plugin doesn't touch the PayPal site as far as the end-user knows for it is all done on your site. It just utilizes their gateway. If you pay an additional $30 (total of $60) you can have your Pro account handle recurring subscriptions but the aMember plug-in currently doesn't work with that option...I see recent rumors to expect that functionality shortly, though, which would be a huge assistance. If just a strict processor/gateway is needed I'd recommend getting a merchant account and use authorize.net but it really depends on the volume you process to where the fees are competitive. I haven't used any of the ones you mentioned though will be looking further into 2checkout for another project I'm working on so take that advice with a grain of salt
Thanks, but $60 a month is too steep. It would be otherwise. I don't want a merchant account - don't want to store credit card information on my server at ALL. Don't want the potential liability. I'd rather give that responsibility to professionals used to securing credit card data. That's why I chose my list above.
Authorize.net SIM integration? There are a few merchant accounts that don't require you to store CC data on your server (check the official amember list).