Not sure if I'm following you. With my Uber configured, I'd usually confirm paying only within the Uber app. My wallet would get notifications and issue payments. If my wallet is not reachable, Uber would tell me that payment failed like it does with an expired CC resulting in the ride not getting booked.

Now my webhoster might not instantly delete my stuff the second my wallet doesn't play along. It could send me a warning email that a payment failed and how it will be re-tried tomorrow etc. again like it does with CC.

All this is compatible with my proposal. What are you missing?

No, I am not working on this but I hope to use this asap instead of CC ;)

Reply to this note

Please Login to reply.

Discussion

I think we are saying the same thing. Ie, fine-grained control.

Important to consider binning the use cases, maybe?

Uber - on-demand, pay-per-use.

Rent/Mortgage - non-negotiable.

Internet Bill - fixed amount, specific day per-month.

Water Bill - variable/consumption based, non-negotiable, specifc day

V4V/charity - completely optional

...just thinking outloud.

Fine line between "budget"-setting features and "trusted-invoicer"-features.

So lets say you rent a car. The company would take your CC and "threaten" to charge it if you return the car dirty or scratched or whatnot. With a Bitcoin wallet I could remove any allowance the minute I receive the key.

For this insurance use case, the wallet would require me to lock up funds with the company. Maybe 2-of-3 with a trusted third party. I see no other way than to involve a third party to force the client's payment.

Of course the third party could also be a respected insurance where the car company would trust to get a payment. This would allow the client to avoid locking up $10k for a car rental in exchange for paying some monthly fee for example.