See how credit cards work (at least where I have lived). Someone fraudulently cloned my card after a petrol station visit and I got it fixed as soon as I noticed the weird transactions. The bank or VISA footed that cost. UK has statutory law on this. Probably because of how CCs used to work with that carbon copy crap.
In the US merchants are the ones footing that cost, either in merchant fees (which they then pass on to the Customer in the form of higher prices) or directly (by the credit card company refusing to pay the merchant).
It might be different now, but in the late 90s I sold some laptops to a buyer using a stolen credit card. The cardholders had no fraud liability but my company ended-up having to eat the cost of the stolen laptops. The credit card company simply didn't pay the amount of the fraud in their settlement with us.
These kinds of Next issues are why I stopped using it.
It is not bugs per-se as every framework has them.
It is that you are utterly stuck when they do and even 100s of thumbs up on issues don't get things fixed.
Case in point: can't defer chunk scripts anymore. Hard to get good performance scores as this is untenable.
Fetch cache limit is 2Mb or something like that and enforced by Verel. You need to fork NextJS and self host it to fix.
Probably 2 or 3 other such issues I forgot as well
Any over opinionated "batteries welded" frameworks will have this issue.
Use any of the usual MVC suspects like Rails for example and you avoid being stuck. You can find fixes or swap libraries. They tend to have battle tested out such issues anyway.
