Firefox/Features/Web Payments

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 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.

Status Summary

Tentative plan for 2018’H2

• Frontend: Basic card UI implementation. Known dependencies include:
  • 1. (On-going) UX design reiteration V1.7: Jacqueline is on it. (see also: Web Payment - Basic Card (MVP) design doc.
  • 2. Front-end Resources: 3 Engineers
  • 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

• 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).

Achivement 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 Detail

Preference: dom.payments.request.enabled

2017'H2

Platform (ETA 2017'Q3): API developlment Follow-up

Bugzilla query error

Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 429 [1] => Unknown Error ) ) 1

Platform (ETA 2017'Q3): UI Implementation Support

Bugzilla query error

Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 429 [1] => Unknown Error ) ) 1

Platform (ETA 2017'Q3): Compat. test coverage & compliance

Bugzilla query error

Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 429 [1] => Unknown Error ) ) 1

2017'H1

Timeline & Architecture

• https://goo.gl/IeXiMk

Milestone 1 (ETA Mar. 31th)

Bugzilla query error

Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 429 [1] => Unknown Error ) ) 1

Milestone 2 (ETA Apr. 28th)

Bugzilla query error

Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 429 [1] => Unknown Error ) ) 1

Milestone 3 (ETA June. 30th)

Bugzilla query error

Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 429 [1] => Unknown Error ) ) 1

Quality Assurance

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

Project Members

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
• Program Management: Wesly Huang

Discussion

• IRC: #payments
• Weekly Meeting Notes
• Web Payment Mailing list:webpayments@mozilla.com
• Auto Fill Mailing list: autofill@lists.mozilla.org

Reference Link

• Product/Project
  • Product Requirements (shared with “Form-autofill”)
  • Meeting Notes
  • Meeting Notes (2016-12-29 to 2017-08-16)

• Engineering
  • Front-end Work Breakdown
  • Intent to Implement
  • Platform implementation Architecture
  • Local Code Repository
  • Bugzilla Component: DOM: Web Payments
  • Payment Request API Specification
  • Payment Handler API Specification
  • Privacy & Security Considerations

• User Experience
  • Basic Card UI Spec
  • Interaction Mockup
  • Visual Mockup
  • Prototype for User Research