Ask HN: How do you bill your clients? (for your app)
We are building a software service that will be paid for based on a monthly subscription model. We are not really interested in reinventing any wheels and writing a billing system, and are interested in what you all are doing for your applications.
Do you create bridges to other third party billing system? If so, which ones do you recommend to integrate with (we are a ruby on rails application).
If you think its a bad idea to use a pre-existing billing system, could you give reasons why you feel that way?
Thanks for the advice!
21 comments
[ 3.1 ms ] story [ 70.2 ms ] threadThat's what we use on our main Rails app (as opposed to PayPal on our other main subscription-based offering). It works great. The only hangup has been accepting international currencies (we're having to work with a different company for that).
The transaction fees are low, too–which actually makes a difference when you start getting a lot of subscribers.
http://www.braintreepaymentsolutions.com/ http://www.activemerchant.org/ https://peepcode.com/products/activemerchant-pdf
If we have to build it internally, that is what we are trying to avoid.
ActiveMerchant just connects your app to a gateway for cc approval and processing.
Braintree has very nice reports on transactions and it's very easy to refund a payment.
Beyond that, you are dealing with Rails after all–it's pretty easy to scaffold out some reports from your subscriber base.
All in all, I would choose this over PayPal regardless of the fees. The user experience is far superior.
Also, be careful with that peep-code PDF; their design isn't really the best so keep that in mind when reading through it and take their content merely as a suggestion. They couple their Orders with Transactions in a funky way.
Another thing, when dealing with BrainTree, be sure to pester them about how much the SecureVault costs. They came to us 6 months after we started using them and demanded that we pay $0.10-$0.15 anytime we touched a customer in the SecureVault. After a few back-and-forth's via email, they finally waived these fee's because they neglected to bring it up when we negotiated our rates.
In technical terms of payment gateway APIs, I liked Google Checkout's the best. They had a nice asynch RESTful XML API that made a lot of sense; although I didn't really like that fact that we had to send users through the Google Checkout screens. We had to move away from GCO because they didn't support recurring billing.
Has anybody used the Amazon Flexible Payment System?
http://railskits.com/
Regarding Brad's comments about our pricing, we've discussed this directly with him and agree that the specific communcation with him could have been done better. At the same time, we've expressed to him that we didnt' think the tone of his statement was fair or accurate. We always offer complete transparency in our pricing and do not use bait and switch tactics that are so commonly used in the industry.
@callmeed - thank you for your comments. You guys have been great to work with.
Another great thing about these guys is that you can actually email or call them and a person will pick up the phone. Good luck doing that with GCO, PayPal, or AFPS.
Also, as Jamie said, they offer an API to query payment data; while this isn't an asynch API like what Google offers, it at least opens up the possibility of writing a batch process that reconciles data between your application and Braintree.
Overall BT has been very responsive to our needs and, as a result, I have recommended them to many of the YC Summer '08 companies, along with many other companies I've talked to outside of YC.
I was also looking into blinksale and its API integration, thoughts?
cheers
justin