diff --git a/specs/paymentrequest.html b/specs/paymentrequest.html
index d53215c8..d6d35c44 100644
--- a/specs/paymentrequest.html
+++ b/specs/paymentrequest.html
@@ -779,13 +779,6 @@ <h2>PaymentResponse interface</h2>
         };
       </pre>
 
-      <p class="issue" data-number="50" title="How are payment requests and responses passed between the browser and third-party native wallets?">
-        How are payment messages routed between the browser and native payment
-        apps? The spec should give developers some idea of how the integration
-        might happen via a NOTE or similar mechanism to ensure that people know
-        it won't be just the OS vendors providing payment apps.
-      </p>
-
       <p>
         A <code><dfn>PaymentResponse</dfn></code> is returned when a user has selected a payment method and
         approved a payment request. It contains the following fields:
@@ -1087,6 +1080,13 @@ <h2>User agent delegates payment request algorithm</h2>
           <a><code>abort</code></a> to account for the situation where this may fail in the <code>delegated</code>
           state.</p>
         </div>
+
+        <p class="issue" data-number="50" title="How are payment requests and responses passed between the browser and third-party native wallets?">
+          This specification should describe how the user agent will pass the 
+          payment request data and the complete signal to a native payment app 
+          and also how it will receive the payment response from the payment app.
+        </p>
+
       </section>
 
       <section>