Web Payments Working Group - Activity in 2025
No matches.
TR publications
-
1 document published.
-
Secure Payment Confirmation published as a Candidate Recommendation Draft. History of Secure Payment Confirmation
-
Past meetings
GitHub
w3c/web-based-payment-handler
-
1 issue opened.
-
Webview Meta support Payment Request/Handler API? w3c/web-based-payment-handler#424, by @AdaltonLeite.
-
w3c/secure-payment-confirmation
-
2 issues received 4 new comments.
-
Proposal: Extending Payment Confirmation experience to include line items w3c/secure-payment-confirmation#313 (2 comments by @stephenmcgruer, @vthub)
-
Proposal: Leveraging FIDO User Verification Index (UVI) as a Cross-Browser PSD2 "Possession Factor" for Passkeys w3c/secure-payment-confirmation#306 (2 comments by @ianbjacobs, @iinuwa)
-
-
1 pull request opened.
-
Update for 18 Aug 2025 process w3c/secure-payment-confirmation#318, by @ianbjacobs.
-
-
2 pull requests merged.
-
Update for 18 Aug 2025 process w3c/secure-payment-confirmation#318.
-
Introduce UX guidelines documentation w3c/secure-payment-confirmation#311.
-
-
1 pull request received 3 new comments.
-
Introduce UX guidelines documentation w3c/secure-payment-confirmation#311 (3 comments by @ianbjacobs, @stephenmcgruer)
-
w3c/payment-request
-
1 issue received 1 new comment.
-
Distinguish between user aborting and handler errors w3c/payment-request#1040 (1 comment by @stephenmcgruer)
-
Past meetings
Participants
-
1 participant joined.
-
Isaiah Inuwa (Bitwarden) joined.
-
-
1 organization joined.
-
Bitwarden joined.
-
GitHub
w3c/payment-request
-
1 issue opened.
-
Support for DPC "instrument" in Payment Request w3c/payment-request#1051, by @jcayzac.
-
-
3 issues received 10 new comments.
-
Distinguish between user aborting and handler errors w3c/payment-request#1040 (5 comments by @ianbjacobs, @stephenmcgruer)
-
Are integer values for PaymentCurrencyAmount.value left as integers? w3c/payment-request#624 (3 comments by @cyberphone, @marcoscaceres, @tomayac)
-
Support for DPC "instrument" in Payment Request w3c/payment-request#1051 (2 comments by @ianbjacobs, @tblachowicz)
-
-
1 pull request opened.
-
Allow payment handlers to report back errors via Payment Request API w3c/payment-request#1050, by @stephenmcgruer.
-
w3c/secure-payment-confirmation
-
1 issue opened.
-
Double authentication in Click To Pay checkout w3c/secure-payment-confirmation#317, by @tblachowicz.
-
-
7 issues received 11 new comments.
-
Backup of the payment bit should be defined in SPC spec w3c/secure-payment-confirmation#278 (3 comments by @ianbjacobs, @stephenmcgruer)
-
SPC for Recurring payments w3c/secure-payment-confirmation#185 (2 comments by @stephenmcgruer, @tblachowicz)
-
Proposal: Extending Payment Confirmation experience to include line items w3c/secure-payment-confirmation#313 (2 comments by @stephenmcgruer, @tblachowicz)
-
Support for multiple RPs in the Payment Request API for SPC w3c/secure-payment-confirmation#310 (1 comment by @stephenmcgruer)
-
Ameliorate the need for re-authentication upon re-creating BBKs w3c/secure-payment-confirmation#287 (1 comment by @stephenmcgruer)
-
Double-authentication problem when BBK not available w3c/secure-payment-confirmation#315 (1 comment by @stephenmcgruer)
-
Regarding support for BBK feature detection w3c/secure-payment-confirmation#290 (1 comment by @stephenmcgruer)
-
Past meetings
Participants
-
1 participant joined.
-
Darwin Yang (Google LLC) joined.
-
GitHub
w3c/secure-payment-confirmation
-
1 issue opened.
-
Double-authentication problem when BBK not available w3c/secure-payment-confirmation#315, by @tblachowicz.
-
-
3 issues received 4 new comments.
-
Could cards be authenticators for SPC (or WebAuthn)? w3c/secure-payment-confirmation#276 (2 comments by @aschGHub, @ianbjacobs)
-
Proposal: Extending Payment Confirmation experience to include line items w3c/secure-payment-confirmation#313 (1 comment by @tblachowicz)
-
w3c/payment-request
-
1 issue opened.
-
Browser autofill unavailable for payment apps w3c/payment-request#1049, by @dtjones404.
-
-
2 issues received 5 new comments.
-
Browser autofill unavailable for payment apps w3c/payment-request#1049 (4 comments by @dtjones404, @gregjopa, @ianbjacobs, @stephenmcgruer)
-
Distinguish between user aborting and handler errors w3c/payment-request#1040 (1 comment by @mountainhippo)
-
TR publications
-
2 documents published.
-
Payment Request API published as a Candidate Recommendation Draft. History of Payment Request API
-
Payment Handler API published as a Working Draft. History of Payment Handler API
-
Past meetings
-
1 meeting.
Participants
-
1 chair stepped down.
-
Praveena Subrahmanyam stepped down as a chair.
-
-
13 participants joined.
-
Tommaso De Orchi (Futurae Technologies AG) joined.
-
Srdjan Marinvoic (Futurae Technologies AG) joined.
-
Spyros Vlachos (Futurae Technologies AG) joined.
-
Andrew Comminos (Meta) joined.
-
James Andersen (Meta) joined.
-
Benjamin Kelly (Meta) joined.
-
Cathy Li (Meta) joined.
-
Ehsan Toreini (Samsung Electronics Co., Ltd.) joined.
-
GandhiKishor Addanki (Samsung Electronics Co., Ltd.) joined.
-
Mahesh Kulkarni (Samsung Electronics Co., Ltd.) joined.
-
Laszlo Gombos (Samsung Electronics Co., Ltd.) joined.
-
Dongwoo Joshua Im (Samsung Electronics Co., Ltd.) joined.
-
Aneesh Ali Nainamvalappil Cheriyakath (Google LLC) joined.
-
-
23 participants left.
-
Spyros Vlachos (Futurae Technologies AG) left.
-
Ehsan Toreini (Samsung Electronics Co., Ltd.) left.
-
Benjamin Kelly (Meta) left.
-
Heather Flanagan (Spherical Cow Consulting) left.
-
Cathy Li (Meta) left.
-
Sam Tang (Airbnb Inc) left.
-
Praveena Subrahmanyam (Airbnb Inc) left.
-
Jorge Barboza (Airbnb Inc) left.
-
Claire Thompson (Airbnb Inc) left.
-
Yun Cho (Airbnb Inc) left.
-
Bryan Luo (Amazon) left.
-
Wanli Yang (Airbnb Inc) left.
-
GandhiKishor Addanki (Samsung Electronics Co., Ltd.) left.
-
Mahesh Kulkarni (Samsung Electronics Co., Ltd.) left.
-
Laszlo Gombos (Samsung Electronics Co., Ltd.) left.
-
Dongwoo Joshua Im (Samsung Electronics Co., Ltd.) left.
-
Linda Toth (Conexxus) left.
-
David Ezell (Conexxus) left.
-
Jean-Yves ROSSI (CANTON CONSULTING) left.
-
Adrian Hope-Bailie (W3C Invited Experts) left.
-
Nicholas Burris (Google LLC) left.
-
Sahel Sharify (Google LLC) left.
-
JAYADEVI NATARAJAN (PayPal) left.
-
-
7 organizations joined.
-
Meta joined.
-
Samsung Electronics Co., Ltd. joined.
-
Spherical Cow Consulting joined.
-
Capital One Discover Network joined.
-
Apple Inc. joined.
-
PayPal joined.
-
Ignite Retail Technology joined.
-
GitHub
w3c/payment-request
-
1 issue closed.
-
Question about Api request in android app w3c/payment-request#1044.
-
-
2 issues received 6 new comments.
-
Distinguish between user aborting and handler errors w3c/payment-request#1040 (5 comments by @dtjones404, @ianbjacobs, @marcoscaceres)
-
-
1 pull request opened.
-
Updating spec editors w3c/payment-request#1048, by @rsolomakhin.
-
-
1 pull request merged.
-
Updating spec editors w3c/payment-request#1048.
-
-
1 pull request received 4 new comments.
-
Updating spec editors w3c/payment-request#1048 (4 comments by @marcoscaceres, @rsolomakhin, @stephenmcgruer)
-
w3c/web-based-payment-handler
-
1 pull request opened.
-
Updating spec owners w3c/web-based-payment-handler#423, by @rsolomakhin.
-
-
1 pull request merged.
-
Updating spec owners w3c/web-based-payment-handler#423.
-
-
1 pull request received 8 new comments.
-
Updating spec owners w3c/web-based-payment-handler#423 (8 comments by @ianbjacobs, @romandev, @rsolomakhin)
-
w3c/payment-method-manifest
-
1 pull request opened.
-
Updating spec editors w3c/payment-method-manifest#49, by @rsolomakhin.
-
-
1 pull request merged.
-
Updating spec editors w3c/payment-method-manifest#49.
-
-
1 pull request received 1 new comment.
w3c/secure-payment-confirmation
-
1 issue received 2 new comments.
-
Ameliorate the need for re-authentication upon re-creating BBKs w3c/secure-payment-confirmation#287 (2 comments by @dpelegero-rpgc, @stephenmcgruer)
-
-
1 pull request opened.
-
Update spec editors w3c/secure-payment-confirmation#314, by @rsolomakhin.
-
-
1 pull request merged.
-
Update spec editors w3c/secure-payment-confirmation#314.
-
-
2 pull requests received 6 new comments.
-
Introduce UX guidelines documentation w3c/secure-payment-confirmation#311 (5 comments by @stephenmcgruer)
-
TR publications
-
4 documents published.
-
Payment Request API published twice as a Candidate Recommendation Draft. History of Payment Request API
-
Secure Payment Confirmation published twice as a Candidate Recommendation Draft. History of Secure Payment Confirmation
-
Past meetings
Participants
-
10 participants joined.
-
Sami Tikkala (Visa) joined.
-
Sid Vishnoi (Interledger Foundation) joined.
-
Alan Wang (Mastercard Incorporated) joined.
-
Vivian Lee (American Express Company) joined.
-
Ashwany Rayu (JCB CO., LTD.) joined.
-
Daniel Wyckoff (Shopify) joined.
-
Zandré van Heerden (Entersekt) joined.
-
Johan de Swardt (Entersekt) joined.
-
Frederik Mennes (OneSpan) joined.
-
Yannick SEVEANT (FIME) joined.
-
-
7 participants left.
-
Juliana Cafik (Microsoft Corporation) left.
-
Christian Aabye (Visa) left.
-
Douglas Fisher (Visa) left.
-
Holger Kunkat (Mastercard Incorporated) left.
-
Laura Townsend (Merchant Advisory Group) left.
-
Imran Ahmed (Entersekt) left.
-
Vesa Parkkinen (Entersekt) left.
-
-
19 organizations joined.
-
CRITAC joined.
-
Yubico joined.
-
Google LLC joined.
-
Futurae Technologies AG joined.
-
Visa joined.
-
Interledger Foundation joined.
-
Retail Payments Global Consulting Group joined.
-
Netflix Inc. joined.
-
Discover Financial Services LLC joined.
-
1Password joined.
-
Mastercard Incorporated joined.
-
Merchant Advisory Group joined.
-
Netcetera joined.
-
JCB CO., LTD. joined.
-
Block, Inc. joined.
-
Shopify joined.
-
Entersekt joined.
-
OneSpan joined.
-
Rakuten Group, Inc. joined.
-
GitHub
w3c/secure-payment-confirmation
-
2 issues opened.
-
Proposal: Extending Payment Confirmation experience to include line items w3c/secure-payment-confirmation#313, by @vthub.
-
Seeking input on prioritization of increased support for authenticators that can be used with SPC w3c/secure-payment-confirmation#312, by @ianbjacobs.
-
-
2 issues received 3 new comments.
-
Non-normative UX guidelines for implementors and integrators w3c/secure-payment-confirmation#309 (2 comments by @stephenmcgruer)
-
Proposal: Extending Payment Confirmation experience to include line items w3c/secure-payment-confirmation#313 (1 comment by @ianbjacobs)
-
-
1 pull request opened.
-
Introduce UX guidelines documentation w3c/secure-payment-confirmation#311, by @stephenmcgruer.
-
-
1 pull request received 44 new comments.
-
Introduce UX guidelines documentation w3c/secure-payment-confirmation#311 (44 comments by @ianbjacobs, @raginpirate, @stephenmcgruer)
-
w3c/payment-request
-
1 pull request opened.
-
Update README.md w3c/payment-request#1047, by @ianbjacobs.
-
-
1 pull request merged.
-
Update README.md w3c/payment-request#1047.
-
Lifecycle
-
1 charter started.
-
Chartered until 31 July 2027. Participants had to rejoin under this charter.
-
TR publications
-
1 document published.
-
Secure Payment Confirmation published as a Candidate Recommendation Draft. History of Secure Payment Confirmation
-
Past meetings
Participants
-
2 participants joined.
-
Daniel Pelegero (Retail Payments Global Consulting Group) joined.
-
Gurpreet Kaur Mangera (Rakuten Group, Inc.) joined.
-
-
6 participants left.
-
Clinton Allen (American Express Company) left.
-
Yannick SEVEANT (FIME) left.
-
Joel DI MANNO (FIME) left.
-
Jean Fang (FIME) left.
-
Vincent Kuntz (ISO 20022 Registration Authority) left.
-
Kris Ketels (ISO 20022 Registration Authority) left.
-
-
3 organizations joined.
-
American Express Company joined.
-
FIME joined.
-
Retail Payments Global Consulting Group joined.
-
-
34 organizations left.
-
Retail Payments Global Consulting Group left.
-
Spherical Cow Consulting left.
-
Capital One Discover Network left.
-
CRITAC left.
-
Meta left.
-
1Password left.
-
Ignite Retail Technology left.
-
Netcetera left.
-
Block, Inc. left.
-
PayPal left.
-
Microsoft Corporation left.
-
Interledger Foundation left.
-
CANTON CONSULTING left.
-
Apple Inc. left.
-
Ministry of Digital Affairs, Taiwan left.
-
Airbnb Inc left.
-
Netflix Inc. left.
-
Samsung Electronics Co., Ltd. left.
-
Conexxus left.
-
Yubico left.
-
OneSpan left.
-
Amazon left.
-
Merchant Advisory Group left.
-
Shopify left.
-
American Express Company left.
-
Mastercard Incorporated left.
-
Rakuten Group, Inc. left.
-
JCB CO., LTD. left.
-
Google LLC left.
-
Visa left.
-
Entersekt left.
-
Discover Financial Services LLC left.
-
FIME left.
-
ISO 20022 Registration Authority left.
-
GitHub
w3c/secure-payment-confirmation
-
4 issues opened.
-
Support for multiple RPs in the Payment Request API for SPC w3c/secure-payment-confirmation#310, by @fahads9.
-
Non-normative UX guidelines for implementors and integrators w3c/secure-payment-confirmation#309, by @stephenmcgruer.
-
Spec: Fetch images with the context of the PaymentRequest w3c/secure-payment-confirmation#307, by @pejic.
-
Proposal: Leveraging FIDO User Verification Index (UVI) as a Cross-Browser PSD2 "Possession Factor" for Passkeys w3c/secure-payment-confirmation#306, by @JeanDim.
-
-
5 issues closed.
-
Define members in the IDL (not separately) w3c/secure-payment-confirmation#302.
-
Impact of passkeys on SPC (formerly synced credentials) w3c/secure-payment-confirmation#174.
-
Is it possible for a user to downgrade a credential creation request? w3c/secure-payment-confirmation#154.
-
UX behavior when there are no matching credentials w3c/secure-payment-confirmation#98.
-
Using CredentialsContainer.get() instead of Payment Request API w3c/secure-payment-confirmation#56.
-
-
10 issues received 22 new comments.
-
Ameliorate the need for re-authentication upon re-creating BBKs w3c/secure-payment-confirmation#287 (9 comments by @ianbjacobs, @pejic, @stephenmcgruer)
-
Support for multiple RPs in the Payment Request API for SPC w3c/secure-payment-confirmation#310 (3 comments by @stephenmcgruer, @tblachowicz)
-
Define members in the IDL (not separately) w3c/secure-payment-confirmation#302 (2 comments by @pejic, @stephenmcgruer)
-
Using CredentialsContainer.get() instead of Payment Request API w3c/secure-payment-confirmation#56 (2 comments by @ianbjacobs)
-
Non-normative UX guidelines for implementors and integrators w3c/secure-payment-confirmation#309 (1 comment by @stephenmcgruer)
-
Impact of passkeys on SPC (formerly synced credentials) w3c/secure-payment-confirmation#174 (1 comment by @ianbjacobs)
-
Is it possible for a user to downgrade a credential creation request? w3c/secure-payment-confirmation#154 (1 comment by @ianbjacobs)
-
UX behavior when there are no matching credentials w3c/secure-payment-confirmation#98 (1 comment by @ianbjacobs)
-
Proposal: Leveraging FIDO User Verification Index (UVI) as a Cross-Browser PSD2 "Possession Factor" for Passkeys w3c/secure-payment-confirmation#306 (1 comment by @ianbjacobs)
-
Should SPC be limited to passkeys with the payment bit set? w3c/secure-payment-confirmation#299 (1 comment by @ianbjacobs)
-
-
2 pull requests opened.
-
Add wpt tests for browser bound keys and auth another way. w3c/secure-payment-confirmation#308, by @pejic.
-
บอยCreate SECURITY.md w3c/secure-payment-confirmation#305, by @kritsana841300.
-
-
2 pull requests merged.
-
Rely on the IDL definitions for dictionary members. w3c/secure-payment-confirmation#304.
-
Add wpt tests for browser bound keys and auth another way. w3c/secure-payment-confirmation#308.
-
-
1 pull request closed.
-
บอยCreate SECURITY.md w3c/secure-payment-confirmation#305.
-
-
3 pull requests received 10 new comments.
-
Rely on the IDL definitions for dictionary members. w3c/secure-payment-confirmation#304 (7 comments by @pejic, @stephenmcgruer)
-
Add wpt tests for browser bound keys and auth another way. w3c/secure-payment-confirmation#308 (2 comments by @pejic, @stephenmcgruer)
-
Add browser binding to the secure payment confirmation spec w3c/secure-payment-confirmation#286 (1 comment by @stephenmcgruer)
-
w3c/payment-method-manifest
-
1 pull request opened.
-
Update the specification to use HTTP HEAD instead of HTTP GET w3c/payment-method-manifest#48, by @rsolomakhin.
-
-
1 pull request merged.
-
Update the specification to use HTTP HEAD instead of HTTP GET w3c/payment-method-manifest#48.
-
-
1 pull request received 3 new comments.
-
Update the specification to use HTTP HEAD instead of HTTP GET w3c/payment-method-manifest#48 (3 comments by @rsolomakhin, @stephenmcgruer)
-
TR publications
-
5 documents published.
-
Secure Payment Confirmation published 5 times as a Candidate Recommendation Draft. History of Secure Payment Confirmation
-
Past meetings
Participants
-
1 participant joined.
-
Desigan Chinniah (Interledger Foundation) joined.
-
-
3 participants left.
-
Bill Collins (Discover Financial Services LLC) left.
-
Fawad Nisar (Discover Financial Services LLC) left.
-
Ramesh Gorintla (Discover Financial Services LLC) left.
-
GitHub
w3c/secure-payment-confirmation
-
1 issue opened.
-
Define members in the IDL (not separately) w3c/secure-payment-confirmation#302, by @pejic.
-
-
5 issues closed.
-
Add issuer and payment system logos to transaction dialog w3c/secure-payment-confirmation#197.
-
Implementing a time out for fallback UX w3c/secure-payment-confirmation#254.
-
Request to increase icon size w3c/secure-payment-confirmation#184.
-
Broken links in Secure Payment Confirmation w3c/secure-payment-confirmation#301.
-
Proposal: WebAuthn-agnostic browser binding for Secure Payment Confirmation w3c/secure-payment-confirmation#271.
-
-
8 issues received 13 new comments.
-
Define members in the IDL (not separately) w3c/secure-payment-confirmation#302 (4 comments by @domfarolino, @pejic)
-
Proposal: WebAuthn-agnostic browser binding for Secure Payment Confirmation w3c/secure-payment-confirmation#271 (2 comments by @ianbjacobs, @stephenmcgruer)
-
Should SPC be limited to passkeys with the payment bit set? w3c/secure-payment-confirmation#299 (2 comments by @ianbjacobs, @ve7jtb)
-
Add issuer and payment system logos to transaction dialog w3c/secure-payment-confirmation#197 (1 comment by @stephenmcgruer)
-
Implementing a time out for fallback UX w3c/secure-payment-confirmation#254 (1 comment by @stephenmcgruer)
-
UX behavior when there are no matching credentials w3c/secure-payment-confirmation#98 (1 comment by @ianbjacobs)
-
URL handling for icons/logos should only allow `https`, `http`, and `data` URLs w3c/secure-payment-confirmation#300 (1 comment by @ianbjacobs)
-
-
2 pull requests opened.
-
Rely on the IDL definitions for dictionary members. w3c/secure-payment-confirmation#304, by @pejic.
-
[Editorial] Fix broken link w3c/secure-payment-confirmation#303, by @ianbjacobs.
-
-
4 pull requests merged.
-
[Editorial] Fix broken link w3c/secure-payment-confirmation#303.
-
[Spec] Add support for a 'details' string for PaymentCredentialInstrument w3c/secure-payment-confirmation#298.
-
[Spec] Add browser bound keys privacy and security considerations. w3c/secure-payment-confirmation#296.
-
Add browser binding to the secure payment confirmation spec w3c/secure-payment-confirmation#286.
-
-
3 pull requests received 39 new comments.
-
Add browser binding to the secure payment confirmation spec w3c/secure-payment-confirmation#286 (29 comments by @domfarolino, @pejic)
-
Rely on the IDL definitions for dictionary members. w3c/secure-payment-confirmation#304 (6 comments by @ianbjacobs, @pejic, @stephenmcgruer, @tabatkins)
-
[Spec] Add support for a 'details' string for PaymentCredentialInstrument w3c/secure-payment-confirmation#298 (4 comments by @pejic, @stephenmcgruer)
-
w3c/payment-request
-
1 issue received 1 new comment.
TR publications
-
7 documents published.
-
Secure Payment Confirmation published 7 times as a Candidate Recommendation Draft. History of Secure Payment Confirmation
-
Past meetings
Participants
-
5 participants joined.
-
Amit Trivedi (Capital One Discover Network) joined.
-
Shunsuke Oka (Rakuten Group, Inc.) joined.
-
Shuji Nomura (JCB CO., LTD.) joined.
-
Hirotsugu Harada (JCB CO., LTD.) joined.
-
Ehsan Toreini (Samsung Electronics Co., Ltd.) joined.
-
GitHub
w3c/secure-payment-confirmation
-
3 issues opened.
-
Broken links in Secure Payment Confirmation w3c/secure-payment-confirmation#301, by @dontcallmedom-bot.
-
URL handling for icons/logos should only allow `https`, `http`, and `data` URLs w3c/secure-payment-confirmation#300, by @stephenmcgruer.
-
Should SPC be limited to passkeys with the payment bit set? w3c/secure-payment-confirmation#299, by @ianbjacobs.
-
-
1 issue closed.
-
Proposal: Expanding output states for SPC w3c/secure-payment-confirmation#275.
-
-
1 issue received 6 new comments.
-
Add issuer and payment system logos to transaction dialog w3c/secure-payment-confirmation#197 (6 comments by @darwinlyang, @Goosth, @ianbjacobs, @stephenmcgruer)
-
-
8 pull requests opened.
-
[Spec] Add support for a 'details' string for PaymentCredentialInstrument w3c/secure-payment-confirmation#298, by @stephenmcgruer.
-
Add the TAG security and privacy self-review questionnaire for BBKs. w3c/secure-payment-confirmation#297, by @pejic.
-
[Spec] Add browser bound keys privacy and security considerations. w3c/secure-payment-confirmation#296, by @pejic.
-
[Spec] Avoid using `.com` domains in code/description examples w3c/secure-payment-confirmation#295, by @stephenmcgruer.
-
[Spec] Add support for displaying logos from facilitating payment entities w3c/secure-payment-confirmation#294, by @stephenmcgruer.
-
Adjustments to BBK requirements w3c/secure-payment-confirmation#293, by @ianbjacobs.
-
[Spec] Introduce additional output states w3c/secure-payment-confirmation#292, by @stephenmcgruer.
-
[Spec] Un-nest section 4 (Authentication) w3c/secure-payment-confirmation#291, by @stephenmcgruer.
-
-
6 pull requests merged.
-
Add the TAG security and privacy self-review questionnaire for BBKs. w3c/secure-payment-confirmation#297.
-
[Spec] Add support for displaying logos from facilitating payment entities w3c/secure-payment-confirmation#294.
-
Adjustments to BBK requirements w3c/secure-payment-confirmation#293.
-
[Spec] Introduce additional output states w3c/secure-payment-confirmation#292.
-
[Spec] Avoid using `.com` domains in code/description examples w3c/secure-payment-confirmation#295.
-
[Spec] Un-nest section 4 (Authentication) w3c/secure-payment-confirmation#291.
-
-
8 pull requests received 165 new comments.
-
[Spec] Add support for displaying logos from facilitating payment entities w3c/secure-payment-confirmation#294 (47 comments by @darwinlyang, @iadawn, @ianbjacobs, @pejic, @rsolomakhin, @stephenmcgruer)
-
Add browser binding to the secure payment confirmation spec w3c/secure-payment-confirmation#286 (42 comments by @domfarolino, @pejic)
-
Adjustments to BBK requirements w3c/secure-payment-confirmation#293 (20 comments by @Goosth, @ianbjacobs, @pejic)
-
[Spec] Add browser bound keys privacy and security considerations. w3c/secure-payment-confirmation#296 (19 comments by @ianbjacobs, @pejic, @stephenmcgruer)
-
Add the TAG security and privacy self-review questionnaire for BBKs. w3c/secure-payment-confirmation#297 (15 comments by @ianbjacobs, @pejic)
-
[Spec] Introduce additional output states w3c/secure-payment-confirmation#292 (14 comments by @pejic, @stephenmcgruer)
-
[Spec] Add support for a 'details' string for PaymentCredentialInstrument w3c/secure-payment-confirmation#298 (6 comments by @ianbjacobs, @stephenmcgruer)
-
[Spec] Un-nest section 4 (Authentication) w3c/secure-payment-confirmation#291 (2 comments by @pejic, @stephenmcgruer)
-
w3c/webpayments
-
1 issue received 3 new comments.
w3c/web-based-payment-handler
-
1 issue opened.
-
Issue with canMakePayment Returning False on Android Device in Chrome w3c/web-based-payment-handler#422, by @AdaltonLeite.
-
-
1 issue closed.
-
Issue with canMakePayment Returning False on Android Device in Chrome w3c/web-based-payment-handler#422.
-
-
1 issue received 4 new comments.
-
Issue with canMakePayment Returning False on Android Device in Chrome w3c/web-based-payment-handler#422 (4 comments by @AdaltonLeite, @rsolomakhin)
-
w3c/payment-request
-
1 issue opened.
-
Question about Api request in android app w3c/payment-request#1044, by @AdaltonLeite.
-
-
1 issue received 5 new comments.
-
Question about Api request in android app w3c/payment-request#1044 (5 comments by @AdaltonLeite, @ianbjacobs, @rsolomakhin)
-
TR publications
-
3 documents published.
-
Secure Payment Confirmation published twice as a Candidate Recommendation Draft. History of Secure Payment Confirmation
-
Payment Request API published as a Candidate Recommendation Draft. History of Payment Request API
-
Past meetings
-
1 meeting.
Participants
-
4 participants joined.
-
Benjamin Kelly (Meta) joined.
-
Heather Flanagan (Spherical Cow Consulting) joined.
-
Afrizal Chen (Netcetera) joined.
-
Albert Schibani (Capital One Discover Network) joined.
-
-
5 participants left.
-
Karl Carter (Snake Nation) left.
-
Tawanda Brandon Sibanda (Snake Nation) left.
-
Kenneth Friedman (The Clearing House) left.
-
Dave Fortney (The Clearing House) left.
-
Jeffrey Williams (The Clearing House) left.
-
-
2 organizations joined.
-
Spherical Cow Consulting joined.
-
Capital One Discover Network joined.
-
-
2 organizations left.
-
Snake Nation left.
-
The Clearing House left.
-
GitHub
w3c/secure-payment-confirmation
-
3 issues opened.
-
Regarding support for BBK feature detection w3c/secure-payment-confirmation#290, by @ianbjacobs.
-
Specify storage type hint for browser bound keys w3c/secure-payment-confirmation#288, by @pejic.
-
Ameliorate the need for re-authentication upon re-creating BBKs w3c/secure-payment-confirmation#287, by @pejic.
-
-
1 issue closed.
-
Should/could isSecurePaymentConfirmationAvailable return an enum rather than a boolean? w3c/secure-payment-confirmation#284.
-
-
1 issue reopened.
-
UX behavior when there are no matching credentials w3c/secure-payment-confirmation#98, by @ianbjacobs.
-
-
2 issues received 2 new comments.
-
Regarding support for BBK feature detection w3c/secure-payment-confirmation#290 (1 comment by @stephenmcgruer)
-
UX behavior when there are no matching credentials w3c/secure-payment-confirmation#98 (1 comment by @ianbjacobs)
-
-
1 pull request merged.
-
[Spec] Add output enum for isSecurePaymentConfirmationAvailable and rename API w3c/secure-payment-confirmation#285.
-
-
2 pull requests received 76 new comments.
-
Add browser binding to the secure payment confirmation spec w3c/secure-payment-confirmation#286 (72 comments by @domfarolino, @ianbjacobs, @pejic, @stephenmcgruer)
-
[Spec] Add output enum for isSecurePaymentConfirmationAvailable and rename API w3c/secure-payment-confirmation#285 (4 comments by @ianbjacobs, @stephenmcgruer)
-
Past meetings
Participants
-
1 participant joined.
-
Kester Quist-Aphetsi (CRITAC) joined.
-
-
1 organization joined.
-
CRITAC joined.
-
GitHub
w3c/secure-payment-confirmation
-
2 issues received 6 new comments.
-
Proposal: WebAuthn-agnostic browser binding for Secure Payment Confirmation w3c/secure-payment-confirmation#271 (4 comments by @Croccodoyle, @ianbjacobs, @mountainhippo, @stephenmcgruer)
-
Should/could isSecurePaymentConfirmationAvailable return an enum rather than a boolean? w3c/secure-payment-confirmation#284 (2 comments by @domenic, @stephenmcgruer)
-
-
2 pull requests opened.
-
Add browser binding to the secure payment confirmation spec w3c/secure-payment-confirmation#286, by @pejic.
-
[Spec] Add output enum for isSecurePaymentConfirmationAvailable and rename API w3c/secure-payment-confirmation#285, by @stephenmcgruer.
-
-
2 pull requests received 47 new comments.
-
Add browser binding to the secure payment confirmation spec w3c/secure-payment-confirmation#286 (42 comments by @ianbjacobs, @pejic, @stephenmcgruer)
-
[Spec] Add output enum for isSecurePaymentConfirmationAvailable and rename API w3c/secure-payment-confirmation#285 (5 comments by @domenic, @ianbjacobs, @stephenmcgruer)
-
w3c/webpayments
-
1 issue received 3 new comments.
TR publications
-
1 document published.
-
Secure Payment Confirmation published as a Candidate Recommendation Draft. History of Secure Payment Confirmation
-
Past meetings
-
1 meeting.
Participants
-
2 participants joined.
-
Jeremy Weeks (Netflix Inc.) joined.
-
Cathy Li (Meta) joined.
-
-
3 participants left.
-
Giulio Andreoli (Apple Inc.) left.
-
BASTIEN LATGE (W3C Invited Experts) left.
-
Christina Hulka (W3C Invited Experts) left.
-
-
1 organization joined.
-
Meta joined.
-
GitHub
w3c/secure-payment-confirmation
-
1 issue opened.
-
Should/could isSecurePaymentConfirmationAvailable return an enum rather than a boolean? w3c/secure-payment-confirmation#284, by @stephenmcgruer.
-
-
1 issue closed.
-
Update SPC spec to reflect that credential create in cross-origin iframe is now allowed in WebAuthn w3c/secure-payment-confirmation#267.
-
-
1 issue received 6 new comments.
-
Should/could isSecurePaymentConfirmationAvailable return an enum rather than a boolean? w3c/secure-payment-confirmation#284 (6 comments by @pejic, @rsolomakhin, @stephenmcgruer)
-
-
4 pull requests opened.
-
w3c.json/data/app/com.serve.mobile-OvsZK19aa6VO7PawmiRJwA==/base.apk w3c/secure-payment-confirmation#283, by @samss084.
-
Marcoscaceres patch 1 w3c/secure-payment-confirmation#282, by @samss084.
-
[Spec] Remove references to create in cross origin iframe w3c/secure-payment-confirmation#281, by @stephenmcgruer.
-
[Spec] Separate 'SPC credential' from 'third-party enabled SPC credential' w3c/secure-payment-confirmation#280, by @stephenmcgruer.
-
-
2 pull requests merged.
-
[Spec] Remove references to create in cross origin iframe w3c/secure-payment-confirmation#281.
-
[Spec] Separate 'SPC credential' from 'third-party enabled SPC credential' w3c/secure-payment-confirmation#280.
-
-
2 pull requests closed.
-
w3c.json/data/app/com.serve.mobile-OvsZK19aa6VO7PawmiRJwA==/base.apk w3c/secure-payment-confirmation#283.
-
Marcoscaceres patch 1 w3c/secure-payment-confirmation#282.
-
-
3 pull requests received 8 new comments.
-
[Spec] Remove references to create in cross origin iframe w3c/secure-payment-confirmation#281 (4 comments by @ianbjacobs, @stephenmcgruer)
-
w3c.json/data/app/com.serve.mobile-OvsZK19aa6VO7PawmiRJwA==/base.apk w3c/secure-payment-confirmation#283 (2 comments by @rsolomakhin, @stephenmcgruer)
-
[Spec] Separate 'SPC credential' from 'third-party enabled SPC credential' w3c/secure-payment-confirmation#280 (2 comments by @ianbjacobs, @stephenmcgruer)
-
w3c/webpayments
-
1 issue opened.
-
what's the effort status? w3c/webpayments#264, by @cryptid11.
-
-
1 issue closed.
-
what's the effort status? w3c/webpayments#264.
-
-
1 issue received 1 new comment.
Past meetings
Participants
-
5 participants joined.
-
Jon Southall (PayPal) joined.
-
Mia Therese Jamili (PayPal) joined.
-
Rene Leveille (1Password) joined.
-
Max Crone (1Password) joined.
-
Nicholas Steele (1Password) joined.
-
-
7 participants left.
-
Andreas Efthymiou (Visa) left.
-
Akshaykumar Gaikwad (PayPal) left.
-
Grégoire Leleux (Worldline) left.
-
Jean-Michel GIRARD (Worldline) left.
-
Olivier Maas (Worldline) left.
-
Denis Lesieur (Worldline) left.
-
Gavin Shenker (Visa) left.
-
-
1 organization joined.
-
1Password joined.
-
-
1 organization left.
-
Worldline left.
-
GitHub
w3c/payment-request
-
1 issue opened.
-
Handling in-app shipping changes w3c/payment-request#1042, by @dtjones404.
-
-
2 issues received 6 new comments.
-
Handling in-app shipping changes w3c/payment-request#1042 (5 comments by @dtjones404, @ianbjacobs, @rsolomakhin)
-
Distinguish between user aborting and handler errors w3c/payment-request#1040 (1 comment by @rsolomakhin)
-
-
1 pull request closed.
-
3iCreate generator-generic-ossf-slsa3-publish.yml w3c/payment-request#1038.
-