> at the moment the only way that you can have a program make an automated payment and have that program verifiable by your customer. Far from the only way, un

> at the moment the only way that you can have a program make an automated payment and have that program verifiable by your customer. Far from the only way, unless you restrict the "only" to the ability to verify the software before it runs. if you allow the more general case, and the one I think most customers would care about, the concern is a verifiable guarantee that if their flight is cancelled, the insurance will pay out within X hours of the official cancellation of the flight. However, this is already verifiable by the dumb contract. Noting that this "dumb" contract can be enforced by law. The law (and the regulations on the insurance industry) are a publicly verifiable claim about the payments process. Yes, the public verification stops at the interface layer (and hides the application layer), but we usually accept this as a good principle of software design, don't we?