The [https://www.w3.org/TR/payment-request/ 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.
== Status Summary ==
Development is paused.
=== Development Update - Milestones 4 Delivery - Tuesday, December 11, 2018 ===
<p> </p>
Below is a weekly engineering development update.
<p> </p>
* Status: '''Green''' - In Development.
* Team has completed 23 out of 26 bugs required by the conclusion of Iteration #5 (Dec 10 - Dec 21) to remain on schedule.
* Team has completed 88% of the entire Milestone 4 Backlog which is forecast to be completed on December 21.
* View [https://docs.google.com/spreadsheets/d/19ZsqjD_H4fOjg7iPKBsMQ_toM1ywAvvd5hqvI0p1QGI/edit#gid=1990398980 Project Tracking Dashboard] for current schedule progress and backlog.
* Bugzilla Queries:
** [https://mzl.la/2GoDoCJ Work Currently In Development]
** [https://mzl.la/2FDB7b4 Available Project Work]
** [https://mzl.la/2CgrKvg Completed Project Work]
<p> </p>
=== 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 ==
