Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I would avoid integrating directly with stripe, since if any trouble ever happens with your account (chargebacks, etc), and they terminate it, you need to change all your code before you can resume accepting payments. For this reason I recommend using an abstraction layer to buffer for payment gateways. One good option is Chargebee, which integrates with 12+ different gateways. This way, the same code can control different payment options, and you are not limited to one gateway.


Thank you, that is great information to have in mind! As I wrote in another answer, the subscription will most likely end up as a separate service so it wouldn't be a problem for customers to access the application if I get trouble with Stripe, at least. I would imagine that having a third party gateway would add to the expenses. I am not really too interested in that in the beginning.

Could you educate me when a chargeback would occur using Stripe?




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

Search: