Firefox/Features/Web Payments: Difference between revisions

Firefox/Features/Web Payments (view source)

Revision as of 17:06, 20 December 2017

70 bytes removed , 20 December 2017

no edit summary

Jeangong

canmove, Confirmed users

1,104

edits

@@ Line 5: / Line 5: @@
 The overall objective is to increase user engagement, satisfaction, and retention for frequent online shoppers. We believe this can be achieved by enabling users to complete forms and “check out” in e-commerce flows as quickly and securely as possible.
-The W3C PaymentRequest API is currently in draft stage and has momentum. The API is extensible to any payment source without requiring the browser to be Payment Card Industry compliant. compliant.
+The W3C PaymentRequest API is currently in draft stage and has momentum. The API is extensible to any payment source without requiring the browser to be Payment Card Industry compliant.
 == Status Summary ==
-===== Tentative plan for 2017’H2 =====
+===== Tentative plan for 2018’H2 =====
-* Frontend: Basic card UI implementation. Knwon dependencies include:
+* Frontend: Basic card UI implementation. Known dependencies include:
-** 1. (On-going)    Relevant SecReview (both UI & implementation) is green: Paul. T is on it. (see also: Initial review on API design)
+** 1. (On-going)   UX design reiteration V1.7: Jacqueline is on it. (see also: Web Payment - Basic Card (MVP) design doc.
-** 2. (TBConfirmed) Front-end resource: Dolske's team?
+** 2. Front-end Resources: 3 Engineers
-** 3. (TBConfirmed) Reviewer’s availability: partially confirmed. (MattN + others)
+** 3. (TBConfirmed) Reviewer’s availability: MattN
 ** 4. (TBConfirmed) No other feature dependency (e.g., Any Lockbox dependency?)
 ** 5. (TBConfirmed) Compliance for Basic card UI (or that’s only for Payment Handler?)? e.g., PA-DSS by PA-QSA