Hey @Brystefor, I'm @Rafsark's co-founder.
We could have spent more time on idempotency, indeed.
We have not deep dived into the 3 other aspects you mentioned indeed, we're actually planning to
1/ open-source the articles and add additional challenges as they are mentioned
2/ open our roadmap based on these inputs as well
Thanks for sharing! Will ping you back here when it's live
PS: we had not thought of financial regulation changes indeed!
Oh, I didn't even realize this was a blog for an open source project. I assumed it was someones personal blog.
Two other things that you may want to consider:
1. PCI compliance. If you're involved in the storage of payment information, you may want to look into these regulations.
2. Regarding point 3 of your mission "...only integrating with specific partners to lock you in (e.g., Stripe Billing only working with Stripe Payments)...". I think there are many companies out there who want to integrate with more than a single payment provider (eg Braintree, Stripe, Adyen, etc) but run into this problem. It increases the cost of payments due to the "rent-seeker" charge method they use. Providing a design framework for how a single company could integrate with multiple providers could be beneficial. This is something I've considered trying to build, but I think it could fit with this initiative.
Hi @Brystephor! I'm Anh-Tho, one of the cofounders of Lago.
We're building an open-source alternative to Stripe Billing indeed, but we want to share our personal experience, hence the personal blog post.
We'll open our repo very soon and our public roadmap too. Thanks for adding the 2 points, we're working on 'a design framework for how a single company could integrate with multiple providers could be beneficial.' indeed!
