Ask HN: Stripe closed us after one $1,500 invoice and never asked for evidence

150 points - yesterday at 7:49 PM


We're a small business that sells pre-booked appointments with homeowners to local contractors, billed per appointment that actually happens.

Our first client agreed to this on a recorded call and saved his card through a $1 Stripe payment link, which we planned to use for billing later. That $1 payment went through.

A few weeks later we invoiced him $1,500 for 3 completed appointments and charged the saved card. Stripe blocked the payment. Two days after that the account was closed with this wording: payments "don't appear to have been authorized by the customer."

What happened next:

- We appealed through the Dashboard with an appeal letter, our company documents and the invoice. It was rejected the next day as an "unacceptable level of risk."

- Support told us our "business model presents a level of risk we're unable to support" and that the decision is final.

- After a Stripe employee escalated it internally, we got a short email saying Stripe still won't accept payments for our business.

In all of this, nobody asked us for the call recording, our messages with the client, or a confirmation from the client himself. As far as we know, he never disputed anything, and he has told us he is paying by bank transfer outside Stripe.

I'm not saying our setup is perfect. It's a new account, the first real charge was large compared to the $1 test, and billing a saved card later is probably what looked wrong. If there's something specific we should fix, I'll fix it.

What I'm asking:

1. Is there anyone at Stripe who can look at this with the evidence, including getting the client on a call?

2. For people who've been through this: how would you structure per-appointment billing so it doesn't look unauthorized (an invoice with a link each time, an email confirmation before each charge, something else)?

I can share the account details, the call recording and the messages with anyone from Stripe who wants to look. Thanks for reading.

Comments

philsquared_ today at 12:51 AM
This is as high risk as it comes... imagine a person bought a lemonade from you for $1 then later on you charged them $1500 because you saved their cc. That is all stripe sees.

You need to not charge the $1 at all first of all because technically that is a fraudulent transaction since the customer is expecting to pay $1500 not $1501. Stripes docs literally say this by the way... you can always run an auth but that isn't my recommendation...

You should be sending them payable invoices through stripes invoice system not manually charging a saved card. In this case you should have sent 3 $500 invoices.

Stripe is not wrong in this case. You made yourself look like a scammer.

breue yesterday at 10:29 PM
I had stripe fleece me for 4.5k - tried to complain about them on HN - they nerfed the post: https://news.ycombinator.com/item?id=50398646

The sad part is I was one of their first customers - I helped onboard over a 70 clients for them over the years.

And my top project generated them $1.6m in pure fees revenue. I even tried emailing Patrick and John - they don't care one bit. Its sad - they used to have a soul - became a ruthless/soulless company.

Sorry you are dealing with this...

didgeoridoo yesterday at 10:00 PM
Yeah unfortunately this charge pattern could not have looked MORE like merchant fraud. The right approach would have been to use https://docs.stripe.com/payments/setup-intents and set it for off-session usage.

You still might have gotten a payment hold on the first transaction until someone in risk could take a peek at your site to make sure you had all the right disclosures in place, but you probably would have kept the account.

codingdave yesterday at 9:45 PM
I have no knowledge specific to Stripe or your case, but do I know that the pattern you just described - a small 1 dollar payment followed by a large payment - is the exact pattern that criminals use to test stolen credit cards numbers. My bank will automatically reject anything following that pattern, put a hold on my card, and call me to confirm whether or not I have my card.

So yeah, if your business model calls for pattern matching with how stolen cards are used, that could very well be unacceptable risk to Stripe.

A_D_E_P_T yesterday at 11:00 PM
> 2. For people who've been through this: how would you structure per-appointment billing so it doesn't look unauthorized (an invoice with a link each time, an email confirmation before each charge, something else)?

Have you tried simply sending invoices via Stripe? Works for me, without a hitch. And it's pretty flexible; you can do a lot to modify terms, add notes, send email notices to multiple parties, etc.

If that won't work, there are payment processors who specialize in "high risk" accounts. Paykings come to mind. I've actually heard good things.

lossolo today at 1:03 AM
Why not just choose a different payment processor? They clearly don't want your business, and it's a free market. Why not take your business elsewhere instead of wasting hours or even days trying to get in touch with Stripe after being rejected 3+ times?
buckleyourshoe yesterday at 10:47 PM
I would be interested to hear about better alternatives that have functional support. We ran into problems with Google Cloud and were able to migrate to options with much better customer support. Are there payment providers like this available?
brudgers yesterday at 10:56 PM
We're a small business that sells pre-booked appointments with homeowners to local contractors, billed per appointment that actually happens.

I imagine that's not a dissimilar transaction pattern to how escort services and similar businesses might try to use Stripe.

Obviously there's no easy way for Stripe to tell if you are actually doing what you say you are doing.

In addition, based on my having a more than passing familiarity with laws regulating construction contracting [1], I would not be surprised if there are jurisdictions where your service is in violation of the laws and regulations governing construction contracting.

Even if it is legal where you are, there's no obvious way for Stripe to know that's the only place you operate. And if you only operate locally, you can use a local bank to process credit cards...assuming you meet normal criteria -- if you don't meet normal criteria, it's reasonable for Stripe to decline your credit card processing business.

So my advice, if you want to operate locally work with a local banker, a local lawyer, and a local insurance agent. These might not scale, but scaling is only a problem once you have a going business. Good luck.

[1] The laws regarding construction contracting are an "is" I am not arguing that those laws are/aren't an "ought."

1123581321 yesterday at 10:00 PM
Stripe stresses written authorization when you capture intent to pay.
Aeseir yesterday at 11:39 PM
I'll be first to say that Stripe is a shit company and I cannot wait to see a competitor detroy them.

Now onto main problem.

Issue is the $1 followed by large payment.

A lot of banks will flag this as suspicious, in some cases block the payment, or even proceed with investigation.

There is nothing telling Stripe that this is a potentially legitimate payment so they blocked it.

The fact they are shit company and don't explain this to you is another issue.

TZubiri today at 12:03 AM
I'm not an expert but:

>Client puts credit card details for 1$.

>You charge client for 1500$

The billing model is a bit high risk, the cleanest way to do it is to send the invoice to your customer for the specific amount you want to charge, unless it's a variable charge that is billed at the end of month, but you'd only do this if you are super well established, and have solid internal accounting, like AWS.

>- We appealed through the Dashboard with an appeal letter, our company documents and the invoice. It was rejected the next day as an "unacceptable level of risk."

I see this mistake often, but often from the consumer side, as a business you should know better. When you dispute some transaction with a financial provider, you only dispute the transaction itself, not the underlying contract, it's unrealistic to expect the financial provider to act as a judge.

This is a matter you need to take to a court, not to the financial provider.

Lessons learned, take care of your next payment processor, plenty of fish in the sea.

deleted yesterday at 10:40 PM
wewewedxfgdf yesterday at 11:26 PM
Sounds like Stripe is on the same road as Paypal.
Traubenfuchs yesterday at 9:55 PM
Hi, you are on the frontpage of hackernews and have reached our premium support.

The CEO or CTO of Stripe will be with you shortly.

replwoacause yesterday at 10:25 PM
I'm so tired of these big companies giving poor customer support unless they get called out on social media.
Hizonner today at 12:24 AM
Of course, you prominently disclose these kickbacks to the homeowners in advance, right?

Is it just me, or is everybody involved in this entire story kind of a sleazebag?

layoutaai today at 12:50 AM
[flagged]