diff --git a/bip-0272.mediawiki b/bip-0272.mediawiki
index 098cb7681f..301b3cefa2 100644
--- a/bip-0272.mediawiki
+++ b/bip-0272.mediawiki
@@ -1,7 +1,7 @@
 <pre>
   BIP: 272
   Title: Simplified Payment Protocol URIs
-  Author: Wallet Workshop
+  Author: Wallet Workshop, Aleksandar Dinkov
   Created: 2019-02-22
 </pre>
 
@@ -16,50 +16,43 @@ Allow users to click on a link in a web page or email or scan a QR codes to
 initiate the payment protocol, while being backwards-compatible with existing
 bitcoin wallets.
 
+The backwards compatibility comes in the sense that existing wallets will recognize that they cannot handle this URI, thanks to the required parameter ("req-bip272").
+
 ==Specification==
 
-The bitcoin: URI scheme is extended with an additional, optional
-"r" parameter, whose value is a URL from which a PaymentRequest
-message should be fetched (characters not allowed within the scope
-of a query parameter must be percent-encoded as described in RFC 3986
-and bip-0003).
+The bitcoin: URI scheme from BIP-21 is extended with additional parameters.
 
-If the "r" parameter is provided and backwards compatibility
-is not required, then the bitcoin address portion of the URI may be
-omitted (the URI will be of the form: bitcoin:?r=... ).
+{|
+! Parameter
+! Required
+! Description
+|-
+| req-bip272
+| Yes
+| An empty parameter, signaling wallets that this is a BIP-272 URI. Incompatible wallets will know that they cannot handle it.
+|-
+| r
+| Yes
+| a URL from which a BIP-270 PaymentRequest message should be fetched.
+|}
 
-When Bitcoin wallet software that supports this BIP receives a
-bitcoin: URI with a request parameter, it should ignore the bitcoin
-address/amount/label/message in the URI and instead fetch a
-PaymentRequest message and then follow the payment protocol, as
-described in BIP 70.
+When Bitcoin wallet software that supports this BIP receives a bitcoin: URI with a "req-bip272" parameter, it MUST ignore all of the parameters (and path) described in BIP-21 (bitcoin address/amount/label/message) and instead fetch a PaymentRequest message and then follow the payment protocol, as described in BIP 270.
 
-Bitcoin wallets must support fetching PaymentRequests via the
-HTTPS protocol; they may support other protocols. Wallets must
-include an "Accept" HTTP header in HTTPS requests (as defined
-in RFC 2616):
+Bitcoin wallets must support fetching PaymentRequests via the HTTPS protocol; they may support other protocols. Wallets must include an "Accept" HTTP header in HTTPS requests (as defined in RFC 2616):
 
 <pre>Accept: application/bitcoinsv-paymentrequest</pre>
 
-If a PaymentRequest cannot be obtained (perhaps the server is
-unavailable), then the customer should be informed that the merchant's
-payment processing system is unavailable. In the case of an HTTP
-request, status codes which are neither success nor error (such as
-redirect) should be handled as outlined in RFC 2616.
+If a PaymentRequest cannot be obtained (perhaps the server is unavailable), then the customer should be informed that the merchant's payment processing system is unavailable. In the case of an HTTP request, status codes which are neither success nor error (such as redirect) should be handled as outlined in RFC 2616.
 
 ==Compatibility==
 
-Wallet software that does not support this BIP will simply ignore the
-r parameter and will initiate a payment to bitcoin address.
+Wallet software that does not support this BIP will simply see the required parameter "req-bip272" and know that it cannot handle this URI. It will notify the user of the incompatability.
 
 ==Examples==
-A backwards-compatible request:
-<pre>
-bitcoin:mq7se9wy2egettFxPbmn99cK8v5AFq55Lx?sv&amount=0.11&r=https://merchant.com/pay.php?h%3D2a8628fc2fbe
-</pre>
-Non-backwards-compatible equivalent:
+
+All BIP-272 URIs will look pretty similar:
 <pre>
-bitcoin:?sv&r=https://merchant.com/pay.php?h%3D2a8628fc2fbe
+bitcoin:?req-bip272&r=https://merchant.com/pay.php?h%3D2a8628fc2fbe
 </pre>
 
 ==References==