Firefox/Features/Web Payments: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(→‎Project Members: remove line)
(Major cleanup)
Line 1: Line 1:
== Introduction ==
== Introduction ==


This feature targets to enable a frequent online shopper to make online purchases without having to fill in all of the personal and payment information over and over again. Together with the feature “Form-autofill”, it saves user's time and effort when making online purchases by storing their personal and payment information in a profile and automatically populating form fields and payment information when the user requires it.
The [https://developer.mozilla.org/en-US/docs/Web/API/Payment_Request_API Payment Request API] makes online purchases easier without having to fill in all of the personal and payment information over and over again. Together with the [[Firefox/Features/Form_Autofill|form autofill feature]], it saves user's time and effort when making online purchases by storing their personal and payment information in Firefox to be used when a merchant requests payment.  The Payment Request UI provides consistency across merchant sites.


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 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.
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 (PCI) compliant.


== Status Summary ==
== Status Summary ==
Line 30: Line 30:
** (Done) Payment Request Handler API Proposal. It's been merged into the renamed Payment "Handler" API (was the Payment "App" API) spec.
** (Done) Payment Request Handler API Proposal. It's been merged into the renamed Payment "Handler" API (was the Payment "App" API) spec.


== Development Detail ==
== Development ==
'''Preference:''' dom.payments.request.enabled
'''Preference:''' dom.payments.request.enabled


* [[Firefox/Features/Web_Payments/DOM|DOM]]
=== Front-end ===
* Bugzilla Component: [https://bugzilla.mozilla.org/buglist.cgi?component=Web%20Payments%20UI&product=Toolkit&bug_status=__open__ Toolkit: Web Payments UI] ([https://bugzilla.mozilla.org/enter_bug.cgi?product=Toolkit&component=WebPayments%20UI&status_whiteboard=%5Bwebpayments%5D%20%5Btriage%5D file a bug])
* [https://docs.google.com/spreadsheets/d/1oHoMGVe-FtKmzxMQO-0FhHAe625LxjcVd8m0jB3OF9g/edit#gid=0 Front-end Work Breakdown]
* [[Firefox/Features/Web_Payments/Privacy_%26_Security_Considerations|Privacy & Security Considerations]]
* [https://firefox-source-docs.mozilla.org/toolkit/components/payments/docs/index.html Developer Documentation]
 
=== [[Firefox/Features/Web_Payments/DOM|DOM]] ===
See [[Firefox/Features/Web_Payments/DOM]] for more info.
* Bugzilla Component: [https://bugzilla.mozilla.org/buglist.cgi?component=DOM%3A%20Web%20Payments&product=Core&bug_status=__open__&list_id=13533834 DOM: Web Payments]
* [https://groups.google.com/forum/#!topic/mozilla.dev.platform/n-2o58jcTK8 Intent to Implement]
* [https://docs.google.com/presentation/d/1gevKHz3q3s2WoKWdrgUGKm4XHeE-kGYwJVwdp4u3vuY/edit#slide=id.g11edd6636a_0_0 Platform implementation Architecture]
* Old
** [https://github.com/edenchuang/gecko-dev DOM Code WIP Repository]


== Quality Assurance ==
== Quality Assurance ==
Line 73: Line 85:
** [https://docs.google.com/document/d/14T4C_ToW2XSCaKeGIG3fGMcm5OTnM0Ra8cBzbht7xx0/edit Meeting Notes]
** [https://docs.google.com/document/d/14T4C_ToW2XSCaKeGIG3fGMcm5OTnM0Ra8cBzbht7xx0/edit Meeting Notes]
** [https://docs.google.com/document/d/1BYTSOJq7_CNJk5WZpRosN6nRV1jthteJtdPyu017o8E/edit# Meeting Notes (2016-12-29 to 2017-08-16)]
** [https://docs.google.com/document/d/1BYTSOJq7_CNJk5WZpRosN6nRV1jthteJtdPyu017o8E/edit# Meeting Notes (2016-12-29 to 2017-08-16)]
** [https://docs.google.com/spreadsheets/d/1rtWflNUMuAEch8x8Bzhozq5KzF2GBpxc2ubpYivj-88/edit#gid=228952903 Project Tracking]


* Engineering
* W3C Specifications
** [https://docs.google.com/spreadsheets/d/1oHoMGVe-FtKmzxMQO-0FhHAe625LxjcVd8m0jB3OF9g/edit#gid=0 Front-end Work Breakdown]
** [https://groups.google.com/forum/#!topic/mozilla.dev.platform/n-2o58jcTK8 Intent to Implement]
** [https://docs.google.com/presentation/d/1gevKHz3q3s2WoKWdrgUGKm4XHeE-kGYwJVwdp4u3vuY/edit#slide=id.g11edd6636a_0_0 Platform implementation Architecture]
** [https://bugzilla.mozilla.org/buglist.cgi?component=DOM%3A%20Web%20Payments&product=Core&bug_status=__open__&list_id=13533834 Bugzilla Component: DOM: Web Payments]
** [https://w3c.github.io/payment-request/ W3C Payment Request API Specification]
** [https://w3c.github.io/payment-request/ W3C Payment Request API Specification]
** [https://w3c.github.io/payment-handler/ W3C Payment Handler API Specification]
** [https://w3c.github.io/payment-handler/ W3C Payment Handler API Specification]
** [[Firefox/Features/Web_Payments/Privacy_%26_Security_Considerations|Privacy & Security Considerations]]
** Old
*** [https://github.com/edenchuang/gecko-dev DOM Code WIP Repository]


* User Experience
* User Experience

Revision as of 00:17, 17 March 2018

Introduction

The Payment Request API makes online purchases easier without having to fill in all of the personal and payment information over and over again. Together with the form autofill feature, it saves user's time and effort when making online purchases by storing their personal and payment information in Firefox to be used when a merchant requests payment. The Payment Request UI provides consistency across merchant sites.

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 (PCI) compliant.

Status Summary

Tentative plan for 2018’H2
  • Frontend: Basic card UI implementation. Known dependencies include:
    • 1. (Completed) UX design reiteration V1.7: Jacqueline. (see also: Web Payment - Basic Card (MVP) design doc.
    • 2. Front-end Resources: 3 Engineers
    • 3. (Confirmed) Reviewer’s availability: MattN
    • 4. (Confirmed) No other feature dependency (e.g., Any Lockbox dependency?)
    • 5. (Confirmed) Compliance for Basic card UI (or that’s only for Payment Handler?)? e.g., PA-DSS by PA-QSA
  • Platform: Ensure Payment Request APIs “ready to enable” (disable until FE ready) in Q3
    • API Compat. test coverage / compliance
    • Basic card spec. implementation
    • (Q3 and more) Marcos keeps working on W3C spec of both the Payment Handler/Request
    • (Q3 and more) Bridging UI and the Request API (subject to FE’s actual progress), including 2 parts:
      • Connecting UI: ongoing and will complete in Q3;
      • IntegrationL requires FE completion to start (e.g., fix bugs during UI integration and verification on merchant website like WooCommerce).
Achievement in 2017'H1
    • (Done) Payment Request API development.
    • (Done) User research of Payment Request (Basic Card) UX.
    • (Done) Payment Request Handler API Proposal. It's been merged into the renamed Payment "Handler" API (was the Payment "App" API) spec.

Development

Preference: dom.payments.request.enabled

Front-end

DOM

See Firefox/Features/Web_Payments/DOM for more info.

Quality Assurance

  • TBD. The pure API development in H1 doesn't require QA involvement (UI level verification). We will have unit/autotest instead.

Project Members

2018'H1 (Jan.~)
  • Product: Jeff Griffiths (transition to Cindy Hsiang)
  • User Experience: Jacqueline Savory (UX), Erin Pang (VisD)
  • User Research: Sharon Bautista
  • Front-End Engineering: Justin Dolske, Matthew Noorenberghe (Tech Lead), Jared Wein, Samuel Foster
  • Platform Engineering: Marcos Caceres, Peter Saint-Andre
  • Program Management: Jean Gong
2017'H2 (Sep.~)
  • Product: Jeff Griffiths
  • User Experience: Jacqueline Savory (UX)
  • Engineering: Justin Dolske, Matthew Noorenberghe (Tech Lead), Marcos Caceres (Architect), Jared Wein, Samuel Foster
  • Program Management: Jean Gong
2017'H1 (~Aug.)
  • Product: Joe Cheng
  • User Experience: Juwei Huang (UX), Fang Shih (Visual)
  • Engineering: Marcos Caceres (Architect), Ben Tian (TDC Tech Lead), Alphan Chen, Eden Chuang, Matthew Noorenberghe (Front-end oversight)
  • Program Management: Wesly Huang

Discussion

References

Retrieved from "https://wiki.allizom.org/index.php?title=Firefox/Features/Web_Payments&oldid=1190593"