Firefox/Features/Web Payments: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(delete status history)
(delete milestones section)
Line 16: Line 16:
* [[Firefox/Features/Web_Payments/Tokenization | Tokenization]]
* [[Firefox/Features/Web_Payments/Tokenization | Tokenization]]
* [https://firefox-source-docs.mozilla.org/browser/components/payments/docs/index.html Developer Documentation]
* [https://firefox-source-docs.mozilla.org/browser/components/payments/docs/index.html Developer Documentation]
==== Milestones ====
[https://docs.google.com/spreadsheets/d/1oHoMGVe-FtKmzxMQO-0FhHAe625LxjcVd8m0jB3OF9g/edit#gid=1193040724 from the breakdown document]
;M1
:End-to-end test with valid user data and merchant update/change events, no Fx validation, generic merchant error string, only already stored cards/addresses
;M2
:add/edit screens, only basic validation (e.g. non-empty) and address-field-specific merchant-provided errors
;M3 (Q3)
:FTU, data validation & error recovery, ready to enable on Nightly-only / Partner / End-to-end User Testing (not riding the trains)
;M4 (Q4)
:tab modal payment sheet, handling spec additions (e.g. retry, merchant field-specific errors, and new events) and UI bug fixes (not polish), gathering user testing and merchant feedback
;Later
:a11y, address autofill de-duplication fixes, security edge cases, final strings, P1 telemetry probes, "update" badge, UI feature complete, ready for release users, visual polish/animations


=== [[Firefox/Features/Web_Payments/DOM|DOM]] ===
=== [[Firefox/Features/Web_Payments/DOM|DOM]] ===

Revision as of 14:16, 9 July 2020

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 Payment Request API is a Candidate Recommendation and has already been implemented in other major web browsers. The API is extensible to any payment method without requiring the browser to be Payment Card Industry (PCI) compliant.

Development

Preference: dom.payments.request.enabled

Front-end

DOM

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

Quality Assurance

  • Softvision is verifying bugs

Project Members

2018 (Jan.~Dec.)
  • Product: 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.~Dec.)
  • 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.mozilla.org/index.php?title=Firefox/Features/Web_Payments&oldid=1228902"