BIP 0073 - Revision history

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

2019-09-24T17:59:11Z

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

@@ Line 1: / Line 1: @@
 {{bip}}
 <pre>
    BIP: 73
-   Title: Use "Accept" header for response type negotiation with Payment Request URLs
+  Layer: Applications
    Author: Stephen Pair <stephen@bitpay.com>
-   Status: Draft
+  Comments-Summary: No comments yet.
    Type: Standards Track
-   Created: 27-08-2013
+   Created: 2013-08-27
 </pre>
-{{BipMoved|bip-0073.mediawiki}}
+==Abstract==
-[[Category:BIP]]
+<img src=bip-0073/a.png></img><img src=bip-0073/b.png></img>

2015-12-29T13:47:44Z

Removing redundant parameter.

2013-12-06T08:29:00Z

2013-12-06T08:28:48Z

Github move

@@ Line 10: / Line 10: @@
 </pre>
-==Abstract==
+{{BipMoved|bip-0073.mediawiki|BIP 0073}}
 [[File:BIP_0073a.png]]&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[File:BIP_0073b.png]]
 [[Category:BIP]]

2013-08-29T12:30:38Z

Compatibility

← Older revision		Revision as of 12:30, 29 August 2013
Line 59:		Line 59:

	Only QR scanning wallets that implement this BIP will be able to process QR		Only QR scanning wallets that implement this BIP will be able to process QR
	codes containing payment request URLs. There are two possible workarounds QR		codes containing payment request URLs. There are two possible workarounds for QR
	scanning wallets that do not implement this BIP: 1) the server gives the user an		scanning wallets that do not implement this BIP: 1) the server gives the user an
	option to change the QR code to a bitcoin: URI or 2) the user scans the code with		option to change the QR code to a bitcoin: URI or 2) the user scans the code with

2013-08-29T12:29:02Z

Specification

← Older revision		Revision as of 12:29, 29 August 2013
Line 42:		Line 42:
	the client accepts a bitcoin URI. A media type of application/bitcoin-paymentrequest		the client accepts a bitcoin URI. A media type of application/bitcoin-paymentrequest
	specifies that the client can process a payment request. In the absence of an		specifies that the client can process a payment request. In the absence of an
	Accept: header, the server is ~~expect~~ to respond with text/html suitable for		Accept: header, the server is expected to respond with text/html suitable for
	rendering in a browser. An HTML response will ensure that QR codes scanned		rendering in a browser. An HTML response will ensure that QR codes scanned
	by non Bitcoin wallet QR scanners are useful (they could render an HTML page		by non Bitcoin wallet QR scanners are useful (they could render an HTML page

2013-08-28T13:20:08Z

Compatibility

← Older revision		Revision as of 13:20, 28 August 2013
Line 58:		Line 58:
	==Compatibility==		==Compatibility==

	QR scanning wallets that ~~do not support~~ this BIP will ~~not~~ be able to process QR		Only QR scanning wallets that implement this BIP will be able to process QR
	codes containing ~~non bitcoin URIs~~. There are two possible workarounds: 1) the		codes containing payment request URLs. There are two possible workarounds QR
	server gives the user an option to change the QR code to a bitcoin: URI or 2) the		scanning wallets that do not implement this BIP: 1) the server gives the user an
	user scans the code with a generic QR code scanner.		option to change the QR code to a bitcoin: URI or 2) the user scans the code with
			a generic QR code scanner.

			In the second scenario, if the server responds with a webpage containing a link
			to a bitcoin URI, the user can complete the payment by clicking that link provided
			the user has a wallet installed on their device and it supports bitcoin URIs. If the
			wallet/device does not have support for bitcoin URIs, the user can fall back on
			address copy/paste.

	This BIP should be fully compatible with BIP 70 assuming it is required that wallets		This BIP should be fully compatible with BIP 70 assuming it is required that wallets

2013-08-28T13:14:05Z

Specification

← Older revision		Revision as of 13:14, 28 August 2013
Line 47:		Line 47:
	with a payment link that when clicked would open a wallet on the device).		with a payment link that when clicked would open a wallet on the device).

	It is not ~~request~~ that the client and server support the full semantics of an		It is not required that the client and server support the full semantics of an
	HTTP Accept header. If application/bitcoin-paymentrequest is specified in the		HTTP Accept header. If application/bitcoin-paymentrequest is specified in the
	header, the server should send a payment request regardless of anything else		header, the server should send a payment request regardless of anything else

2013-08-28T13:13:51Z

Specification

← Older revision		Revision as of 13:13, 28 August 2013
Line 45:		Line 45:
	rendering in a browser. An HTML response will ensure that QR codes scanned		rendering in a browser. An HTML response will ensure that QR codes scanned
	by non Bitcoin wallet QR scanners are useful (they could render an HTML page		by non Bitcoin wallet QR scanners are useful (they could render an HTML page
	with a payment link that when clicked would open a wallet on the device).		with a payment link that when clicked would open a wallet on the device).

			It is not request that the client and server support the full semantics of an
			HTTP Accept header. If application/bitcoin-paymentrequest is specified in the
			header, the server should send a payment request regardless of anything else
			specified in the Accept header. If text/uri-list is specified (but not
			application/bitcoin-paymentrequest), a valid Bitcoin URI should be returned. If
			neither is specified, the server can return an HTML page. When a uri-list is returned
			only the first item in the list is used (and expected to be a bitcoin URI), any additional
			URIs should be ignored.

	==Compatibility==		==Compatibility==

2013-08-28T13:10:13Z

Abstract

← Older revision		Revision as of 13:10, 28 August 2013
Line 20:		Line 20:
	a payment request.		a payment request.

	Implementation of this BIP does not require full payment request [[BIP 0070\|BIP 70]] support.		Implementation of this BIP does not require full payment request ([[BIP 0070\|BIP 70]]) support.

	==Motivation==		==Motivation==