UI automation is necessary for accessibility

To be clear, I wrote in reply to the possibility /micro-payment system/ must have some kind of recovery mechanism, even though (as you stated) that is technically very hard to solve, which kind of falls out of your comment.

I agree, it is technically hard to solve, and I agree with you it is a social problem. So I'm pointing out that there are micro-payment systems which just ignore that problem, and it is indeed left as a social problem to solve. In which case problem #3 is solved - it can't happen. Problem #2 is potentially solvable, depending on context. Problem #1 is partly solved - the resources were paid for, and the server of the resources was not (financially) harmed.

The implication in your comment was there was a problem that the micro-payment system itself had to solve somehow, even though it was hard to solve / unsolvable at the technical level. I'm saying micro-payment systems definitely already exist, with reasonably non-trivial use, and they do so without having tried to tackle the problem you (possibly) implied needing solving.

I.e., the micro-payment system can go ahead and be used, and that social issue of recoverability can be left for later solving (by probably a plethora of different social solutions, which may evolve). It's not an obstacle as such.

I can pay for a variety of things (digital services particularly) with said micro-payment system. I can buy (e)SIMs, VPNs, email hosting, VPs, Proton accounts and other similar services, AI hosting, contract developors, donate to various orgs (inc. FSF), etc., etc.. It's already bootstrapped and being used. Maybe it's not perfect enough for you, but it's good enough for a chunk of users.