←back to thread

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

(justuseapp.com)
693 points hienyimba | 2 comments | 14 Sep 21 10:51 UTC | HN request time: 0s | 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. mmerlin ◴[14 Sep 21 12:37 UTC] No.28523809[source]▶
Proceed with launch as planned and validate your market first of all.

After you have validation of customer buy-in and market acceptance, when you have time and/or funds to spend on your Stripe-alternative feature sprint, setup and integrate a 2nd payment gateway for redundancy.

(as per the commenter above whose biz was banned from Stripe for 7 days by the imperfect non-recourse ban-bot)

Maybe even choose a different gateway that is more cost effective per transaction for a subset of your global customers, and code your system to route customers payments to the preferentially lower-priced gateway for their country.

Then if one gateway bans you, it's not a showstopper and your business is not severely damaged.

replies(1): >>28524073 #
2. 0des ◴[14 Sep 21 13:00 UTC] No.28524073[source]▶
>code your system to route customers payments to the preferentially lower-priced gateway for their country.

This is pretty clever, thanks!