Skip to content

Issues: w3c/payment-request

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

49 Open 469 Closed
49 Open 469 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Improved error codes
#1040 opened Nov 26, 2024 by dtjones404
@rsolomakhin
10
Revise user activation model
#1036 opened Sep 18, 2024 by marcoscaceres
2
How can the Privacy Sandbox affect the payment request API?
#1034 opened Sep 17, 2024 by AdaltonLeite
1
Missing tasks in parallel steps in Payment Request API
#1032 opened Sep 10, 2024 by dontcallmedom-bot
3 tasks
Consider spec-ing when a user agent should allow activationless PaymentRequest
#1022 opened Feb 13, 2024 by stephenmcgruer
Authentication of merchant domain and details
#1014 opened Nov 14, 2023 by mimi89999
9
payment credentials management Future Candidate Feature
#1004 opened Apr 11, 2023 by asma1402
1
User activation et webauthn
#1002 opened Mar 27, 2023 by asma1402
3
Localization and string metadata for descriptions Future Candidate Feature i18n-needs-resolution Issue the Internationalization Group has raised and looks for a response on.
#948 opened Mar 31, 2021 by aphillips
16
Split shipping address from Payment Request API 1.0
#939 opened Feb 9, 2021 by danyao
1
11
Allow user activation to be delegated to a child frame to trigger request.show()
#917 opened Jun 17, 2020 by danyao
13
Make "total" and "details" optional Future Candidate Feature
#912 opened May 4, 2020 by maxlgu
11
Missing definition of retrying a payment as a concept Editorial
#889 opened Jan 2, 2020 by marcoscaceres
Ship Mode Update for PO BOX Future Candidate Feature
#888 opened Dec 10, 2019 by ForTheJim
1
5
Pass SKU instead of Total Future Candidate Feature
#879 opened Sep 3, 2019 by ianbjacobs
12
Location declaration Future Candidate Feature
#870 opened Jun 25, 2019 by davidbenoit
9
Help strings for requested fields? Future Candidate Feature
#864 opened Apr 10, 2019 by ianbjacobs
1
Add quantity prop to items Future Candidate Feature
#861 opened Apr 8, 2019 by felipenmoura
5
Should Payment Request enable optional Total for some use cases? Future Candidate Feature
#858 opened Apr 3, 2019 by ianbjacobs
4
Fine-grained error reporting with canMakePayment() Future Candidate Feature
#847 opened Mar 8, 2019 by ianbjacobs
2
Richer negotiation re: address redaction? Formal Objection Future Candidate Feature i18n-tracker Group bringing to attention of Internationalization, or tracked by i18n but not needing response. privacy-needs-resolution Issue the Privacy Group has raised and looks for a response on.
#842 opened Feb 28, 2019 by samuelweiler Proposed Rec
3
46
Change of approach for gesture to invoke Payment Sheet proposal - needs discussion
#834 opened Feb 14, 2019 by mattsaxonwp
9
Extensibility of PaymentResponse.complete(result) Extensibility Future Candidate Feature proposal - needs discussion SRC
#817 opened Dec 6, 2018 by adrianhopebailie
@marcoscaceres @rsolomakhin
9
Include payment handler information in response Future Candidate Feature Priority: Postponed
#815 opened Nov 27, 2018 by ianbjacobs
1
De-dup "user aborts the payment request" and "abort the update" Editorial
#814 opened Nov 27, 2018 by marcoscaceres
ProTip! Exclude everything labeled bug with -label:bug.