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.
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.
IIRC it also comes with 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?”
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.
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.
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."
The CEO or CTO of Stripe will be with you shortly.
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...
> 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!