But this question has come up before at HN and other places. Here are the collection of links on subscription. Pretty everything you need to know!
# http://www.sitepoint.com/forums/showthread.php?t=453028 # http://news.ycombinator.com/item?id=115723 (Recommended) # http://www.37signals.com/svn/posts/753-ask-37signals-how-do-... (Recommended) # http://discuss.joelonsoftware.com/default.asp?biz.5.550062.1... # http://news.ycombinator.com/item?id=48040 # http://news.ycombinator.com/item?id=47960 # http://news.ycombinator.com/item?id=12010 # http://news.ycombinator.com/item?id=47958 # http://news.ycombinator.com/item?id=33322 (Recommended) # http://news.ycombinator.com/item?id=49787 # http://news.ycombinator.com/item?id=12082 # http://groups.google.com/group/activemerchant/msg/635e1fec35... # http://blog.robwebb2k.com/2007/10/19/braintree-payment-solut... Braintree Reccomendation- (Recommended) # http://www.webmasterworld.com/ecommerce/3496741.htm # http://www.merchant-account-services.org/blog/building-a-rec... # http://www.merchant-account-services.org/article/payment-gat...
the problem with paypal's solution is that you either require your customer to create a paypal account which is a hassle and looks a bit unprofessional, or you store the credit card information yourself to do recurring billing. if you store credit cards yourself, in order to be PCI compliant you have to store them on a separate machine on a separate network from your web servers. if you're starting out small, that can be a big pain. paypal does offer recurring billing to an extent but you don't have much control over the process.
braintree offers "securevault" which lets you store the credit card info at their site and they return you a token for each customer. when you need to do recurring billing, you just submit the request to their server and pass a token instead of a credit card number and they take care of the rest.
Good option if you're a rails app.
https://www.braintreepaymentsolutions.com/get-started-now/fo...
They have some big names and they sound like a startup to look out for.
37signals doesn't even accept PayPal, which I think is one smart move.
The downside is you pretty much need to meet the huge requirements by the credit card companies to do it on your own servers. Which is why you need to find a merchant account provider that offers a way to store the data on their servers that meet those requirements. CDGCommerce is one, it gets very good reviews on all the webmaster forums and they have good rates.
Easy to learn, simple to integrate and test. No horror stories but my needs are simple and traffic small.
I don't know if you can charge each month however.
But I also see and advantage herein. You don't have to save the credit number and other sensitive details, so they can't be stolen on your servers.
Worth a look, particularly if you're using Rails as a framework (which I guess you might be since you cite Rails apps as examples).
-zuora -aria
they want 5-10k in implementation, 1k per month minimum, and 2-4% of your sales (keep in mind, that is ON TOP of processing fees)