Live data from Hacker News

Stripe's Payment APIs: the first 10 years (2020)

stripe.dev

51–56 of 56 posts

Re: Stripe's Payment APIs: the first 10 years (2020)

#51
post #33

Earlier quoted context omitted.

In my experience, you couldn’t just setup an account and start selling, you had to contact their sales team and they let you know if they want your business. Stripe has no real competitor.

It has lots of competitors. They bought out LemonSqueezy exactly because it was a competitor that quickly gained a lot of mindshare. Polar.sh is another one. The thing you're talking about with Paddle is just checking you're not selling offline, physical stuff.

Last I checked, Polar was using Stripe under the hood.

EDIT: Yup. Via their pricing page:

   Polar is currently built on Stripe, and we cover their 2.9% + 30¢ fee from ours. However, they impose a few additional fees for certain transactions that we need to pass on.

Re: Stripe's Payment APIs: the first 10 years (2020)

#53

Earlier quoted context omitted.

Having done a major migration with Stripe, at a startup, I disagree. They have lots of products, but you don't need most of them and can ignore them. What's left is, in my experience, the correct amount of complexity. We looked at Braintree, and it was just missing things that we were legally required to support, we looked at Judopay and it was... lacking (a nearby founder describe Judopay as treating payments like a…

> Having done a major migration with Stripe, at a startup, I disagree Initial integration is very simple and developer-friendly. The complexity comes later.

The migration I did was from the basic Stripe product to the complex one. I did it because we were legally required to do the transition. Stripe was the only major vendor with the technology ready for that migration.

Re: Stripe's Payment APIs: the first 10 years (2020)

#54
post #39

Earlier quoted context omitted.

How is that different than any other payment processor? Interchange isn't free anywhere

Stripe's fees are well above interchange fees (especially in Europe). On top of that Stripe's pricing for other features (e.g. invoicing and subscriptions) is also a percentage, so you end up paying a ton for those features.

And other payment processors don't charge a fee for invoicing and subscriptions?

Re: Stripe's Payment APIs: the first 10 years (2020)

#55
post #54

Earlier quoted context omitted.

Stripe's fees are well above interchange fees (especially in Europe). On top of that Stripe's pricing for other features (e.g. invoicing and subscriptions) is also a percentage, so you end up paying a ton for those features.

And other payment processors don't charge a fee for invoicing and subscriptions?

I'm not sure if they all charge a percentage of your money transfers for that. At work we decided to migrate that part to an internal system anyway.

Re: Stripe's Payment APIs: the first 10 years (2020)

#56
post #2

Stripe's APIs have grown so complicated to support so many different shapes of large enterprise workflows that they have to color code the entities to make you think it's simple. You'll be processing events from totally different yet slightly overlapping entity types for building a simple subscription service and having to synthetically handle 12 month billing. The docs won't adequately explain which events should tr…

[dead]
Post reply on HN