BIP 0072 - Revision history

934: Update BIP text with latest version from https://github.com/bitcoin/bips/blob/b5723035e23896d0/bip-0072.mediawiki

2019-09-24T18:00:25Z

Update BIP text with latest version from https://github.com/bitcoin/bips/blob/b5723035e23896d0/bip-0072.mediawiki

@@ Line 1: / Line 1: @@
 {{bip}}
 <pre>
    BIP: 72
    Title: bitcoin: uri extensions for Payment Protocol
    Author: Gavin Andresen <gavinandresen@gmail.com>
    Status: Final
    Type: Standards Track
-   Created: 29-07-2013
+   Created: 2013-07-29
 </pre>
-{{BipMoved|bip-0072.mediawiki}}
+==References==
-[[Category:BIP]]
+[[http://www.w3.org/Protocols/rfc2616/rfc2616.html|RFC 2616]] : Hypertext Transfer Protocol -- HTTP/1.1

934: Removing redundant parameter.

2015-12-29T13:47:33Z

Removing redundant parameter.

← Older revision		Revision as of 13:47, 29 December 2015
Line 10:		Line 10:
	</pre>		</pre>

	{{BipMoved\|bip-0072.mediawiki~~\|BIP 0072~~}}		{{BipMoved\|bip-0072.mediawiki}}

	[[Category:BIP]]		[[Category:BIP]]

TheRealSteve: updated status

2015-06-13T15:04:49Z

updated status

← Older revision		Revision as of 15:04, 13 June 2015
Line 5:		Line 5:
	Title: bitcoin: uri extensions for Payment Protocol		Title: bitcoin: uri extensions for Payment Protocol
	Author: Gavin Andresen <gavinandresen@gmail.com>		Author: Gavin Andresen <gavinandresen@gmail.com>
	Status: ~~Draft~~		Status: Final
	Type: Standards Track		Type: Standards Track
	Created: 29-07-2013		Created: 29-07-2013

Wumpus: Github move

2013-12-06T08:27:47Z

Github move

@@ Line 10: / Line 10: @@
 </pre>
-==Abstract==
+{{BipMoved|bip-0072.mediawiki|BIP 0072}}
 [[Category:BIP]]

Gavinandresen: Changed request param to just 'r'

2013-12-04T02:59:57Z

Changed request param to just 'r'

Gavinandresen: Require Accept: header

2013-08-28T01:33:54Z

Require Accept: header

← Older revision		Revision as of 01:33, 28 August 2013
Line 39:		Line 39:

	Bitcoin wallets must support fetching PaymentRequests via http and		Bitcoin wallets must support fetching PaymentRequests via http and
	https protocols; they may support other protocols.		https protocols; they may support other protocols. Wallets must
			include an Accept HTTP header in HTTP requests:
			<pre>Accept: application/bitcoin-paymentrequest</pre>

	If a PaymentRequest cannot be obtained (perhaps the server is		If a PaymentRequest cannot be obtained (perhaps the server is

Gavinandresen: Formatting

2013-08-08T00:27:39Z

Formatting

← Older revision		Revision as of 00:27, 8 August 2013
Line 56:		Line 56:
	</pre>		</pre>
	Non-backwards-compatible equivalent:		Non-backwards-compatible equivalent:
			<pre>
	bitcoin:?request=https%3A%2F%2Fmerchant.com%2Fpay.php%3Fh%3D2a8628fc2fbe		bitcoin:?request=https%3A%2F%2Fmerchant.com%2Fpay.php%3Fh%3D2a8628fc2fbe
			</pre>
	[[Category:BIP]]		[[Category:BIP]]

Gavinandresen: If request given, allow bitcoin address to be optional.

2013-08-08T00:27:01Z

If request given, allow bitcoin address to be optional.

← Older revision		Revision as of 00:27, 8 August 2013
Line 27:		Line 27:
	message should be fetched (unsafe and reserved octets in the URL value		message should be fetched (unsafe and reserved octets in the URL value
	must be encoded as described in RFC 1738).		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		When Bitcoin wallet software that supports this BIP receives a

Gavinandresen: Allow URIs with no address

2013-08-08T00:24:10Z

Allow URIs with no address

← Older revision		Revision as of 00:24, 8 August 2013
Line 46:		Line 46:
	request parameter and will initiate a payment to bitcoin address.		request parameter and will initiate a payment to bitcoin address.

	==~~Example~~==		==Examples==
			A backwards-compatible request:
	<pre>		<pre>
	bitcoin:mq7se9wy2egettFxPbmn99cK8v5AFq55Lx?amount=0.11&request=https%3A%2F%2Fmerchant.com%2Fpay.php%3Fh%3D2a8628fc2fbe		bitcoin:mq7se9wy2egettFxPbmn99cK8v5AFq55Lx?amount=0.11&request=https%3A%2F%2Fmerchant.com%2Fpay.php%3Fh%3D2a8628fc2fbe
	</pre>		</pre>
			Non-backwards-compatible equivalent:
			bitcoin:?request=https%3A%2F%2Fmerchant.com%2Fpay.php%3Fh%3D2a8628fc2fbe

	[[Category:BIP]]		[[Category:BIP]]

Gavinandresen: Initial spec

2013-07-31T02:06:13Z

Initial spec

New page

{{bip}}

<pre>
BIP: 72
Title: bitcoin: uri extensions for Payment Protocol
Author: Gavin Andresen <gavinandresen@gmail.com>
Status: Draft
Type: Standards Track
Created: 29-07-2013
</pre>

==Abstract==

This BIP describes an extension to the bitcoin: URI scheme (BIP 21) to
support the payment protocol (BIP 70).

==Motivation==

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.

==Specification==

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).

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.

==Compatibility==

Wallet software that does not support this BIP will simply ignore the
request parameter and will initiate a payment to bitcoin address.

==Example==

<pre>
bitcoin:mq7se9wy2egettFxPbmn99cK8v5AFq55Lx?amount=0.11&request=https%3A%2F%2Fmerchant.com%2Fpay.php%3Fh%3D2a8628fc2fbe
</pre>

[[Category:BIP]]

← Older revision		Revision as of 02:59, 4 December 2013
Line 24:		Line 24:

	The bitcoin: URI scheme is extended with an additional, optional		The bitcoin: URI scheme is extended with an additional, optional
	"~~request~~" parameter, whose value is a URL from which a PaymentRequest		"r" parameter, whose value is a URL from which a PaymentRequest
	message should be fetched (unsafe and reserved octets in the URL value		message should be fetched (unsafe and reserved octets in the URL value
	must be encoded as described in RFC 1738).		must be encoded as described in RFC 1738).

	If the "~~request~~" parameter is provided and backwards compatibility		If the "r" parameter is provided and backwards compatibility
	is not required, then the bitcoin address portion of the URI may be		is not required, then the bitcoin address portion of the URI may be
	omitted (the URI will be of the form: bitcoin:?~~request~~=... ).		omitted (the URI will be of the form: bitcoin:?r=... ).

	When Bitcoin wallet software that supports this BIP receives a		When Bitcoin wallet software that supports this BIP receives a
	bitcoin: URI with a ~~request~~ parameter, it should ignore the bitcoin		bitcoin: URI with a r parameter, it should ignore the bitcoin
	address/amount/label/message in the URI and instead fetch a		address/amount/label/message in the URI and instead fetch a
	PaymentRequest message and then follow the payment protocol, as		PaymentRequest message and then follow the payment protocol, as
Line 50:		Line 50:

	Wallet software that does not support this BIP will simply ignore the		Wallet software that does not support this BIP will simply ignore the
	~~request~~ parameter and will initiate a payment to bitcoin address.		r parameter and will initiate a payment to bitcoin address.

	==Examples==		==Examples==
	A backwards-compatible request:		A backwards-compatible request:
	<pre>		<pre>
	bitcoin:mq7se9wy2egettFxPbmn99cK8v5AFq55Lx?amount=0.11&~~request~~=https%3A%2F%2Fmerchant.com%2Fpay.php%3Fh%3D2a8628fc2fbe		bitcoin:mq7se9wy2egettFxPbmn99cK8v5AFq55Lx?amount=0.11&r=https%3A%2F%2Fmerchant.com%2Fpay.php%3Fh%3D2a8628fc2fbe
	</pre>		</pre>
	Non-backwards-compatible equivalent:		Non-backwards-compatible equivalent:
	<pre>		<pre>
	bitcoin:?~~request~~=https%3A%2F%2Fmerchant.com%2Fpay.php%3Fh%3D2a8628fc2fbe		bitcoin:?r=https%3A%2F%2Fmerchant.com%2Fpay.php%3Fh%3D2a8628fc2fbe
	</pre>		</pre>
	[[Category:BIP]]		[[Category:BIP]]