From 2ff14067b312261f1ce876b125295e651e429237 Mon Sep 17 00:00:00 2001
From: Manu Sporny <msporny@digitalbazaar.com>
Date: Wed, 16 Mar 2016 15:05:05 -0400
Subject: [PATCH] Add reference to issue #50.

---
 specs/paymentrequest.html | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/specs/paymentrequest.html b/specs/paymentrequest.html
index 837cc43e..d53215c8 100644
--- a/specs/paymentrequest.html
+++ b/specs/paymentrequest.html
@@ -779,6 +779,13 @@ <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: