Web Payments Working Group - Activity in 2022
No matches.
TR publications
-
2 documents published.
-
Payment Handler API published as a Working Draft. History of Payment Handler API
-
Secure Payment Confirmation published as a Working Draft. History of Secure Payment Confirmation
-
Past meetings
-
6 meetings.
Participants
-
1 chair stepped down.
-
Praveena Subrahmanyam stepped down as a chair.
-
-
1 Team contact stepped down.
-
Ian Jacobs stepped down as a Team contact.
-
-
1 participant joined.
-
Franck Delache (Shopify) joined.
-
-
53 participants left.
-
Uchi Uchibeke (Coil Technologies, Inc.) left.
-
Lionel Basdevant (Criteo) left.
-
Tawanda Brandon Sibanda (Snake Nation) left.
-
Ainsley Hargest (Federal Reserve Bank of Minneapolis) left.
-
Peter Milne (Criteo) left.
-
DAVID LAGARDERE (Criteo) left.
-
Sam Tang (Airbnb Inc) left.
-
Praveena Subrahmanyam (Airbnb Inc) left.
-
Gustavo Kok (Netflix Inc.) left.
-
Thierry Locard (Netflix Inc.) left.
-
Huaqi Shan (China Mobile Communications Corporation) left.
-
Song XU (China Mobile Communications Corporation) left.
-
Babu Muttineni (Yahoo Holdings Inc.) left.
-
Lauren Jones (Huawei) left.
-
Shuxin Ouyang (Huawei) left.
-
Chris Wood (W3C Invited Experts) left.
-
Aanchal Malhotra (Ripple) left.
-
Xin Kang (Huawei) left.
-
Jorge Barboza (Airbnb Inc) left.
-
Duy-Tung LUU (CANTON CONSULTING) left.
-
Claire Thompson (Airbnb Inc) left.
-
Mathieu Hofman (W3C Invited Experts) left.
-
Marco Medina (Netflix Inc.) left.
-
Yun Cho (Airbnb Inc) left.
-
Andrey Bannikov (Meta) left.
-
Chris Dee (Worldpay - FIS) left.
-
Robert Martin (Capital One Discover Network) left.
-
Jonathan Vokes (Worldpay - FIS) left.
-
Joshua Karoly (Netflix Inc.) left.
-
Luke Mulks (Brave Software Inc.) left.
-
Pranjal Jumde (Brave Software Inc.) left.
-
Kenneth Friedman (The Clearing House) left.
-
Dave Fortney (The Clearing House) left.
-
Jeffrey Williams (The Clearing House) left.
-
Wanli Yang (Airbnb Inc) left.
-
Giulio Andreoli (Apple Inc.) left.
-
Andy Estes (Apple Inc.) left.
-
Frank Hoffman (Klarna) left.
-
Marcos Caceres (Apple Inc.) left.
-
Luce MOINECOURT (CANTON CONSULTING) left.
-
yaohua wu (China Mobile Communications Corporation) left.
-
Magda Sypula (Apple Inc.) left.
-
Samuel Weinig (Apple Inc.) left.
-
Nick Shearer (Apple Inc.) left.
-
Theresa O'Connor (Apple Inc.) left.
-
lin li (China Mobile Communications Corporation) left.
-
Hong LIu (China Mobile Communications Corporation) left.
-
Katie Haritos-Shea (Knowbility) left.
-
Jean-Yves ROSSI (CANTON CONSULTING) left.
-
Vincent Kuntz (ISO 20022 Registration Authority) left.
-
Kris Ketels (ISO 20022 Registration Authority) left.
-
Ian Jacobs (W3C) left.
-
Devin Rousso (Apple Inc.) left.
-
-
5 organizations joined.
-
Samsung Electronics Co., Ltd. joined.
-
Conexxus joined.
-
Yubico joined.
-
OneSpan joined.
-
Amazon joined.
-
GitHub
w3c/secure-payment-confirmation
-
2 issues opened.
-
Register SPC-related WebAuthn extensions in IANA registry w3c/secure-payment-confirmation#220, by @stephenmcgruer.
-
Use lowercase values in enum w3c/secure-payment-confirmation#219, by @dontcallmedom.
-
-
1 issue closed.
-
Proposal: Enhancement - Opt-out link w3c/secure-payment-confirmation#172.
-
-
2 issues received 8 new comments.
-
Use lowercase values in enum w3c/secure-payment-confirmation#219 (7 comments by @dontcallmedom, @foolip, @rsolomakhin, @stephenmcgruer)
-
Proposal: Remove User Activation requirement for authentication w3c/secure-payment-confirmation#216 (1 comment by @stephenmcgruer)
-
-
1 pull request merged.
-
Add showOptOut option to spec w3c/secure-payment-confirmation#215.
-
-
1 pull request received 4 new comments.
-
Add showOptOut option to spec w3c/secure-payment-confirmation#215 (4 comments by @nickburris, @stephenmcgruer)
-
w3c/web-based-payment-handler
-
1 issue opened.
-
WPT test suite needs updating to match spec + implementations w3c/web-based-payment-handler#405, by @stephenmcgruer.
-
-
1 pull request merged.
-
[Spec] Remove user-identifiable information from canMakePayment w3c/web-based-payment-handler#404.
-
-
1 pull request received 3 new comments.
-
[Spec] Remove user-identifiable information from canMakePayment w3c/web-based-payment-handler#404 (3 comments by @rsolomakhin, @stephenmcgruer)
-
Lifecycle
-
1 charter started.
-
Chartered until 2 August 2023. Participants had to rejoin under this charter.
-
TR publications
-
1 document published.
-
Secure Payment Confirmation published as a Working Draft. History of Secure Payment Confirmation
-
Past meetings
-
6 meetings.
Participants
-
5 participants joined.
-
Chii-Ren Tsai (Visa) joined.
-
Tony England (Visa) joined.
-
Arman Aygen (W3C Invited Experts) joined.
-
Joel DI MANNO (FIME) joined.
-
Suzie Annézo--Sébire (FIME) joined.
-
-
8 participants left.
-
Chii-Ren Tsai (Visa) left.
-
Krystian Czesak (Shopify) left.
-
Faraz Babar (American Express Company) left.
-
Jean Carlo Emer (Stripe) left.
-
Christian Weiss (Stripe) left.
-
Michelle Bu (Stripe) left.
-
Uno Veski (Discover Financial Services LLC) left.
-
Joel DI MANNO (FIME) left.
-
-
13 organizations joined.
-
Merchant Advisory Group joined.
-
Shopify joined.
-
American Express Company joined.
-
Mastercard Incorporated joined.
-
Worldline joined.
-
Rakuten Group, Inc. joined.
-
JCB CO., LTD. joined.
-
Google LLC joined.
-
Visa joined.
-
Entersekt joined.
-
VE3 joined.
-
Discover Financial Services LLC joined.
-
FIME joined.
-
-
43 organizations left.
-
Snake Nation left.
-
Federal Reserve Bank of Minneapolis left.
-
Yahoo Holdings Inc. left.
-
FIME left.
-
VE3 left.
-
Criteo left.
-
Worldline left.
-
Verizon left.
-
Ripple left.
-
Kodansha, Publishers, Ltd. left.
-
Pundi X left.
-
Huawei left.
-
OneSpan left.
-
Mastercard Incorporated left.
-
Meta left.
-
Rakuten Group, Inc. left.
-
Capital One Discover Network left.
-
Klarna left.
-
Netflix Inc. left.
-
Google LLC left.
-
Apple Inc. left.
-
Mozilla Foundation left.
-
Amazon left.
-
CANTON CONSULTING left.
-
Entersekt left.
-
Discover Financial Services LLC left.
-
JCB CO., LTD. left.
-
Knowbility left.
-
Coil Technologies, Inc. left.
-
The Clearing House left.
-
Merchant Advisory Group left.
-
Shopify left.
-
American Express Company left.
-
Samsung Electronics Co., Ltd. left.
-
ISO 20022 Registration Authority left.
-
Visa left.
-
Brave Software Inc. left.
-
Conexxus left.
-
China Mobile Communications Corporation left.
-
Airbnb Inc left.
-
Yubico left.
-
Stripe left.
-
Worldpay - FIS left.
-
GitHub
w3c/secure-payment-confirmation
-
1 issue opened.
-
Proposal: Remove User Activation requirement for authentication w3c/secure-payment-confirmation#216, by @stephenmcgruer.
-
-
2 issues received 7 new comments.
-
Using CredentialsContainer.get() instead of Payment Request API w3c/secure-payment-confirmation#56 (5 comments by @adrianhopebailie, @Goosth, @ianbjacobs, @stephenmcgruer)
-
Add issuer and payment system logos to transaction dialog w3c/secure-payment-confirmation#197 (2 comments by @apouillard, @mountainhippo)
-
-
3 pull requests opened.
-
Updated patent policy paragraph after rechartering w3c/secure-payment-confirmation#217, by @ianbjacobs.
-
Add showOptOut option to spec w3c/secure-payment-confirmation#215, by @nickburris.
-
[Spec] Expand 'payment attack' section for on-path attacks w3c/secure-payment-confirmation#214, by @stephenmcgruer.
-
-
2 pull requests merged.
-
Updated patent policy paragraph after rechartering w3c/secure-payment-confirmation#217.
-
[Spec] Expand 'payment attack' section for on-path attacks w3c/secure-payment-confirmation#214.
-
-
2 pull requests received 24 new comments.
-
Add showOptOut option to spec w3c/secure-payment-confirmation#215 (21 comments by @ianbjacobs, @nickburris, @stephenmcgruer)
-
[Spec] Expand 'payment attack' section for on-path attacks w3c/secure-payment-confirmation#214 (3 comments by @rsolomakhin, @stephenmcgruer)
-
w3c/web-based-payment-handler
-
1 pull request opened.
-
[Spec] Remove user-identifiable information from canMakePayment w3c/web-based-payment-handler#404, by @stephenmcgruer.
-
-
1 pull request received 1 new comment.
-
[Spec] Remove user-identifiable information from canMakePayment w3c/web-based-payment-handler#404 (1 comment by @stephenmcgruer)
-
w3c/payment-request
-
1 pull request opened.
-
Remove note since in practice we have a 1.1 branch w3c/payment-request#1001, by @ianbjacobs.
-
-
1 pull request merged.
-
Remove note since in practice we have a 1.1 branch w3c/payment-request#1001.
-
-
2 pull requests received 5 new comments.
-
Remove note since in practice we have a 1.1 branch w3c/payment-request#1001 (4 comments by @ianbjacobs, @marcoscaceres)
-
Revert "Drop PaymentAddress, shipping + billing address support (#955)" w3c/payment-request#996 (1 comment by @marcoscaceres)
-
Past meetings
-
7 meetings.
Participants
-
3 participants joined.
-
Nobuyoshi Seo (JCB CO., LTD.) joined.
-
Jinho Bang (W3C Invited Experts) joined.
-
Uchi Uchibeke (Coil Technologies, Inc.) joined.
-
-
1 participant left.
-
Jinho Bang (W3C Invited Experts) left.
-
GitHub
w3c/payment-request
-
1 pull request opened.
-
Define JSON-serialize using the Infra algorithm for it. w3c/payment-request#999, by @jyasskin.
-
-
1 pull request merged.
-
Define JSON-serialize using the Infra algorithm for it. w3c/payment-request#999.
-
-
1 pull request received 1 new comment.
-
Revert "Drop PaymentAddress, shipping + billing address support (#955)" w3c/payment-request#996 (1 comment by @marcoscaceres)
-
Lifecycle
-
1 charter extension.
-
Charter extended until 31 October 2022.
-
TR publications
-
7 documents published.
-
Payment Method Identifiers published as a Recommendation. History of Payment Method Identifiers
-
Payment Request API published as a Recommendation. History of Payment Request API
-
Secure Payment Confirmation published 4 times as a Working Draft. History of Secure Payment Confirmation
-
Payment Handler API published as a Working Draft. History of Payment Handler API
-
Past meetings
-
10 meetings.
Participants
-
2 participants joined.
-
Rick Byers (Google LLC) joined.
-
Fahad Saleem (Mastercard Incorporated) joined.
-
GitHub
w3c/secure-payment-confirmation
-
5 issues opened.
-
Add locale hint for browser UX w3c/secure-payment-confirmation#209, by @ianbjacobs.
-
`DOMString` for `payeeName` vs. `USVString` for other fields? w3c/secure-payment-confirmation#208, by @aphillips.
-
Term 'monkey-patch' may not be inclusive? w3c/secure-payment-confirmation#207, by @aphillips.
-
Error example contains a hardcoded string w3c/secure-payment-confirmation#206, by @aphillips.
-
language and direction metadata needed? w3c/secure-payment-confirmation#205, by @aphillips.
-
-
6 issues closed.
-
Add locale hint for browser UX w3c/secure-payment-confirmation#209.
-
`DOMString` for `payeeName` vs. `USVString` for other fields? w3c/secure-payment-confirmation#208.
-
Error example contains a hardcoded string w3c/secure-payment-confirmation#206.
-
Localization topics to address w3c/secure-payment-confirmation#93.
-
i18n Review Checklist for Secure Payment Confirmation (headed to CR) w3c/secure-payment-confirmation#202.
-
Term 'monkey-patch' may not be inclusive? w3c/secure-payment-confirmation#207.
-
-
9 issues received 9 new comments.
-
language and direction metadata needed? w3c/secure-payment-confirmation#205 (1 comment by @aphillips)
-
Make it easy to determine whether a user agent supports SPC w3c/secure-payment-confirmation#81 (1 comment by @stephenmcgruer)
-
Consider separating the SPC powers of Third Party invocation and Payment display w3c/secure-payment-confirmation#157 (1 comment by @ianbjacobs)
-
How do RPs determine when to enroll the user? w3c/secure-payment-confirmation#124 (1 comment by @ianbjacobs)
-
Error example contains a hardcoded string w3c/secure-payment-confirmation#206 (1 comment by @ianbjacobs)
-
`DOMString` for `payeeName` vs. `USVString` for other fields? w3c/secure-payment-confirmation#208 (1 comment by @ianbjacobs)
-
i18n Review Checklist for Secure Payment Confirmation (headed to CR) w3c/secure-payment-confirmation#202 (1 comment by @ianbjacobs)
-
Term 'monkey-patch' may not be inclusive? w3c/secure-payment-confirmation#207 (1 comment by @ianbjacobs)
-
-
4 pull requests opened.
-
[Explainer] Update explainer.md for latest Security & Privacy changes w3c/secure-payment-confirmation#213, by @stephenmcgruer.
-
[Spec] Add SecurePaymentConfirmationRequest.locale w3c/secure-payment-confirmation#212, by @stephenmcgruer.
-
[Spec] Use USVString rather than DOMString w3c/secure-payment-confirmation#211, by @stephenmcgruer.
-
[Spec] Remove example code with a hard-coded error string w3c/secure-payment-confirmation#210, by @stephenmcgruer.
-
-
4 pull requests merged.
-
[Explainer] Update explainer.md for latest Security & Privacy changes w3c/secure-payment-confirmation#213.
-
[Spec] Add SecurePaymentConfirmationRequest.locale w3c/secure-payment-confirmation#212.
-
[Spec] Use USVString rather than DOMString w3c/secure-payment-confirmation#211.
-
[Spec] Remove example code with a hard-coded error string w3c/secure-payment-confirmation#210.
-
-
1 pull request closed.
-
Displayable string language/dir support from document context w3c/secure-payment-confirmation#192.
-
-
5 pull requests received 21 new comments.
-
[Spec] Add SecurePaymentConfirmationRequest.locale w3c/secure-payment-confirmation#212 (15 comments by @aphillips, @ianbjacobs, @stephenmcgruer)
-
[Explainer] Update explainer.md for latest Security & Privacy changes w3c/secure-payment-confirmation#213 (2 comments by @ianbjacobs, @stephenmcgruer)
-
[Spec] Use USVString rather than DOMString w3c/secure-payment-confirmation#211 (2 comments by @aphillips, @stephenmcgruer)
-
[Spec] Remove example code with a hard-coded error string w3c/secure-payment-confirmation#210 (1 comment by @stephenmcgruer)
-
Displayable string language/dir support from document context w3c/secure-payment-confirmation#192 (1 comment by @ianbjacobs)
-
w3c/payment-request
-
1 issue opened.
-
"current settings object's relevant global object" is not defined w3c/payment-request#994, by @Ms2ger.
-
-
1 issue closed.
-
"current settings object's relevant global object" is not defined w3c/payment-request#994.
-
-
2 pull requests opened.
-
Editorial: use different global w3c/payment-request#997, by @marcoscaceres.
-
Revert "Drop PaymentAddress, shipping + billing address support (#955)" w3c/payment-request#996, by @marcoscaceres.
-
-
1 pull request merged.
-
Editorial: use different global w3c/payment-request#997.
-
-
3 pull requests received 10 new comments.
-
Revert "Drop PaymentAddress, shipping + billing address support (#955)" w3c/payment-request#996 (8 comments by @ianbjacobs, @marcoscaceres, @stephenmcgruer)
-
w3c/payment-request#998 (1 comment by @w3cbot)
-
w3c/web-based-payment-handler
-
1 issue opened.
-
Broken references in Payment Handler API w3c/web-based-payment-handler#402, by @dontcallmedom-bot.
-
-
1 issue closed.
-
Broken references in Payment Handler API w3c/web-based-payment-handler#402.
-
-
1 issue received 1 new comment.
-
Remove "instrument" concept from PaymentManager w3c/web-based-payment-handler#371 (1 comment by @ianbjacobs)
-
-
1 pull request opened.
-
Fix some broken links w3c/web-based-payment-handler#403, by @ianbjacobs.
-
-
1 pull request merged.
-
Fix some broken links w3c/web-based-payment-handler#403.
-
-
1 pull request received 3 new comments.
TR publications
-
5 documents published.
-
Secure Payment Confirmation published 5 times as a Working Draft. History of Secure Payment Confirmation
-
Past meetings
-
7 meetings.
Participants
-
1 participant joined.
-
Rose Robertson (Shopify) joined.
-
-
3 participants left.
-
Rami Josef (Worldpay - FIS) left.
-
Danny Russell (Worldpay - FIS) left.
-
Bart de Water (Shopify) left.
-
GitHub
w3c/secure-payment-confirmation
-
3 issues opened.
-
Broken "Object" xref in § Set SPC Transaction Mode w3c/secure-payment-confirmation#203, by @Ms2ger.
-
i18n Review Checklist for Secure Payment Confirmation (headed to CR) w3c/secure-payment-confirmation#202, by @ianbjacobs.
-
Add issuer and payment system logos to transaction dialog w3c/secure-payment-confirmation#197, by @ianbjacobs.
-
-
2 issues closed.
-
Broken "Object" xref in § Set SPC Transaction Mode w3c/secure-payment-confirmation#203.
-
rp vs. rpId w3c/secure-payment-confirmation#191.
-
-
3 issues received 4 new comments.
-
Broken "Object" xref in § Set SPC Transaction Mode w3c/secure-payment-confirmation#203 (2 comments by @stephenmcgruer)
-
-
5 pull requests opened.
-
[Spec] Dictionary members should be sequence not FrozenArray w3c/secure-payment-confirmation#201, by @stephenmcgruer.
-
Add fast checklist.md w3c/secure-payment-confirmation#200, by @ianbjacobs.
-
Updating privacy self-review questionnaire responses w3c/secure-payment-confirmation#199, by @ianbjacobs.
-
[Spec] Rename rp --> rpId in CollectedClientAdditionalPaymentData w3c/secure-payment-confirmation#198, by @stephenmcgruer.
-
[Spec] Allow either required or preferred for residentKey w3c/secure-payment-confirmation#196, by @stephenmcgruer.
-
-
5 pull requests merged.
-
[Spec] Rename rp --> rpId in CollectedClientAdditionalPaymentData w3c/secure-payment-confirmation#198.
-
[Spec] Dictionary members should be sequence not FrozenArray w3c/secure-payment-confirmation#201.
-
Add fast checklist.md w3c/secure-payment-confirmation#200.
-
Updating privacy self-review questionnaire responses w3c/secure-payment-confirmation#199.
-
[Spec] Allow either required or preferred for residentKey w3c/secure-payment-confirmation#196.
-
-
1 pull request received 8 new comments.
-
[Spec] Rename rp --> rpId in CollectedClientAdditionalPaymentData w3c/secure-payment-confirmation#198 (8 comments by @ianbjacobs, @stare893, @stephenmcgruer)
-
w3c/payment-method-id
-
1 issue closed.
-
Prepare for Proposed Recommendation w3c/payment-method-id#56.
-
-
1 issue received 1 new comment.
w3c/webpayments
-
1 pull request opened.
-
Add privacy concerns README w3c/webpayments#261, by @rsolomakhin.
-
-
1 pull request received 4 new comments.
-
Add privacy concerns README w3c/webpayments#261 (4 comments by @ianbjacobs, @rsolomakhin, @stephenmcgruer)
-
w3c/web-based-payment-handler
-
1 issue received 2 new comments.
-
Request for use cases: "canmakepayment" event w3c/web-based-payment-handler#401 (2 comments by @ianbjacobs, @stephenmcgruer)
-
-
1 pull request received 2 new comments.
w3c/payment-request
-
1 issue received 1 new comment.
TR publications
-
1 document published.
-
Payment Request API 1.1 published as a First Public Working Draft. History of Payment Request API 1.1
-
Past meetings
-
6 meetings.
Participants
-
1 participant joined.
-
Soumya Chakrabarty (JCB CO., LTD.) joined.
-
-
1 participant left.
-
Liquan Gu (Google LLC) left.
-
GitHub
w3c/web-based-payment-handler
-
1 issue opened.
-
Request for use cases: "canmakepayment" event w3c/web-based-payment-handler#401, by @rsolomakhin.
-
w3c/payment-request
-
1 issue opened.
-
is PaymentRequestUpdateEvent still needed? w3c/payment-request#991, by @dontcallmedom.
-
-
3 issues closed.
-
Manually trigger payment event. w3c/payment-request#989.
-
Custom .data validation during construction of PaymentRequest w3c/payment-request#975.
-
1 issue received 1 new comment.
-
3 pull requests merged.
-
Define concepts for converting and validating `.data` w3c/payment-request#977.
-
passing data on complete() w3c/payment-request#982.
-
Proposed addition: validate .data on construction w3c/payment-request#976.
-
-
3 pull requests received 18 new comments.
-
Define concepts for converting and validating `.data` w3c/payment-request#977 (9 comments by @marcoscaceres, @stephenmcgruer)
-
passing data on complete() w3c/payment-request#982 (8 comments by @marcoscaceres, @rsolomakhin, @stephenmcgruer)
-
w3c/payment-request#990 (1 comment by @w3cbot)
-
w3c/secure-payment-confirmation
-
1 issue closed.
-
Spec: move validation of some input parameters to construction time w3c/secure-payment-confirmation#194.
-
-
1 issue received 3 new comments.
-
Integrating SPC with Open Banking w3c/secure-payment-confirmation#51 (3 comments by @ianbjacobs, @janaka, @SensibleWood)
-
-
1 pull request merged.
-
[Spec] Move some input validation to construction time w3c/secure-payment-confirmation#195.
-
-
1 pull request received 7 new comments.
-
[Spec] Move some input validation to construction time w3c/secure-payment-confirmation#195 (7 comments by @rsolomakhin, @stephenmcgruer)
-
Past meetings
-
6 meetings.
Participants
-
1 participant joined.
-
Grégoire Leleux (FIME) joined.
-
GitHub
w3c/secure-payment-confirmation
-
2 issues opened.
-
Spec: move validation of some input parameters to construction time w3c/secure-payment-confirmation#194, by @stephenmcgruer.
-
rp vs. rpId w3c/secure-payment-confirmation#191, by @rlin1.
-
-
2 issues closed.
-
How can SPC be used in conjunction with a frictionless 3DS flow? w3c/secure-payment-confirmation#29.
-
Encrypt SPC Credential Identifiers in authentication flows to increase privacy w3c/secure-payment-confirmation#77.
-
-
8 issues received 11 new comments.
-
Proposal: Enhancement - Opt-out link w3c/secure-payment-confirmation#172 (3 comments by @ianbjacobs, @rsolomakhin)
-
Supporting roaming authenticators w3c/secure-payment-confirmation#12 (2 comments by @Goosth, @stephenmcgruer)
-
Improving understanding of who is authenticating for whom w3c/secure-payment-confirmation#187 (1 comment by @rlin1)
-
How can SPC be used in conjunction with a frictionless 3DS flow? w3c/secure-payment-confirmation#29 (1 comment by @ianbjacobs)
-
Impact of passkeys on SPC (formerly synced credentials) w3c/secure-payment-confirmation#174 (1 comment by @rlin1)
-
Encrypt SPC Credential Identifiers in authentication flows to increase privacy w3c/secure-payment-confirmation#77 (1 comment by @ianbjacobs)
-
-
3 pull requests opened.
-
[Spec] Move some input validation to construction time w3c/secure-payment-confirmation#195, by @stephenmcgruer.
-
[Spec] Add WPT test information to the spec w3c/secure-payment-confirmation#193, by @stephenmcgruer.
-
Displayable string language/dir support from document context w3c/secure-payment-confirmation#192, by @ianbjacobs.
-
-
2 pull requests merged.
-
[Spec] Add WPT test information to the spec w3c/secure-payment-confirmation#193.
-
Additional guidance regarding credentials and privacy w3c/secure-payment-confirmation#189.
-
-
3 pull requests received 7 new comments.
-
Additional guidance regarding credentials and privacy w3c/secure-payment-confirmation#189 (4 comments by @ianbjacobs, @npdoty)
-
Displayable string language/dir support from document context w3c/secure-payment-confirmation#192 (2 comments by @ianbjacobs, @stephenmcgruer)
-
[Spec] Add WPT test information to the spec w3c/secure-payment-confirmation#193 (1 comment by @stephenmcgruer)
-
w3c/payment-request
-
1 issue opened.
-
Manually trigger payment event. w3c/payment-request#989, by @Nnamso.
-
-
1 issue received 1 new comment.
-
1 pull request received 2 new comments.
-
Define concepts for converting and validating `.data` w3c/payment-request#977 (2 comments by @stephenmcgruer)
-
Past meetings
-
7 meetings.
Participants
-
3 participants joined.
-
Marcos Caceres (Apple Inc.) joined.
-
Sue Koomen (American Express Company) joined.
-
Matt Crothers (American Express Company) joined.
-
-
9 participants left.
-
David Singer (Apple Inc.) left.
-
Jennifer Lau (American Express Company) left.
-
Manish Deliwala (American Express Company) left.
-
werner bruinings (American Express Company) left.
-
Amy Slack (American Express Company) left.
-
Jay Patel (American Express Company) left.
-
Lauren Helt (American Express Company) left.
-
Alaric Eby (American Express Company) left.
-
Scott Zinn (American Express Company) left.
-
GitHub
w3c/secure-payment-confirmation
-
4 issues opened.
-
Improving understanding of who is authenticating for whom w3c/secure-payment-confirmation#187, by @ianbjacobs.
-
SPC for non-payment use cases w3c/secure-payment-confirmation#186, by @ianbjacobs.
-
SPC for Recurring payments w3c/secure-payment-confirmation#185, by @ianbjacobs.
-
Request to increase icon size w3c/secure-payment-confirmation#184, by @ianbjacobs.
-
-
3 issues closed.
-
Clarification on requiring user activation for credential creation in cross-origin iframes to mitigation cross-site tracking w3c/secure-payment-confirmation#128.
-
11.3 & 11.4: define the mitigation w3c/secure-payment-confirmation#143.
-
11.2 define the mitigation w3c/secure-payment-confirmation#142.
-
-
10 issues received 27 new comments.
-
Improving understanding of who is authenticating for whom w3c/secure-payment-confirmation#187 (5 comments by @ianbjacobs, @SensibleWood, @stephenmcgruer)
-
11.2 define the mitigation w3c/secure-payment-confirmation#142 (4 comments by @ianbjacobs, @samuelweiler, @stephenmcgruer)
-
SPC for non-payment use cases w3c/secure-payment-confirmation#186 (4 comments by @ianbjacobs, @SensibleWood, @stare893)
-
Clarification on requiring user activation for credential creation in cross-origin iframes to mitigation cross-site tracking w3c/secure-payment-confirmation#128 (3 comments by @caraitto, @stephenmcgruer)
-
11.3 & 11.4: define the mitigation w3c/secure-payment-confirmation#143 (3 comments by @ianbjacobs, @samuelweiler)
-
Encrypt SPC Credential Identifiers in authentication flows to increase privacy w3c/secure-payment-confirmation#77 (2 comments by @ianbjacobs, @npdoty)
-
SPC for Recurring payments w3c/secure-payment-confirmation#185 (2 comments by @ianbjacobs, @SensibleWood)
-
Request to increase icon size w3c/secure-payment-confirmation#184 (2 comments by @ianbjacobs, @stephenmcgruer)
-
Proposal: Enhancement - Opt-out link w3c/secure-payment-confirmation#172 (1 comment by @stephenmcgruer)
-
Consider separating the SPC powers of Third Party invocation and Payment display w3c/secure-payment-confirmation#157 (1 comment by @ianbjacobs)
-
-
2 pull requests opened.
-
Additional guidance regarding credentials and privacy w3c/secure-payment-confirmation#189, by @ianbjacobs.
-
[Spec] Add link from 11.2 to 4.1.4 w3c/secure-payment-confirmation#188, by @stephenmcgruer.
-
-
2 pull requests merged.
-
[Spec] Require user-activation for credential creation in cross-origin iframe w3c/secure-payment-confirmation#178.
-
[Spec] Add link from 11.2 to 4.1.4 w3c/secure-payment-confirmation#188.
-
-
3 pull requests received 7 new comments.
-
[Spec] Require user-activation for credential creation in cross-origin iframe w3c/secure-payment-confirmation#178 (4 comments by @nickburris, @stephenmcgruer)
-
[Spec] Add link from 11.2 to 4.1.4 w3c/secure-payment-confirmation#188 (2 comments by @samuelweiler, @stephenmcgruer)
-
Additional guidance regarding credentials and privacy w3c/secure-payment-confirmation#189 (1 comment by @ianbjacobs)
-
Past meetings
-
6 meetings.
Participants
-
1 participant joined.
-
Marie Jordan (Visa) joined.
-
-
3 participants left.
-
Marcos Caceres (Apple Inc.) left.
-
Krish Yallam (Barclays Bank PLC) left.
-
Lawrence Cheng (Barclays Bank PLC) left.
-
-
1 organization left.
-
Barclays Bank PLC left.
-
GitHub
w3c/secure-payment-confirmation
-
5 issues closed.
-
Accessible icon information w3c/secure-payment-confirmation#127.
-
Rich merchant details displayed in the payment confirmation dialog w3c/secure-payment-confirmation#48.
-
Multiple versions of card art icon? (E.g. to support dark mode) w3c/secure-payment-confirmation#1.
-
Privacy consideration: GDPR w3c/secure-payment-confirmation#109.
-
Is the "payment" extension a part of Relying Party - Client Platform API signature? w3c/secure-payment-confirmation#97.
-
-
10 issues received 23 new comments.
-
Proposal: Enhancement - Opt-out link w3c/secure-payment-confirmation#172 (9 comments by @christiaanbrand, @ianbjacobs, @stare893, @stephenmcgruer)
-
Is the "payment" extension a part of Relying Party - Client Platform API signature? w3c/secure-payment-confirmation#97 (4 comments by @ianbjacobs, @stephenmcgruer, @ynojima)
-
Impact of passkeys on SPC (formerly synced credentials) w3c/secure-payment-confirmation#174 (2 comments by @ianbjacobs)
-
Accessible icon information w3c/secure-payment-confirmation#127 (2 comments by @ianbjacobs, @michael-n-cooper)
-
Is it possible for a user to downgrade a credential creation request? w3c/secure-payment-confirmation#154 (1 comment by @ianbjacobs)
-
Rich merchant details displayed in the payment confirmation dialog w3c/secure-payment-confirmation#48 (1 comment by @ianbjacobs)
-
Multiple versions of card art icon? (E.g. to support dark mode) w3c/secure-payment-confirmation#1 (1 comment by @ianbjacobs)
-
Clarification on requiring user activation for credential creation in cross-origin iframes to mitigation cross-site tracking w3c/secure-payment-confirmation#128 (1 comment by @ianbjacobs)
-
-
3 pull requests opened.
-
[Spec] Add note on SPC opt-in, and misc clarifications w3c/secure-payment-confirmation#183, by @stephenmcgruer.
-
[Spec] Be clearer about authentication ceremony privacy in 4.1.4 w3c/secure-payment-confirmation#182, by @stephenmcgruer.
-
Add a note in example on meaning of canMakePayment w3c/secure-payment-confirmation#181, by @ianbjacobs.
-
-
3 pull requests merged.
-
[Spec] Add note on SPC opt-in, and misc clarifications w3c/secure-payment-confirmation#183.
-
[Spec] Be clearer about authentication ceremony privacy in 4.1.4 w3c/secure-payment-confirmation#182.
-
Add a note in example on meaning of canMakePayment w3c/secure-payment-confirmation#181.
-
-
2 pull requests received 12 new comments.
-
[Spec] Add note on SPC opt-in, and misc clarifications w3c/secure-payment-confirmation#183 (11 comments by @ianbjacobs, @stephenmcgruer)
-
[Spec] Be clearer about authentication ceremony privacy in 4.1.4 w3c/secure-payment-confirmation#182 (1 comment by @stephenmcgruer)
-
w3c/payment-method-manifest
-
1 issue closed.
-
Spec cleanup for "default_applications" w3c/payment-method-manifest#44.
-
w3c/payment-request
-
1 pull request opened.
-
Editorial: typo fix w3c/payment-request#988, by @ianbjacobs.
-
-
1 pull request merged.
-
Editorial: typo fix w3c/payment-request#988.
-
Lifecycle
-
1 charter extension.
-
Charter extended until 31 August 2022.
-
Past meetings
-
7 meetings.
Participants
-
5 participants joined.
-
Jorge Vargas (Capital One Discover Network) joined.
-
Dennis Hills (Yubico) joined.
-
Nicholas Burris (Google LLC) joined.
-
Uno Veski (Discover Financial Services LLC) joined.
-
Bill Collins (Discover Financial Services LLC) joined.
-
-
1 participant left.
-
Jeff Hodges (Google LLC) left.
-
GitHub
w3c/secure-payment-confirmation
-
6 issues closed.
-
Proposal: Add `payeeName` as alternative to `payeeOrigin` w3c/secure-payment-confirmation#163.
-
[Spec] Registration example is misleading around whether an iframe is required w3c/secure-payment-confirmation#168.
-
Conditionally-shown Transaction UX and WebAuthn w3c/secure-payment-confirmation#92.
-
What are requirements when more than one SPC credential matches? w3c/secure-payment-confirmation#69.
-
Does the API support timeout? w3c/secure-payment-confirmation#67.
-
Requirements and Good Practices around Unenrollment w3c/secure-payment-confirmation#63.
-
-
22 issues received 32 new comments.
-
Localization topics to address w3c/secure-payment-confirmation#93 (5 comments by @aphillips, @ianbjacobs, @rsolomakhin)
-
Consider separating the SPC powers of Third Party invocation and Payment display w3c/secure-payment-confirmation#157 (4 comments by @ianbjacobs, @stephenmcgruer)
-
Clarification on requiring user activation for credential creation in cross-origin iframes to mitigation cross-site tracking w3c/secure-payment-confirmation#128 (3 comments by @ianbjacobs, @jcemer-stripe, @stephenmcgruer)
-
Rich merchant details displayed in the payment confirmation dialog w3c/secure-payment-confirmation#48 (2 comments by @stephenmcgruer)
-
Impact of passkeys on SPC (formerly synced credentials) w3c/secure-payment-confirmation#174 (1 comment by @ljharb)
-
Proposal: add Relying Party id as a required input to SPC authentication w3c/secure-payment-confirmation#164 (1 comment by @stephenmcgruer)
-
Make it easy to determine whether a user agent supports SPC w3c/secure-payment-confirmation#81 (1 comment by @ianbjacobs)
-
Should SPC be invokable outside of a PaymentRequest flow? w3c/secure-payment-confirmation#65 (1 comment by @ianbjacobs)
-
Using CredentialsContainer.get() instead of Payment Request API w3c/secure-payment-confirmation#56 (1 comment by @ianbjacobs)
-
Suggestion to enable Frictionless Flows w3c/secure-payment-confirmation#34 (1 comment by @ianbjacobs)
-
How can SPC be used in conjunction with a frictionless 3DS flow? w3c/secure-payment-confirmation#29 (1 comment by @ianbjacobs)
-
Multiple versions of card art icon? (E.g. to support dark mode) w3c/secure-payment-confirmation#1 (1 comment by @JeanDim)
-
Conditionally-shown Transaction UX and WebAuthn w3c/secure-payment-confirmation#92 (1 comment by @stephenmcgruer)
-
11.3 & 11.4: define the mitigation w3c/secure-payment-confirmation#143 (1 comment by @stephenmcgruer)
-
Is the "payment" extension a part of Relying Party - Client Platform API signature? w3c/secure-payment-confirmation#97 (1 comment by @stephenmcgruer)
-
What are requirements when more than one SPC credential matches? w3c/secure-payment-confirmation#69 (1 comment by @ianbjacobs)
-
Requirements and Good Practices around Unenrollment w3c/secure-payment-confirmation#63 (1 comment by @ianbjacobs)
-
Provide support for Out of Band Authentication to a secondary device w3c/secure-payment-confirmation#30 (1 comment by @ianbjacobs)
-
-
5 pull requests opened.
-
Add payeeName input to spec w3c/secure-payment-confirmation#180, by @nickburris.
-
[Spec] Make example clearer about iframe interactions w3c/secure-payment-confirmation#179, by @stephenmcgruer.
-
[Spec] Require user-activation for credential creation in cross-origin iframe w3c/secure-payment-confirmation#178, by @stephenmcgruer.
-
[Spec] Remove outdated write-up from 11.3 w3c/secure-payment-confirmation#177, by @stephenmcgruer.
-
[Spec] Remove example from 11.2 w3c/secure-payment-confirmation#176, by @stephenmcgruer.
-
-
4 pull requests merged.
-
Add payeeName input to spec w3c/secure-payment-confirmation#180.
-
[Spec] Make example clearer about iframe interactions w3c/secure-payment-confirmation#179.
-
[Spec] Remove outdated write-up from 11.3 w3c/secure-payment-confirmation#177.
-
[Spec] Remove example from 11.2 w3c/secure-payment-confirmation#176.
-
-
4 pull requests received 15 new comments.
-
Add payeeName input to spec w3c/secure-payment-confirmation#180 (10 comments by @ianbjacobs, @nickburris, @stephenmcgruer)
-
Using displayName for icon accessibility w3c/secure-payment-confirmation#162 (2 comments by @ianbjacobs, @RealJoshue108)
-
[Spec] Remove outdated write-up from 11.3 w3c/secure-payment-confirmation#177 (2 comments by @ianbjacobs)
-
[Spec] Make example clearer about iframe interactions w3c/secure-payment-confirmation#179 (1 comment by @stephenmcgruer)
-
w3c/payment-request
-
1 pull request opened.
-
Editorial: use associated Document in place of responsible document w3c/payment-request#985, by @miketaylr.
-
-
1 pull request merged.
-
Editorial: use associated Document in place of responsible document w3c/payment-request#985.
-
-
1 pull request received 1 new comment.
-
w3c/payment-request#986 (1 comment by @w3cbot)
-
Past meetings
-
6 meetings.
Participants
-
2 participants joined.
-
Urs Gubser (Worldline) joined.
-
Steve Cole (Merchant Advisory Group) joined.
-
-
4 participants left.
-
Sebastian Elfors (Yubico) left.
-
Michel Weksler (Airbnb Inc) left.
-
Peter Saint-Andre (Mozilla Foundation) left.
-
Robert Savage (Merchant Advisory Group) left.
-
GitHub
w3c/secure-payment-confirmation
-
1 issue opened.
-
Impact of passkeys on SPC (formerly synced credentials) w3c/secure-payment-confirmation#174, by @ianbjacobs.
-
-
2 issues closed.
-
Proposal: add Relying Party id as a required input to SPC authentication w3c/secure-payment-confirmation#164.
-
Should SPC allow for a failed download of the payment instrument icon? w3c/secure-payment-confirmation#125.
-
-
2 issues received 4 new comments.
-
Proposal: Enhancement - Opt-out link w3c/secure-payment-confirmation#172 (3 comments by @cyberphone, @ianbjacobs, @jcemer-stripe)
-
Should SPC allow for a failed download of the payment instrument icon? w3c/secure-payment-confirmation#125 (1 comment by @domfarolino)
-
-
2 pull requests opened.
-
Update README.md - fix spelling of name w3c/secure-payment-confirmation#175, by @christiaanbrand.
-
Require Relying Party ID as input w3c/secure-payment-confirmation#173, by @nickburris.
-
-
3 pull requests merged.
-
Update README.md - fix spelling of name w3c/secure-payment-confirmation#175.
-
Require Relying Party ID as input w3c/secure-payment-confirmation#173.
-
Add option to allow instrument icon download fail w3c/secure-payment-confirmation#171.
-
-
2 pull requests received 20 new comments.
-
Require Relying Party ID as input w3c/secure-payment-confirmation#173 (16 comments by @ianbjacobs, @nickburris, @stephenmcgruer)
-
Add option to allow instrument icon download fail w3c/secure-payment-confirmation#171 (4 comments by @ianbjacobs, @nickburris)
-
w3c/payment-request
-
1 issue opened.
-
.hasEnrolledInstrument() throws exception "NotAllowedError: Exceeded query quota for hasEnrolledInstrument" w3c/payment-request#984, by @DevendraDev.
-
-
1 issue closed.
-
1 issue received 1 new comment.
-
.hasEnrolledInstrument() throws exception "NotAllowedError: Exceeded query quota for hasEnrolledInstrument" w3c/payment-request#984 (1 comment by @rsolomakhin)
-
Past meetings
Participants
-
5 participants joined.
-
Sameer Tare (Mastercard Incorporated) joined.
-
Carey Ferro (Discover Financial Services LLC) joined.
-
Jeremy Ney (Google LLC) joined.
-
Lionel Basdevant (Criteo) joined.
-
Tawanda Brandon Sibanda (Snake Nation) joined.
-
-
5 participants left.
-
Diana Pauliks (Discover Financial Services LLC) left.
-
John Carrier (International Forecourt Standards Forum) left.
-
Ian Brown (International Forecourt Standards Forum) left.
-
Florent Lambert (Lyra Network) left.
-
Alexandre Fournier (Lyra Network) left.
-
-
1 organization joined.
-
Snake Nation joined.
-
-
2 organizations left.
-
International Forecourt Standards Forum left.
-
Lyra Network left.
-
GitHub
w3c/secure-payment-confirmation
-
1 issue opened.
-
Proposal: Enhancement - Opt-out link w3c/secure-payment-confirmation#172, by @jcemer-stripe.
-
-
3 issues received 5 new comments.
-
Should SPC allow for a failed download of the payment instrument icon? w3c/secure-payment-confirmation#125 (3 comments by @jcemer-stripe, @stephenmcgruer)
-
Clarification on requiring user activation for credential creation in cross-origin iframes to mitigation cross-site tracking w3c/secure-payment-confirmation#128 (1 comment by @ianbjacobs)
-
-
1 pull request opened.
-
Add option to allow instrument icon download fail w3c/secure-payment-confirmation#171, by @nickburris.
-
-
1 pull request received 14 new comments.
-
Add option to allow instrument icon download fail w3c/secure-payment-confirmation#171 (14 comments by @ianbjacobs, @nickburris, @rlin1, @stephenmcgruer)
-
w3c/webpayments
-
1 pull request opened.
-
Add SRC user recognition use case w3c/webpayments#260, by @ianbjacobs.
-
-
1 pull request received 9 new comments.
-
Add SRC user recognition use case w3c/webpayments#260 (9 comments by @ianbjacobs, @stephenmcgruer, @tblachowicz)
-
w3c/payment-request
-
1 issue received 11 new comments.
-
Allow custom data for the active payment method to be provided to `PaymentResponse.prototype.complete` w3c/payment-request#981 (11 comments by @cyberphone, @dcrousso, @marcoscaceres, @nickjshearer)
-
-
1 pull request opened.
-
passing data on complete() w3c/payment-request#982, by @marcoscaceres.
-
-
1 pull request merged.
-
Add internationalization support for human readable labels w3c/payment-request#971.
-
-
1 pull request received 3 new comments.