The process described in BIP70 might be ok for a simple happy path
scenario, but what if things don't work so smoothly. I'm not talking
here about technical issues, but _very common_ business scenarios such as:
e.g. Merchant cancels request before payment is sent, such as when:-
- the merchant
Over http, the merchant doesn't have the ability to reach out to the
consumer's bitcoin wallet on their own. So sending Cancel Payment
Request to the user is impossible.
If the customer doesn't want to send, nothing ever needs to happen. So
sending a Reject Payment Request to the merchant is
Is BIP70 limited to http only?
What about face to face scenarios, or realtime like ticket sales or gambling,
and socket and/or bluetooth type connections?
div Original message /divdivFrom: Christophe Biocca
Mail list logo