Have a look at my post "Payment Protocol for Face-to-face payments". In
short: I implemented BIP70 using combinations of either QR-code or NFC
plus Bluetooth. You can download a working preview app from:
https://github.com/schildbach/bitcoin-wallet/releases/tag/v3.30-bitcoinj0.11
On 02/03/2014 0
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?
Tim Tuxworth
Founder Go-Taxi.biz
Original message From: Christophe Biocca
Date:2014/02/03 10:49 AM (GMT-08:00)
To: Tim
It's not limited to HTTP. I was pointing out that unsolicited
merchant-to-consumer messages don't work on HTTP (and a lot of other
situations), and so you can't add a need for it to the payment
protocol (since it wouldn't be usable in the majority of cases).
On Mon, Feb 3, 2014 at 3:30 PM, Tim Tux
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 u
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
5 matches
Mail list logo
