> 2.9% + 30¢ Very expensive!
Don't think there is a cheaper alternative to stripe. Polar and Dodo is 4% + 40¢
Show HN: We built an open source, zero webhooks payment processor
21–30 of 230 posts
Re: Show HN: We built an open source, zero webhooks payment processor
#22> 2.9% + 30¢ Very expensive!
Isn't this pretty much what every processor everywhere charges? I have been out of the industry for 10+ years but I remember this being pretty standard.
Re: Show HN: We built an open source, zero webhooks payment processor
#23It looks like you need to update this file https://github.com/flowglad/flowglad/tree/main/platform#read... Its still using the Mintlify starter kit
thanks for heads up, fixing
Re: Show HN: We built an open source, zero webhooks payment processor
#24Earlier quoted context omitted.
For now, yes. The game plan over time is to get deeper into the actual card rails side of things. But first we really want to nail the developer experience.
Who cares about developer experience? Genuinely asking, because I’m a developer too and I certainly don’t care. What we care about is solving the actual problem of payments with the downstream companies.
“Well your payments platform doesn’t actually do payments, but the developer experience of doing nothing was flawless!”
Sorry for the snark, but been in payments a long time, and seen too much of this nonsense.
Re: Show HN: We built an open source, zero webhooks payment processor
#25> 2.9% + 30¢ Very expensive!
Isn't this pretty much what every processor everywhere charges? I have been out of the industry for 10+ years but I remember this being pretty standard.
It ain't by much, but we're a tiny bit cheaper than Stripe when you consider how much they charge for Billing (.7% for them vs .65% for us). And pretty much every Stripe integration uses Stripe Billing (unless they pair with a 3rd part billing SaaS)
Re: Show HN: We built an open source, zero webhooks payment processor
#26Re: Show HN: We built an open source, zero webhooks payment processor
#27Earlier quoted context omitted.
Closer-to-the metal integrations with providers is definitely a big headache. Solving that problem takes a bit longer because you need bank partnerships, in many cases have to pass compliance screens, etc. We're aiming to tackle the more tractable part first which is the developer experience
If you're trying to be like Vercel—it's a red flag for any reasonable person when you clearly spent more effort on your landing page than your actual product. What made Stripe so successful is that, I personally would not even attempt, like you said, "integrations with providers" "bank partnerships" "compliance screens" because that sounds basically impossible.
"It's hard so you shouldn't try doing it"
thank you, very productive reply
Re: Show HN: We built an open source, zero webhooks payment processor
#28[under-the-rug stub] [see https://news.ycombinator.com/item?id=45988611 for explanation]
What sold me on flowglad was the single source of truth and not having to hold customer stripe info in my DB. Although it took me a little while to figure that out lol
Six minutes after this story was posted on HN you made this HN account to post this. So when you say it took you a little while to figure out... by little while you mean less than six minutes?
Re: Show HN: We built an open source, zero webhooks payment processor
#29> 2.9% + 30¢ Very expensive!
Standard.
Re: Show HN: We built an open source, zero webhooks payment processor
#30Stripe billing definitely leaves something to be desired and agree that a layer on top can improve the DX tremendously.
What differentiates you from competitors like Lago and Autumn?