←back to thread

Stripe banned us for payment disputes but we never had a single dispute

(justuseapp.com)
693 points hienyimba | 1 comments | 14 Sep 21 10:51 UTC | HN request time: 0.219s | source
Show context
0des ◴[14 Sep 21 12:12 UTC] No.28523494[source]▶
As someone with a pre-launch SaaS who just signed up for Stripe, reading this has me shook up a little bit. I'm Stripe-integrated for payments, and poised to go through Stripe Atlas soon, or at least I was.. Now I have no idea what to do. I know that OP's story isn't spotless, but what if it's my thing that gets in this situation too?

I wish I could say I'm joking but I don't need this right now, I'm ~90 days out from launch, I should be tweaking final touches, not building just-in-case backup integrations with other processors.

replies(6): >>28523538 #>>28523607 #>>28523809 #>>28524057 #>>28524718 #>>28527471 #
1. arihant ◴[14 Sep 21 13:46 UTC] No.28524718[source]▶
Use a middleware like Chargebee. Your subscriptions will be saved and there will be no change in UX when you are forced to change the underlying payment processor. Even before launch (assuming you’re a US business) you can have a backup in form of PayPal Payflow Pro, which integrates fine with chargebee.