Most active commenters
  • yaythefuture(3)

←back to thread

1624 points yaythefuture | 11 comments | | HN request time: 0.001s | source | bottom

Saw https://news.ycombinator.com/item?id=32261868 from a couple weeks ago and figured I'd share my own story.

3 weeks ago, I woke up to a pissed off customer telling me her payments were broken. My startup uses Stripe Connect to accept payments on behalf of our clients, and when I looked into it, I found that Stripe had decided to deactivate her account. Reason listed: 'Other'.

Great.

I contact Stripe via chat, and I learn nothing. Frontline support says "we'll look into it." Days go by, still nothing. Meanwhile, this customer is losing a massive amount of business and suffering.

After a few days, my team and I go at them from as many angles as possible. We're on the phone, we're on Twitter, we're reaching out to connections who work there / used to work there, and of course, we reach out to patio11. All of these support channels give us nothing except "we've got a team looking into it". But Stripe's frontline seems to be prohibited from offering any other info, I assume for liability reasons. "We wouldn't want to accidentally tell you the reason this happened, and have it be a bad one."

We ask: 1. Why was this account flagged? "I don't have that information" 2. What can we do to get this fixed? "I don't have access to that information. 3. Who does? "I don't have access to that information" 4. What can you do about this? "I've escalated your case. It's being reviewed."

I should mention at this point that I've been running this business since 2016, my customers have been more or less the same since then, and I've had (back when it was apparently possible) several phone conversations with Stripe staff about my business model. They know exactly who our customers are and what services we offer, and have approved it as such.

After a week of templated email responses and endless anxiety, we finally got an email from Stripe letting us know that they had reviewed the account and reactivated it. We never got a reason for why any of this had happened, despite asking for one multiple times. Oh well, still good news right? Except nope, this was only the beginning.

This morning I woke up to an email that about 35% of my client accounts had been deactivated and were "Under review", the kicker here being that one of those accounts is the same one they already reviewed last week! This is either the work of incompetent staff or (more likely) a bad algorithm. No reasonable human could make this mistake after last week's drama.

So currently, my product doesn't work for 35% of my customers. Cue torrent of pissed off customer emails.

And the best part is, this time I have an email from Stripe this time: Apparently these accounts are being flagged, despite the notes on our file, and despite the review completed literally last week, as not in compliance with Stripe's ToS. They suggest that if I believe this was done in error, I should reach out to customer support. Oh, you mean the same customer support that can't give me literally any information at all other than "We have a team looking into it"? The same customer support that won't give me any estimates as to how long it's going to take to put this fire out? The same customer support that literally looked into this a week ago and found no issues!?

I feel like I'm going crazy over here. These accounts have hundreds of thousands of dollars in them being held hostage by an utterly incompetent team / algorithm that seems to lack any and all empathy for the havoc they wreak on businesses when they pull the rug out from under them with no warning, nor for the impact they have on customers when they all of a sudden lose all ability to make money. And all that for an account that has been using Stripe for nearly 7 years without issue!

This goes so far beyond "customer support declining at scale." If lack of customer support means that critical integrations start to fail, that's not a customer support failure, that's a fundamental business failure.

Show context
edwinwee ◴[] No.32854831[source]
I work at Stripe. Could you email me at edwin@stripe.com and I can dig into this?
replies(5): >>32854864 #>>32854901 #>>32854933 #>>32854981 #>>32855086 #
1. MonkeyMalarky ◴[] No.32854864[source]
Here it is! The raison d'etre of these posts to HN!
replies(3): >>32854957 #>>32854965 #>>32855057 #
2. aliqot ◴[] No.32854957[source]
Bless Edwin for being here for us, always, time after time, but what a sad state of affairs.
replies(1): >>32855008 #
3. mikece ◴[] No.32854965[source]
Someone reaching out in this case is nice but what about folks who can't get their complaint to the top of the HN front page? I'm hopeful the OP gets everything sorted out but these no-warning, no-explanation, no-recourse suspensions need to be prohibited when the only thing a company says is "TOS violation."
replies(2): >>32855085 #>>32855132 #
4. jlbbellefeuille ◴[] No.32855008[source]
Edwin has saved me before too. Love Edwin.
replies(1): >>32858314 #
5. bee_rider ◴[] No.32855057[source]
It is nice that people can get a quick fix by hitting the front page here, but for the rest of the community we have to realize that this is does nothing to fix the systemic issue (of course I'm just stating the obvious here, but might as well make it explicit).
6. MonkeyMalarky ◴[] No.32855085[source]
Completely agreed. In the past, my employer has been in the same position with a different platform and to say it is an existential and Kafkesque nightmare is an understatement.
7. ball_of_lint ◴[] No.32855132[source]
There's a variety of cases where the only legal messaging around the suspension is approximately that. Whether or not Stripe is doing wrong here, they do have to comply with US law and that type of law will result in that shape of suspension and therefore this type of story appearing on HN.
8. yaythefuture ◴[] No.32858314{3}[source]
I'm proud to announce that Edwin officially pulled through for us today. All our accounts have been reactivated.

There are clearly problems at Stripe. But this kind human is not one of them.

replies(2): >>32858393 #>>32860387 #
9. trollied ◴[] No.32858393{4}[source]
You need to explain what happened, and what sector you operate in. Doing this support stuff on HN as a last resort & getting on the front page is crap in the first place, not feeding back is even worse.
replies(1): >>32865041 #
10. jlokier ◴[] No.32860387{4}[source]
I would still recommend you change your payment backend to direct your customer payments via one or more "backup" processors asap. Perhaps leave Stripe altogether if you prefer, once that's done, or keep Stripe around as the backup.

After all, they have a track record of screwing you over again, after fixing and checking your account. Whatever triggered that could do it again when you least expect it, despite Edwin's good work. Probably the triggers haven't changed as you are still running the same business.

(Like several other commenters, I was thinking of using Stripe as a main payment processor before seeing this article because of their great API, documentation, test mode and ease of setup. They seemed like a good choice, but I had wrongly assumed they were reasonable and reliable and if there were issues they could be resolved; that I didn't need to worry about Stripe being shady themselves. Now I've learned Stripe is like the Paypal of old when it comes to killing a business abruptly with no warning or recourse. That's so severe it cancels out every benefit and feature. With much disappointment I now feel it will be necessary to evaluate other services instead.)

11. yaythefuture ◴[] No.32865041{5}[source]
Edwin broke it down here: https://news.ycombinator.com/item?id=32859520