frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

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

160•snirgbs•5h ago•59 comments

Ask HN: What does building hardware with AI look like?

5•mjs06•9h ago•0 comments

Ask HN: What do coding interviews look like in the age of AI?

7•frankhorrigan•4h ago•3 comments

Ask HN: What are you working on? (November 2026)

303•david927•1w ago•1089 comments

Tell HN: Google Search to start locking down search behind a login wall

44•exploraz•2d ago•29 comments

Vercel should fork and maintain Deno

15•gfalcao•1d ago•13 comments

Ask HN: What is the state of self-hosting email in 2026?

45•0o777•2d ago•33 comments

Ask HN: Dropbox privacy policy, cause for concern?

10•herodoturtle•19h ago•2 comments

ChatGPT Desktop forwards your SSH agent to remote machines

221•DenGorbachev•6d ago•80 comments

Tell HN: Cloudflare's abuse report form is a blank page

17•basilikum•2d ago•6 comments

Anthropic, can you please make up your mind with your models?

5•xlayn•20h ago•7 comments

Ask HN: Which open source LLM works best locally, and on what hardware?

4•donkan168•9h ago•18 comments

Ask HN: What AI agent infrastructure are you using in 2026?

3•aurumagent•1d ago•2 comments

Ask HN: Do you still enjoy coding in C++?

66•hasley•6d ago•90 comments

Ask HN: What are the most useful, concrete AI skills to independently learn?

88•shnock•1d ago•52 comments

Ask HN: Best books you read in 2026?

13•013•1d ago•5 comments

Ask HN: How did you convince family and friends to join your XMPP/Matrix server?

102•mtlynch•1w ago•98 comments

Ask HN: Do you see a human written book more valuable than an AI written one?

11•znano•2d ago•23 comments

Using LLMs outside of reflection is an anti-pattern

4•jcarmackdaddy•2d ago•0 comments

Tell HN: Major Microsoft Outlook/Exchange Online/Teams Outage in the Americas

14•wmchen•3d ago•2 comments

You've reached the end!

Open in hackernews

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

160•snirgbs•5h ago
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

codingdave•3h ago
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.

pstuart•2h ago
Out of idle curiosity, how might such a business such as the OP's be able to arrange payments to use Stripe without getting shut down?
rtpg•2h ago
Don't charge $1 first? API-wise you can attach a card to a customer without charging it.

Maybe the $1500 thing still fails anyways but it won't look as much like fraud?

Or, y'know, just send the $1500 invoice after the fact and have that involve the client put in the card details there as a first shot. You _should_ (IIRC) be able to charge + capture the card in one go.

alwa•2h ago
Be upfront about the plan when you do the initial authorization. Stripe lets you signal a “set up a card on file” intent for this purpose, which doesn’t involve actually charging it $1.

IIRC it either provides or expects you to provide user-facing language like “you’re putting this card on file with this merchant, you know they’re going to charge it in the future according to their policies, right?”

https://docs.stripe.com/payments/cards/save-and-reuse

https://docs.stripe.com/payments/save-and-reuse

Or, like, send a fresh invoice for the $1500.

But charging a sale for $1 as a way to make sure the card is good is not the way. It maybe used to be the way in the low-fi days of physical terminals and phoned-in authorizations, but not today.

Either way I imagine you might earn more benefit-of-the-doubt once you’ve established a track record of smooth transactions.

accountrequired•1h ago
wild guess, but, if you can get the customer to click a fresh invoice link, maybe Stripe can analyze the browser/connection be more confident the charge is legitimate. it can then also be an interactive invoice with confirmation text message, for example.
Traubenfuchs•3h ago
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.

lostlogin•2h ago
Any comment on the other story here, from user breue?
weird-eye-issue•2h ago
Yeah bud they'll be right on that.
noir_lord•1h ago
I think they are on a yacht - https://www.washingtonpost.com/technology/2026/11/11/state-d...
misiti3780•14m ago
not a great look.
didgeoridoo•3h ago
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.

1123581321•3h ago
Stripe stresses written authorization when you capture intent to pay.
hackernud3s•1h ago
What? You mean have them write on paper and upload a photo of it?
antonvs•1h ago
For best results, use a carrier pigeon.
1123581321•1h ago
Haha. For anyone seriously wondering, it means that they clearly assent through something they can read, that you can store and reproduce in a payment dispute, e.g., a web app with credible database records and maybe a confirmation email.

You can manually type in numbers without this - this is classified as a phone order and you pay a higher rate for the risk. And they will evaluate your worthiness to enter/continue entering phone orders, so, unfortunately, probably a similar outcome as what happened to OP.

hackernud3s•1h ago
I've set up Stripe dozens of times and this is the first I'm hearing of this.
1123581321•42m ago
Capturing intent you charge later? I’m skeptical.
replwoacause•3h ago
I'm so tired of these big companies giving poor customer support unless they get called out on social media.
breue•3h ago
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...

weird-eye-issue•2h ago
So you allowed people to do card testing on your platform and never recognized it was happening? You have to keep on top of things like that especially if using Stripe Connect where users can withdraw money since you are facilitating theft and money laundering

> there was very little negligence on our side

Lol

> they nerfed the post

Nobody nerfed the post. It just isn't interesting since it's your fault. Lesson learned, hopefully!

matheusmoreira•2h ago
So the corporation doesn't care about a guy who generated 1.6 million dollars in fees and onboarded additional clients? Even when they post about their problem publicly on HN?

I suppose it's hopeless for the rest of us.

weird-eye-issue•1h ago
He misused their platform by failing to do proper verification of marketplace users and transactions and allowed criminals to extract several thousand dollars from victims of credit card theft. He's the one at fault here and his unverified claims about fees sounds like it's from a different project anyways so what exactly do you expect support to do? Roll out the red carpet and help him out with these fees related to the funds he helped launder? If he was negligent and didn't do the proper verifications of the buyers and sellers on his platform then he shouldn't have set it up in the first place. It's basic common sense and if he's really used Stripe so much he would know that. Instead of immediately blaming Stripe why don't you ask him if he followed all of the best practices for using Stripe Connect

It's a relatively risky thing to implement so you should only do it if you have all the checks in place and can accept a certain level of risk: https://docs.stripe.com/connect/risk-management

buckleyourshoe•2h ago
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•2h ago
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."

A_D_E_P_T•2h ago
> 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.

wewewedxfgdf•2h ago
Sounds like Stripe is on the same road as Paypal.
Aeseir•1h ago
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•1h ago
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.

Hizonner•1h ago
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?

philsquared_•40m ago
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.

josephcsible•12m ago
Stripe is wrong in this case. They'd only be right to leave you banned if you are a scammer. If you're not a scammer but just look like one, you should be able to get your ban overturned.
lossolo•28m ago
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?
anonymous908213•2h ago
It's also the pattern that millions of businesses use. It's like pattern matching against transactions on days that end in "y". You certainly will capture all fraudulent transactions that way, but...
ShinyLeftPad•2h ago
Criminals? I think AWS (or something similarly large) used to hold a dollar to make sure the card works, it's a pattern that is used
matheusmoreira•1h ago
I don't get it... I've had plenty of actual corporations test my credit card in that exact manner.

PayPal for example literally turned this into second factor authentication mechanism: they charged me some random amount and demanded to know the value they charged me. Apparently this is proof that I have access to the associated bank account.

antonvs•1h ago
Google (Gcloud) has done this in the past for me as well. Worse, the small payments sometimes originate from unusual places like Canada or Australia (I'm in the US), so I get bank notifications about them. I haven't seen one of these charges recently, though.
esperent•44m ago
I used to see this but in the last couple of years I've just seen a "card check" with no actual money taken. So maybe it's an old pattern?
crazygringo•32m ago
You seem to be confusing two things.

It's common for payment processors like PayPal to charge your bank account to ensure you control it, and then they refund it.

Charging your credit card is totally different. That is not common at all, and indeed there's no reason to.

hackernud3s•30m ago
Also known as a "subscription". It's pretty common.
1123581321•11m ago
No, that’s treated differently. We’re talking about when you capture permission to charge variable amounts later, from events Stripe can’t see. For example, this thread is about someone capturing $1 to validate a card, and charging $1,500 later for in-person appointments. That is still fraught in best circumstances because it used the wrong Stripe API, but it needed a better paper trail than the phone call to have a chance of being allowed.
aleqs•1h ago
You're trying hard to make it sound that this user and not Stripe is at fault here, without saying anything concrete/specific at all. If it was the user's fault - what specifically did they do wrong and what should have they done differently (doing ID checks on all users/buyers is obviously not a real solution for many reasons)?

Stripe is the one actually facilitating the payments, verifying the cards, enabling card testing, etc.

breue•1h ago
he should becomes stripe's public defender/lawyer
weird-eye-issue•1h ago
It's called common sense. Great work helping criminals launder money btw. In the future do some basic verification alright?
weird-eye-issue•1h ago
> doing ID checks on all users/buyers is obviously not a real solution for many reasons

I have a feeling you really don't understand how this works or what even happened. The problem is the sellers pretending to be buyers using fake credit cards to buy their own stuff and then getting money transferred to them. So while you say it's impossible yes you absolutely need to do verification of all of these sellers before you start sending them stolen money.

You've never even used Stripe have you?

aleqs•1h ago
Sellers buying their own products is just one way credit card fraud can work, and that's not what card testing is of itself.

You CANNOT prevent card testing by verifying seller IDs.

> You've never even used Stripe have you?

You seem to be very naively confident about your stripe knowledge for whatever reason, but again, you failed to point out any specific problem or solution in the scenario above.

Do you have a stripe connect platform? It would be hilarious if your didn't after all of that posturing. Please share and we can see how well it's set up to prevent card testing :)

weird-eye-issue•57m ago
Why are you arguing with me about the exact same points in two different places? jfc just reply here where I already replied to you

https://news.ycombinator.com/item?id=50512468

wonnage•46m ago
I’m so confused, your one previous submission on HN is an issue where Stripe failed to catch fraud and you had to do it manually, but now you’re here defending those same Stripe tools

https://news.ycombinator.com/item?id=36197160

weird-eye-issue•35m ago
> now you’re here defending those same Stripe tools

Where am I doing that? Connect and Radar are very different products. I was complaining about what turned out to be an exploit for a short period of time in Stripe Radar. It was being abused at a large scale on my product and similar ones and so I manually refunded transactions and worked with Stripe to flag similar ones and at the end of the day zero fraud actually got through without being refunded within a couple days.

That's a much different scenario from the one I replied to where they never verified the transactions or the "sellers" on his platform. See the difference? I spotted an issue and refunded the fraud, he didn't. That's the responsibility of the merchant.

When fraud does get through and leads to a chargeback I don't whine to Stripe because I have time to catch and refund those transactions. I was whining when hundreds of obviously fraudulent transactions got through Radar since that is specifically a paid product to help prevent fraud (it's not perfect even on a good day, and that's fine)

aleqs•1h ago
It's very interesting actually, and there is no evidence that they 'allowed card testing on your platform'. Not to mention it would be stripe that would be the main facilitator of card testing in this scenario, so it would be on them to detect and alert the user if that was happening.
weird-eye-issue•1h ago
No evidence? They said that's exactly what happened in that thread, I guess you missed that

Card testing is the merchant's responsibility because whether it gets through or not largely depends on settings the merchant controls. I guess you've never used Stripe, otherwise how would you not know that?

And yes even if you use Stripe Radar and the recommended integrations which will prevent most card testing you still have to have a process to manually review transactions from time to time. Again, merchant's responsibility. If you don't like that, don't take credit card payments....

aleqs•1h ago
That's not what they said at all. Feel free to provide a quote.

Just because you or stripe says 'the merchant is responsible for X' or 'this merchant allows card testing' doesn't make it true or valid, or that it even makes sense (stripe says its a 'shared' responsibility btw). It's the stripe API that actually enables card testing and individual merchants literally have no reliable way of preventing it.

> If you don't like that, don't take credit card payments.

Or maybe just don't use stripe? ;)

weird-eye-issue•1h ago
Here is the link of them saying that's "exactly" what happened: https://news.ycombinator.com/item?id=50399297

> individual merchants literally have no reliable way of preventing it

I'm a merchant. I've processed millions in transactions for my business. I've also manually refunded dozens of card test transactions that made it through Radar. Tell me again about how it's "literally" impossible to prevent?

> Or maybe just don't use stripe? ;)

Sure, but this happens with every company :) It's the nature of fraud online

> Please share and we can see how well it's set up to prevent card testing :)

It would make you happy to know our fraudulent dispute rate is well under 0.1% due to a combination of using Stripe Radar rules and periodic manual checks on transactions

> You CANNOT prevent card testing by verifying seller IDs.

I know. But it takes away the main incentive to do fraud on the platform in the first place. Card testing will still happen, just at a smaller scale. It's similar to the affiliate fraud that we deal with and when we switched to manually verifying our affiliates before they could sign up the card testing also dropped.

The_President•2h ago
Loading their dashboard now takes as long as brewing an 11 oz k-cup coffee.
aleqs•1h ago
Are you still using stripe today, or have you found something else?
breue•1h ago
yes, unfortunately i have a lot of projects with them and don't know of a better alternative.
ElProlactin•36m ago
> I had stripe fleece me for 4.5k...

In your post, you stated:

> I structured an overall secure system - there was very little negligence on our side

Overall secure system? Very little negligence?

Since the other comment critical of yours is being downvoted, for clarity: it appears you set up a service where you allowed individuals to set up accounts and sell their products or services to other people. Your service facilitated this, ostensibly for a fee. Fraudsters set up accounts and then proceeded to buy from themselves using stolen credit cards. Apparently, your service allowed the fraudsters to withdraw the funds from their fraudulent sales before you or Stripe caught on, leaving you on the hook to deal with the chargebacks and fees.

You also said this "all happened so fast", which suggests a planned, coordinated attack, which is not uncommon for credit card fraud these days.

Online payments suck and it's not comfortable dealing with big companies like Stripe. There are lots of horror stories about Stripe, PayPal, etc. that are legitimate, but yours doesn't sound like one of them.

Any service under which you allow individuals to sell things and you facilitate the transaction is inherently risky. Stripe might support this model (Stripe Connect) but no payment provider can completely insulate you from fraud in this model, and none is going to provide "insurance" for your losses if something goes wrong. It also doesn't matter that you had been an early user, referred other people to them, generated $x in fees from other projects, etc. Being a loyal customer doesn't give you a free pass to run an inherently risky business model carelessly and get bailed out when the risk becomes real.

Expecting Stripe to cover your losses was unrealistic. You were actually extremely lucky your total loss was only $4,500. It could have been much, much worse.

breue•25m ago
do you work for stripe? no one was expecting them to take the full loss - they provided zero help on bank reversals/debits - which they had some partial ability to help with. they could have even reduced the fees they collected as a result of the whole thing - but they offered absolutely zero help. if you do work there - this is not meant to offend you...
ElProlactin•14m ago
I do not, and this is not a helpful response.

Instead of insinuating that I must be an employee of Stripe because I questioned your complaint about Stripe, why don't you engage substantively with the discussion? Is there anything I wrote about what you described that is factually incorrect?

If you've built dozens of projects that have generated millions of dollars in fees for Stripe, one would expect you to have a pretty good understanding of payment processing, and the rules and risks. I also find it a bit odd that in another comment, you said you can't find an alternative to Stripe. If you're running services generating millions of dollars in fees, I'd expect you to have acquired your own merchant accounts directly and be using a multi-merchant strategy.

In any case, just to repeat: running a service in which you facilitate credit card payments for unrelated third parties is inherently risky and any payment platform that even allows it is not going to cover your losses if you fall victim to abuse or fraud.

ElProlactin•7m ago
In response to your edits:

1. Why would they reduce the fees? This type of fraud is a headache even for companies like Stripe. The fees run the business, and dealing with these sorts of issues is part of the business.

2. With this type of fraud, if you allowed your fraudulent sellers to access the funds from their fraudulent transactions on your service so quickly that they withdrew the funds before you knew what was happening, that money was moved the minute it hit the connected accounts. As I said, the model you were running was inherently risky, and you apparently made the biggest mistake possible: you let the third parties you were facilitating payments for, most of whom ostensibly had no history with you, access their funds without delay.