Yep, international/amex cards aren't enabled by default by most POS providers (_due to the high fees on the merchant side_) and most small businesses don't really know or care enough to enable them.
In fact, card acceptance has gone _up_ in my experience. Unless you're using a very small shop which just has a QR code, most businesses now use a POS which supports a lot of payment methods including cards.
I agree that a lot of businesses now actively don't manage cash as they used to earlier... it's very difficult to get low-value notes as the central bank seems to be slowly reducing the supply by not printing as per demand.
I think that's a very simplistic take, it doesn't account for people who need to support children's education and/or healthcare for parents.
Both are areas where costs are going up at a rate which is much higher than official inflation rates, and comp increases often don't even match inflation!
So the need for working till you're forced to give up still remains.
We used to have self-hosted runners on Hetzner dedicated servers, and we migrated to UbiCloud ~6 months ago.
Unless you can optimise your CI runtime to be very balanced and fast, you're going to have a lot of jobs queued during working hours ... although it costs more per minute, the fact that CI jobs are bursty means it works out not too much costlier but with less queue time.
What's the plan for monetization? Your license is Apache 2.0, which I'm not sure makes sense from having customers pay.
In contrast, Lago uses AGPL-3.0 and has an open-core model (not sure if the premium features are source available or not), which makes it more clearer on how they're going to make money.
One more data point: at work we use Stripe for most regions [1], but in our largest region (South Africa) we have to use Paystack [2] (a Stripe subsidiary). The API isn't 1:1 compatible and there's no plans to do so in the near future. Having multiple providers is a must for us to consider a solution.
Lago is better in that they have have support for custom payment integrations [3].
Most banking sites log you out very aggressively, and a lot of them require some sort of 2FA during login. It's quite inconvenient to have to do this login dance every time you need to make a transaction -- with an app, you can use a PIN or biometrics to start using it.
I assume it depends on the nature of the diff? I do a lot of code review at $JOB, and sometimes the diff is so obvious that there's no need to look further.
OTOH if the code is something that I've haven't looked at in a while or don't understand that much, I'll read around a bit and see if there's a way the diff can be improved.
It was raised to 5x of that in February, but doesn't help as that requires the bank to be declared as failed. The regulator (RBI) has refused to do that in multiple instances, most notably in the case of PMC Bank a few months ago.