21–30 of 299 posts
Earlier quoted context omitted.
Yes. it's 0.5% per payment* on top of 0.4% per "invoice". Quite hefty fees considering credit card fee is 2.9%
Woa I’m selecting payment processors right now — does this mean the “subscription” / “billing” fees of 0.5% are on top of the 2.9%?! https://stripe.com/billing
I've noticed Stripe products tend to be buggy and/or half-finished. What's the deal with that? Anyone know why a company with so much talent and great product that seem polished seem to have critical issues?
I thought I was crazy looking at their API and thinking it was crap because everyone seems to praise the Stripe API. I ran into undocumented sections around line items for Checkout objects, and the whole loop-around to go from Checkout Session -> Payment Intent -> Charge Information -> Order Information -> Line Items (or whatever order the 4 separate, synchronous requests our app has to do to get cart line items) is…
Could be to support payment methods in Europe and countries other than the US?
Earlier quoted context omitted.
I thought I was crazy looking at their API and thinking it was crap because everyone seems to praise the Stripe API. I ran into undocumented sections around line items for Checkout objects, and the whole loop-around to go from Checkout Session -> Payment Intent -> Charge Information -> Order Information -> Line Items (or whatever order the 4 separate, synchronous requests our app has to do to get cart line items) is…
> Like, why do we even need Payment Intent? Could be to support payment methods in Europe and countries other than the US?
https://stripe.com/payments/checkout
It's supposed to make payments easier with a Stripe-hosted payments page. However, creating a server-side Checkout session, and then getting line items from an order, is an unnecessarily convoluted series of requests.
Earlier quoted context omitted.
In the post he says: >I had noticed that my cashflow for the previous 2-3 months seemed to be tanking a bit A bit? Revenue from all US customers went to zero for three months! That should have been a giant hole. This is like driving your car into a lake, hearing a "bang" as the engine explodes, then complaining that there's no "you have driven into a lake" warning light on the dashboard.
You are assuming that a large number of their customers are from the U.S. not knowing what business they are in, their customer pool might be 90% Canadian. The whole world doesn't necessarily target U.S. customers.
> I have functionally 1/3 of my customers that I am going to have to back-bill for months of subscription fees
I'm not quite understanding the need to put them on blast here. Yes, they should have been more apologetic and they should certainly have escalated your ticket more quickly. But they made the changes you wanted seen: better documentation & better process, and reaching out to customers proactively when they see this problem.
When companies behave this way it feels like you're being gaslit, which is extremely frustrating. The author may have gotten the result they initially wanted, but it would have felt like a huge, disrespectful, slap in the face.
Earlier quoted context omitted.
Woa I’m selecting payment processors right now — does this mean the “subscription” / “billing” fees of 0.5% are on top of the 2.9%?! https://stripe.com/billing
Somewhere it says the first million is free, so if you're small time it's effectively free
[edit] I’m willing to be educated, please tell me how this isn’t Invoices with stored payments (which I’ve now seen has an additional fee too)
Earlier quoted context omitted.
In the post he says: >I had noticed that my cashflow for the previous 2-3 months seemed to be tanking a bit A bit? Revenue from all US customers went to zero for three months! That should have been a giant hole. This is like driving your car into a lake, hearing a "bang" as the engine explodes, then complaining that there's no "you have driven into a lake" warning light on the dashboard.
You are assuming that a large number of their customers are from the U.S. not knowing what business they are in, their customer pool might be 90% Canadian. The whole world doesn't necessarily target U.S. customers.
Since they also mention that they would like to hear what people think about this situation, here's my take:
They deployed a major change/migration to their billing system, implementing a brand new product, and seemingly didn't bother to investigate how it was going beyond cursory looks at a dashboard. Even though they did notice a strange dip in revenue. That seems fairly negligent for one of the most critical aspects of your product. Doesn't take that much time to take a glance at a more detailed view than a dashboard.
Stripe definitely could have been sending more notifications of failed invoices, made the documentation more clear, or been smarter about disabling automatic_tax for customers outside the user's tax jurisdiction. I don't know if the webhooks solution they mention is their standard for these kind of things or how much responsibility is reasonable for the user to monitor those. It does sound like they have/had at least some deficiencies with the new product that would have warranted a more generous response.
The author did seem to realize what was up and how they could have fixed it but chose not to because they were mad at Stripe. I feel like the wrath is somewhat overblown, sometimes you take a risk on a brand new product and have to babysit it a bit more than something mature.
Earlier quoted context omitted.
You are assuming that a large number of their customers are from the U.S. not knowing what business they are in, their customer pool might be 90% Canadian. The whole world doesn't necessarily target U.S. customers.
The author mentions "functionally 1/3 of my customers" and "I can not stress how much this has f*cked over my business." Since they also mention that they would like to hear what people think about this situation, here's my take: They deployed a major change/migration to their billing system, implementing a brand new product, and seemingly didn't bother to investigate how it was going beyond cursory looks at a dashbo…
> But what is your definition of "check to make sure the integration was working correctly"? Once you know what was going wrong, it's easy but unhelpful to say "you should have checked to see if that thing was going wrong".
I'm sure he checked that Canadian tax was working, because that's what he bought Stripe Tax for. He didn't expect it to silently screw up his US customer payments, because he did not need to pay tax for them. He reasonably expected that Stripe Tax should have no impact on the payment of invoices for which no tax is owed.
I'm not quite understanding the need to put them on blast here. Yes, they should have been more apologetic and they should certainly have escalated your ticket more quickly. But they made the changes you wanted seen: better documentation & better process, and reaching out to customers proactively when they see this problem.
If they have a pattern of customer service problems then it's best that people know it.