Update reference to issue w3c#48.

msporny · Mar 29, 2016 · 06a2444 · 06a2444
1 parent c006928
commit 06a2444
Showing 1 changed file with 6 additions and 33 deletions.
diff --git a/specs/paymentrequest.html b/specs/paymentrequest.html
@@ -282,39 +282,6 @@ <h2>PaymentRequest constructor</h2>
             ["visa", "bitcoin", "bobpay.com"]
           </pre>
 
-
-          <div class="issue" data-number="48" title="Should list of accepted payment methods be strings or objects?">
-            <p>
-              Should the list of acceptable payment methods be listed as simple
-              strings or complex objects? If simple strings, as proposed above,
-              then how can price vary based on the payment method? The following
-              example shows an alternative way of providing acceptable payment
-              methods that allows for price variation based on payment method.
-            </p>
-
-            <pre class="example highlight">
-  acceptedScheme: [{
-    scheme: [
-      'https://w3id.org/payment-schemes#Visa',
-      'https://w3id.org/payment-schemes#Mastercard',
-      'https://w3id.org/payment-schemes#Discover'
-    ],
-    transfer: {
-      amount: '4.35',
-      currency: 'USD'
-    },
-    paymentRequestService: 'https://merchant-psp.example.com/services/getPaymentInfo'
-  }, {
-    scheme: 'https://w3id.org/payment-schemes#Bitcoin',
-    transfer: {
-      amount: '0.0177',
-      currency: 'BTC'
-    },
-    destination: '3QJmV3qfvL9SuYo34YihAf3sRCW3qSinyC'
-  }
-            </pre>
-          </div>
-
           <p>The <code>details</code> object contains information about the transaction that the
           user is being asked to complete such as the line items in an order.</p>
           <pre class="example highlight">
@@ -386,6 +353,12 @@ <h2>PaymentRequest constructor</h2>
           a preference and allow users to express a preference that overrides merchant preferences.
         </div>
 
+        <div class="issue" data-number="48" title="Should list of accepted payment methods be strings or objects?">
+          There is an open issue about whether the list of supported payment
+          methods should be passed to the user agent as a simple sequence of
+          strings or as a more complex and flexible object structure.
+        </div>
+
         <p>
           The <a><code>PaymentRequest</code></a> constructor MUST act as follows:
         </p>