Harmonize card payment / best practices
authorIan Jacobs <ij@w3.org>
Fri, 17 Jul 2015 09:30:57 -0500
changeset 835 18247c1eda13
parent 834 1176e28a4a3c
child 836 f430583203ac
Harmonize card payment / best practices

Moved two docs to optional section
latest/charters/payments-wg-charter.html
--- a/latest/charters/payments-wg-charter.html	Fri Jul 17 09:19:31 2015 -0500
+++ b/latest/charters/payments-wg-charter.html	Fri Jul 17 09:30:57 2015 -0500
@@ -379,28 +379,8 @@
                 seamlessly interface with Websites running inside the mobile device's user agent.
             </li>
         </ul>
-        <h4 id="Card_Payments_1.0">Card Payments 1.0 (optional)</h4>
-
-        <p>A very large proportion of payments on the Web are conducted using payment cards from one of the global card
-            schemes. The group should attempt to define a standardized specialisation of the payment flow specifically
-            for payment cards.</p>
 
-        <p>A generic card payment standard could:</p>
-        <ul>
-            <li>Demonstrate how a debit-pull payment scheme should be implemented using the Web Payments 1.0
-                standard.
-            </li>
-            <li>Take advantage of new security technologies such as EMVco Tokenisation to improve on the existing
-                methods of using cards on the Web.
-            </li>
-            <li>Standardize a single payment scheme that is reusable by all payment card schemes globally to kick-start
-                adoption of the Web Payments 1.0 standard.
-            </li>
-        </ul>
-        <p>Development of such a standard will require collaboration by the group with the owners of the existing global
-            card schemes.</p>
-
-        <h4>Test Suites</h4>
+	        <h4>Test Suites</h4>
 
         <p>The Web Payments Working Group anticipates developing test suites for Recommendation-track specifications it develops.</p>
 
@@ -446,7 +426,31 @@
             </tbody>
         </table>
 
-        <h3 id="best_practices">Instrument Discovery Good Practices</h3>
+	<h3 id="optional">Optional Deliverables</h3>
+        <h4 id="Card_Payments_1.0">Card Payments 1.0</h4>
+
+        <p>A very large proportion of payments on the Web are conducted using payment cards from one of the global card
+            schemes. The group should attempt to define a standardized specialisation of the payment flow specifically
+            for payment cards.</p>
+
+        <p>A generic card payment standard could:</p>
+        <ul>
+            <li>Demonstrate how a debit-pull payment scheme should be implemented using the Web Payments 1.0
+                standard.
+            </li>
+            <li>Take advantage of new security technologies such as EMVco Tokenisation to improve on the existing
+                methods of using cards on the Web.
+            </li>
+            <li>Standardize a single payment scheme that is reusable by all payment card schemes globally to kick-start
+                adoption of the Web Payments 1.0 standard.
+            </li>
+        </ul>
+        <p>Development of such a standard will require collaboration by the group with the owners of the existing global
+          card schemes.</p>
+
+	<h4 id="Card_Payments_1.0">Card Payments 1.0</h4>
+
+        <h4 id="best_practices">Instrument Discovery Good Practices</h4>
 
 	<p>This charter does not include a deliverable for a standard mechanism to discover &mdash; via the payer's wallet(s)&mdash; available payment instruments. However, the Working Group may document good practices and recommend algorithms for the discovery of payer payment
             instruments. This involves good practice approaches for discovering the supported payer