bitcoin/bips
1
0
Fork 0
mirror of https://github.com/bitcoin/bips.git synced 2025-05-12 12:03:29 +00:00
Code Issues Releases Wiki Activity

Added note about handling multiple copies of a Payment message, to ensure resend is safe

Browse Source 
in case of a transport layer failure.
This commit is contained in:
Ross Nicoll 2014-04-26 16:59:23 +01:00
parent 694314d296
commit d8bd74baf8
No known key found for this signature in database
GPG Key ID: 9142E5F7E533CE3B
1 changed files with 5 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
bip-0070.mediawiki
View File

@ -156,6 +156,11 @@ If the customer authorizes payment, then the Bitcoin client:
# If PaymentDetails.payment_url is specified, POST a Payment message to that URL. The Payment message is serialized and sent as the body of the POST request. # If PaymentDetails.payment_url is specified, POST a Payment message to that URL. The Payment message is serialized and sent as the body of the POST request.
Errors communicating with the payment_url server should be communicated to the user. Errors communicating with the payment_url server should be communicated to the user.
The merchant's server should handle receiving multiple copies of the same Payment
message in response to a single PaymentRequest. This is required to ensure that in
case of a transport level failure during transmission, recovery is possible by
re-sending the Payment message. The endpoint URL must remain valid for at least
the same period of time as the original PaymentRequest.
PaymentDetails.payment_url should be secure against man-in-the-middle PaymentDetails.payment_url should be secure against man-in-the-middle
attacks that might alter Payment.refund_to (if using HTTP, it must be attacks that might alter Payment.refund_to (if using HTTP, it must be