Hacker News new | past | comments | ask | show | jobs | submit login

Well, technically you have all the customer data in your gateway's info manager (like Authorize.net's CIM), but it would still be a real bitch to take that and do anything useful with it. Plus, the clock is ticking on your 30 days to get it migrated to your new setup.



CC, EXP and CVC as well ?

Without those you won't be doing much in terms of migration.

Other than contacting the customer, figure you'll lose 75% or more of your business that way.


In our case, all that stuff is handled via the Authorize.net CIM. Chargify stores everything in the CIM and just makes calls to Authorize's API.

To be clear: we can leave Chargify, but Authorize has us locked in.


What does chargify do for you that the authorize.net api can not do for you?


Honestly, I haven't looked closely at the raw A.net API. I heard about Chargify, pricing looked good, and it fit my model. Basically, I wanted someone else to deal with dunning, expired cards, running the periodic charges, etc, etc.

I write about it more here: http://peachshake.com/2010/06/15/saas-subscription-billing-o...

Up to now, I've been nothing but pleased with Chargify. This change makes me question their sanity a bit, though.


Here is the PDF with the authorize.net recurring billing integration information:

http://developer.authorize.net/api/arb/




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: