Firefox/Features/Web Payments: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
 
(132 intermediate revisions by 5 users not shown)
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 manually fill personal and payment information for every purchase. 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 [https://www.w3.org/TR/payment-handler/ Payment Handler API] builds upon Payment Request by providing a pluggable protocol (based on service workers) which facilitates purchasing through third party payment providers. Payment Handlers allows web-based payment applications to act as Payment Request payment methods which can be integrated into merchant websites.


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.
=== Related Project Pages ===


== Status Summary ==
==== Project Tracking ====


===== Tentative plan for 2018’H2 =====
* Dashboard - ''TBD''
* 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
==== Mana ====
** 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 =====
* [https://mana.mozilla.org/wiki/display/SRC/Web+Payments Web Payments Project Page]
** (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 ==
==== Wiki ====
'''Preference:''' dom.payments.request.enabled
* [https://wiki.mozilla.org/Firefox/Features/Form_Autofill Form Autofill General]
* [https://wiki.mozilla.org/Firefox/Features/Form_Autofill/Credit_Cards Credit Card Autofill]
* TBD Addresses
 
== Bugzilla ==
 
=== Bug Queries ===
* [https://mzl.la/3gGRi5t MVP Project Work Currently In Development]
* [https://mzl.la/38F5GbP Available MVP Project Work]
* [https://mzl.la/2CoG6LO Completed MVP Project Work]
* [https://mzl.la/3elwT4B Bugs Requiring Triage]
* [https://bugzilla.mozilla.org/buglist.cgi?component=WebPayments%20UI&product=Firefox&bug_status=__open__ Firefox :: WebPayments UI] ([https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&component=WebPayments%20UI&status_whiteboard=%5Bwebpayments%5D%20%5Btriage%5D file a bug])
* [https://bugzilla.mozilla.org/buglist.cgi?component=DOM%3A%20Web%20Payments&product=Core&bug_status=__open__&list_id=13533834 DOM: Web Payments]
 
=== Bug Tagging ===
* ph1-mvp: Whiteboard tag for MVP bugs team is commiting to complete within the schedule.
* ph1-reserve: Whiteboard tag for low-priority bugs the team is not committing to complete within the schedule.
* ph-triage: Whiteboard tag for bugs that require triage (clear this tag once triaged).


===== 2017'H2 =====
=== Bug Lists ===


====== Front-end: TBD ======
==== All MVP Bugs ====
* [https://mzl.la/3iNNpNR View Bugzilla Query].


====== Platform (ETA 2017'Q3): API developlment Follow-up ======
<bugzilla>
<bugzilla>
    {
{
         "whiteboard":["WP-MVP","M4"],
         "whiteboard": "ph1-mvp",      
        "status":["NEW","REOPENED","ASSIGNED","RESOLVED","VERIFIED","CLOSED"],
         "include_fields":"id, summary, status, assigned_to, priority"
         "include_fields": "id, summary, status, resolution, assigned_to, depends_on, blocks, whiteboard"
}
    }
</bugzilla>
</bugzilla>


====== Platform (ETA 2017'Q3): UI Implementation Support ======
==== All Reserve Bugs ====
<bugzilla>
* [https://mzl.la/2ZR6mql View Bugzilla Query].
    {
        "blocks": 1383597,
        "status":["NEW","REOPENED","ASSIGNED","RESOLVED","VERIFIED","CLOSED"],
        "include_fields": "id, summary, status, resolution, assigned_to, depends_on, blocks, whiteboard"
    }
</bugzilla>


====== Platform (ETA 2017'Q3): Compat. test coverage & compliance ======
<bugzilla>
<bugzilla>
    {
{
         "blocks": 1380546,
         "whiteboard": "ph1-reserve",      
        "status":["NEW","REOPENED","ASSIGNED","RESOLVED","VERIFIED","CLOSED"],
         "include_fields":"id, summary, status, assigned_to, priority"
         "include_fields": "id, summary, status, resolution, assigned_to, depends_on, blocks, whiteboard"
}
    }
</bugzilla>
</bugzilla>


===== 2017'H1 =====
==== Bugs Requiring Triage ====
 
* [https://mzl.la/3elwT4B View Bugzilla Query].
====== Timeline & Architecture ======
*https://goo.gl/IeXiMk


====== Milestone 1 (ETA Mar. 31th) ======
<bugzilla>
<bugzilla>
    {
{
         "whiteboard":["WP-MVP","M1"],
         "whiteboard": "ph-triage",      
        "status":["NEW","REOPENED","ASSIGNED","RESOLVED","VERIFIED","CLOSED"],
         "include_fields":"id, summary, status, assigned_to, priority"
         "include_fields": "id, summary, status, resolution, assigned_to, depends_on, blocks, whiteboard"
}
    }
</bugzilla>
====== Milestone 2 (ETA Apr. 28th) ======
<bugzilla>
    {
        "whiteboard":["WP-MVP","M2"],
        "status":["NEW","REOPENED","ASSIGNED","RESOLVED","VERIFIED","CLOSED"],
        "include_fields": "id, summary, status, resolution, assigned_to, depends_on, blocks, whiteboard"
    }
</bugzilla>
====== Milestone 3 (ETA June. 30th) ======
<bugzilla>
    {
        "whiteboard":["WP-MVP","M3"],
        "status":["NEW","REOPENED","ASSIGNED","RESOLVED","VERIFIED","CLOSED"],
        "include_fields": "id, summary, status, resolution, assigned_to, depends_on, blocks, whiteboard"
    }
</bugzilla>
</bugzilla>


== Quality Assurance ==
== Debugging Tips ==
* TBD. The pure API development in H1 doesn't require QA involvement (UI level verification). We will have unit/auto test instead.
 
'''Preference:''' dom.payments.request.enabled


== Project Members ==
== Discussion ==


===== 2017'H2 (Sep.~) =====
* Slack: #payments-team, #payments-leads
* Product: Jeff Griffiths
* Chat: tbd
* User Experience: Jacqueline Savory (UX)
* [https://docs.google.com/document/d/1aS-lhG91H0ukUI5fs88uAdAmYRSrPHM6IdTcVsN-DEc/edit# Weekly Meeting Notes]
* Engineering: Justin Dolske, Matthew Noorenberghe (Tech Lead), Marcos Caceres (Architect), Jared Wein, Samuel Foster
* Program Management: Jean Gong


===== 2017'H1 (~Aug.) =====
== References ==
* 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 ==
=== W3C Specifications ===
** [https://w3c.github.io/payment-request/ W3C Payment Request API Specification]
** [https://w3c.github.io/payment-handler/ W3C Payment Handler API Specification]


* IRC: #payments
=== Product/Project ===
* [https://goo.gl/czomYf Weekly Meeting Notes ]
* [[Firefox/Features/Web_Payments/Privacy_%26_Security_Considerations|Privacy & Security Considerations]]
* Web Payment Mailing list:[mailto:webpayments@mozilla.com webpayments@mozilla.com]
* [https://firefox-source-docs.mozilla.org/browser/components/payments/docs/index.html In-Tree Developer Documentation]
* Auto Fill Mailing list: [mailto:autofill@lists.mozilla.org autofill@lists.mozilla.org]
* [https://docs.google.com/presentation/d/1gevKHz3q3s2WoKWdrgUGKm4XHeE-kGYwJVwdp4u3vuY/edit#slide=id.g11edd6636a_0_0 Payment Request Implementation Architecture (slides)]


== Reference Link ==
=== User Experience ===


* Product/Project
== Historical ==
** [https://docs.google.com/document/d/1Rk6SIH_O_wab1CsphHhuwmvT8gXCG-D0B0ki0R3dmC4/edit?ts=577b1d52#heading=h.ifofy8kjhyvh Product Requirements (shared with “Form-autofill”)]
** [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)]


* Engineering
Payment Request was originally developed in 2017 and 2018. Development was halted prior to shipping. Below are links to some of the resources associated with that project.
** [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://github.com/edenchuang/gecko-dev Local Code Repository]
** [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/browser-payment-api/ Payment Request API Specification]
** [https://w3c.github.io/webpayments-payment-apps-api/ Payment Handler API Specification]
** [[Firefox/Features/Web_Payments/Privacy_%26_Security_Considerations|Privacy & Security Considerations]]


* User Experience
* [https://docs.google.com/document/d/1Rk6SIH_O_wab1CsphHhuwmvT8gXCG-D0B0ki0R3dmC4/edit?ts=577b1d52#heading=h.ifofy8kjhyvh Product Requirements (shared with “Form-autofill”)]
** [https://mozilla.invisionapp.com/share/BJBRO1O27 Basic Card UI Spec]
* [https://docs.google.com/document/d/14T4C_ToW2XSCaKeGIG3fGMcm5OTnM0Ra8cBzbht7xx0/edit Meeting Notes]
** [https://mozilla.invisionapp.com/share/RDAIXK5JZ Interaction Mockup]
* [https://docs.google.com/document/d/1BYTSOJq7_CNJk5WZpRosN6nRV1jthteJtdPyu017o8E/edit# Meeting Notes (2016-12-29 to 2017-08-16)]
** [https://mozilla.invisionapp.com/share/QHBQ4VD9Z Visual Mockup]
* [https://docs.google.com/spreadsheets/d/1rtWflNUMuAEch8x8Bzhozq5KzF2GBpxc2ubpYivj-88/edit#gid=228952903 Project Tracking]
** [https://marcoscaceres.github.io/web-payments-proto/ Prototype for User Research]
* [https://mozilla.invisionapp.com/share/YAFI31XR3KP Basic Card UX Spec] ([https://mozilla.invisionapp.com/share/BJBRO1O27 old v1.6])
* [https://mozilla.invisionapp.com/share/SDFY4PA4EQ7 Basic Card UI Spec]
* [https://mozilla.invisionapp.com/share/RDAIXK5JZ Interaction Mockup]
* [https://mozilla.invisionapp.com/share/QHBQ4VD9Z Visual Mockup]
* [https://marcoscaceres.github.io/web-payments-proto/ Prototype for User Research] [https://youwenliang.github.io/web-payment/ Version 2]


[[Category:Firefox]]
[[Category:Firefox]]

Latest revision as of 15:24, 9 July 2020

Introduction

The Payment Request API makes online purchases easier without having to manually fill personal and payment information for every purchase. 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 Payment Handler API builds upon Payment Request by providing a pluggable protocol (based on service workers) which facilitates purchasing through third party payment providers. Payment Handlers allows web-based payment applications to act as Payment Request payment methods which can be integrated into merchant websites.

Related Project Pages

Project Tracking

  • Dashboard - TBD

Mana

Wiki

Bugzilla

Bug Queries

Bug Tagging

  • ph1-mvp: Whiteboard tag for MVP bugs team is commiting to complete within the schedule.
  • ph1-reserve: Whiteboard tag for low-priority bugs the team is not committing to complete within the schedule.
  • ph-triage: Whiteboard tag for bugs that require triage (clear this tag once triaged).

Bug Lists

All MVP Bugs

Full Query
ID Summary Status Assigned to Priority
1616863 Payment Request dialog container styles broken RESOLVED Marcos Caceres [:marcosc] P1
1645972 PaymentRequest's show() must consume user activation NEW --
1651600 Re-enable mochitests and wpt tests for Payment Request NEW P5
1652639 Stub PaymentHandler DOM bindings to allow prototyping NEW P3
1654227 Enable web platform tests for Payment Request RESOLVED Marcos Caceres [:marcosc] P1

5 Total; 3 Open (60%); 2 Resolved (40%); 0 Verified (0%);


All Reserve Bugs

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);


Bugs Requiring Triage

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);


Debugging Tips

Preference: dom.payments.request.enabled

Discussion

References

W3C Specifications

Product/Project

User Experience

Historical

Payment Request was originally developed in 2017 and 2018. Development was halted prior to shipping. Below are links to some of the resources associated with that project.