Payment Request: Difference between revisions

From Bitcoin Wiki
Jump to navigation Jump to search
Gavinandresen (talk | contribs)
Gisado (talk | contribs)
m fix link
 
(3 intermediate revisions by 2 users not shown)
Line 7: Line 7:
== Specification ==
== Specification ==


See https://gist.github.com/4120476 for the current specification. After some prototyping it is expected the specification will become one or more BIPs.
See [[BIP 0070]] for the current specification.


== Extensions ==
== Extensions ==
Line 19: Line 19:
|-
|-
| 100 || (available) || (available)
| 100 || (available) || (available)
|-
| 101 || (available) || (available)
|-
|-
|}
|}
Line 50: Line 48:
|-
|-
|}
|}
[[Category:Technical]]

Latest revision as of 12:06, 10 February 2015

Payment Requests

Payment Requests are a proposed new way to make Bitcoin payments.

Instead of sending somebody a bitcoin address and asking them to pay to that address, you give them a PaymentRequest message which bundles up more information than is contained in just a bitcoin address. A SignedPaymentRequest bundles a PaymentRequest with a digital identity and signature, so you can be sure that you are paying the correct person or merchant.

Specification

See BIP 0070 for the current specification.

Extensions

To avoid conflicts, implementations should use this page to register extensions to the protocol.

PaymentRequest

Field Number Name Description
100 (available) (available)

SignedPaymentRequest

Field Number Name Description
100 (available) (available)

Payment

Field Number Name Description
100 (available) (available)

PaymentACK

Field Number Name Description
100 (available) (available)