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

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.

169 points | by snirgbs 12 hours ago

22 comments

  • breue 9 hours 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...

    • ElProlactin 6 hours 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 6 hours 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 6 hours 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 6 hours 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.

    • aleqs 8 hours ago
      Are you still using stripe today, or have you found something else?
      • breue 8 hours ago
        yes, unfortunately i have a lot of projects with them and don't know of a better alternative.
    • weird-eye-issue 8 hours 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!

      • aleqs 8 hours 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 8 hours 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 7 hours 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 7 hours 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.

              • aleqs 5 hours ago
                What does you being a merchant have to do with anything? Your understanding of how card testing works seems very surface-level to be honest - card testers generally will not test and buy from the same platform, for example.

                > 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.

                • weird-eye-issue 4 hours ago
                  > What does you being a merchant have to do with anything?

                  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.

      • matheusmoreira 8 hours 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 8 hours 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

          • aleqs 8 hours 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.

            • weird-eye-issue 8 hours 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 7 hours 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 :)

            • breue 8 hours ago
              he should becomes stripe's public defender/lawyer
              • weird-eye-issue 8 hours ago
                It's called common sense. Great work helping criminals launder money btw. In the future do some basic verification alright?
          • wonnage 7 hours 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 6 hours 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)

    • The_President 8 hours ago
      Loading their dashboard now takes as long as brewing an 11 oz k-cup coffee.
  • philsquared_ 7 hours 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 6 hours 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.
      • dannyw 6 hours ago
        We still don’t know what OP’s business actually is. From the description, it sounds very similar to activities like an escort business.

        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.

        • refulgentis 5 hours ago
          Isn't it in the first line? "Pre-booked appointments with homeowners, sold to local contractors" is appointment setting for home-improvement contractors: you line up a homeowner who wants a roofer, HVAC tech, etc., and the contractor pays per appointment that actually happens. That's a common, boring industry.

          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."

      • lmz 6 hours ago
        "Indistinguishable from scammer without manual intervention" isn't really scalable. 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?
        • Dylan16807 1 hour ago
          > "Indistinguishable from scammer without manual intervention" isn't really scalable.

          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.

  • didgeoridoo 9 hours 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.

  • codingdave 10 hours 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.

    • matheusmoreira 8 hours 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.

      • crazygringo 6 hours 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.

      • esperent 7 hours 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?
        • nicolas_t 6 hours ago
          Yes card checks with no money taken have been officiallg encouraged since early 2010s. I remember making the change on a few sites I had 15 years ago.

          It's a very old pattern but is no longer used for a reason

      • antonvs 7 hours 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.
      • cowlevel 6 hours ago
        Well PayPal is not a client of stripe or a client of PayPal. They have relationships and proper contracts with real banks, not some rentseeking riskminimising SaaS middleman.
    • pstuart 9 hours 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?
      • alwa 8 hours 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.

      • rtpg 8 hours 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.

      • accountrequired 7 hours 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.
      • cowlevel 6 hours ago
        Why not charge them $500 at the time they do the thing that costs $500
    • ShinyLeftPad 8 hours 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
    • anonymous908213 8 hours 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...
  • A_D_E_P_T 8 hours 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.

  • openspend 29 minutes ago
    I was reluctant with Stripe and made a somewhat effort to limit Stripe using openspend.net. In the early stages, I am looking for feedback on the product direction.
  • buckleyourshoe 9 hours 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 8 hours 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."

  • 1123581321 9 hours ago
    Stripe stresses written authorization when you capture intent to pay.
    • hackernud3s 8 hours ago
      What? You mean have them write on paper and upload a photo of it?
      • 1123581321 7 hours 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 7 hours ago
          I've set up Stripe dozens of times and this is the first I'm hearing of this.
          • 1123581321 7 hours ago
            Capturing intent you charge later? I’m skeptical.
            • hackernud3s 6 hours ago
              Also known as a "subscription". It's pretty common.
              • 1123581321 6 hours 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.
                • hackernud3s 5 hours ago
                  I agree that it's sketchier the way OP is doing it but Stripe calls that a payment intent either way. Or maybe it wasn't a payment intent the way OP did it, it's not clear.
      • antonvs 7 hours ago
        For best results, use a carrier pigeon.
  • dannyw 6 hours ago
    OP, what does your company actually do? Is your business compliant with the Stripe ToS?

    What kind of appointments? What services?

  • Aeseir 8 hours 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.

    • nicolas_t 6 hours ago
      The problem is that any competitor will start out good and then eventually become like stripe or paypal. It's not a high margin business (so can't easily spend to long on CS) there's a lot of frwud, etc...
  • alwa 6 hours ago
    My clanker senses started tingling a couple of uniformly-textured mini-paragraphs in. On that hunch, I ran it through Pangram. Who confidently assess this post to be 100% AI-generated.

    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/ )

  • cowlevel 6 hours ago
    Have you considered ditching Stripe and setting something up with an actual bank rather than a rentseeking middleman?
    • openspend 25 minutes ago
      Stripe's value is in accepting credit/debit cards. Banks won't deal with small businesses. Banks used to take months to give businesses a way to accept payments online and not sure if it has changed since then.

      I am building openspend.net and looking for feedback on the product's direction.

  • lossolo 6 hours 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?
  • wewewedxfgdf 8 hours ago
    Sounds like Stripe is on the same road as Paypal.
  • TZubiri 7 hours 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 7 hours 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?

    • JDups 5 hours ago
      It does read as the kind of "lead generation" grift from hustle bro AI boosters you see all over social media. But I don't know anything about the home improvement contracting business so I don't know how widespread this practice is in reality.
  • replwoacause 9 hours ago
    I'm so tired of these big companies giving poor customer support unless they get called out on social media.
  • ABlockShoes 5 minutes ago
    [flagged]
  • layoutaai 7 hours ago
    [flagged]
  • Traubenfuchs 10 hours 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.