Web Payments Working Group - Activity in 2024
No matches.
Past meetings
-
1 meeting.
GitHub
w3c/payment-request
-
1 issue received 11 new comments.
-
Distinguish between user aborting and handler errors w3c/payment-request#1040 (11 comments by @dtjones404, @rsolomakhin, @stephenmcgruer)
-
w3c/secure-payment-confirmation
-
1 issue received 2 new comments.
-
Proposal: WebAuthn-agnostic browser binding for Secure Payment Confirmation w3c/secure-payment-confirmation#271 (2 comments by @pejic, @rsolomakhin)
-
TR publications
-
3 documents published.
-
Secure Payment Confirmation published 3 times as a Candidate Recommendation Draft. History of Secure Payment Confirmation
-
Past meetings
-
1 meeting.
Participants
-
1 participant left.
-
Moe Jangda (Block, Inc.) left.
-
GitHub
w3c/payment-request
-
1 issue opened.
-
Distinguish between user aborting and handler errors w3c/payment-request#1040, by @dtjones404.
-
w3c/secure-payment-confirmation
-
1 issue opened.
-
Backup of the payment bit should be defined in SPC spec w3c/secure-payment-confirmation#278, by @timcappalli.
-
-
1 issue received 8 new comments.
-
Proposal: WebAuthn-agnostic browser binding for Secure Payment Confirmation w3c/secure-payment-confirmation#271 (8 comments by @benedictvantrigt, @christiaanbrand, @ianbjacobs, @pejic, @tblachowicz)
-
-
2 pull requests merged.
-
Clarify that RP can use its own credentials even if extension not specified w3c/secure-payment-confirmation#272.
-
Creation of BBK requirements document w3c/secure-payment-confirmation#277.
-
-
2 pull requests received 18 new comments.
-
Clarify that RP can use its own credentials even if extension not specified w3c/secure-payment-confirmation#272 (9 comments by @ianbjacobs, @stephenmcgruer)
-
Creation of BBK requirements document w3c/secure-payment-confirmation#277 (9 comments by @ianbjacobs, @rsolomakhin, @stephenmcgruer)
-
w3c/web-based-payment-handler
-
1 issue opened.
-
Native app flow doesn't work in chrome 130 w3c/web-based-payment-handler#421, by @AdaltonLeite.
-
-
1 issue closed.
-
Native app flow doesn't work in chrome 130 w3c/web-based-payment-handler#421.
-
-
2 issues received 4 new comments.
-
Native app flow doesn't work in chrome 130 w3c/web-based-payment-handler#421 (3 comments by @AdaltonLeite, @rsolomakhin)
-
Does PaymentManager need to be exposed to Worker scope? w3c/web-based-payment-handler#340 (1 comment by @skyclouds2001)
-
Past meetings
-
1 meeting.
Participants
-
1 participant joined.
-
Zane Durkin (Ignite Retail Technology) joined.
-
GitHub
w3c/secure-payment-confirmation
-
1 issue opened.
-
Could cards be authenticators for SPC (or WebAuthn)? w3c/secure-payment-confirmation#276, by @ianbjacobs.
-
-
1 issue received 2 new comments.
-
Could cards be authenticators for SPC (or WebAuthn)? w3c/secure-payment-confirmation#276 (2 comments by @ianbjacobs, @RByers)
-
-
1 pull request opened.
-
Creation of BBK requirements document w3c/secure-payment-confirmation#277, by @ianbjacobs.
-
-
1 pull request received 1 new comment.
-
Creation of BBK requirements document w3c/secure-payment-confirmation#277 (1 comment by @rsolomakhin)
-
w3c/web-based-payment-handler
-
1 issue opened.
-
Question about biometric authentication w3c/web-based-payment-handler#420, by @AdaltonLeite.
-
-
1 issue received 3 new comments.
-
Question about biometric authentication w3c/web-based-payment-handler#420 (3 comments by @AdaltonLeite, @rsolomakhin)
-
w3c/payment-request
-
1 issue opened.
-
[Question] Native applications w3c/payment-request#1037, by @AdaltonLeite.
-
-
3 issues closed.
-
Proposal to add optional "description" string field to PaymentShippingOption dictionary w3c/payment-request#902.
-
[Question] Native applications w3c/payment-request#1037.
-
Question about use case Payment Request API w3c/payment-request#1033.
-
-
2 issues received 2 new comments.
-
Proposal to add optional "description" string field to PaymentShippingOption dictionary w3c/payment-request#902 (1 comment by @ianbjacobs)
-
-
1 pull request opened.
-
3iCreate generator-generic-ossf-slsa3-publish.yml w3c/payment-request#1038, by @Tinamaam.
-
-
1 pull request received 1 new comment.
-
3iCreate generator-generic-ossf-slsa3-publish.yml w3c/payment-request#1038 (1 comment by @rsolomakhin)
-
TR publications
-
1 document published.
-
Payment Request API published as a Candidate Recommendation Draft. History of Payment Request API
-
Past meetings
Participants
-
4 participants joined.
-
Ioana Chiorean (Interledger Foundation) joined.
-
Junhui He (Google LLC) joined.
-
Joshua Thomas (Ignite Retail Technology) joined.
-
Brian McManus (Ignite Retail Technology) joined.
-
-
3 participants left.
-
Joseph Xu (American Express Company) left.
-
Shyam Sheth (Google LLC) left.
-
Anne Pouillard (Worldline) left.
-
-
1 organization joined.
-
Ignite Retail Technology joined.
-
GitHub
w3c/secure-payment-confirmation
-
1 issue opened.
-
Proposal: Expanding output states for SPC w3c/secure-payment-confirmation#275, by @stephenmcgruer.
-
-
1 issue reopened.
-
Document End-User Guide w3c/secure-payment-confirmation#266, by @ianbjacobs.
-
-
2 issues received 9 new comments.
-
Proposal: WebAuthn-agnostic browser binding for Secure Payment Confirmation w3c/secure-payment-confirmation#271 (7 comments by @ianbjacobs, @rsolomakhin, @stephenmcgruer)
-
w3c/payment-request
-
6 issues opened.
-
Revise user activation model w3c/payment-request#1036, by @marcoscaceres.
-
Need help with using Payment Request API with Apple Pay w3c/payment-request#1035, by @baskarmib.
-
How can the Privacy Sandbox affect the payment request API? w3c/payment-request#1034, by @AdaltonLeite.
-
Question about use case Payment Request API w3c/payment-request#1033, by @AdaltonLeite.
-
Missing tasks in parallel steps in Payment Request API w3c/payment-request#1032, by @dontcallmedom-bot.
-
Support iOS w3c/payment-request#1030, by @AdaltonLeite.
-
-
3 issues closed.
-
Need help with using Payment Request API with Apple Pay w3c/payment-request#1035.
-
Relax user activation requirement for show() w3c/payment-request#1025.
-
Support iOS w3c/payment-request#1030.
-
-
5 issues received 6 new comments.
-
Need help with using Payment Request API with Apple Pay w3c/payment-request#1035 (1 comment by @ianbjacobs)
-
How can the Privacy Sandbox affect the payment request API? w3c/payment-request#1034 (1 comment by @ianbjacobs)
-
1 pull request merged.
-
[Spec] Restore changes since REC w3c/payment-request#1029.
-
-
1 pull request received 1 new comment.
-
w3c/payment-request#1031 (1 comment by @w3cbot)
-
w3c/web-based-payment-handler
-
1 issue opened.
-
Missing tasks in parallel steps in Payment Handler API w3c/web-based-payment-handler#419, by @dontcallmedom-bot.
-
-
1 issue received 2 new comments.
-
Enum values that ignore naming conventions in Payment Handler API w3c/web-based-payment-handler#418 (2 comments by @ianbjacobs, @rsolomakhin)
-
TR publications
-
5 documents published.
-
Payment Request API published as a Candidate Recommendation Snapshot. History of Payment Request API
-
Payment Request API published 3 times as a Candidate Recommendation Draft. History of Payment Request API
-
Secure Payment Confirmation published as a Candidate Recommendation Draft. History of Secure Payment Confirmation
-
Past meetings
Participants
-
8 participants joined.
-
Abrar Rahman Protyasha (Apple Inc.) joined.
-
Shaun Warman (PayPal) joined.
-
Siddharth Mangesh Gothoskar (PayPal) joined.
-
Akshaykumar Gaikwad (PayPal) joined.
-
Wade Jensen (PayPal) joined.
-
Sharanya Chandrasekaran (PayPal) joined.
-
Andreas Efthymiou (Visa) joined.
-
Henna Kapur (Visa) joined.
-
-
2 participants left.
-
Vinoth Madhavan (PayPal) left.
-
Krithivasan Swamynathan (PayPal) left.
-
GitHub
w3c/web-based-payment-handler
-
2 issues opened.
-
Enum values that ignore naming conventions in Payment Handler API w3c/web-based-payment-handler#418, by @dontcallmedom-bot.
-
API naming and confusion w3c/web-based-payment-handler#417, by @rsolomakhin.
-
-
2 issues received 6 new comments.
-
API naming and confusion w3c/web-based-payment-handler#417 (4 comments by @ianbjacobs, @rsolomakhin, @stephenmcgruer)
-
Broken references in Payment Handler API w3c/web-based-payment-handler#412 (2 comments by @ianbjacobs, @tidoust)
-
w3c/secure-payment-confirmation
-
2 issues opened.
-
Proposal: Remove `showOptOut` from SPC w3c/secure-payment-confirmation#274, by @stephenmcgruer.
-
"payment" WebAuthn extension does not report successful registration w3c/secure-payment-confirmation#273, by @stephenmcgruer.
-
-
2 issues received 8 new comments.
-
Proposal: Remove `showOptOut` from SPC w3c/secure-payment-confirmation#274 (5 comments by @Goosth, @rsolomakhin, @sarobrien)
-
Proposal: WebAuthn-agnostic browser binding for Secure Payment Confirmation w3c/secure-payment-confirmation#271 (3 comments by @ianbjacobs, @sarobrien, @stephenmcgruer)
-
-
1 pull request opened.
-
Clarify that RP can use its own credentials even if extension not specified w3c/secure-payment-confirmation#272, by @ianbjacobs.
-
w3c/payment-request
-
1 issue opened.
-
Collecting refunds w3c/payment-request#1028, by @Shorty049980.
-
-
2 issues closed.
-
is PaymentRequestUpdateEvent still needed? w3c/payment-request#991.
-
Collecting refunds w3c/payment-request#1028.
-
-
2 issues reopened.
-
Adding custom fields next after shipping options have been added. w3c/payment-request#548, by @ianbjacobs.
-
Split shipping address from Payment Request API 1.0 w3c/payment-request#939, by @ianbjacobs.
-
-
11 issues received 11 new comments.
-
PaymentRequest does not handle the case of store pickup w3c/payment-request#389 (1 comment by @ianbjacobs)
-
Shipping Address Validation - Suggest Alternate Address w3c/payment-request#537 (1 comment by @ianbjacobs)
-
Adding custom fields next after shipping options have been added. w3c/payment-request#548 (1 comment by @ianbjacobs)
-
Pre-calculate shipping costs for available addresses w3c/payment-request#615 (1 comment by @ianbjacobs)
-
Proposal to add optional "description" string field to PaymentShippingOption dictionary w3c/payment-request#902 (1 comment by @ianbjacobs)
-
Split shipping address from Payment Request API 1.0 w3c/payment-request#939 (1 comment by @ianbjacobs)
-
2 pull requests opened.
-
[Spec] Restore changes since REC w3c/payment-request#1029, by @stephenmcgruer.
-
Chore: set spec to auto-publish as CRD status w3c/payment-request#1027, by @marcoscaceres.
-
-
2 pull requests merged.
-
Revert "Drop PaymentAddress, shipping + billing address support (#955)" w3c/payment-request#996.
-
Chore: set spec to auto-publish as CRD status w3c/payment-request#1027.
-
-
3 pull requests received 7 new comments.
-
[Spec] Restore changes since REC w3c/payment-request#1029 (3 comments by @ianbjacobs, @stephenmcgruer)
-
Chore: set spec to auto-publish as CRD status w3c/payment-request#1027 (2 comments by @ianbjacobs, @stephenmcgruer)
-
Revert "Drop PaymentAddress, shipping + billing address support (#955)" w3c/payment-request#996 (2 comments by @ianbjacobs, @marcoscaceres)
-
Participants
-
11 participants joined.
-
Derek Hanson (Yubico) joined.
-
Bjorn Hjelm (Yubico) joined.
-
Padmanabhan K (PayPal) joined.
-
Pavan Yanamadala (PayPal) joined.
-
Hemnath Dhananjayan (PayPal) joined.
-
Vanitha Balusamy (PayPal) joined.
-
Vinoth Madhavan (PayPal) joined.
-
Kavya Ramesh (PayPal) joined.
-
Krithivasan Swamynathan (PayPal) joined.
-
Noormina Abuthahir (PayPal) joined.
-
JAYADEVI NATARAJAN (PayPal) joined.
-
-
3 participants left.
-
Urs Gubser (Worldline) left.
-
Manish Garg (VE3) left.
-
John Fontana (Yubico) left.
-
-
1 organization left.
-
VE3 left.
-
GitHub
w3c/secure-payment-confirmation
-
1 issue received 1 new comment.
-
Proposal: WebAuthn-agnostic browser binding for Secure Payment Confirmation w3c/secure-payment-confirmation#271 (1 comment by @ianbjacobs)
-
w3c/payment-request
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Status section improvement in preparation for CR Snapshot w3c/payment-request#1026, by @ianbjacobs.
-
-
2 pull requests merged.
-
Status section improvement in preparation for CR Snapshot w3c/payment-request#1026.
-
Revert spec to REC state w3c/payment-request#1021.
-
-
1 pull request received 3 new comments.
-
Revert "Drop PaymentAddress, shipping + billing address support (#955)" w3c/payment-request#996 (3 comments by @marcoscaceres)
-
GitHub
w3c/payment-request
-
1 issue received 2 new comments.
-
Alternative 'Pay' button wording options for Browser UI (the button in the sheet) w3c/payment-request#701 (2 comments by @gillesbouvier-qz, @ianbjacobs)
-
-
1 pull request received 4 new comments.
-
Revert "Drop PaymentAddress, shipping + billing address support (#955)" w3c/payment-request#996 (4 comments by @marcoscaceres)
-
w3c/secure-payment-confirmation
-
2 issues received 3 new comments.
-
Proposal: WebAuthn-agnostic browser binding for Secure Payment Confirmation w3c/secure-payment-confirmation#271 (2 comments by @RByers, @stephenmcgruer)
-
How will new passkey providers impact SPC w3c/secure-payment-confirmation#260 (1 comment by @ianbjacobs)
-
Past meetings
-
1 meeting.
GitHub
w3c/secure-payment-confirmation
-
2 issues opened.
-
Proposal: WebAuthn-agnostic browser binding for Secure Payment Confirmation w3c/secure-payment-confirmation#271, by @stephenmcgruer.
-
Google payment solutions w3c/secure-payment-confirmation#270, by @Myahr208.
-
-
1 issue closed.
-
Google payment solutions w3c/secure-payment-confirmation#270.
-
-
2 issues received 7 new comments.
-
Proposal: WebAuthn-agnostic browser binding for Secure Payment Confirmation w3c/secure-payment-confirmation#271 (5 comments by @ianbjacobs, @RByers)
-
w3c/payment-request
-
1 issue received 2 new comments.
-
Relax user activation requirement for show() w3c/payment-request#1025 (2 comments by @ianbjacobs, @rsolomakhin)
-
-
2 pull requests received 48 new comments.
-
Revert "Drop PaymentAddress, shipping + billing address support (#955)" w3c/payment-request#996 (46 comments by @ianbjacobs, @marcoscaceres)
-
Past meetings
-
1 meeting.
Participants
-
1 participant joined.
-
Eric Groves (Block, Inc.) joined.
-
-
2 participants left.
-
Ishna Neamatullah (Google LLC) left.
-
Westin Wrzesinski (Shopify) left.
-
GitHub
w3c/payment-request
-
1 issue opened.
-
Relax user activation requirement for show() w3c/payment-request#1025, by @marcoscaceres.
-
-
1 pull request received 5 new comments.
-
Revert "Drop PaymentAddress, shipping + billing address support (#955)" w3c/payment-request#996 (5 comments by @marcoscaceres)
-
w3c/secure-payment-confirmation
-
1 issue opened.
-
Limitations for showing transaction data w3c/secure-payment-confirmation#269, by @kseybold.
-
-
2 issues received 6 new comments.
-
Limitations for showing transaction data w3c/secure-payment-confirmation#269 (5 comments by @ianbjacobs, @rsolomakhin, @stephenmcgruer)
-
Improving understanding of who is authenticating for whom w3c/secure-payment-confirmation#187 (1 comment by @ianbjacobs)
-
Past meetings
-
1 meeting.
Participants
-
4 participants joined.
-
Rogerio Matsui (Rakuten Group, Inc.) joined.
-
Juan Pablo Marzetti (Block, Inc.) joined.
-
Vasilii Trofimchuk (Block, Inc.) joined.
-
Nakjo Shishkov (Netcetera) joined.
-
-
1 organization joined.
-
Netcetera joined.
-
GitHub
w3c/payment-request
-
1 pull request received 3 new comments.
w3c/secure-payment-confirmation
-
1 issue received 1 new comment.
-
Add issuer and payment system logos to transaction dialog w3c/secure-payment-confirmation#197 (1 comment by @ianbjacobs)
-
TR publications
-
1 document published.
-
Payment Request API 1.1 published as a Working Draft. History of Payment Request API 1.1
-
Past meetings
Participants
-
3 participants joined.
-
Imran Ahmed (Entersekt) joined.
-
Moe Jangda (Block, Inc.) joined.
-
Grégoire Leleux (Worldline) joined.
-
-
1 organization joined.
-
Block, Inc. joined.
-
GitHub
w3c/payment-request
-
1 issue opened.
-
Consider spec-ing when a user agent should allow activationless PaymentRequest w3c/payment-request#1022, by @stephenmcgruer.
-
-
8 issues reopened.
-
Richer negotiation re: address redaction? w3c/payment-request#842, by @ianbjacobs.
-
PaymentRequest does not handle the case of store pickup w3c/payment-request#389, by @ianbjacobs.
-
Shipping Address Validation - Suggest Alternate Address w3c/payment-request#537, by @ianbjacobs.
-
Pre-filter shipping addresses, e.g. by country w3c/payment-request#614, by @ianbjacobs.
-
Pre-calculate shipping costs for available addresses w3c/payment-request#615, by @ianbjacobs.
-
Merchant-specified default shipping address w3c/payment-request#653, by @ianbjacobs.
-
Ship Mode Update for PO BOX w3c/payment-request#888, by @ianbjacobs.
-
Proposal to add optional "description" string field to PaymentShippingOption dictionary w3c/payment-request#902, by @ianbjacobs.
-
-
9 issues received 9 new comments.
-
Split shipping address from Payment Request API 1.0 w3c/payment-request#939 (1 comment by @ianbjacobs)
-
PaymentRequest does not handle the case of store pickup w3c/payment-request#389 (1 comment by @ianbjacobs)
-
Shipping Address Validation - Suggest Alternate Address w3c/payment-request#537 (1 comment by @ianbjacobs)
-
Pre-calculate shipping costs for available addresses w3c/payment-request#615 (1 comment by @ianbjacobs)
-
Proposal to add optional "description" string field to PaymentShippingOption dictionary w3c/payment-request#902 (1 comment by @ianbjacobs)
-
2 pull requests opened.
-
Revert spec to REC state w3c/payment-request#1021, by @marcoscaceres.
-
Editorial: link allowlist self properly. w3c/payment-request#1020, by @marcoscaceres.
-
-
1 pull request merged.
-
Editorial: link allowlist self properly. w3c/payment-request#1020.
-
-
2 pull requests received 20 new comments.
-
Revert "Drop PaymentAddress, shipping + billing address support (#955)" w3c/payment-request#996 (17 comments by @marcoscaceres, @rsolomakhin, @stephenmcgruer)
-
[Spec] Relax user activation requirement for show() w3c/payment-request#1009 (3 comments by @marcoscaceres, @stephenmcgruer)
-
TR publications
-
2 documents published.
-
Payment Request API 1.1 published twice as a Working Draft. History of Payment Request API 1.1
-
Participants
-
7 participants joined.
-
Melissa Sebastian (Entersekt) joined.
-
Vesa Parkkinen (Entersekt) joined.
-
Kenneth Raymond Diaz (Entersekt) joined.
-
Westin Wrzesinski (Shopify) joined.
-
Ravi Shekhar (PayPal) joined.
-
Haribalu V (PayPal) joined.
-
Suzie Annézo--Sébire (FIME) joined.
-
-
2 participants left.
-
Tim Cappalli (Okta) left.
-
Suzie Annézo--Sébire (FIME) left.
-
-
1 organization joined.
-
PayPal joined.
-
GitHub
w3c/secure-payment-confirmation
-
2 issues opened.
-
Update SPC spec to reflect that credential create in cross-origin iframe is now allowed in WebAuthn w3c/secure-payment-confirmation#267, by @stephenmcgruer.
-
Document End-User Guide w3c/secure-payment-confirmation#266, by @maltfield.
-
-
2 issues received 6 new comments.
-
Document End-User Guide w3c/secure-payment-confirmation#266 (5 comments by @AbdoALPOP, @ianbjacobs, @maltfield)
-
Update SPC spec to reflect that credential create in cross-origin iframe is now allowed in WebAuthn w3c/secure-payment-confirmation#267 (1 comment by @stephenmcgruer)
-
w3c/payment-request
-
1 issue closed.
-
Potential typos w3c/payment-request#1015.
-
-
1 pull request merged.
-
Editorial: Small fixes w3c/payment-request#1016.
-
-
2 pull requests received 2 new comments.
-
w3c/payment-request#1019 (1 comment by @w3cbot)
-