Open Bug 1318984 (paymentrequest) Opened 7 years ago Updated 1 year ago

[meta] Implement W3C Payment Request API

Categories

(Core :: DOM: Web Payments, enhancement, P2)

enhancement

Tracking

()

People

(Reporter: marcosc, Unassigned)

References

(Depends on 7 open bugs, Blocks 1 open bug, )

Details

(Keywords: dev-doc-needed, DevAdvocacy, meta, Whiteboard: [DevRel:P2])

This meta bug is for implementation of the Payment Request API, part of the larger strategy to bring payments to the web ("Web Payments").
Keywords: dev-doc-needed
Blocks: webpayments
Alias: paymentrequest
Depends on: 1318987
Depends on: 1318988
Depends on: 1318989
Depends on: 1318990
Depends on: 1318991
Depends on: 1318993
Keywords: DevAdvocacy
Whiteboard: [DevRel:P2]
Component: DOM → DOM: Web Payments
Depends on: 1375345
Depends on: paymentrequest-wpt
Depends on: 1383597
Depends on: 1435157
Depends on: 1435161
No longer depends on: 1435157
Depends on: 1436903
Depends on: 1432079
Depends on: 1441709
Depends on: 1441752
Depends on: 1442078
Depends on: 1435155
Depends on: 1442453
Depends on: 1443914
Priority: -- → P2
Depends on: 1474499
Depends on: 1480872
Depends on: 1483083
Assignee: nobody → echuang
Depends on: 1490587
Depends on: 1490599
Depends on: 1468356
No longer depends on: 1490587
Depends on: 1492295
Depends on: 1472026
Depends on: 1368949
Depends on: 1447178
Depends on: 1496656
Depends on: 1497110
Depends on: 1497699
Depends on: 1499954
Depends on: 1499992
Depends on: 1504032
Type: defect → enhancement
Depends on: 1546893
Assignee: echuang → nobody

I've been trying to find any information about the status of this feature but haven't found any so I'm sorry to be resorting to this comment: is this still actively being worked on? Where can I track the progress?

(In reply to mail from comment #2)

I've been trying to find any information about the status of this feature but haven't found any so I'm sorry to be resorting to this comment: is this still actively being worked on? Where can I track the progress?

We are currently only maintaining the DOM implementation, but we don’t plan on shipping it in a product at this point. That may change in the future, but we don’t have any concrete plans.

(In reply to Marcos Caceres [:marcosc] from comment #3)

(In reply to mail from comment #2)
We are currently only maintaining the DOM implementation, but we don’t plan on shipping it in a product at this point. That may change in the future, but we don’t have any concrete plans.

If this is indeed the case, shouldn't the platform-status page (https://platform-status.mozilla.org/) mark this as abandoned? Currently, the page seems to imply that this is being actively worked on and would eventually land in a future Firefox version.

(In reply to YG from comment #4)

If this is indeed the case, shouldn't the platform-status page (https://platform-status.mozilla.org/) mark this as abandoned?

No.

Currently, the page seems to imply that this is being actively worked on and would eventually land in a future Firefox version.

The current status reflects our position - and also what I said above. This work has not been abandoned.

(In reply to Marcos Caceres [:marcosc] from comment #5)

(In reply to YG from comment #4)

Currently, the page seems to imply that this is being actively worked on and would eventually land in a future Firefox version.

The current status reflects our position - and also what I said above. This work has not been abandoned.

Can you help me understand what this means? :

we don’t plan on shipping it in a product at this point

(In reply to YG from comment #6)

(In reply to Marcos Caceres [:marcosc] from comment #5)

The current status reflects our position - and also what I said above. This work has not been abandoned.

Can you help me understand what this means? :

we don’t plan on shipping it in a product at this point

Sure. We often develop/prototype features that we don't immediately ship in products (Firefox and Fenix, for instance) - see our "intent to prototype" in our exposure guidelines: https://wiki.mozilla.org/ExposureGuidelines#Intent_to_prototype

(please see also the dev-platform mailing list for other prototypes)

We do prototypes to understand how things work, to see if the spec is any good, and to understand if a product is viable (or not!) from a privacy and security perspective.

An API is not a itself a "product": a product requires, for example, localization, dev tools support, possibly its own section in Firefox's preferences, etc. etc. So to get something into Firefox/Fenix proper (not just Gecko) means a large part of the company needs to be involved. We are still at the "prototyping phase"... that involves not just writing code, but also collaborating on the spec with our colleagues at the W3C (Google, Apple, Microsoft, and the payment industry etc.).

I wouldn't expect to see this in Firefox proper for maybe a year or two. However, that doesn't mean we are not actively working on it. If you check the W3C repository for the spec, you can see I'm actively participating in the discussions and we are updating the spec often based on those discussions:

https://github.com/w3c/payment-handler/
https://github.com/w3c/payment-request/

Hope that helps clarify things!

I'll just add that this is the right bug to track progress on this feature. All related bugs we fix will be reflected in this bug.

(In reply to Marcos Caceres [:marcosc] from comment #7)

(In reply to YG from comment #6)
...
Hope that helps clarify things!

That does, thank you for the explanation.

As an aside, this seems like a good candidate to list here: https://mozilla.github.io/standards-positions/ unless that page is only for future features.

I'll just add that this is the right bug to track progress on this feature. All related bugs we fix will be reflected in this bug.

FWIW, I arrived at this bug from the platform-status page.

Depends on: 1646556

Seriously guys, this bug has been on the roadmap since 5 years back!

Mozilla have left W3C payment activity which BTW suffered from an extremely poor analysis of the problem space. W3C did not only take on payments, but the entire "checkout" scenario including:

  1. Payment method selection
  2. Collecting customer information (name, address, etc.)
  3. The payment operation itself
    All of this was supposed to be performed through a single monolithic API and associated browser "chrome".

What has happened during the 6+ years this activity have been running?

#1 would require major payment pages redesign as well as a very high acceptance.
#2 is currently being deprecated. It is not even obvious that payments and gathering customer information is done in the same step.
#3 well, since the W3C deliverables must "By Definition" NOT compete or challenge the members' own offerings (including Apple and Google Pay), the only thing left are UNDERPERFORMING solutions of no or little interest to anybody.

The only browser-vendor left is Google. It would take a miracle to get this effort back on track. A fundamental problem is that the payment industry (particularly banks) do not participate in or fund open standardization. Another problem is that an application-specific API becomes very close to a "product" which is incompatible with application-neutral platforms like browsers.

I would be interested in implementing the PaymentRequest interface.
However since PaymentRequest is useless without concrete implementations, I would also implement FIDO Web Pay:
https://lists.w3.org/Archives/Public/public-payments-wg/2021Jun/0021.html

How do I proceed?

Depends on: 1721897

PaymentHandler have finally been ditched by the W3C:
https://www.w3.org/Payments/WG/charter-2021.html

"Payment Handler API and Payment Method Manifest do not yet have sufficient
cross-browser implementation experience to advance to Recommendation.
However, the implementation in Chromium browsers enables experimentation,
and for this reason the Working Group intends to maintain it as a Working Draft.
If the implementation landscape changes, the Working Group will revisit the question"

The next victim seems to be PaymentRequest itself:
https://www.w3.org/2021/08/02-wpwg-spc-minutes.html

"Rouslan: In the future we'd like to move closer to WebAuthn as an extension to public key credential
… it might take .5-1 year to make the translation
… and that would decouple SPC from payment request API and put it closer to Credential Management API"

Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.