←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.241s | 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 #
soco ◴[14 Sep 21 12:21 UTC] No.28523607[source]▶
Like another commenter said, think about your payment processor like another thing which needs redundancy. Have another one prepared - braintree or whatever.
replies(1): >>28523656 #
0des ◴[14 Sep 21 12:25 UTC] No.28523656[source]▶
That's my initial assumption. I'm curious if this is common behavior to have two integrations, or if it is prohibited by the TOS.
replies(4): >>28523779 #>>28523859 #>>28529295 #>>28529586 #
1. fragmede ◴[14 Sep 21 19:15 UTC] No.28529586[source]▶
You're the customer, but you're a business customer, not a consumer customer. B2C vs B2B is different, and the contracts involved are different, and it's different way of thinking. The Internet I have at my house prohibits reselling because I'm buying it as a consumer. If I'm buying a business Comcast account, there's an expectation by Comcast that I'm going to be reselling the Internet access (like if I own a coffee shop or something). Thus, imo it's not common, but it's also not prohibited. (But I am not a lawyer and this is not legal advice.)

As for having two integrations, what's your opportunity cost? You'll want a backup integration, but imo that's in the same category as having a backup cloud to run on in case AWS goes down. Which, you do, but the time spent working on that is time spent not working on the product.