Viewing profile — agreeahmed
agreeahmed
HN member- Joined
- Sun, Jul 01, 2018, 7:45 AM UTC
- HN karma
- 295
- Public activity
- 73 items
- HN profile
- View on Hacker News ↗
About agreeahmed
https://github.com/flowglad/flowglad
Recent public activity
-
comment
Comment #46298361
Builder of an open source payments provider [0]. You could dynamically switch payments providers based on the situation, but as of today: - you would have to integrate into multipl…
-
comment
Comment #46109855
We're using trigger.dev for processing workflows and we really love the product (and team)
-
comment
Comment #46078473
The "storing my source of truth externally" is super fair, and something we plan to address soon by giving you the ability to store this data on your side. So you'll still get all …
-
comment
Comment #46065511
Appreciate the feedback. This work happens in all frontend "cultures" (a phrase I will be lovingly borrowing, thank you). But a payment provider can't really take this work off a d…
-
comment
Comment #46062751
If you want to have a direct relationship with your acquiring bank then yours would is a pretty optimal flow. For folks who just want to get set up and get going quickly and don't …
-
comment
Comment #46062288
Yes, we have similar compliance things we consider to Stripe and PayPal. We believe the best experience will only need one onboarding, which would mean we need to process the payme…
-
comment
Comment #46060583
Exactly. If you’re too committed to framework agnosticism you end up leaving your users a bunch of last mile work that they have to do with every integration, and maintain through …
-
comment
Comment #46058044
Very interesting. How do you handle billing with that setup? Are there billing SaaSes that will integrate with that set up, or did you have to build your own? Since we’re the payme…
-
comment
Comment #46057781
Glad to hear the pain points resonate with you, and we’d love to hear any thoughts you have on how we could address them better. Re open source: the SaaS is under AGPLv3, and the r…
-
comment
Comment #46057512
The SaaS is open source too, it’s AGPLv3. Pasting the full root license file below: — Flowglad is fully open source. - ./packages: MIT - ./playground: MIT - ./platform: AGPLv3
-
comment
Comment #46054585
We eat all the webhook pain so you don’t have to. Much of our code is dealing with complex state transitions triggered webhooks. We just avail you the end result. Instead of having…
-
comment
Comment #46054560
This is why we committed to getting deeper into the payment processing side. Yes, we can service this with our current arrangement because we are not a merchant of record. When you…
-
comment
Comment #46054449
The benefit is that our hooks get entitlement data directly to your frontend. Stripe Elements just focus on payments forms. But what about how payments state impacts what features …
-
comment
Comment #46054264
There are a few billing engines that have shipped entitlement management offerings. We’re focused on making the best DX for managing entitlements as possible. A lot of that comes d…
-
comment
Comment #46054224
Not in the immediate term at least. Our initial focus is deliver an amazing experience for software builders.
-
comment
Comment #46053739
We built our own billing engine so the total cost to you is .65% (on top of the normal 2.9%). By comparison Stripe Billing costs .70%
-
comment
Comment #46053171
Webhooks are absolutely the right tool for async / background jobs, or events driven domains. I’m not sure payments, and its flip side of entitlements, is best modeled as an events…
-
comment
Comment #46053110
That’s a devilish engineering question. If you are truly framework agnostic you limit how much work you can do for your users, because a lot of the work happens inside of the frame…
-
comment
Comment #46052838
With Flowglad you’d pay ever so slightly less than you would with a vanilla Stripe integration which usually includes Stripe Billing. That total cost is 3.6% (2.9% per charge + .7%…
-
comment
Comment #46052800
That’s a great point. We started with React because that’s what we knew best and the community we were most embedded in. We have no dogmatic attachment to React. We hope to support…
-
comment
Comment #46052473
Totally. When you look at the history of payments processing usually new entrants start with a significant technical improvement and then quickly graduate into learning how to pric…
-
comment
Comment #46052044
You should be able to access it via the “Set Up” tab in your navigation bar. It’s step 3 “verify and enable live payments” - we’ll clear up that copy, thank you for flagging!
-
comment
Comment #46051982
Thank you! That’s exactly what we saw after speaking with a bunch of devs. They wanted to iterate on pricing as they all figure out how to price their AI products. It turns out tha…
-
comment
Comment #46051941
Under the hood we are using Stripe to process the payments, but you set up a Stripe sub account through our platform using Stripe Connect
-
comment
Comment #46051927
No that’s the total cost to you. This isn’t a BYOK setup, you create a Stripe account through us using Stripe Connect