One micro-transaction doesn't need to imply one credit card transaction. A micropayments solution could work like PayPal, whereby every user has a balance. Then it's just database transactions within their own system.
The tricky part is the chicken-egg problem; does user adoption or developer adoption come first? I expect that one of the existing major tech companies would need to do it.
Apple, Google, Microsoft: Can build it into their browser, and are already facilitating payments via their app stores and existing user accounts.
Stripe: Already have the developer adoption in Stripe checkout.
The limiting factor might be CS & disputes. There is an average support cost of transactions, and it might be higher than what they could make on fees. I think some automation could bring that cost down in the future as well, though.
The tricky part is the chicken-egg problem; does user adoption or developer adoption come first? I expect that one of the existing major tech companies would need to do it.
Apple, Google, Microsoft: Can build it into their browser, and are already facilitating payments via their app stores and existing user accounts.
Stripe: Already have the developer adoption in Stripe checkout.
The limiting factor might be CS & disputes. There is an average support cost of transactions, and it might be higher than what they could make on fees. I think some automation could bring that cost down in the future as well, though.