Live data from Hacker News

SaaS Subscription Billing, or How to avoid getting your n*ts in a vice

peachshake.com

1–10 of 43 posts

Re: SaaS Subscription Billing, or How to avoid getting your n*ts in a vice

#2
Chargify seems to be on the right path. I do think they could use some work on their flexibility though.

Holding credit card data is always a bitch. Paypal website payments pro's API lets you issue coupons and discounts that are baked into the initial signup. However midcycle its tough to issue a discount.

They also have some bugs in their API with their callback urls etc.

Re: SaaS Subscription Billing, or How to avoid getting your n*ts in a vice

#3
If you're concerned about credit card portability (as this blog author is), your only real options are Braintree's vault or Recurly. Chargify still stores the CC at the gateway level, so you have gateway lockin, which is no different than the PayPal/Amazon case the author bemoans.

Re: SaaS Subscription Billing, or How to avoid getting your n*ts in a vice

#4
I just finished building part of our billing system that signs up users for subscriptions. We're using metered billing and that part of our service doesn't report anything yet, but so far using chargify has been a great experience.

We don't need to hold CC stuff. We don't deal with dunning. We don't do anything except tell chargify how much our user has used and give them users credentials.

It seems to work very well.

Re: SaaS Subscription Billing, or How to avoid getting your n*ts in a vice

#8
From Braintree's site:

To try and help address this problem, we created a Credit Card Data Portability initiative (press release). It's an opt-in community of payment providers that agree to allow a merchant to port credit card and other associated information if the merchant ever decides to move to another provider.

http://www.braintreepaymentsolutions.com/blog/data-portabili...

Post reply on HN