dido:public:ra:xapend:xapend.b_stds:defact:bitcoin:bips:bip_0070
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
dido:public:ra:xapend:xapend.b_stds:defact:bitcoin:bips:bip_0070 [2019/05/27 21:38] nick created |
dido:public:ra:xapend:xapend.b_stds:defact:bitcoin:bips:bip_0070 [2021/08/09 14:47] (current) murphy |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ======== BIP 0070 - Payment Protocol ======== | + | ==== BIP 0070 - Payment Protocol ==== |
| - | [[dido:public:stds:defact:bitcoin | return to the Bitcoin Standards ]] | + | [[dido:public:ra:xapend:xapend.b_stds:defact:bitcoin:bips| return to the Bitcoin Improvement Proposals ]] |
| <table> | <table> | ||
| Line 9: | Line 9: | ||
| | Comments-Summary | No comments yet. | | | Comments-Summary | No comments yet. | | ||
| | Comments-URI | [[https://github.com/bitcoin/bips/wiki/Comments:BIP-0070]] | | | Comments-URI | [[https://github.com/bitcoin/bips/wiki/Comments:BIP-0070]] | | ||
| - | | Staus | Final | | + | | Status | Final | |
| | Type | Standards Track | | | Type | Standards Track | | ||
| | Created | 2013-07-29 | | | Created | 2013-07-29 | | ||
| Line 16: | Line 16: | ||
| </table> | </table> | ||
| - | : **Note**: The following is an excerpt from the official Bitcoin site. It is provided here as a connivence and is not authoritative. Refer to the original document(s) as the authoritative reference. | + | : **Note**: The following is an excerpt from the official Bitcoin site. It is provided here as a convenience and is not authoritative. Refer to the original document(s) as the authoritative reference. |
| - | ====== Abstract ====== | + | === Abstract === |
| - | This BIP describes a protocol for communication between a merchant and their customer, enabling both a better customer experience and better security against man-in-the-middle attacks on the payment process. | + | //This BIP describes a protocol for communication between a merchant and their customer, enabling both a better customer experience and better security against [[dido:public:ra:xapend:xapend.a_glossary:m:mitm|man-in-the-middle attacks]] on the payment process.// |
| - | + | ||
| - | ====== Motivation ====== | + | |
| - | : //The current, minimal Bitcoin payment protocol operates as follows:// | + | |
| + | === Motivation === | ||
| + | //The current, minimal [[dido:public:ra:xapend:xapend.a_glossary:b:bitcoin|Bitcoin]] payment protocol operates as follows:// | ||
| - //Customer adds items to an online shopping basket, and decides to pay using Bitcoin.// | - //Customer adds items to an online shopping basket, and decides to pay using Bitcoin.// | ||
| - //Merchant generates a unique payment address, associates it with the customer's order, and asks the customer to pay.// | - //Merchant generates a unique payment address, associates it with the customer's order, and asks the customer to pay.// | ||
| - | - //Customer copies the Bitcoin address from the merchant's web page and pastes it into whatever wallet they are using OR follows a bitcoin: link and their wallet is launched with the amount to be paid.// | + | - //Customer copies the Bitcoin address from the merchant's web page and pastes it into whatever [[dido:public:ra:xapend:xapend.a_glossary:b:bitcoin_wallet|wallet]] they are using OR follows a bitcoin: link and their wallet is launched with the amount to be paid.// |
| - //Customer authorizes payment to the merchant's address and broadcasts the transaction through the Bitcoin p2p network.// | - //Customer authorizes payment to the merchant's address and broadcasts the transaction through the Bitcoin p2p network.// | ||
| - //Merchant's server detects payment and after sufficient transaction confirmations considers the transaction final.// | - //Merchant's server detects payment and after sufficient transaction confirmations considers the transaction final.// | ||
| - | : //This BIP extends the above protocol to support several new features:// | + | //This BIP extends the above protocol to support several new features:// |
| - //Human-readable, secure payment destinations-- customers will be asked to authorize payment to "example.com" instead of an inscrutable, 34-character bitcoin address.// | - //Human-readable, secure payment destinations-- customers will be asked to authorize payment to "example.com" instead of an inscrutable, 34-character bitcoin address.// | ||
| - //Secure proof of payment, which the customer can use in case of a dispute with the merchant.// | - //Secure proof of payment, which the customer can use in case of a dispute with the merchant.// | ||
| Line 35: | Line 34: | ||
| - //Payment received messages, so the customer knows immediately that the merchant has received, and has processed (or is processing) their payment.// | - //Payment received messages, so the customer knows immediately that the merchant has received, and has processed (or is processing) their payment.// | ||
| - //Refund addresses, automatically given to the merchant by the customer's wallet software, so merchants do not have to contact customers before refunding overpayments or orders that cannot be fulfilled for some reason.// | - //Refund addresses, automatically given to the merchant by the customer's wallet software, so merchants do not have to contact customers before refunding overpayments or orders that cannot be fulfilled for some reason.// | ||
| - | |||
| - | |||
| - | |||
| - | |||
dido/public/ra/xapend/xapend.b_stds/defact/bitcoin/bips/bip_0070.1559007499.txt.gz · Last modified: 2019/05/27 21:38 by nick
