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

Status Summary

Tentative plan for 2017’H2

Frontend: Basic card UI implementation. Knwon dependencies include:
- 1. (On-going) Relevant SecReview (both UI & implementation) is green: Paul. T is on it. (see also: Initial review on API design)
- 2. (TBConfirmed) Front-end resource: Dolske's team?
- 3. (TBConfirmed) Reviewer’s availability: partially confirmed. (MattN + others)
- 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