Difference between revisions of "BIP 0072"
(If request given, allow bitcoin address to be optional.)
|Line 56:||Line 56:|
Revision as of 00:27, 8 August 2013
This page describes a BIP (Bitcoin Improvement Proposal).
BIP: 72 Title: bitcoin: uri extensions for Payment Protocol Author: Gavin Andresen <firstname.lastname@example.org> Status: Draft Type: Standards Track Created: 29-07-2013
This BIP describes an extension to the bitcoin: URI scheme (BIP 21) to support the payment protocol (BIP 70).
Allow users to click on a link in a web page or email to initiate the payment protocol, while being backwards-compatible with existing bitcoin wallets.
The bitcoin: URI scheme is extended with an additional, optional "request" parameter, whose value is a URL from which a PaymentRequest message should be fetched (unsafe and reserved octets in the URL value must be encoded as described in RFC 1738).
If the "request" parameter is provided and backwards compatibility is not required, then the bitcoin address portion of the URI may be omitted (the URI will be of the form: bitcoin:?request=... ).
When Bitcoin wallet software that supports this BIP receives a bitcoin: URI with a request parameter, it should ignore the bitcoin address/amount/label/message in the URI and instead fetch a PaymentRequest message and then follow the payment protocol, as described in BIP 70.
Bitcoin wallets must support fetching PaymentRequests via http and https protocols; they may support other protocols.
If a PaymentRequest cannot be obtained (perhaps the server is unavailable), then the customer should be informed that the merchant's payment processing system is unavailable.
Wallet software that does not support this BIP will simply ignore the request parameter and will initiate a payment to bitcoin address.
A backwards-compatible request: