Good question. I'm open to it, but this project is already not very successful (see my comments in an old thread here: https://news.ycombinator.com/item?id=35461596). I think I'm just a bit burnt out on it. Perhaps open-sourcing it will reinvigorate the project a bit. Ultimately I made it to scratch my own itch and I'm happy with what it is now, so at the very least I can use it for my own needs.
I would be happy to hear any advice for better payment processors, of course.
This comes up a lot but instead of victim shaming, we need to look at the fact that a lot of small mom and pop indie businesses do not have the resources, time and need to really have a backup plan like the one you are suggesting. The cost of implementing a backup processor for a small indie business is almost always not worth it. In hindsight in this case, one could argue but no.
Instead, we need to hold Stripe responsible to do a better due diligence upfront if they want to do business with these small indie hackers. That was the point of Stripe and now they have become that giant incumbent.
I am not advocating against Stripe relaxing their rules. I am just saying that they need to do better job enforcing early on than one random day. If it was not good enough today, it was not good enough on Day 1. Stripe needs to invest in figuring that out early. Reject me on Day 1 than Day 90 or a year later.
