Web Payments Working Group - Activity in 2026
No matches.
TR publications
-
1 document published.
-
Secure Payment Confirmation published as a Candidate Recommendation Draft. History of Secure Payment Confirmation
-
Past meetings
-
1 meeting.
Participants
-
1 participant joined.
-
Jose Javier Garza Cuartero (PayPal) joined.
-
-
1 organization left.
-
Retail Payments Global Consulting Group left.
-
GitHub
w3c/web-based-payment-handler
-
1 issue opened.
-
Proposal: Service worker-less Web-based Payment Handlers w3c/web-based-payment-handler#433, by @stephenmcgruer.
-
-
1 issue received 1 new comment.
-
Proposal: Service worker-less Web-based Payment Handlers w3c/web-based-payment-handler#433 (1 comment by @ianbjacobs)
-
-
1 pull request opened.
-
Allow web-based payment handlers to reject with PaymentHandlerAppError w3c/web-based-payment-handler#432, by @stephenmcgruer.
-
w3c/secure-payment-confirmation
-
1 pull request merged.
-
Update the Specification for Locale Validation w3c/secure-payment-confirmation#345.
-
-
1 pull request received 10 new comments.
-
Update the Specification for Locale Validation w3c/secure-payment-confirmation#345 (10 comments by @darwinlyang, @ianbjacobs, @stephenmcgruer)
-
w3c/payment-request
-
2 issues received 4 new comments.
-
Proposal: Structured Payment Handler Errors via a DOMException-Derived Interface w3c/payment-request#1076 (3 comments by @ianbjacobs, @stephenmcgruer)
-
Allow a payment handler to request a larger initial window size w3c/payment-request#1075 (1 comment by @stephenmcgruer)
-
-
1 pull request opened.
-
Add PaymentHandlerAppError interface for structured handler errors w3c/payment-request#1078, by @stephenmcgruer.
-
TR publications
-
1 document published.
-
Web-based Payment Handler API published as a Working Draft. History of Web-based Payment Handler API
-
Past meetings
-
1 meeting.
Participants
-
4 participants joined.
-
Divyarani Raghupatruni (W3C Invited Experts) joined.
-
Daniel Pelegero (Capital One Discover Network) joined.
-
Michael Kohler (Interledger Foundation) joined.
-
Jorge Vargas (Capital One Discover Network) joined.
-
GitHub
w3c/web-based-payment-handler
-
1 issue opened.
-
Remove "*" functionality for supported_origins w3c/web-based-payment-handler#430, by @stephenmcgruer.
-
-
1 issue closed.
-
Remove "*" functionality for supported_origins w3c/web-based-payment-handler#430.
-
-
1 pull request opened.
-
Remove reference to "*" for supported_origins w3c/web-based-payment-handler#431, by @stephenmcgruer.
-
-
1 pull request merged.
-
Remove reference to "*" for supported_origins w3c/web-based-payment-handler#431.
-
w3c/payment-request
-
1 issue opened.
-
Allow payment handlers to invoke another payment handler w3c/payment-request#1077, by @raginpirate.
-
-
1 issue closed.
-
How can the Privacy Sandbox affect the payment request API? w3c/payment-request#1034.
-
-
3 issues received 7 new comments.
-
Allow a payment handler to request a larger initial window size w3c/payment-request#1075 (3 comments by @dtjones404, @raginpirate, @stephenmcgruer)
-
Proposal: Structured Payment Handler Errors via a DOMException-Derived Interface w3c/payment-request#1076 (2 comments by @dtjones404, @ianbjacobs)
-
How can the Privacy Sandbox affect the payment request API? w3c/payment-request#1034 (2 comments by @ianbjacobs, @stephenmcgruer)
-
w3c/secure-payment-confirmation
-
2 issues opened.
-
Enhanced SPC targeting the EU Digital Identity Wallet w3c/secure-payment-confirmation#346, by @cyberphone.
-
Should we add the Payment Request id to the signed SPC data (to facilitate connection between authentication and transaction)? w3c/secure-payment-confirmation#344, by @ianbjacobs.
-
-
1 issue received 1 new comment.
-
[spec] SPC Locale Field to Return Error on Language Mismatch w3c/secure-payment-confirmation#343 (1 comment by @darwinlyang)
-
-
1 pull request opened.
-
Update the Specification for Locale Validation w3c/secure-payment-confirmation#345, by @darwinlyang.
-
-
1 pull request received 21 new comments.
-
Update the Specification for Locale Validation w3c/secure-payment-confirmation#345 (21 comments by @darwinlyang, @ianbjacobs, @stephenmcgruer)
-
Past meetings
-
1 meeting.
Participants
-
5 participants joined.
-
Sabine Schaller (Interledger Foundation) joined.
-
Patryk Les (Yubico) joined.
-
Olvis Enrique Gil Ríos (W3C Invited Experts) joined.
-
Vaishnavi T Srinivasan (Apple Inc.) joined.
-
Westin Wrzesinski (Shopify) joined.
-
GitHub
w3c/payment-request
-
2 issues opened.
-
Proposal: Structured Payment Handler Errors via a DOMException-Derived Interface w3c/payment-request#1076, by @stephenmcgruer.
-
Allow a payment handler to request a larger initial window size w3c/payment-request#1075, by @dtjones404.
-
-
3 issues received 12 new comments.
-
Allow a payment handler to request a larger initial window size w3c/payment-request#1075 (5 comments by @dtjones404, @ianbjacobs, @stephenmcgruer)
-
Proposal: Structured Payment Handler Errors via a DOMException-Derived Interface w3c/payment-request#1076 (4 comments by @ianbjacobs, @stephenmcgruer)
-
Distinguish between user aborting and handler errors w3c/payment-request#1040 (3 comments by @dtjones404, @ianbjacobs, @stephenmcgruer)
-
w3c/secure-payment-confirmation
-
3 issues opened.
-
[spec] SPC Locale Field to Return Error on Language Mismatch w3c/secure-payment-confirmation#343, by @darwinlyang.
-
add w3c/secure-payment-confirmation#342, by @Vargas1205.
-
, w3c/secure-payment-confirmation#341, by @Vargas1205.
-
-
3 issues closed.
-
, w3c/secure-payment-confirmation#341.
-
add w3c/secure-payment-confirmation#342.
-
Regarding support for BBK feature detection w3c/secure-payment-confirmation#290.
-
-
4 issues received 14 new comments.
-
[spec] SPC Locale Field to Return Error on Language Mismatch w3c/secure-payment-confirmation#343 (11 comments by @aphillips, @darwinlyang, @ianbjacobs, @Jlightma, @xfq)
-
Regarding support for BBK feature detection w3c/secure-payment-confirmation#290 (1 comment by @stephenmcgruer)
-
-
3 pull requests merged.
-
Explainer for supporting connected roaming authenticators w3c/secure-payment-confirmation#338.
-
Explainer for supporting non-queryable authenticators w3c/secure-payment-confirmation#340.
-
[Editorial] Organize explainers, requirements, and explorations w3c/secure-payment-confirmation#339.
-
-
3 pull requests received 4 new comments.
-
Explainer for supporting non-queryable authenticators w3c/secure-payment-confirmation#340 (2 comments by @ianbjacobs, @stephenmcgruer)
-
Explainer for supporting connected roaming authenticators w3c/secure-payment-confirmation#338 (1 comment by @ianbjacobs)
-
Switch from 'credentialIds' to 'allowCredentials' w3c/secure-payment-confirmation#337 (1 comment by @ianbjacobs)
-
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.
-
David Worthington (Visa) joined.
-
Amit Varia (Google LLC) joined.
-
-
1 participant left.
-
Daniel Pelegero (Retail Payments Global Consulting Group) left.
-
-
1 organization left.
-
Discover Financial Services LLC left.
-
GitHub
w3c/secure-payment-confirmation
-
2 issues opened.
-
SPC should take in sequence<PublicKeyCredentialDescriptor>, not BufferSource w3c/secure-payment-confirmation#336, by @stephenmcgruer.
-
Export w3c/secure-payment-confirmation#335, by @marlouybio143-source.
-
-
3 issues closed.
-
Export w3c/secure-payment-confirmation#335.
-
[Security] SPC should disallow extensions that expose private relying party sign in data w3c/secure-payment-confirmation#326.
-
Gap between BBK requirements and specification w3c/secure-payment-confirmation#321.
-
-
3 issues received 9 new comments.
-
[Spec] SPC is overly restrictive on what constitutes "third party" w3c/secure-payment-confirmation#328 (7 comments by @davidbenoit, @ianbjacobs, @nsatragno, @stephenmcgruer)
-
Gap between BBK requirements and specification w3c/secure-payment-confirmation#321 (1 comment by @ianbjacobs)
-
-
4 pull requests opened.
-
Explainer for supporting non-queryable authenticators w3c/secure-payment-confirmation#340, by @stephenmcgruer.
-
[Editorial] Organize explainers, requirements, and explorations w3c/secure-payment-confirmation#339, by @stephenmcgruer.
-
Explainer for supporting connected roaming authenticators w3c/secure-payment-confirmation#338, by @stephenmcgruer.
-
Switch from 'credentialIds' to 'allowCredentials' w3c/secure-payment-confirmation#337, by @stephenmcgruer.
-
-
4 pull requests merged.
-
Editorial: small cleanup of examples w3c/secure-payment-confirmation#263.
-
Update from api.csswg.org/bikeshed to spec-generator w3c/secure-payment-confirmation#325.
-
Disallow webauthn extensions in cross-origin authentication ceremonies w3c/secure-payment-confirmation#332.
-
Bbk spec alignment w3c/secure-payment-confirmation#334.
-
-
1 pull request closed.
-
Update Github changelog link w3c/secure-payment-confirmation#262.
-
-
1 pull request received 1 new comment.
w3c/payment-method-manifest
-
2 pull requests opened.
-
Update build workflow and add auto-publish workflow w3c/payment-method-manifest#53, by @stephenmcgruer.
-
Allow up to 3 same-site redirects when fetching Link header w3c/payment-method-manifest#52, by @stephenmcgruer.
-
-
2 pull requests merged.
-
Allow up to 3 same-site redirects when fetching Link header w3c/payment-method-manifest#52.
-
Update build workflow and add auto-publish workflow w3c/payment-method-manifest#53.
-
-
2 pull requests received 7 new comments.
-
Allow up to 3 same-site redirects when fetching Link header w3c/payment-method-manifest#52 (5 comments by @ianbjacobs, @stephenmcgruer)
-
Update build workflow and add auto-publish workflow w3c/payment-method-manifest#53 (2 comments by @ianbjacobs, @stephenmcgruer)
-
TR publications
-
3 documents published.
-
Payment Request API published 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
-
1 meeting.
Participants
-
1 participant joined.
-
Rowan Merewood (Google LLC) joined.
-
-
6 participants left.
-
Jeff Owenson (Discover Financial Services LLC) left.
-
Jorge Vargas (Capital One Discover Network) left.
-
Leigh Garner (Discover Financial Services LLC) left.
-
Henna Kapur (Visa) left.
-
Otto Mora (Ethereum Foundation) left.
-
Padmanabhan K (PayPal) left.
-
GitHub
w3c/secure-payment-confirmation
-
1 issue opened.
-
Hj w3c/secure-payment-confirmation#333, by @vic37hu-web.
-
-
1 issue closed.
-
Hj w3c/secure-payment-confirmation#333.
-
-
3 issues received 9 new comments.
-
[Security] SPC should disallow extensions that expose private relying party sign in data w3c/secure-payment-confirmation#326 (4 comments by @John-Earnshaw, @stephenmcgruer)
-
Gap between BBK requirements and specification w3c/secure-payment-confirmation#321 (4 comments by @darwinlyang, @John-Earnshaw)
-
[Spec] SPC is overly restrictive on what constitutes "third party" w3c/secure-payment-confirmation#328 (1 comment by @ianbjacobs)
-
-
2 pull requests opened.
-
Bbk spec alignment w3c/secure-payment-confirmation#334, by @John-Earnshaw.
-
Disallow webauthn extensions in cross-origin authentication ceremonies w3c/secure-payment-confirmation#332, by @stephenmcgruer.
-
-
2 pull requests merged.
-
Bbk req update w3c/secure-payment-confirmation#330.
-
Update UX Guidelines for Payment entity logos with actual dimensions for desktop w3c/secure-payment-confirmation#331.
-
-
3 pull requests received 25 new comments.
-
Bbk spec alignment w3c/secure-payment-confirmation#334 (12 comments by @darwinlyang, @ianbjacobs, @John-Earnshaw, @pejic, @stephenmcgruer)
-
Bbk req update w3c/secure-payment-confirmation#330 (9 comments by @ianbjacobs, @John-Earnshaw, @stephenmcgruer)
-
Disallow webauthn extensions in cross-origin authentication ceremonies w3c/secure-payment-confirmation#332 (4 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)
-
-
2 pull requests opened.
-
chore: export handler algos w3c/payment-request#1074, by @marcoscaceres.
-
chore: export payment method w3c/payment-request#1073, by @marcoscaceres.
-
-
2 pull requests merged.
-
chore: export handler algos w3c/payment-request#1074.
-
chore: export payment method w3c/payment-request#1073.
-
TR publications
-
2 documents published.
-
Secure Payment Confirmation published twice as a Candidate Recommendation Draft. History of Secure Payment Confirmation
-
Past meetings
Participants
-
3 participants joined.
-
Sid Sahoo (Google LLC) joined.
-
Eliza Pancake (Ethereum Foundation) joined.
-
Otto Mora (Ethereum Foundation) joined.
-
-
1 organization joined.
-
Ethereum Foundation joined.
-
GitHub
w3c/secure-payment-confirmation
-
2 issues opened.
-
Broken links in Secure Payment Confirmation w3c/secure-payment-confirmation#329, by @dontcallmedom-bot.
-
[Spec] SPC is overly restrictive on what constitutes "third party" w3c/secure-payment-confirmation#328, by @stephenmcgruer.
-
-
1 issue closed.
-
Broken links in Secure Payment Confirmation w3c/secure-payment-confirmation#329.
-
-
1 issue reopened.
-
[Security] SPC should disallow extensions that expose private relying party sign in data w3c/secure-payment-confirmation#326, by @stephenmcgruer.
-
-
4 issues received 15 new comments.
-
Supporting roaming authenticators w3c/secure-payment-confirmation#12 (7 comments by @bhjelm-yubico, @rlin1, @stephenmcgruer)
-
Gap between BBK requirements and specification w3c/secure-payment-confirmation#321 (5 comments by @ianbjacobs, @jcayzac, @stephenmcgruer)
-
[Security] SPC should disallow extensions that expose private relying party sign in data w3c/secure-payment-confirmation#326 (2 comments by @ianbjacobs, @stephenmcgruer)
-
Should SPC be limited to passkeys with the payment bit set? w3c/secure-payment-confirmation#299 (1 comment by @aschGHub)
-
-
3 pull requests opened.
-
Update UX Guidelines for Payment entity logos with actual dimensions for desktop w3c/secure-payment-confirmation#331, by @darwinlyang.
-
Bbk req update w3c/secure-payment-confirmation#330, by @John-Earnshaw.
-
Create allowlist for webauthn extensions accessed via SPC w3c/secure-payment-confirmation#327, by @stephenmcgruer.
-
-
1 pull request merged.
-
Create allowlist for webauthn extensions accessed via SPC w3c/secure-payment-confirmation#327.
-
-
2 pull requests received 24 new comments.
-
Create allowlist for webauthn extensions accessed via SPC w3c/secure-payment-confirmation#327 (22 comments by @ianbjacobs, @nsatragno, @pejic, @stephenmcgruer)
-
Update UX Guidelines for Payment entity logos with actual dimensions for desktop w3c/secure-payment-confirmation#331 (2 comments by @darwinlyang, @stephenmcgruer)
-
w3c/payment-request
-
1 issue opened.
-
Should Payment Request API handle non-human payment flows? w3c/payment-request#1072, by @hemanth.
-
-
3 issues received 4 new comments.
-
Should Payment Request API handle non-human payment flows? w3c/payment-request#1072 (2 comments by @hemanth, @ianbjacobs)
-
Revert activation relaxation in show() -- find a general platform solution instead w3c/payment-request#1064 (1 comment by @RByers)
-
SecurityError vs NotAllowedError for "allowed to use" check w3c/payment-request#1071 (1 comment by @marcoscaceres)
-
-
1 pull request received 7 new comments.
-
fix: restore transient activation requirement in show() w3c/payment-request#1066 (7 comments by @ianbjacobs, @marcoscaceres, @RByers, @stephenmcgruer)
-
TR publications
-
1 document published.
-
Web-based Payment Handler API published as a Working Draft. History of Web-based Payment Handler API
-
Past meetings
-
1 meeting.
Participants
-
3 participants joined.
-
Dario Salice (Futurae Technologies AG) joined.
-
Tim Cappalli (Okta) joined.
-
Nikos Karapanos (Futurae Technologies AG) joined.
-
-
5 participants left.
-
Chris Wilson (Google LLC) left.
-
Tommaso De Orchi (Futurae Technologies AG) left.
-
Kester Quist-Aphetsi (CRITAC) left.
-
Nobuyoshi Seo (JCB CO., LTD.) left.
-
Tomoya Horiguchi (JCB CO., LTD.) left.
-
-
1 organization joined.
-
Okta joined.
-
-
1 organization left.
-
CRITAC left.
-
GitHub
w3c/payment-request
-
1 issue opened.
-
SecurityError vs NotAllowedError for "allowed to use" check w3c/payment-request#1071, by @zcorpan.
-
-
1 issue received 1 new comment.
-
SecurityError vs NotAllowedError for "allowed to use" check w3c/payment-request#1071 (1 comment by @stephenmcgruer)
-
-
1 pull request received 2 new comments.
-
fix: restore transient activation requirement in show() w3c/payment-request#1066 (2 comments by @marcoscaceres, @stephenmcgruer)
-
w3c/web-based-payment-handler
-
1 issue closed.
-
Allow web-based payment handlers to report back internal error via Payment Request API w3c/web-based-payment-handler#428.
-
-
1 pull request merged.
-
Allow web-based payment handlers to report back internal error w3c/web-based-payment-handler#429.
-
w3c/secure-payment-confirmation
-
2 issues received 3 new comments.
-
Gap between BBK requirements and specification w3c/secure-payment-confirmation#321 (2 comments by @darwinlyang, @John-Earnshaw)
-
[Security] SPC should disallow extensions that expose private relying party sign in data w3c/secure-payment-confirmation#326 (1 comment by @stephenmcgruer)
-
TR publications
-
8 documents published.
-
Payment Request API published 6 times 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
GitHub
w3c/secure-payment-confirmation
-
3 issues opened.
-
[Security] SPC should disallow extensions that expose private relying party sign in data w3c/secure-payment-confirmation#326, by @nsatragno.
-
Enum values that ignore naming conventions in Secure Payment Confirmation w3c/secure-payment-confirmation#322, by @dontcallmedom-bot.
-
Gap between BBK requirements and specification w3c/secure-payment-confirmation#321, by @John-Earnshaw.
-
-
4 issues closed.
-
SPC for Recurring payments w3c/secure-payment-confirmation#185.
-
SPC for non-payment use cases w3c/secure-payment-confirmation#186.
-
Should SPC be invokable outside of a PaymentRequest flow? w3c/secure-payment-confirmation#65.
-
Enum values that ignore naming conventions in Secure Payment Confirmation w3c/secure-payment-confirmation#322.
-
-
6 issues received 10 new comments.
-
Suggestion to enable Frictionless Flows w3c/secure-payment-confirmation#34 (2 comments by @ianbjacobs)
-
Gap between BBK requirements and specification w3c/secure-payment-confirmation#321 (2 comments by @ianbjacobs, @stephenmcgruer)
-
Enum values that ignore naming conventions in Secure Payment Confirmation w3c/secure-payment-confirmation#322 (2 comments by @darwinlyang, @stephenmcgruer)
-
Should SPC be invokable outside of a PaymentRequest flow? w3c/secure-payment-confirmation#65 (1 comment by @ianbjacobs)
-
-
3 pull requests opened.
-
Update from api.csswg.org/bikeshed to spec-generator w3c/secure-payment-confirmation#325, by @kfranqueiro.
-
Add an explainer for the Get SPC Capabilities API w3c/secure-payment-confirmation#324, by @darwinlyang.
-
(Editorial) With the closure of issue 65, we can remove note related to PR API w3c/secure-payment-confirmation#323, by @ianbjacobs.
-
-
3 pull requests merged.
-
(Editorial) With the closure of issue 65, we can remove note related to PR API w3c/secure-payment-confirmation#323.
-
Add an explainer for the Get SPC Capabilities API w3c/secure-payment-confirmation#324.
-
Add the SPC Capabilities API to the Spec w3c/secure-payment-confirmation#320.
-
-
1 pull request received 14 new comments.
-
Add an explainer for the Get SPC Capabilities API w3c/secure-payment-confirmation#324 (14 comments by @ianbjacobs, @stephenmcgruer)
-
w3c/payment-request
-
4 issues opened.
-
Revert activation relaxation in show() -- find a general platform solution instead w3c/payment-request#1064, by @marcoscaceres.
-
Clearer interaction state algorithms w3c/payment-request#1060, by @marcoscaceres.
-
Can we delete the Feature-Policy tests? w3c/payment-request#1058, by @marcoscaceres.
-
Over-reliance on AbortError w3c/payment-request#1057, by @marcoscaceres.
-
-
4 issues closed.
-
Can we delete the Feature-Policy tests? w3c/payment-request#1058.
-
Distinguish between user aborting and handler errors w3c/payment-request#1040.
-
Handling in-app shipping changes w3c/payment-request#1042.
-
Browser autofill unavailable for payment apps w3c/payment-request#1049.
-
-
5 issues received 10 new comments.
-
Distinguish between user aborting and handler errors w3c/payment-request#1040 (4 comments by @dtjones404, @marcoscaceres, @stephenmcgruer)
-
Can we delete the Feature-Policy tests? w3c/payment-request#1058 (2 comments by @marcoscaceres, @stephenmcgruer)
-
Browser autofill unavailable for payment apps w3c/payment-request#1049 (2 comments by @marcoscaceres, @stephenmcgruer)
-
Revert activation relaxation in show() -- find a general platform solution instead w3c/payment-request#1064 (1 comment by @marcoscaceres)
-
-
5 pull requests opened.
-
fix: restore transient activation requirement in show() w3c/payment-request#1066, by @marcoscaceres.
-
Update index.html to remove obsolete text w3c/payment-request#1065, by @deniak.
-
[Editorial] Fix exporting of three algorithms w3c/payment-request#1061, by @stephenmcgruer.
-
fix: use InvalidStateError for non-fully-active document checks w3c/payment-request#1056, by @marcoscaceres.
-
-
4 pull requests merged.
-
Update index.html to remove obsolete text w3c/payment-request#1065.
-
fix: use InvalidStateError for non-fully-active document checks w3c/payment-request#1056.
-
[Editorial] Fix exporting of three algorithms w3c/payment-request#1061.
-
Allow payment handlers to report back errors via Payment Request API w3c/payment-request#1050.
-
-
1 pull request closed.
-
Gg w3c/payment-request#1059.
-
-
6 pull requests received 21 new comments.
-
fix: use InvalidStateError for non-fully-active document checks w3c/payment-request#1056 (10 comments by @ianbjacobs, @marcoscaceres, @stephenmcgruer)
-
Allow payment handlers to report back errors via Payment Request API w3c/payment-request#1050 (6 comments by @marcoscaceres, @stephenmcgruer)
-
fix: restore transient activation requirement in show() w3c/payment-request#1066 (2 comments by @ianbjacobs, @marcoscaceres)
-
w3c/payment-request#1063 (1 comment by @w3cbot)
-
w3c/payment-request#1062 (1 comment by @w3cbot)
-
[Editorial] Fix exporting of three algorithms w3c/payment-request#1061 (1 comment by @stephenmcgruer)
-
w3c/web-based-payment-handler
-
1 issue opened.
-
Allow web-based payment handlers to report back internal error via Payment Request API w3c/web-based-payment-handler#428, by @stephenmcgruer.
-
-
1 issue received 3 new comments.
-
Allow web-based payment handlers to report back internal error via Payment Request API w3c/web-based-payment-handler#428 (3 comments by @stephenmcgruer)
-
-
1 pull request opened.
-
Allow web-based payment handlers to report back internal error w3c/web-based-payment-handler#429, by @stephenmcgruer.
-
-
1 pull request received 7 new comments.
-
Allow web-based payment handlers to report back internal error w3c/web-based-payment-handler#429 (7 comments by @romandev, @stephenmcgruer)
-
w3c/payment-method-manifest
-
1 pull request opened.
-
Update from api.csswg.org/bikeshed to spec-generator w3c/payment-method-manifest#51, by @kfranqueiro.
-
-
1 pull request received 1 new comment.
-
Update from api.csswg.org/bikeshed to spec-generator w3c/payment-method-manifest#51 (1 comment by @w3cbot)
-
TR publications
-
2 documents published.
-
Web-based Payment Handler API published twice as a Working Draft. History of Web-based Payment Handler API
-
Past meetings
-
1 meeting.
Participants
-
2 participants joined.
-
Jean Fang (FIME) joined.
-
John Earnshaw (American Express Company) joined.
-
GitHub
w3c/secure-payment-confirmation
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Add the SPC Capabilities API to the Spec w3c/secure-payment-confirmation#320, by @darwinlyang.
-
-
1 pull request received 19 new comments.
-
Add the SPC Capabilities API to the Spec w3c/secure-payment-confirmation#320 (19 comments by @darwinlyang, @ianbjacobs, @stephenmcgruer)
-
w3c/payment-request
-
1 issue received 2 new comments.
-
Distinguish between user aborting and handler errors w3c/payment-request#1040 (2 comments by @marcoscaceres, @stephenmcgruer)
-
-
1 pull request opened.
-
[Editorial] Update spec to reference web-based-payment-handler w3c/payment-request#1054, by @stephenmcgruer.
-
-
1 pull request merged.
-
[Editorial] Update spec to reference web-based-payment-handler w3c/payment-request#1054.
-
-
1 pull request received 1 new comment.
-
w3c/payment-request#1055 (1 comment by @w3cbot)
-
w3c/payment-method-manifest
-
1 pull request opened.
-
[Editorial] Update spec for rename to web-based-payment-handler w3c/payment-method-manifest#50, by @stephenmcgruer.
-
-
1 pull request merged.
-
[Editorial] Update spec for rename to web-based-payment-handler w3c/payment-method-manifest#50.
-
w3c/web-based-payment-handler
-
3 pull requests opened.
-
[Editorial] Rename 'payment handler' to 'web-based payment handler' in the spec text w3c/web-based-payment-handler#427, by @stephenmcgruer.
-
Update README.md w3c/web-based-payment-handler#426, by @stephenmcgruer.
-
Update README.md w3c/web-based-payment-handler#425, by @ianbjacobs.
-
-
3 pull requests merged.
-
[Editorial] Rename 'payment handler' to 'web-based payment handler' in the spec text w3c/web-based-payment-handler#427.
-
Update README.md w3c/web-based-payment-handler#426.
-
Update README.md w3c/web-based-payment-handler#425.
-
-
1 pull request received 5 new comments.
-
[Editorial] Rename 'payment handler' to 'web-based payment handler' in the spec text w3c/web-based-payment-handler#427 (5 comments by @ianbjacobs, @romandev, @stephenmcgruer)
-
TR publications
-
1 document published.
-
Payment Request API published as a Candidate Recommendation Draft. History of Payment Request API
-
Past meetings
Participants
-
5 participants left.
-
Lukasz Olejnik (W3C Invited Experts) left.
-
Matt Crothers (American Express Company) left.
-
Sophie Rainford (American Express Company) left.
-
Amit Trivedi (Capital One Discover Network) left.
-
Albert Schibani (Capital One Discover Network) left.
-
GitHub
w3c/payment-request
-
1 issue received 3 new comments.
-
Distinguish between user aborting and handler errors w3c/payment-request#1040 (3 comments by @marcoscaceres, @stephenmcgruer)
-
-
1 pull request opened.
-
Editorial: clarify payment-relevant browsing context definition w3c/payment-request#1052, by @webmonch.
-
-
1 pull request merged.
-
Editorial: clarify payment-relevant browsing context definition w3c/payment-request#1052.
-
-
3 pull requests received 12 new comments.
-
Allow payment handlers to report back errors via Payment Request API w3c/payment-request#1050 (8 comments by @marcoscaceres, @stephenmcgruer)
-
Editorial: clarify payment-relevant browsing context definition w3c/payment-request#1052 (3 comments by @ianbjacobs, @marcoscaceres, @w3cbot)
-
w3c/payment-request#1053 (1 comment by @w3cbot)
-
w3c/secure-payment-confirmation
-
1 issue opened.
-
Support for immediate mediation for friction-less payment with SPC (in 1PC) w3c/secure-payment-confirmation#319, by @tblachowicz.
-
-
4 issues received 9 new comments.
-
Support for immediate mediation for friction-less payment with SPC (in 1PC) w3c/secure-payment-confirmation#319 (4 comments by @kenrb, @stephenmcgruer)
-
Regarding support for BBK feature detection w3c/secure-payment-confirmation#290 (3 comments by @darwinlyang, @ianbjacobs)
-
Double authentication in Click To Pay checkout w3c/secure-payment-confirmation#317 (1 comment by @Goosth)
-
Support for multiple RPs in the Payment Request API for SPC w3c/secure-payment-confirmation#310 (1 comment by @tblachowicz)
-
w3c/web-based-payment-handler
-
1 issue closed.
-
Webview Meta support Payment Request/Handler API? w3c/web-based-payment-handler#424.
-
-
1 issue received 1 new comment.
-
Webview Meta support Payment Request/Handler API? w3c/web-based-payment-handler#424 (1 comment by @stephenmcgruer)
-