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.
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...
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.
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.
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.
To me it seems like dependency on another intermediary for your payment processing as well as paying premium for that is not worth picking stripe over any traditional acquiring method, maybe I am missing something?
> 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!
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....
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? ;)
> 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.
> 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?
Uhh.. didn't you just demonstrate in the first sentence that you haven't prevented it?
> It would make you happy
It would make me happy if you shared a link to your platform :)
> Card testing will still happen, just at a smaller scale.
There's no reason to believe that seller ID verification will have any effect on card testing at all.
Well, I personally have quite a bit of experience since we have processed millions of dollars across tens of thousands of transactions and seen just about every type of fraud there is and have experience with detecting and preventing it and handling chargebacks. But other than that, yeah its not relevant at all ;)
> card testers generally will not test and buy from the same platform, for example
Well we offer low cost subscriptions so they will test/purchase those to test cards.
> Uhh.. didn't you just demonstrate in the first sentence that you haven't prevented it?
It is not about preventing 100% of fraudulent transactions from coming through. That is impossible, although of course it would be ideal. The achievable goal is about preventing chargebacks which is where the real fees and issues come from.
> There's no reason to believe that seller ID verification will have any effect on card testing at all.
Again, preventing fraudulent sellers will lower the incentive for fraud on the platform, which includes less card testing. Speaking from experience, which I have a feeling you have none of.
Anyways you seem very hung up about my use of "card testing". Whether they are testing cards or using stolen ones to launder money its really the same issue in this context. Usually the issue is both. If you just wanted to be pedantic go back to Reddit.
I suppose it's hopeless for the rest of us.
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
Stripe is the one actually facilitating the payments, verifying the cards, enabling card testing, etc.
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?
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 :)
https://news.ycombinator.com/item?id=50512468
https://news.ycombinator.com/item?id=36197160
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)
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.
I’m not saying that’s what OP does, but $1 + $1500 and being super vague about the commercial activity doesn’t help.
If OP wasn’t fully transparent and messaged stripe support explaining their business as “we connect homeowners with pre booked appointments” to Stripe then yeah, anyone who works in the field would’ve closed as unsupported business.
It did put a smile on my face, realizing how easy it is to miscommunicate. I never would have imagined someone hearing that and thinking "Ah, escort service."
Their fees on $1500 should be able to pay for a couple minutes of human verification, let alone what they make on future business.
> After all, this is the first occurence, who's to say this isn't some accomplice's card and they're not going to scam the next 10 customers?
You could say that about most businesses with recurring charges. Tripping this flag doesn't say much about whether there will be problems in the future. And if stripe just told them not to save card info for the future that would negate the red flag and put them on par with any new customer, there's absolutely no need to blacklist them.
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.
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.
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.
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.
It's a very old pattern but is no longer used for a reason
Stripe is only allowed to process payments in a country by primarily by partnering with local regulated financial institutions through a BIN sponsorship, acquiring bank partnership model, or by obtaining its own local licensing and direct banking network memberships.
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.
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.
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.
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."
But that’s not the business the OP described.
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.
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.
What kind of appointments? What services?
I wouldn't do the $1 test in the next time. Send an invoice each time and let the customer pay it. Their credit card should be on file but they initiate the action to pay the 1.5k.
The pattern described here is quite literally Stolen Card Checking 101. At the sole-proprietor, “even meth enthusiasts routinely come up with this” level of sophistication. With some “AI agent”-tier twists around oddly-recorded phone calls (with a first-and-only customer over many weeks), and logic that doesn’t really square against the way humans behave with each other in actual commercial relationships.
In the spirit of responding to the strongest possible interpretation, I grant that maybe OP’s green account is one of somebody who’s embarrassed by Stripe’s reaction to their enterprise, or timid about their English writing skills in a forum like this one—if that’s you, OP, I really, really don’t mean to be negative toward you, and I apologize for the grumpy tone. My reaction is to the AI-ness of it all, not to newcomers making earnest mistakes. (And I’d advise not trusting your AI’s business advice…)
That said, Stripe’s systems would be negligent if they didn’t shut this down.
I feel quite sure Stripe’s wizened safety folks weren’t fooled for a second. All of their communications described here seem… well, both precise and consistent with the facts the AI appellant lays out. The whole thing appears sketchy and fly-by-night from Stripe’s vantage point, and the business that operates this way is all well and good but is outside of their appetite for risk.
I guess my broader question is—and I know it’s by no means a novel one around here: our effort engaging with such a silly set of facts—is it still worth it as an object lesson for the actual newcomers who’re first encountering these kinds of questions?
(If you’re one of those, our very own @patio11 is a national treasure - https://www.bitsaboutmoney.com/ )
I am building openspend.net and looking for feedback on the product's direction.
>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.
Is it just me, or is everybody involved in this entire story kind of a sleazebag?
The CEO or CTO of Stripe will be with you shortly.