==== BIP 0073 - Use "Accept" header for response type negotiation with Payment Request URLs ====
[[dido:public:ra:xapend:xapend.b_stds:defact:bitcoin:bips| return to the Bitcoin Improvement Proposals ]]

<table>
<caption>Data sheet for Use "Accept" header for response type negotiation with Payment Request URLs </caption>
| Title                      | Use "Accept" header for response type negotiation with Payment Request URLs  |
| Layer                      | Applications |
| Author                     | Stephen Pair	 |
| Comments-Summary           | No comments yet. |
| Comments-URI               | [[https://github.com/bitcoin/bips/wiki/Comments:BIP-0073]]    |
| Status                     | Final | 
| Type                       | Standards Track | 
| Created                    | 2013-08-27  |
| Post History               |   |
| Description                | [[https://github.com/bitcoin/bips/blob/master/bip-0073.mediawiki]] |
</table>

  : **Note**: The following is an excerpt from the official [[dido:public:ra:xapend:xapend.a_glossary:b:bitcoin|Bitcoin]] site. It is provided here as a convenience and is not authoritative. Refer to the original document(s) as the authoritative reference.

=== Abstract ===
  : //This BIP describes an enhancement to the payment protocol ([[dido:public:ra:xapend:xapend.b_stds:defact:bitcoin:bips:bip_0070| BIP 70]]) that addresses the need for short URLs when scanning from QR codes. It generalizes the specification for the behavior of a payment request URL in a way that allows the [[dido:public:ra:xapend:xapend.a_glossary:c:client|client]] and [[dido:public:ra:xapend:xapend.a_glossary:s:server|server]] to negotiate the content of the response using the HTTP Accept: header field. Specifically, the client can indicate to the server whether it prefers to receive a bitcoin URI or a payment request.//

  : //Implementation of this BIP does not require full payment request ([[dido:public:ra:xapend:xapend.b_stds:defact:bitcoin:bips:bip_0070| BIP 70]]) support.//

=== Motivation ===
  : //The payment protocol augments the bitcoin: uri scheme with an additional "payment" parameter that specifies a URL where a payment request can be downloaded. This creates long URIs that, when rendered as a QR code, have a high information density. Dense QR codes can be difficult to scan resulting in a more frustrating user experience. The [[dido:public:ra:xapend:xapend.a_glossary:g:goal|goal]] is to create a standard that would allow QR scanning wallets to use less dense QR codes. It also makes general purpose QR code scanners more usable with bitcoin accepting websites.//