←back to thread

158 points interesting_att | 5 comments | | HN request time: 0.949s | source

Hi Guys--

I started a Stripe account (even incorporated through them) for a basic graphic design and web design service business.

I process a few charges and even though I didn't get a single chargeback or dispute, Stripe decided to deactivate my account and said they would refund all the charges that were processed.

Which would have been fine with me. They said they would refund on Oct 17, but that date came and past. So I kept emailing.

Now they're saying they're holding all the funds for 120 days because of "elevated risk".

Which is insane because they have already withdrawn all the funds, meaning their risk would be zero if they refunded everyone.

I am beyond hurt and confused as I did need this money for my daughter. These decisions have real impacts on real families.

What do you do in this scenario? I have tried contacting support at Stripe but seems to be of no help.

Show context
johnhaddock ◴[] No.33301001[source]
I’m the person leading the project to make sure that people have fewer bad experiences with Stripe. I’m not sure what is driving the uptick in posts on the subject to HN in particular (obviously we pay attention to broader online discussion in addition to monitoring our support systems, though we know it creates an incentive for people to publicize their situation).

On the topic of Stripe and these kinds of incidents more broadly, there’s a lot to say, but here are a few pieces of context that are probably relevant:

- We are a giant distributed bounty system for people to find interesting and scalable ways to defraud us.

- We’ve seen significant upticks in certain kinds of fraud over the past couple of months. When businesses default, Stripe takes on the loss. It’s worth noting that certain kinds of fraud, like card testing, can also have significant collateral costs for legitimate Stripe businesses, and our systems and processes are not only to protect Stripe itself.

- We are far from oblivious to the harm that mistakes in our systems can cause. (I interact with a lot of these cases personally.) One of my highest priorities is creating better appeals flows for when we’re wrong.

- We’ve shipped 7 substantial improvements just in the last 10 days that should meaningfully reduce the occurrence of false positives.

- Publicly-described facts of specific cases don’t always match the actual facts. Stripe is sometimes just wrong. (We made some mistakes that I feel bad about in one recent case and we ended up bringing the company’s founders to an all hands last week to make sure we learned as much as possible.) But users do also sometimes publicly misrepresent what’s going on. We’re also restricted by privacy rules to not share specifics in those cases.

- Stripe works with millions of businesses and we see all kinds of “rare” failure modes fairly frequently. (Disputes between staff at a business, business impersonation, businesses that start legitimate and go bad, and so on.)

- I’m working on a post to share some of our broader philosophy + policy changes that I hope to publish before the end of this year. In that, I’m also hoping we can share some relevant metrics. If HNers have any suggestions for things that might be useful to see covered (though obviously certain things can’t be publicly disclosed), feel free to suggest them.

Ultimately, we work hard to be worthy of the trust of businesses across the internet, and my personal mandate (supported by many others, from our cofounders down) is to find effective new ways of making mistakes less likely. “Uniformly good support at scale, in a highly adversarial environment, with very financially-motivated actors” is not easy, but I’m pretty confident that we can make a lot of progress.

It goes without saying we're working on a review of OP situation. I’m happy to take general questions as well. You can also always reach me directly at jhaddock@stripe.com.

replies(7): >>33301036 #>>33301240 #>>33301249 #>>33301348 #>>33301998 #>>33302054 #>>33314426 #
1. johnhaddock ◴[] No.33301313[source]
We’ve been investigating this case for the past 24 hours, and it's not straightforward. I can’t share more publicly here, but we’re in touch directly with OP.
replies(1): >>33301560 #
2. throwawayacc2 ◴[] No.33301560[source]
OP can you lay out your version of the events please? And also give written permission to the Stripe guy to lay out his version? I want to see how the two compare. Feel like watching some drama this evening.
replies(1): >>33301626 #
3. dymk ◴[] No.33301626{3}[source]
OP giving written permission to Stripe is going to result in exactly nothing detailed being posted here by Stripe.
4. unethical_ban ◴[] No.33302080[source]
It is mind-bogglingly hilarious how many people in this thread think banks do this stuff for fun, or are even legally allowed to talk about a case. The fact that Stripe people are even in this thread, frankly, is huge.

Just because the person you're talking to is a representative of a scolded vendor does not give you the right to be a jackass.

5. drivebycomment ◴[] No.33302130[source]
> What are you doing to solve OPs problem?

That assumes the OP's problem deserves to be solved. We have no way of knowing that unfortunately, as there's non trivial chance OP did something not quite kosher knowingly or unknowingly.