From 869b99a4562233553b877e252e442eab62bb6a15 Mon Sep 17 00:00:00 2001 From: Matt Corallo Date: Fri, 18 Oct 2024 21:47:53 +0000 Subject: [PATCH] if i had a quarter for every time a second-language english speaker corrected my english... --- bip-XXXX.mediawiki | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/bip-XXXX.mediawiki b/bip-XXXX.mediawiki index f5894635a3..a3b90a359f 100644 --- a/bip-XXXX.mediawiki +++ b/bip-XXXX.mediawiki @@ -81,7 +81,7 @@ I.e. amount=50.00 or amount=50 is treated as 50 BTC, and amount=50,000.00 is inv === Proof of Payment === -The URI MAY include a "pop" (or "req-pop") parameter who's value can be used to build a URI which the wallet application can, after payment completes, "open" to provide proof the payment was completed or other information about the payment. +The URI MAY include a "pop" (or "req-pop") parameter whose value can be used to build a URI which the wallet application can, after payment completes, "open" to provide proof the payment was completed or other information about the payment. The value of a "pop" (or "req-pop") parameter shall be a percent-encoded (per RFC 3986 section 2.1) URI prefix. The wallet application, if it supports providing payment information SHOULD percent-decode the provided URI once, append the query parameter key from which the payment instructions used were read, append a single =, and finally append the Payment Information to the resulting URI and open it with the default system handler for the URI. For payment instructions read from the body of the URI, "onchain" SHALL be used in place of the key.