Web Payments Working Group - Activity in 2021
No matches.
Participants
-
1 participant joined.
-
Ainsley Hargest (Federal Reserve Bank of Minneapolis) joined.
-
-
1 participant left.
-
Jean Luc DI MANNO (FIME) left.
-
-
1 organization joined.
-
Federal Reserve Bank of Minneapolis joined.
-
GitHub
w3c/secure-payment-confirmation
-
3 issues opened.
-
[Spec] Registration example is misleading around whether an iframe is required w3c/secure-payment-confirmation#168, by @stephenmcgruer.
-
Selecting Bank for A2A Transactions w3c/secure-payment-confirmation#166, by @cyberphone.
-
Proposal: add Relying Party id as a required input to SPC authentication w3c/secure-payment-confirmation#164, by @stephenmcgruer.
-
-
1 issue closed.
-
Selecting Bank for A2A Transactions w3c/secure-payment-confirmation#166.
-
-
4 issues received 8 new comments.
-
Consider separating the SPC powers of Third Party invocation and Payment display w3c/secure-payment-confirmation#157 (3 comments by @ianbjacobs)
-
Proposal: add Relying Party id as a required input to SPC authentication w3c/secure-payment-confirmation#164 (2 comments by @Goosth, @stephenmcgruer)
-
Selecting Bank for A2A Transactions w3c/secure-payment-confirmation#166 (2 comments by @cyberphone, @ianbjacobs)
-
Proposal: Add `payeeName` as alternative to `payeeOrigin` w3c/secure-payment-confirmation#163 (1 comment by @ianbjacobs)
-
-
4 pull requests opened.
-
Provide high-level of UX in various failure modes w3c/secure-payment-confirmation#170, by @ianbjacobs.
-
[Misc] Update sequence diagrams for SPC w3c/secure-payment-confirmation#169, by @stephenmcgruer.
-
[Spec] Better define what an SPC credential is and its requirements w3c/secure-payment-confirmation#167, by @stephenmcgruer.
-
Add final "/" to "This version" URL w3c/secure-payment-confirmation#165, by @tidoust.
-
-
4 pull requests merged.
-
Provide high-level of UX in various failure modes w3c/secure-payment-confirmation#170.
-
[Misc] Update sequence diagrams for SPC w3c/secure-payment-confirmation#169.
-
[Spec] Better define what an SPC credential is and its requirements w3c/secure-payment-confirmation#167.
-
Add final "/" to "This version" URL w3c/secure-payment-confirmation#165.
-
-
2 pull requests received 17 new comments.
-
[Spec] Better define what an SPC credential is and its requirements w3c/secure-payment-confirmation#167 (11 comments by @ianbjacobs, @stephenmcgruer)
-
Provide high-level of UX in various failure modes w3c/secure-payment-confirmation#170 (6 comments by @stephenmcgruer)
-
w3c/payment-request
-
1 issue opened.
-
Allow custom data for the active payment method to be provided to `PaymentResponse.prototype.complete` w3c/payment-request#981, by @dcrousso.
-
-
1 issue closed.
-
Use "registrable domain" instead of "eTLD+1" w3c/payment-request#969.
-
-
1 issue received 1 new comment.
-
Allow custom data for the active payment method to be provided to `PaymentResponse.prototype.complete` w3c/payment-request#981 (1 comment by @cyberphone)
-
-
1 pull request merged.
-
Editorial: Changes in response to AC review w3c/payment-request#978.
-
-
2 pull requests received 4 new comments.
-
Editorial: Changes in response to AC review w3c/payment-request#978 (3 comments by @ianbjacobs, @lbdvt)
-
Proposed addition: validate .data on construction w3c/payment-request#976 (1 comment by @marcoscaceres)
-
w3c/webpayments
-
1 issue closed.
-
1 issue received 1 new comment.
-
How do we transition users and merchants from the current system to using the new API and apps? w3c/webpayments#94 (1 comment by @ianbjacobs)
-
-
1 pull request opened.
-
[Privacy] Initial documentation on privacy implications for web payments w3c/webpayments#259, by @stephenmcgruer.
-
-
1 pull request merged.
-
[Privacy] Initial documentation on privacy implications for web payments w3c/webpayments#259.
-
Lifecycle
-
1 charter extension.
-
Charter extended until 31 March 2022.
-
Participants
-
2 chairs appointed.
-
Gerhard Oosthuizen became a chair.
-
Praveena Subrahmanyam became a chair.
-
-
1 chair stepped down.
-
Adrian Hope-Bailie stepped down as a chair.
-
-
2 participants joined.
-
Devin Rousso (Apple Inc.) joined.
-
Ryan Watkins (Mastercard Incorporated) joined.
-
GitHub
w3c/secure-payment-confirmation
-
2 issues opened.
-
Proposal: Add `payeeName` as alternative to `payeeOrigin` w3c/secure-payment-confirmation#163, by @stephenmcgruer.
-
Consider separating the SPC powers of Third Party invocation and Payment display w3c/secure-payment-confirmation#157, by @Goosth.
-
-
3 issues closed.
-
What is a fully qualified origin? w3c/secure-payment-confirmation#149.
-
9.2: punchline first w3c/secure-payment-confirmation#140.
-
explain "registration" earlier w3c/secure-payment-confirmation#137.
-
-
9 issues received 31 new comments.
-
Proposal: Add `payeeName` as alternative to `payeeOrigin` w3c/secure-payment-confirmation#163 (8 comments by @jcemer-stripe, @rsolomakhin, @stephenmcgruer)
-
Accessible icon information w3c/secure-payment-confirmation#127 (6 comments by @ianbjacobs, @jcemer-stripe, @rsolomakhin, @stephenmcgruer)
-
Encrypt SPC Credential Identifiers in authentication flows to increase privacy w3c/secure-payment-confirmation#77 (5 comments by @cyberphone, @Goosth, @ianbjacobs, @stephenmcgruer, @ve7jtb)
-
Consider separating the SPC powers of Third Party invocation and Payment display w3c/secure-payment-confirmation#157 (3 comments by @Goosth, @ianbjacobs, @stephenmcgruer)
-
11.3 & 11.4: define the mitigation w3c/secure-payment-confirmation#143 (3 comments by @cyberphone, @stephenmcgruer)
-
Should SPC allow for a failed download of the payment instrument icon? w3c/secure-payment-confirmation#125 (2 comments by @stephenmcgruer)
-
What are requirements when more than one SPC credential matches? w3c/secure-payment-confirmation#69 (2 comments by @ianbjacobs, @stephenmcgruer)
-
-
7 pull requests opened.
-
Using displayName for icon accessibility w3c/secure-payment-confirmation#162, by @ianbjacobs.
-
[Spec] Editorial: Get rid of "dot" notation for dictionaries w3c/secure-payment-confirmation#161, by @stephenmcgruer.
-
[Spec] Correctly validate payeeOrigin w3c/secure-payment-confirmation#160, by @stephenmcgruer.
-
Implementation note related to N matching credentials w3c/secure-payment-confirmation#159, by @ianbjacobs.
-
Enhanced note about role of user data in example w3c/secure-payment-confirmation#158, by @ianbjacobs.
-
Alt for icon w3c/secure-payment-confirmation#156, by @ianbjacobs.
-
Describe protections against "wrong credential" attack w3c/secure-payment-confirmation#155, by @ianbjacobs.
-
-
7 pull requests merged.
-
[Spec] Correctly validate payeeOrigin w3c/secure-payment-confirmation#160.
-
[Spec] Editorial: Get rid of "dot" notation for dictionaries w3c/secure-payment-confirmation#161.
-
Using displayName for icon accessibility w3c/secure-payment-confirmation#162.
-
Implementation note related to N matching credentials w3c/secure-payment-confirmation#159.
-
Enhanced note about role of user data in example w3c/secure-payment-confirmation#158.
-
Editorial: To address issue 140 w3c/secure-payment-confirmation#148.
-
Describe protections against "wrong credential" attack w3c/secure-payment-confirmation#155.
-
-
1 pull request closed.
-
Alt for icon w3c/secure-payment-confirmation#156.
-
-
9 pull requests received 44 new comments.
-
[Spec] Correctly validate payeeOrigin w3c/secure-payment-confirmation#160 (16 comments by @annevk, @stephenmcgruer)
-
[Spec] Editorial: Get rid of "dot" notation for dictionaries w3c/secure-payment-confirmation#161 (5 comments by @rsolomakhin, @stephenmcgruer)
-
Alt for icon w3c/secure-payment-confirmation#156 (5 comments by @ianbjacobs, @r12a, @rsolomakhin, @stephenmcgruer)
-
Implementation note related to N matching credentials w3c/secure-payment-confirmation#159 (5 comments by @ianbjacobs, @stephenmcgruer)
-
Using displayName for icon accessibility w3c/secure-payment-confirmation#162 (4 comments by @ianbjacobs, @stephenmcgruer)
-
Describe protections against "wrong credential" attack w3c/secure-payment-confirmation#155 (4 comments by @ianbjacobs, @stephenmcgruer)
-
Editorial: To address issue 140 w3c/secure-payment-confirmation#148 (3 comments by @ianbjacobs, @samuelweiler)
-
Enhanced note about role of user data in example w3c/secure-payment-confirmation#158 (1 comment by @ianbjacobs)
-
Suggested clarification and extensions w3c/secure-payment-confirmation#103 (1 comment by @ianbjacobs)
-
w3c/payment-request
-
3 issues opened.
-
Mine w3c/payment-request#979, by @alexanderramos89.
-
Custom .data validation during construction of PaymentRequest w3c/payment-request#975, by @marcoscaceres.
-
-
3 issues closed.
-
Mine w3c/payment-request#979.
-
Localizability of errors w3c/payment-request#951.
-
Istanbul w3c/payment-request#974.
-
-
3 issues received 4 new comments.
-
Localization and string metadata for descriptions w3c/payment-request#948 (2 comments by @ianbjacobs, @r12a)
-
Custom .data validation during construction of PaymentRequest w3c/payment-request#975 (1 comment by @marcoscaceres)
-
-
3 pull requests opened.
-
Editorial: Changes in response to AC review w3c/payment-request#978, by @ianbjacobs.
-
Define concepts for converting and validating `.data` w3c/payment-request#977, by @stephenmcgruer.
-
Proposed addition: validate .data on construction w3c/payment-request#976, by @marcoscaceres.
-
-
1 pull request merged.
-
Editorial: example fixes w3c/payment-request#972.
-
-
5 pull requests received 30 new comments.
-
Add hasEnrolledInstrument() again w3c/payment-request#931 (16 comments by @dcrousso, @marcoscaceres, @rsolomakhin)
-
Define concepts for converting and validating `.data` w3c/payment-request#977 (5 comments by @marcoscaceres, @stephenmcgruer)
-
Proposed addition: validate .data on construction w3c/payment-request#976 (5 comments by @marcoscaceres, @rsolomakhin, @stephenmcgruer)
-
Editorial: Changes in response to AC review w3c/payment-request#978 (3 comments by @marcoscaceres, @mountainhippo)
-
Add internationalization support for human readable labels w3c/payment-request#971 (1 comment by @ianbjacobs)
-
TR publications
-
1 document published.
-
Payment Handler API published as a Working Draft. History of Payment Handler API
-
Past meetings
Participants
-
2 participants joined.
-
Peter Milne (Criteo) joined.
-
Tomoya Horiguchi (JCB CO., LTD.) joined.
-
-
1 organization left.
-
NACHA - The Electronic Payments Association left.
-
GitHub
w3c/secure-payment-confirmation
-
10 issues opened.
-
Is it possible for a user to downgrade a credential creation request? w3c/secure-payment-confirmation#154, by @samuelweiler.
-
What is a fully qualified origin? w3c/secure-payment-confirmation#149, by @annevk.
-
11.3 & 11.4: define the mitigation w3c/secure-payment-confirmation#143, by @samuelweiler.
-
11.2 define the mitigation w3c/secure-payment-confirmation#142, by @samuelweiler.
-
10.2 missing parenthesis w3c/secure-payment-confirmation#141, by @samuelweiler.
-
9.2: punchline first w3c/secure-payment-confirmation#140, by @samuelweiler.
-
payment attack: reorder / clarify w3c/secure-payment-confirmation#139, by @samuelweiler.
-
login attack: relabel actors for clarity w3c/secure-payment-confirmation#138, by @samuelweiler.
-
explain "registration" earlier w3c/secure-payment-confirmation#137, by @samuelweiler.
-
Expand/define "ID&V flow" w3c/secure-payment-confirmation#136, by @samuelweiler.
-
-
11 issues closed.
-
Proposal: support data URLs for card art icons w3c/secure-payment-confirmation#101.
-
FIDO Credential ID vs Payment Instrument ID w3c/secure-payment-confirmation#49.
-
PROPOSAL: Alternative Secure Payment Confirmation Flow w3c/secure-payment-confirmation#15.
-
Expand/define "ID&V flow" w3c/secure-payment-confirmation#136.
-
payment attack: reorder / clarify w3c/secure-payment-confirmation#139.
-
login attack: relabel actors for clarity w3c/secure-payment-confirmation#138.
-
10.2 missing parenthesis w3c/secure-payment-confirmation#141.
-
Clarify security properties of the cryptogram w3c/secure-payment-confirmation#28.
-
How is SPC UX affected by WebAuth values for userVerification w3c/secure-payment-confirmation#119.
-
SPC Relying Party operation should be standardized w3c/secure-payment-confirmation#96.
-
Require AuthenticatorSelection's residentKey for registration w3c/secure-payment-confirmation#129.
-
-
1 issue reopened.
-
Supporting roaming authenticators w3c/secure-payment-confirmation#12, by @samuelweiler.
-
-
17 issues received 36 new comments.
-
Should SPC allow for a failed download of the payment instrument icon? w3c/secure-payment-confirmation#125 (5 comments by @adrianhopebailie, @davordavidovic, @stephenmcgruer)
-
Accessible icon information w3c/secure-payment-confirmation#127 (5 comments by @ianbjacobs, @RealJoshue108, @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 @caraitto, @stephenmcgruer)
-
What is a fully qualified origin? w3c/secure-payment-confirmation#149 (3 comments by @annevk, @stephenmcgruer)
-
10.2 missing parenthesis w3c/secure-payment-confirmation#141 (3 comments by @samuelweiler, @stephenmcgruer)
-
UX behavior when there are no matching credentials w3c/secure-payment-confirmation#98 (3 comments by @ianbjacobs, @stephenmcgruer)
-
11.3 & 11.4: define the mitigation w3c/secure-payment-confirmation#143 (2 comments by @samuelweiler, @stephenmcgruer)
-
Proposal: support data URLs for card art icons w3c/secure-payment-confirmation#101 (2 comments by @ianbjacobs, @stephenmcgruer)
-
explain "registration" earlier w3c/secure-payment-confirmation#137 (2 comments by @ianbjacobs, @stephenmcgruer)
-
FIDO Credential ID vs Payment Instrument ID w3c/secure-payment-confirmation#49 (1 comment by @ianbjacobs)
-
PROPOSAL: Alternative Secure Payment Confirmation Flow w3c/secure-payment-confirmation#15 (1 comment by @ianbjacobs)
-
Clarify security properties of the cryptogram w3c/secure-payment-confirmation#28 (1 comment by @stephenmcgruer)
-
How is SPC UX affected by WebAuth values for userVerification w3c/secure-payment-confirmation#119 (1 comment by @stephenmcgruer)
-
-
12 pull requests opened.
-
Add note on I18N of displayName w3c/secure-payment-confirmation#153, by @ianbjacobs.
-
[Spec] Add note on use of Data URLs w3c/secure-payment-confirmation#152, by @stephenmcgruer.
-
[Spec] Spec the User Agent Automation section w3c/secure-payment-confirmation#151, by @stephenmcgruer.
-
[Spec] Spec the User Agent Automation section w3c/secure-payment-confirmation#150, by @stephenmcgruer.
-
Editorial: To address issue 140 w3c/secure-payment-confirmation#148, by @ianbjacobs.
-
Editorial: Rewording to address 139 w3c/secure-payment-confirmation#147, by @ianbjacobs.
-
Provide more rationale about registration/authentication ratio earlier in the document w3c/secure-payment-confirmation#146, by @ianbjacobs.
-
Expand term id&v w3c/secure-payment-confirmation#145, by @ianbjacobs.
-
[Spec] Replace a.com/b.com with more descriptive URLs w3c/secure-payment-confirmation#144, by @stephenmcgruer.
-
[Spec] Properly spec topOrigin w3c/secure-payment-confirmation#135, by @stephenmcgruer.
-
[Spec] Clearly note privacy requirement for early-exit w3c/secure-payment-confirmation#134, by @stephenmcgruer.
-
[Spec] Specify relying party operations w3c/secure-payment-confirmation#133, by @stephenmcgruer.
-
-
11 pull requests merged.
-
[Spec] Spec the User Agent Automation section w3c/secure-payment-confirmation#151.
-
Add note on I18N of displayName w3c/secure-payment-confirmation#153.
-
[Spec] Add note on use of Data URLs w3c/secure-payment-confirmation#152.
-
[Spec] Properly spec topOrigin w3c/secure-payment-confirmation#135.
-
Provide more rationale about registration/authentication ratio earlier in the document w3c/secure-payment-confirmation#146.
-
Editorial: Rewording to address 139 w3c/secure-payment-confirmation#147.
-
Expand term id&v w3c/secure-payment-confirmation#145.
-
[Spec] Replace a.com/b.com with more descriptive URLs w3c/secure-payment-confirmation#144.
-
[Spec] Clearly note privacy requirement for early-exit w3c/secure-payment-confirmation#134.
-
[Spec] Specify relying party operations w3c/secure-payment-confirmation#133.
-
[Spec] Correctly specify authenticatorSelection requirements w3c/secure-payment-confirmation#132.
-
-
1 pull request closed.
-
[Spec] Spec the User Agent Automation section w3c/secure-payment-confirmation#150.
-
-
9 pull requests received 17 new comments.
-
[Spec] Properly spec topOrigin w3c/secure-payment-confirmation#135 (4 comments by @domfarolino, @stephenmcgruer)
-
[Spec] Clearly note privacy requirement for early-exit w3c/secure-payment-confirmation#134 (4 comments by @ianbjacobs, @stephenmcgruer)
-
[Spec] Spec the User Agent Automation section w3c/secure-payment-confirmation#151 (2 comments by @stephenmcgruer)
-
[Spec] Add note on use of Data URLs w3c/secure-payment-confirmation#152 (2 comments by @stephenmcgruer)
-
Provide more rationale about registration/authentication ratio earlier in the document w3c/secure-payment-confirmation#146 (1 comment by @samuelweiler)
-
[Spec] Replace a.com/b.com with more descriptive URLs w3c/secure-payment-confirmation#144 (1 comment by @stephenmcgruer)
-
[Spec] Correctly specify authenticatorSelection requirements w3c/secure-payment-confirmation#132 (1 comment by @stephenmcgruer)
-
w3c/payment-request
-
2 pull requests opened.
-
Editorial: example fixes w3c/payment-request#972, by @marcoscaceres.
-
Add internationalization support for human readable labels w3c/payment-request#971, by @ianbjacobs.
-
-
1 pull request merged.
-
Editorial: fix a markup typo w3c/payment-request#968.
-
-
2 pull requests received 20 new comments.
-
Add internationalization support for human readable labels w3c/payment-request#971 (19 comments by @aphillips, @ianbjacobs, @marcoscaceres)
-
w3c/payment-request#970 (1 comment by @w3cbot)
-
w3c/web-based-payment-handler
-
1 issue closed.
-
Remove the deprecated basic-card content w3c/web-based-payment-handler#397.
-
-
1 pull request merged.
-
Remove basic-card content w3c/web-based-payment-handler#398.
-
-
1 pull request received 2 new comments.
TR publications
-
5 documents published.
-
Payment Method Identifiers published as a Proposed Recommendation. History of Payment Method Identifiers
-
Payment Request API published as a Proposed Recommendation. History of Payment Request API
-
Payment Method Identifiers published as a Candidate Recommendation Draft. History of Payment Method Identifiers
-
Payment Request API published twice as a Candidate Recommendation Draft. History of Payment Request API
-
Participants
-
5 participants joined.
-
Babu Muttineni (Yahoo Holdings Inc.) joined.
-
Joel DI MANNO (FIME) joined.
-
Jean Luc DI MANNO (FIME) joined.
-
Jean Fang (FIME) joined.
-
Jean Luc Di Manno (FIME) joined.
-
-
1 participant left.
-
Babu Muttineni (Yahoo Holdings Inc.) left.
-
-
2 organizations joined.
-
Yahoo Holdings Inc. joined.
-
FIME joined.
-
GitHub
w3c/payment-request
-
3 issues opened.
-
Use "registrable domain" instead of "eTLD+1" w3c/payment-request#969, by @zcorpan.
-
window.PaymentRequest returns undefined randomly w3c/payment-request#967, by @semcelik.
-
Remove "standardized payment method identifier" content w3c/payment-request#965, by @maxlgu.
-
-
3 issues closed.
-
window.PaymentRequest returns undefined randomly w3c/payment-request#967.
-
Remove "standardized payment method identifier" content w3c/payment-request#965.
-
Extract actionable items from @lknik's review w3c/payment-request#641.
-
-
5 issues received 12 new comments.
-
Localization and string metadata for descriptions w3c/payment-request#948 (6 comments by @aphillips, @ianbjacobs, @marcoscaceres, @r12a)
-
Remove "standardized payment method identifier" content w3c/payment-request#965 (3 comments by @ianbjacobs, @maxlgu, @rsolomakhin)
-
window.PaymentRequest returns undefined randomly w3c/payment-request#967 (1 comment by @stephenmcgruer)
-
Allow locale to be specified by the developer. w3c/payment-request#650 (1 comment by @marcoscaceres)
-
-
2 pull requests opened.
-
Editorial: fix a markup typo w3c/payment-request#968, by @zcorpan.
-
Add support for updateable w3c/payment-request#966, by @ianbjacobs.
-
-
1 pull request merged.
-
Add support for updateable w3c/payment-request#966.
-
-
2 pull requests received 3 new comments.
w3c/secure-payment-confirmation
-
6 issues opened.
-
Document current implementation limitations in Notes w3c/secure-payment-confirmation#130, by @ianbjacobs.
-
Require AuthenticatorSelection's residentKey for registration w3c/secure-payment-confirmation#129, by @maxlgu.
-
Clarification on requiring user activation for credential creation in cross-origin iframes to mitigation cross-site tracking w3c/secure-payment-confirmation#128, by @caraitto.
-
Accessible icon information w3c/secure-payment-confirmation#127, by @ianbjacobs.
-
Should SPC allow for a failed download of the payment instrument icon? w3c/secure-payment-confirmation#125, by @stephenmcgruer.
-
How do RPs determine when to enroll the user? w3c/secure-payment-confirmation#124, by @ianbjacobs.
-
-
5 issues closed.
-
Document current implementation limitations in Notes w3c/secure-payment-confirmation#130.
-
What happens when user cancels during transaction confirmation? w3c/secure-payment-confirmation#66.
-
Specification of the signature w3c/secure-payment-confirmation#40.
-
When SPC runs in an iframe, what permissions are required? w3c/secure-payment-confirmation#68.
-
Special UI for SPC credential enrollment w3c/secure-payment-confirmation#84.
-
-
12 issues received 43 new comments.
-
Localization topics to address w3c/secure-payment-confirmation#93 (11 comments by @aphillips, @ianbjacobs, @rsolomakhin)
-
How do RPs determine when to enroll the user? w3c/secure-payment-confirmation#124 (7 comments by @ianbjacobs, @rsolomakhin, @stephenmcgruer)
-
Should SPC allow for a failed download of the payment instrument icon? w3c/secure-payment-confirmation#125 (6 comments by @davordavidovic, @Goosth, @rsolomakhin, @stephenmcgruer)
-
Clarification on requiring user activation for credential creation in cross-origin iframes to mitigation cross-site tracking w3c/secure-payment-confirmation#128 (4 comments by @caraitto, @rsolomakhin, @stephenmcgruer)
-
Proposal: support data URLs for card art icons w3c/secure-payment-confirmation#101 (4 comments by @adrianhopebailie, @ianbjacobs, @stephenmcgruer)
-
Accessible icon information w3c/secure-payment-confirmation#127 (3 comments by @ianbjacobs, @rsolomakhin)
-
Document current implementation limitations in Notes w3c/secure-payment-confirmation#130 (2 comments by @ianbjacobs, @rsolomakhin)
-
Require AuthenticatorSelection's residentKey for registration w3c/secure-payment-confirmation#129 (2 comments by @maxlgu, @rsolomakhin)
-
What happens when user cancels during transaction confirmation? w3c/secure-payment-confirmation#66 (1 comment by @stephenmcgruer)
-
When SPC runs in an iframe, what permissions are required? w3c/secure-payment-confirmation#68 (1 comment by @stephenmcgruer)
-
Special UI for SPC credential enrollment w3c/secure-payment-confirmation#84 (1 comment by @stephenmcgruer)
-
-
2 pull requests opened.
-
[Spec] Correctly specify authenticatorSelection requirements w3c/secure-payment-confirmation#132, by @stephenmcgruer.
-
[Explainer] Add a diagram showing SPC authentication w3c/secure-payment-confirmation#126, by @stephenmcgruer.
-
-
1 pull request merged.
-
[Explainer] Add a diagram showing SPC authentication w3c/secure-payment-confirmation#126.
-
-
1 pull request closed.
-
Question regarding feature detection w3c/secure-payment-confirmation#74.
-
-
4 pull requests received 8 new comments.
-
[Spec] Correctly specify authenticatorSelection requirements w3c/secure-payment-confirmation#132 (3 comments by @ianbjacobs, @stephenmcgruer)
-
[Explainer] Add a diagram showing SPC authentication w3c/secure-payment-confirmation#126 (3 comments by @ianbjacobs, @stephenmcgruer)
-
w3c/web-based-payment-handler
-
2 issues opened.
-
Remove the deprecated basic-card content w3c/web-based-payment-handler#397, by @maxlgu.
-
Payment Handler enrollment should accept URLs only w3c/web-based-payment-handler#396, by @maxlgu.
-
-
2 issues received 4 new comments.
-
Remove the deprecated basic-card content w3c/web-based-payment-handler#397 (2 comments by @maxlgu, @rsolomakhin)
-
Payment Handler enrollment should accept URLs only w3c/web-based-payment-handler#396 (2 comments by @maxlgu, @rsolomakhin)
-
-
1 pull request opened.
-
Remove basic-card content w3c/web-based-payment-handler#398, by @maxlgu.
-
-
1 pull request received 3 new comments.
-
Remove basic-card content w3c/web-based-payment-handler#398 (3 comments by @ianbjacobs, @maxlgu, @rsolomakhin)
-
w3c/payment-method-id
-
1 pull request opened.
-
Enable addition of new features w3c/payment-method-id#68, by @ianbjacobs.
-
-
1 pull request merged.
-
Enable addition of new features w3c/payment-method-id#68.
-
TR publications
-
5 documents published.
-
Payment Method Identifiers published as a Candidate Recommendation Draft. History of Payment Method Identifiers
-
Payment Request API published twice as a Candidate Recommendation Draft. History of Payment Request API
-
Secure Payment Confirmation published as a First Public Working Draft. History of Secure Payment Confirmation
-
Payment Method: Basic Card published as a Note. History of Payment Method: Basic Card
-
Participants
-
1 chair appointed.
-
Adrian Hope-Bailie became a chair.
-
-
1 chair stepped down.
-
Adrian Hope-Bailie stepped down as a chair.
-
-
3 participants joined.
-
Manjush Menon (Visa) joined.
-
Manjush Menon (Visa) joined.
-
Adrian Hope-Bailie (W3C Invited Experts) joined.
-
-
3 participants left.
-
Manjush Menon (Visa) left.
-
Tom Bellenger (Visa) left.
-
Adrian Hope-Bailie (W3C Invited Experts) left.
-
GitHub
w3c/webpayments
-
3 issues closed.
-
European market - Security concerns w3c/webpayments#210.
-
Specify both pickup and delivery addresses in a single payment request w3c/webpayments#252.
-
4 issues received 4 new comments.
-
Should the Web Payments API cater for the invoicing part of the full web purchase flow ? w3c/webpayments#60 (1 comment by @ianbjacobs)
-
Specify both pickup and delivery addresses in a single payment request w3c/webpayments#252 (1 comment by @ianbjacobs)
-
1 pull request closed.
-
Add mention of private browsing as insufficient w3c/webpayments#253.
-
w3c/secure-payment-confirmation
-
4 issues opened.
-
How is SPC UX affected by WebAuth values for userVerification w3c/secure-payment-confirmation#119, by @ianbjacobs.
-
Privacy consideration: GDPR w3c/secure-payment-confirmation#109, by @ianbjacobs.
-
Proposal: support data URLs for card art icons w3c/secure-payment-confirmation#101, by @stephenmcgruer.
-
UX behavior when there are no matching credentials w3c/secure-payment-confirmation#98, by @ianbjacobs.
-
-
5 issues closed.
-
What degree of user consent is required before a FIDO credential can be used as an SPC credential? w3c/secure-payment-confirmation#79.
-
Integrating SPC with Open Banking w3c/secure-payment-confirmation#51.
-
Enrollment should not interrupt payment response w3c/secure-payment-confirmation#59.
-
Using PaymentCredential for vanilla WebAuthn authentication. w3c/secure-payment-confirmation#39.
-
PROPOSAL 2: No Payment Handler Flow w3c/secure-payment-confirmation#17.
-
-
14 issues received 40 new comments.
-
Proposal: support data URLs for card art icons w3c/secure-payment-confirmation#101 (23 comments by @adrianhopebailie, @ianbjacobs, @jcemer-stripe, @rsolomakhin, @stephenmcgruer)
-
Is the "payment" extension a part of Relying Party - Client Platform API signature? w3c/secure-payment-confirmation#97 (2 comments by @ianbjacobs, @ynojima)
-
Should SPC be invokable outside of a PaymentRequest flow? w3c/secure-payment-confirmation#65 (2 comments by @Goosth, @ianbjacobs)
-
UX behavior when there are no matching credentials w3c/secure-payment-confirmation#98 (2 comments by @stephenmcgruer)
-
What degree of user consent is required before a FIDO credential can be used as an SPC credential? w3c/secure-payment-confirmation#79 (1 comment by @ianbjacobs)
-
SPC Relying Party operation should be standardized w3c/secure-payment-confirmation#96 (1 comment by @stephenmcgruer)
-
Conditionally-shown Transaction UX and WebAuthn w3c/secure-payment-confirmation#92 (1 comment by @stephenmcgruer)
-
Special UI for SPC credential enrollment w3c/secure-payment-confirmation#84 (1 comment by @stephenmcgruer)
-
Enrollment should not interrupt payment response w3c/secure-payment-confirmation#59 (1 comment by @ianbjacobs)
-
Using PaymentCredential for vanilla WebAuthn authentication. w3c/secure-payment-confirmation#39 (1 comment by @ianbjacobs)
-
-
21 pull requests opened.
-
[Spec] Address fixups from spec mentor review w3c/secure-payment-confirmation#122, by @stephenmcgruer.
-
[Editorial] Format parts of spec.bs to 80-wide w3c/secure-payment-confirmation#121, by @stephenmcgruer.
-
Speak to current implementation limitation regarding userVerification w3c/secure-payment-confirmation#120, by @ianbjacobs.
-
Preparing for FPWD (and then auto-publishing) w3c/secure-payment-confirmation#118, by @ianbjacobs.
-
[README] Update the README w3c/secure-payment-confirmation#117, by @stephenmcgruer.
-
[TAG] Update the security/privacy questionnaire w3c/secure-payment-confirmation#116, by @stephenmcgruer.
-
Registration instead of Enrollment w3c/secure-payment-confirmation#115, by @ianbjacobs.
-
[Spec] Write the 'transaction UX' section w3c/secure-payment-confirmation#114, by @stephenmcgruer.
-
[Explainer] Re-write the explainer to best-practices, part 3/n w3c/secure-payment-confirmation#113, by @stephenmcgruer.
-
[Explainer] Re-write the explainer to best-practices, part 2/n w3c/secure-payment-confirmation#112, by @stephenmcgruer.
-
[Spec] Write up Security & Privacy sections w3c/secure-payment-confirmation#111, by @stephenmcgruer.
-
Clarify start/end of API call w3c/secure-payment-confirmation#110, by @ianbjacobs.
-
[Explainer] Re-write the explainer to best-practices, part 1/n w3c/secure-payment-confirmation#108, by @stephenmcgruer.
-
[Spec] Bugfix: rpOrigin --> rp w3c/secure-payment-confirmation#107, by @stephenmcgruer.
-
[Spec] Minor fixups suggested by domfarolino w3c/secure-payment-confirmation#106, by @stephenmcgruer.
-
[Spec] Require that `payeeOrigin` is fully qualified w3c/secure-payment-confirmation#105, by @stephenmcgruer.
-
Note about credential reuse in both directions w3c/secure-payment-confirmation#104, by @ianbjacobs.
-
Suggested clarification and extensions w3c/secure-payment-confirmation#103, by @Goosth.
-
[Testing] Testing PR preview; DO NOT SUBMIT w3c/secure-payment-confirmation#102, by @stephenmcgruer.
-
[Spec] Various spec improvements w3c/secure-payment-confirmation#100, by @stephenmcgruer.
-
Note on API shape w3c/secure-payment-confirmation#99, by @ianbjacobs.
-
-
19 pull requests merged.
-
Speak to current implementation limitation regarding userVerification w3c/secure-payment-confirmation#120.
-
[Spec] Address fixups from spec mentor review w3c/secure-payment-confirmation#122.
-
[Editorial] Format parts of spec.bs to 80-wide w3c/secure-payment-confirmation#121.
-
[Spec] Write the 'transaction UX' section w3c/secure-payment-confirmation#114.
-
[README] Update the README w3c/secure-payment-confirmation#117.
-
[TAG] Update the security/privacy questionnaire w3c/secure-payment-confirmation#116.
-
Preparing for FPWD (and then auto-publishing) w3c/secure-payment-confirmation#118.
-
[Explainer] Re-write the explainer to best-practices, part 3/n w3c/secure-payment-confirmation#113.
-
Registration instead of Enrollment w3c/secure-payment-confirmation#115.
-
[Explainer] Re-write the explainer to best-practices, part 2/n w3c/secure-payment-confirmation#112.
-
Note about credential reuse in both directions w3c/secure-payment-confirmation#104.
-
[Spec] Write up Security & Privacy sections w3c/secure-payment-confirmation#111.
-
Clarify start/end of API call w3c/secure-payment-confirmation#110.
-
[Explainer] Re-write the explainer to best-practices, part 1/n w3c/secure-payment-confirmation#108.
-
[Spec] Bugfix: rpOrigin --> rp w3c/secure-payment-confirmation#107.
-
[Spec] Require that `payeeOrigin` is fully qualified w3c/secure-payment-confirmation#105.
-
[Spec] Minor fixups suggested by domfarolino w3c/secure-payment-confirmation#106.
-
[Spec] Various spec improvements w3c/secure-payment-confirmation#100.
-
Note on API shape w3c/secure-payment-confirmation#99.
-
-
1 pull request closed.
-
[Testing] Testing PR preview; DO NOT SUBMIT w3c/secure-payment-confirmation#102.
-
-
16 pull requests received 139 new comments.
-
Suggested clarification and extensions w3c/secure-payment-confirmation#103 (44 comments by @Goosth, @ianbjacobs, @stephenmcgruer)
-
[Explainer] Re-write the explainer to best-practices, part 1/n w3c/secure-payment-confirmation#108 (42 comments by @Goosth, @ianbjacobs, @rsolomakhin, @stephenmcgruer)
-
[TAG] Update the security/privacy questionnaire w3c/secure-payment-confirmation#116 (13 comments by @ianbjacobs, @rsolomakhin, @stephenmcgruer)
-
[Spec] Write up Security & Privacy sections w3c/secure-payment-confirmation#111 (10 comments by @ianbjacobs, @rsolomakhin, @stephenmcgruer)
-
[Spec] Require that `payeeOrigin` is fully qualified w3c/secure-payment-confirmation#105 (6 comments by @rsolomakhin, @stephenmcgruer)
-
[Spec] Write the 'transaction UX' section w3c/secure-payment-confirmation#114 (3 comments by @domfarolino, @stephenmcgruer)
-
Note about credential reuse in both directions w3c/secure-payment-confirmation#104 (3 comments by @Goosth, @ianbjacobs)
-
[Spec] Various spec improvements w3c/secure-payment-confirmation#100 (3 comments by @ianbjacobs, @stephenmcgruer)
-
Speak to current implementation limitation regarding userVerification w3c/secure-payment-confirmation#120 (2 comments by @ianbjacobs)
-
[Explainer] Re-write the explainer to best-practices, part 3/n w3c/secure-payment-confirmation#113 (2 comments by @rsolomakhin)
-
[Explainer] Re-write the explainer to best-practices, part 2/n w3c/secure-payment-confirmation#112 (2 comments by @ianbjacobs)
-
[Spec] Address fixups from spec mentor review w3c/secure-payment-confirmation#122 (1 comment by @stephenmcgruer)
-
[Editorial] Format parts of spec.bs to 80-wide w3c/secure-payment-confirmation#121 (1 comment by @stephenmcgruer)
-
[Testing] Testing PR preview; DO NOT SUBMIT w3c/secure-payment-confirmation#102 (1 comment by @stephenmcgruer)
-
w3c/payment-method-id
-
2 pull requests opened.
-
Remove "standardized payment method identifiers" w3c/payment-method-id#67, by @marcoscaceres.
-
Deprecate basic card w3c/payment-method-id#66, by @ianbjacobs.
-
-
1 pull request merged.
-
Deprecate basic card w3c/payment-method-id#66.
-
-
1 pull request closed.
-
Remove "standardized payment method identifiers" w3c/payment-method-id#67.
-
-
1 pull request received 4 new comments.
-
Remove "standardized payment method identifiers" w3c/payment-method-id#67 (4 comments by @ianbjacobs, @marcoscaceres)
-
w3c/payment-request
-
1 issue received 2 new comments.
-
Allow user activation to be delegated to a child frame to trigger request.show() w3c/payment-request#917 (2 comments by @rsolomakhin, @stephenmcgruer)
-
-
3 pull requests opened.
-
Editorial: Removed references to Basic Card w3c/payment-request#963, by @ianbjacobs.
-
Make "one Payment UI at a time" optional to align with implementations. w3c/payment-request#962, by @ianbjacobs.
-
Update transient activation to match WebKit w3c/payment-request#961, by @marcoscaceres.
-
-
2 pull requests merged.
-
Editorial: Removed references to Basic Card w3c/payment-request#963.
-
Update transient activation to match WebKit w3c/payment-request#961.
-
-
1 pull request closed.
-
Make "one Payment UI at a time" optional to align with implementations. w3c/payment-request#962.
-
-
3 pull requests received 6 new comments.
-
fix: disallow duplicate PMIs when creating request w3c/payment-request#908 (2 comments by @ianbjacobs, @marcoscaceres)
-
Make "one Payment UI at a time" optional to align with implementations. w3c/payment-request#962 (1 comment by @marcoscaceres)
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
-
Participants
-
3 participants joined.
-
Manish Garg (VE3) joined.
-
Bart de Water (Shopify) joined.
-
Robert Savage (Merchant Advisory Group) joined.
-
-
12 participants left.
-
Kincaid O'Neil (Coil Technologies, Inc.) left.
-
Philibert Dugas (Shopify) left.
-
Michael Elfassy (Shopify) left.
-
Ryan Cliffford (Fiserv) left.
-
Liam Kennedy (Fiserv) left.
-
James Evans-Rong (Fiserv) left.
-
Matt Lockyer (Fiserv) left.
-
Lucian Lauritz (Fiserv) left.
-
Kacie Paine (Merchant Advisory Group) left.
-
Ana Grace (Merchant Advisory Group) left.
-
Bruno Van Haetsdaele (Oxlin) left.
-
Gildas Le Louarn (Oxlin) left.
-
-
1 organization joined.
-
VE3 joined.
-
-
2 organizations left.
-
Fiserv left.
-
Oxlin left.
-
GitHub
w3c/secure-payment-confirmation
-
5 issues opened.
-
Is the "payment" extension a part of Relying Party - Client Platform API signature? w3c/secure-payment-confirmation#97, by @ynojima.
-
SPC Relying Party operation should be standardized w3c/secure-payment-confirmation#96, by @ynojima.
-
Localization topics to address w3c/secure-payment-confirmation#93, by @ianbjacobs.
-
Conditionally-shown Transaction UX and WebAuthn w3c/secure-payment-confirmation#92, by @stephenmcgruer.
-
Special UI for SPC credential enrollment w3c/secure-payment-confirmation#84, by @eric-alvarez.
-
-
13 issues closed.
-
Are Client-side Discoverable Credentials (aka Resident Keys) off the table in this proposal? w3c/secure-payment-confirmation#31.
-
Add profile identifier to payment credential structure to support credential fetching? w3c/secure-payment-confirmation#62.
-
Allow enrollment outside of transaction flow w3c/secure-payment-confirmation#44.
-
Popup UI handling of origin - relying party vs. merchant w3c/secure-payment-confirmation#83.
-
Remove fallbackUrl from explainer w3c/secure-payment-confirmation#57.
-
Does the browser receive credential IDs or instrument IDs? w3c/secure-payment-confirmation#10.
-
Can a merchant ensure that SPC will be used before invoking PR API? w3c/secure-payment-confirmation#8.
-
Is an issuer hosted payment handler necessary for secure-payment-confirmation flow? w3c/secure-payment-confirmation#4.
-
Change payment amount from SPC call within a payment app? w3c/secure-payment-confirmation#42.
-
SPC should not constrain how WebAuthn nonce is created w3c/secure-payment-confirmation#26.
-
How to handle stale displayName and icon? w3c/secure-payment-confirmation#14.
-
Clarify cardinality between PaymentCredential and payment instruments w3c/secure-payment-confirmation#13.
-
Any browser validation of SPC input data required? w3c/secure-payment-confirmation#82.
-
-
20 issues received 36 new comments.
-
Popup UI handling of origin - relying party vs. merchant w3c/secure-payment-confirmation#83 (7 comments by @Goosth, @ianbjacobs, @stephenmcgruer)
-
Special UI for SPC credential enrollment w3c/secure-payment-confirmation#84 (4 comments by @ianbjacobs, @jcemer-stripe, @stephenmcgruer)
-
Are Client-side Discoverable Credentials (aka Resident Keys) off the table in this proposal? w3c/secure-payment-confirmation#31 (3 comments by @ianbjacobs, @SensibleWood)
-
Does the browser receive credential IDs or instrument IDs? w3c/secure-payment-confirmation#10 (3 comments by @ianbjacobs, @stephenmcgruer)
-
Any browser validation of SPC input data required? w3c/secure-payment-confirmation#82 (3 comments by @ianbjacobs, @stephenmcgruer)
-
Make it easy to determine whether a user agent supports SPC w3c/secure-payment-confirmation#81 (2 comments by @ianbjacobs, @stephenmcgruer)
-
Add profile identifier to payment credential structure to support credential fetching? w3c/secure-payment-confirmation#62 (1 comment by @ianbjacobs)
-
Allow enrollment outside of transaction flow w3c/secure-payment-confirmation#44 (1 comment by @ianbjacobs)
-
Conditionally-shown Transaction UX and WebAuthn w3c/secure-payment-confirmation#92 (1 comment by @adrianhopebailie)
-
How can SPC be used in conjunction with a frictionless 3DS flow? w3c/secure-payment-confirmation#29 (1 comment by @ianbjacobs)
-
Can a merchant ensure that SPC will be used before invoking PR API? w3c/secure-payment-confirmation#8 (1 comment by @ianbjacobs)
-
Is an issuer hosted payment handler necessary for secure-payment-confirmation flow? w3c/secure-payment-confirmation#4 (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)
-
Change payment amount from SPC call within a payment app? w3c/secure-payment-confirmation#42 (1 comment by @ianbjacobs)
-
SPC should not constrain how WebAuthn nonce is created w3c/secure-payment-confirmation#26 (1 comment by @ianbjacobs)
-
How to handle stale displayName and icon? w3c/secure-payment-confirmation#14 (1 comment by @ianbjacobs)
-
Clarify cardinality between PaymentCredential and payment instruments w3c/secure-payment-confirmation#13 (1 comment by @ianbjacobs)
-
Requirements and Good Practices around Unenrollment w3c/secure-payment-confirmation#63 (1 comment by @ianbjacobs)
-
-
9 pull requests opened.
-
Remove custom CollectedClientData handling w3c/secure-payment-confirmation#95, by @adrianhopebailie.
-
[Explainer] Remove fallbackUrl entirely w3c/secure-payment-confirmation#94, by @stephenmcgruer.
-
Additional editorial suggestions sections 2 and beyond w3c/secure-payment-confirmation#91, by @ianbjacobs.
-
Editorial review of section 1 w3c/secure-payment-confirmation#90, by @ianbjacobs.
-
[Spec] Add payeeOrigin w3c/secure-payment-confirmation#89, by @stephenmcgruer.
-
[Spec] First draft version of spec w3c/secure-payment-confirmation#88, by @stephenmcgruer.
-
[Spec] Initial skeleton specification file w3c/secure-payment-confirmation#87, by @stephenmcgruer.
-
Update two links after the gh-pages --> main move w3c/secure-payment-confirmation#86, by @stephenmcgruer.
-
Merge pull request #36 from w3c/faq_validation w3c/secure-payment-confirmation#85, by @stephenmcgruer.
-
-
9 pull requests merged.
-
Remove custom CollectedClientData handling w3c/secure-payment-confirmation#95.
-
[Spec] Add payeeOrigin w3c/secure-payment-confirmation#89.
-
[Explainer] Remove fallbackUrl entirely w3c/secure-payment-confirmation#94.
-
Additional editorial suggestions sections 2 and beyond w3c/secure-payment-confirmation#91.
-
Editorial review of section 1 w3c/secure-payment-confirmation#90.
-
[Spec] First draft version of spec w3c/secure-payment-confirmation#88.
-
[Spec] Initial skeleton specification file w3c/secure-payment-confirmation#87.
-
Update two links after the gh-pages --> main move w3c/secure-payment-confirmation#86.
-
Merge pull request #36 from w3c/faq_validation w3c/secure-payment-confirmation#85.
-
-
1 pull request closed.
-
Background & multiple instruments w3c/secure-payment-confirmation#6.
-
-
5 pull requests received 28 new comments.
-
Editorial review of section 1 w3c/secure-payment-confirmation#90 (11 comments by @ianbjacobs, @rsolomakhin, @stephenmcgruer)
-
[Spec] Add payeeOrigin w3c/secure-payment-confirmation#89 (9 comments by @apouillard, @Goosth, @ianbjacobs, @rsolomakhin, @SensibleWood, @stephenmcgruer)
-
Additional editorial suggestions sections 2 and beyond w3c/secure-payment-confirmation#91 (4 comments by @ianbjacobs, @stephenmcgruer)
-
Remove custom CollectedClientData handling w3c/secure-payment-confirmation#95 (2 comments by @davordavidovic, @rsolomakhin)
-
[Spec] First draft version of spec w3c/secure-payment-confirmation#88 (2 comments by @rsolomakhin, @stephenmcgruer)
-
w3c/web-based-payment-handler
-
1 issue opened.
-
InstrumentKey availability w3c/web-based-payment-handler#391, by @apouillard.
-
-
1 issue closed.
-
InstrumentKey availability w3c/web-based-payment-handler#391.
-
-
1 issue received 3 new comments.
-
InstrumentKey availability w3c/web-based-payment-handler#391 (3 comments by @ianbjacobs, @rsolomakhin)
-
-
3 pull requests opened.
-
Updates for respec w3c/web-based-payment-handler#395, by @ianbjacobs.
-
Chore: internal slot syntax changes w3c/web-based-payment-handler#394, by @ianbjacobs.
-
Delete instrument key from PaymentRequestEvent w3c/web-based-payment-handler#393, by @ianbjacobs.
-
-
2 pull requests merged.
-
Delete instrument key from PaymentRequestEvent w3c/web-based-payment-handler#393.
-
Chore: internal slot syntax changes w3c/web-based-payment-handler#394.
-
-
2 pull requests received 2 new comments.
-
Delete instrument key from PaymentRequestEvent w3c/web-based-payment-handler#393 (1 comment by @ianbjacobs)
w3c/payment-request
-
1 issue received 2 new comments.
-
Localization and string metadata for descriptions w3c/payment-request#948 (2 comments by @marcoscaceres, @r12a)
-
TR publications
-
3 documents published.
-
Payment Request API published as a Candidate Recommendation Snapshot. History of Payment Request API
-
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
-
Participants
-
2 participants joined.
-
Susan Pandy (Discover Financial Services LLC) joined.
-
DAVID LAGARDERE (Criteo) joined.
-
-
5 participants left.
-
Benjamin Tidor (Stripe) left.
-
Justin Toupin (Google LLC) left.
-
Zach Koch (Google LLC) left.
-
Brett McDowell (Hedera Hashgraph) left.
-
Paul Madsen (Hedera Hashgraph) left.
-
-
1 organization joined.
-
Criteo joined.
-
-
1 organization left.
-
Hedera Hashgraph left.
-
GitHub
w3c/payment-request
-
2 issues closed.
-
Extract actionable items from Shopify study w3c/payment-request#772.
-
Use Case: 3DS 1.0 flows and invoking PR API from inside an iFrame w3c/payment-request#881.
-
-
5 issues received 7 new comments.
-
Allow user activation to be delegated to a child frame to trigger request.show() w3c/payment-request#917 (3 comments by @marcoscaceres, @mustaqahmed)
-
Use Case: 3DS 1.0 flows and invoking PR API from inside an iFrame w3c/payment-request#881 (1 comment by @ianbjacobs)
-
Localization and string metadata for descriptions w3c/payment-request#948 (1 comment by @rsolomakhin)
-
-
1 pull request opened.
-
chore: auto-publish spec as CRD w3c/payment-request#959, by @marcoscaceres.
-
-
1 pull request merged.
-
chore: auto-publish spec as CRD w3c/payment-request#959.
-
-
1 pull request received 1 new comment.
-
w3c/payment-request#960 (1 comment by @w3cbot)
-
w3c/secure-payment-confirmation
-
4 issues opened.
-
Popup UI handling of origin - relying party vs. merchant w3c/secure-payment-confirmation#83, by @weksler.
-
Any browser validation of SPC input data required? w3c/secure-payment-confirmation#82, by @ianbjacobs.
-
Make it easy to determine whether a user agent supports SPC w3c/secure-payment-confirmation#81, by @ianbjacobs.
-
What degree of user consent is required before a FIDO credential can be used as an SPC credential? w3c/secure-payment-confirmation#79, by @ianbjacobs.
-
-
1 issue closed.
-
Provide support for Out of Band Authentication to a secondary device w3c/secure-payment-confirmation#30.
-
-
6 issues received 17 new comments.
-
Should SPC be invokable outside of a PaymentRequest flow? w3c/secure-payment-confirmation#65 (9 comments by @adrianhopebailie, @ianbjacobs, @rsolomakhin)
-
Make it easy to determine whether a user agent supports SPC w3c/secure-payment-confirmation#81 (3 comments by @ianbjacobs, @stephenmcgruer)
-
Provide support for Out of Band Authentication to a secondary device w3c/secure-payment-confirmation#30 (2 comments by @Goosth, @ianbjacobs)
-
Any browser validation of SPC input data required? w3c/secure-payment-confirmation#82 (1 comment by @stephenmcgruer)
-
Popup UI handling of origin - relying party vs. merchant w3c/secure-payment-confirmation#83 (1 comment by @stephenmcgruer)
-
-
1 pull request opened.
-
Some minor updates w3c/secure-payment-confirmation#80, by @adrianhopebailie.
-
-
2 pull requests merged.
-
Some minor updates w3c/secure-payment-confirmation#80.
-
Allow for dynamic binding of instrument w3c/secure-payment-confirmation#78.
-
-
1 pull request closed.
-
Comments/questions on requirements.md w3c/secure-payment-confirmation#72.
-
-
3 pull requests received 5 new comments.
-
Allow for dynamic binding of instrument w3c/secure-payment-confirmation#78 (2 comments by @ianbjacobs, @stephenmcgruer)
-
Comments/questions on requirements.md w3c/secure-payment-confirmation#72 (2 comments by @stephenmcgruer)
-
w3c/web-based-payment-handler
-
1 issue opened.
-
navigator.credentials.get does not resolve promise when called from the window opened by PaymentRequestEvent.openWindow w3c/web-based-payment-handler#390, by @apouillard.
-
-
1 issue closed.
-
navigator.credentials.get does not resolve promise when called from the window opened by PaymentRequestEvent.openWindow w3c/web-based-payment-handler#390.
-
-
1 issue received 2 new comments.
-
navigator.credentials.get does not resolve promise when called from the window opened by PaymentRequestEvent.openWindow w3c/web-based-payment-handler#390 (2 comments by @apouillard, @rsolomakhin)
-
Participants
-
2 participants joined.
-
Julien Cayzac (Rakuten Group, Inc.) joined.
-
Jean Carlo Emer (Stripe) joined.
-
-
1 participant left.
-
Tom Lowenthal (Brave Software Inc.) left.
-
GitHub
w3c/secure-payment-confirmation
-
8 issues opened.
-
Encrypt SPC Credential Identifiers in authentication flows to increase privacy w3c/secure-payment-confirmation#77, by @ianbjacobs.
-
What are requirements when more than one SPC credential matches? w3c/secure-payment-confirmation#69, by @ianbjacobs.
-
When SPC runs in an iframe, what permissions are required? w3c/secure-payment-confirmation#68, by @ianbjacobs.
-
Does the API support timeout? w3c/secure-payment-confirmation#67, by @ianbjacobs.
-
What happens when user cancels during transaction confirmation? w3c/secure-payment-confirmation#66, by @ianbjacobs.
-
Should SPC be invokable outside of a PaymentRequest flow? w3c/secure-payment-confirmation#65, by @stephenmcgruer.
-
Requirements and Good Practices around Unenrollment w3c/secure-payment-confirmation#63, by @ianbjacobs.
-
Add profile identifier to payment credential structure to support credential fetching? w3c/secure-payment-confirmation#62, by @ianbjacobs.
-
-
4 issues closed.
-
Unable to "decipher" sequence diagram w3c/secure-payment-confirmation#41.
-
Include a field for the RP to provide routing information w3c/secure-payment-confirmation#21.
-
The instrument ID should not be easily usable by the merchant to track the user w3c/secure-payment-confirmation#24.
-
Allow user to request that each instrument have its own credential w3c/secure-payment-confirmation#43.
-
-
16 issues received 38 new comments.
-
Should SPC be invokable outside of a PaymentRequest flow? w3c/secure-payment-confirmation#65 (8 comments by @adrianhopebailie, @cyberphone, @ianbjacobs, @SensibleWood, @stephenmcgruer)
-
Does the API support timeout? w3c/secure-payment-confirmation#67 (5 comments by @ianbjacobs, @rsolomakhin, @SensibleWood, @stephenmcgruer)
-
Encrypt SPC Credential Identifiers in authentication flows to increase privacy w3c/secure-payment-confirmation#77 (3 comments by @ianbjacobs, @rsolomakhin, @stephenmcgruer)
-
Provide support for Out of Band Authentication to a secondary device w3c/secure-payment-confirmation#30 (3 comments by @Goosth, @ianbjacobs)
-
Suggestion to enable Frictionless Flows w3c/secure-payment-confirmation#34 (3 comments by @Goosth, @ianbjacobs)
-
When SPC runs in an iframe, what permissions are required? w3c/secure-payment-confirmation#68 (3 comments by @ianbjacobs, @stephenmcgruer)
-
Using CredentialsContainer.get() instead of Payment Request API w3c/secure-payment-confirmation#56 (3 comments by @adrianhopebailie, @equalsJeffH, @tblachowicz)
-
Clarify cardinality between PaymentCredential and payment instruments w3c/secure-payment-confirmation#13 (2 comments by @ianbjacobs)
-
Include a field for the RP to provide routing information w3c/secure-payment-confirmation#21 (1 comment by @ianbjacobs)
-
The instrument ID should not be easily usable by the merchant to track the user w3c/secure-payment-confirmation#24 (1 comment by @ianbjacobs)
-
Allow user to request that each instrument have its own credential w3c/secure-payment-confirmation#43 (1 comment by @ianbjacobs)
-
FIDO Credential ID vs Payment Instrument ID w3c/secure-payment-confirmation#49 (1 comment by @ianbjacobs)
-
What happens when user cancels during transaction confirmation? w3c/secure-payment-confirmation#66 (1 comment by @stephenmcgruer)
-
Requirements and Good Practices around Unenrollment w3c/secure-payment-confirmation#63 (1 comment by @ianbjacobs)
-
-
10 pull requests opened.
-
Allow for dynamic binding of instrument w3c/secure-payment-confirmation#78, by @ianbjacobs.
-
Update requirements.md w3c/secure-payment-confirmation#76, by @ianbjacobs.
-
Update requirements.md w3c/secure-payment-confirmation#75, by @ianbjacobs.
-
Question regarding feature detection w3c/secure-payment-confirmation#74, by @jcemer-stripe.
-
Add user-activation note to requirements.md w3c/secure-payment-confirmation#73, by @stephenmcgruer.
-
Comments/questions on requirements.md w3c/secure-payment-confirmation#72, by @stephenmcgruer.
-
Update requirements.md w3c/secure-payment-confirmation#71, by @tblachowicz.
-
Clearer benefit/feature descriptions w3c/secure-payment-confirmation#70, by @ianbjacobs.
-
Update explainer with cross-origin notes w3c/secure-payment-confirmation#64, by @stephenmcgruer.
-
Update developer guide for Origin Trial v0.2 w3c/secure-payment-confirmation#61, by @stephenmcgruer.
-
-
5 pull requests merged.
-
Clearer benefit/feature descriptions w3c/secure-payment-confirmation#70.
-
Update requirements.md w3c/secure-payment-confirmation#76.
-
Update explainer with cross-origin notes w3c/secure-payment-confirmation#64.
-
Add some draft user stories w3c/secure-payment-confirmation#60.
-
Update developer guide for Origin Trial v0.2 w3c/secure-payment-confirmation#61.
-
-
2 pull requests closed.
-
Update requirements.md w3c/secure-payment-confirmation#75.
-
Add user-activation note to requirements.md w3c/secure-payment-confirmation#73.
-
-
10 pull requests received 68 new comments.
-
Update requirements.md w3c/secure-payment-confirmation#71 (26 comments by @ianbjacobs, @stephenmcgruer, @tblachowicz)
-
Comments/questions on requirements.md w3c/secure-payment-confirmation#72 (9 comments by @ianbjacobs, @stephenmcgruer)
-
Add some draft user stories w3c/secure-payment-confirmation#60 (9 comments by @Goosth, @ianbjacobs, @stephenmcgruer)
-
Clearer benefit/feature descriptions w3c/secure-payment-confirmation#70 (8 comments by @Goosth, @ianbjacobs)
-
Add user-activation note to requirements.md w3c/secure-payment-confirmation#73 (5 comments by @ianbjacobs, @rsolomakhin, @stephenmcgruer)
-
Update explainer with cross-origin notes w3c/secure-payment-confirmation#64 (4 comments by @ianbjacobs, @rsolomakhin, @stephenmcgruer)
-
Update developer guide for Origin Trial v0.2 w3c/secure-payment-confirmation#61 (4 comments by @dontcallmedom, @ianbjacobs, @stephenmcgruer, @w3cbot)
-
Allow for dynamic binding of instrument w3c/secure-payment-confirmation#78 (1 comment by @ianbjacobs)
-
w3c/payment-request
-
3 issues closed.
-
Missing language/locale negotiation mechanism w3c/payment-request#946.
-
Add dir/lang member on dictionaries whose content is displayed in browser UI w3c/payment-request#327.
-
Google Pay disappears from payment methods list w3c/payment-request#935.
-
-
5 issues received 15 new comments.
-
Localization and string metadata for descriptions w3c/payment-request#948 (3 comments by @marcoscaceres, @xfq)
-
Missing language/locale negotiation mechanism w3c/payment-request#946 (3 comments by @aphillips, @ianbjacobs, @marcoscaceres)
-
Richer negotiation re: address redaction? w3c/payment-request#842 (3 comments by @duerst, @ianbjacobs, @samuelweiler)
-
Google Pay disappears from payment methods list w3c/payment-request#935 (1 comment by @marcoscaceres)
-
3 pull requests opened.
-
looks like a minor typo in the example code w3c/payment-request#958, by @dret.
-
Remove modifiers w3c/payment-request#957, by @marcoscaceres.
-
Derive direction from document element too w3c/payment-request#956, by @marcoscaceres.
-
-
3 pull requests merged.
-
looks like a minor typo in the example code w3c/payment-request#958.
-
Derive direction from document element too w3c/payment-request#956.
-
Drop PaymentAddress, shipping + billing address support w3c/payment-request#955.
-
-
4 pull requests closed.
-
Remove modifiers w3c/payment-request#957.
-
Add optional description to PaymentShippingOption w3c/payment-request#910.
-
Allow incremental request of billing and shipping address w3c/payment-request#873.
-
Add regionCode attribute to PaymentAddress (1.1) w3c/payment-request#836.
-
-
7 pull requests received 40 new comments.
-
Derive direction from document element too w3c/payment-request#956 (14 comments by @aphillips, @ianbjacobs, @marcoscaceres)
-
Drop PaymentAddress, shipping + billing address support w3c/payment-request#955 (12 comments by @ianbjacobs, @jcayzac, @marcoscaceres, @rayankans, @rsolomakhin, @sideshowbarker)
-
Remove modifiers w3c/payment-request#957 (9 comments by @ianbjacobs, @marcoscaceres, @stephenmcgruer)
-
looks like a minor typo in the example code w3c/payment-request#958 (2 comments by @marcoscaceres, @w3cbot)
-
Add optional description to PaymentShippingOption w3c/payment-request#910 (1 comment by @marcoscaceres)
-
Allow incremental request of billing and shipping address w3c/payment-request#873 (1 comment by @marcoscaceres)
-
Add regionCode attribute to PaymentAddress (1.1) w3c/payment-request#836 (1 comment by @marcoscaceres)
-
w3c/web-based-payment-handler
-
1 issue received 2 new comments.
-
Remove "instrument" concept from PaymentManager w3c/web-based-payment-handler#371 (2 comments by @jcayzac)
-
-
1 pull request opened.
-
Remove support for address, contact info from PR API (align with pull request 955) w3c/web-based-payment-handler#389, by @ianbjacobs.
-
-
1 pull request merged.
-
Remove support for address, contact info from PR API (align with pull request 955) w3c/web-based-payment-handler#389.
-
-
1 pull request received 6 new comments.
-
Remove support for address, contact info from PR API (align with pull request 955) w3c/web-based-payment-handler#389 (6 comments by @ianbjacobs, @rsolomakhin)
-
TR publications
-
1 document published.
-
Payment Handler API published as a Working Draft. History of Payment Handler API
-
Participants
-
2 chairs appointed.
-
Nick Telford-Reed became a chair.
-
Nick Telford-Reed became a chair.
-
-
2 chairs stepped down.
-
Nick Telford-Reed stepped down as a chair.
-
Nick Telford-Reed stepped down as a chair.
-
-
12 participants joined.
-
Sam Tang (Airbnb Inc) joined.
-
Douglas Fisher (Visa) joined.
-
Christian Aabye (Visa) joined.
-
BASTIEN LATGE (W3C Invited Experts) joined.
-
werner bruinings (American Express Company) joined.
-
Amy Slack (American Express Company) joined.
-
Praveena Subrahmanyam (Airbnb Inc) joined.
-
Christina Hulka (W3C Invited Experts) joined.
-
Gustavo Kok (Netflix Inc.) joined.
-
Thierry Locard (Netflix Inc.) joined.
-
Nick Telford-Reed (W3C Invited Experts) joined.
-
Nick Telford-Reed (W3C) joined.
-
-
5 participants left.
-
Danyao Wang (Google LLC) left.
-
Vaishali Bulusu (American Express Company) left.
-
Jaromir Divilek (American Express Company) left.
-
Nick Telford-Reed (W3C) left.
-
Nick Telford-Reed (W3C) left.
-
GitHub
w3c/payment-request
-
5 issues closed.
-
Note about localization of payment sheet w3c/payment-request#952.
-
Non-US examples w3c/payment-request#950.
-
ISO 4217 note commentary w3c/payment-request#949.
-
Update reference for ISO 3166-2:2013 w3c/payment-request#945.
-
Use different example of ISO country subdivision code? w3c/payment-request#947.
-
-
5 issues received 13 new comments.
-
ISO 4217 note commentary w3c/payment-request#949 (6 comments by @aphillips, @ianbjacobs, @marcoscaceres)
-
Note about localization of payment sheet w3c/payment-request#952 (2 comments by @aphillips, @marcoscaceres)
-
Split shipping address from Payment Request API 1.0 w3c/payment-request#939 (2 comments by @danyao, @rsolomakhin)
-
-
3 pull requests opened.
-
Drop PaymentAddress, shipping + billing address support w3c/payment-request#955, by @ianbjacobs.
-
Editorial: Editor update w3c/payment-request#954, by @ianbjacobs.
-
Editorial: Different regionCode example w3c/payment-request#953, by @ianbjacobs.
-
-
3 pull requests merged.
-
Recommend Payment UI matches doc's language w3c/payment-request#944.
-
Editorial: Editor update w3c/payment-request#954.
-
Editorial: Different regionCode example w3c/payment-request#953.
-
-
4 pull requests received 28 new comments.
-
Editorial: diversify currencies of examples w3c/payment-request#943 (11 comments by @aphillips, @ianbjacobs, @marcoscaceres)
-
Recommend Payment UI matches doc's language w3c/payment-request#944 (10 comments by @aphillips, @ianbjacobs, @marcoscaceres, @stephenmcgruer)
-
Drop PaymentAddress, shipping + billing address support w3c/payment-request#955 (5 comments by @danyao, @ianbjacobs, @marcoscaceres)
-
Editorial: use unicode name/code for currencies in note w3c/payment-request#942 (2 comments by @ianbjacobs, @marcoscaceres)
-
w3c/secure-payment-confirmation
-
8 issues opened.
-
Enrollment should not interrupt payment response w3c/secure-payment-confirmation#59, by @ianbjacobs.
-
Remove fallbackUrl from explainer w3c/secure-payment-confirmation#57, by @stephenmcgruer.
-
Using CredentialsContainer.get() instead of Payment Request API w3c/secure-payment-confirmation#56, by @tblachowicz.
-
Authentication versus Authorization w3c/secure-payment-confirmation#52, by @cyberphone.
-
Integrating SPC with Open Banking w3c/secure-payment-confirmation#51, by @cyberphone.
-
Support for A2A payments w3c/secure-payment-confirmation#50, by @cyberphone.
-
FIDO Credential ID vs Payment Instrument ID w3c/secure-payment-confirmation#49, by @tblachowicz.
-
Rich merchant details displayed in the payment confirmation dialog w3c/secure-payment-confirmation#48, by @tblachowicz.
-
-
3 issues closed.
-
How to include the transaction details in the FIDO/WebAuthn assertion w3c/secure-payment-confirmation#23.
-
Support for A2A payments w3c/secure-payment-confirmation#50.
-
Authentication versus Authorization w3c/secure-payment-confirmation#52.
-
-
8 issues received 38 new comments.
-
FIDO Credential ID vs Payment Instrument ID w3c/secure-payment-confirmation#49 (18 comments by @adrianhopebailie, @cyberphone, @danyao, @Goosth, @ianbjacobs, @tblachowicz)
-
Remove fallbackUrl from explainer w3c/secure-payment-confirmation#57 (8 comments by @ianbjacobs, @rsolomakhin, @stephenmcgruer, @tblachowicz)
-
Integrating SPC with Open Banking w3c/secure-payment-confirmation#51 (4 comments by @cyberphone, @SensibleWood)
-
Using CredentialsContainer.get() instead of Payment Request API w3c/secure-payment-confirmation#56 (3 comments by @adrianhopebailie, @stephenmcgruer, @tblachowicz)
-
How to include the transaction details in the FIDO/WebAuthn assertion w3c/secure-payment-confirmation#23 (2 comments by @danyao, @ianbjacobs)
-
Allow enrollment outside of transaction flow w3c/secure-payment-confirmation#44 (1 comment by @tblachowicz)
-
-
3 pull requests opened.
-
Add some draft user stories w3c/secure-payment-confirmation#60, by @ianbjacobs.
-
[Explainer] Mark `fallbackUrl` as deprecated w3c/secure-payment-confirmation#58, by @stephenmcgruer.
-
Update scope.md w3c/secure-payment-confirmation#55, by @tblachowicz.
-
-
3 pull requests merged.
-
[Explainer] Mark `fallbackUrl` as deprecated w3c/secure-payment-confirmation#58.
-
Update scope.md w3c/secure-payment-confirmation#55.
-
FAQ: Can the party that calls SPC validate the assertion even if not the RP? w3c/secure-payment-confirmation#36.
-
-
1 pull request received 1 new comment.
w3c/web-based-payment-handler
-
5 pull requests opened.
-
generate WD snapshot w3c/web-based-payment-handler#388, by @deniak.
-
Editorial: fix up HTML xrefs w3c/web-based-payment-handler#387, by @marcoscaceres.
-
chore: migrate to spec-prod w3c/web-based-payment-handler#386, by @marcoscaceres.
-
fix: replace deprecated `wg` with `group` w3c/web-based-payment-handler#385, by @saschanaz.
-
Replace void with undefined in Web IDL w3c/web-based-payment-handler#384, by @foolip.
-
-
5 pull requests merged.
-
generate WD snapshot w3c/web-based-payment-handler#388.
-
Editorial: fix up HTML xrefs w3c/web-based-payment-handler#387.
-
chore: migrate to spec-prod w3c/web-based-payment-handler#386.
-
Editorial: Align with Web IDL specification w3c/web-based-payment-handler#377.
-
Replace void with undefined in Web IDL w3c/web-based-payment-handler#384.
-
-
1 pull request closed.
-
fix: replace deprecated `wg` with `group` w3c/web-based-payment-handler#385.
-
-
2 pull requests received 5 new comments.
-
fix: replace deprecated `wg` with `group` w3c/web-based-payment-handler#385 (3 comments by @foolip, @marcoscaceres, @saschanaz)
-
Replace void with undefined in Web IDL w3c/web-based-payment-handler#384 (2 comments by @foolip, @saschanaz)
-
w3c/payment-method-id
-
1 issue opened.
-
Clarify security check for URL-based payment method identifier w3c/payment-method-id#65, by @fred-wang.
-
-
1 issue received 2 new comments.
-
Clarify security check for URL-based payment method identifier w3c/payment-method-id#65 (2 comments by @fred-wang, @rsolomakhin)
-
Participants
-
14 participants joined.
-
Kincaid O'Neil (Coil Technologies, Inc.) joined.
-
Tom Bellenger (Visa) joined.
-
Shyam Sheth (Google LLC) joined.
-
Stephen McGruer (Google LLC) joined.
-
Benjamin Tidor (Stripe) joined.
-
Denis Lesieur (Worldline) joined.
-
Jean-Michel GIRARD (Worldline) joined.
-
Anne Pouillard (Worldline) joined.
-
Olivier Maas (Worldline) joined.
-
Marcos Caceres (Apple Inc.) joined.
-
Nick Shearer (Apple Inc.) joined.
-
Bruno Van Haetsdaele (Oxlin) joined.
-
Gildas Le Louarn (Oxlin) joined.
-
Mathieu Hofman (W3C Invited Experts) joined.
-
-
6 participants left.
-
Alex Liu (Airbnb Inc) left.
-
Arvind Santhanaraman (Visa) left.
-
Cheryl Mish (Discover Financial Services LLC) left.
-
Clément Warnier de Wailly (CANTON CONSULTING) left.
-
Marcos Caceres (Apple Inc.) left.
-
Mathieu Hofman (W3C Invited Experts) left.
-
-
2 organizations joined.
-
Worldline joined.
-
Oxlin joined.
-
GitHub
w3c/payment-request
-
9 issues opened.
-
Note about localization of payment sheet w3c/payment-request#952, by @aphillips.
-
Localizability of errors w3c/payment-request#951, by @aphillips.
-
Non-US examples w3c/payment-request#950, by @aphillips.
-
ISO 4217 note commentary w3c/payment-request#949, by @aphillips.
-
Localization and string metadata for descriptions w3c/payment-request#948, by @aphillips.
-
Use different example of ISO country subdivision code? w3c/payment-request#947, by @samuelweiler.
-
Missing language/locale negotiation mechanism w3c/payment-request#946, by @aphillips.
-
Update reference for ISO 3166-2:2013 w3c/payment-request#945, by @samuelweiler.
-
ISO 3166 typo w3c/payment-request#940, by @aphillips.
-
-
1 issue closed.
-
ISO 3166 typo w3c/payment-request#940.
-
-
1 issue reopened.
-
Add dir/lang member on dictionaries whose content is displayed in browser UI w3c/payment-request#327, by @marcoscaceres.
-
-
3 issues received 9 new comments.
-
Split shipping address from Payment Request API 1.0 w3c/payment-request#939 (6 comments by @ianbjacobs, @marcoscaceres, @samuelweiler)
-
-
4 pull requests opened.
-
Recommend Payment UI matches doc's language w3c/payment-request#944, by @marcoscaceres.
-
Editorial: diversify currencies of examples w3c/payment-request#943, by @marcoscaceres.
-
Editorial: use unicode name/code for currencies in note w3c/payment-request#942, by @marcoscaceres.
-
Editorial: Typo fix related to ISO 3166-2 w3c/payment-request#941, by @ianbjacobs.
-
-
3 pull requests merged.
-
Editorial: use unicode name/code for currencies in note w3c/payment-request#942.
-
Editorial: diversify currencies of examples w3c/payment-request#943.
-
Editorial: Typo fix related to ISO 3166-2 w3c/payment-request#941.
-
-
2 pull requests received 10 new comments.
-
Editorial: use unicode name/code for currencies in note w3c/payment-request#942 (8 comments by @ianbjacobs, @marcoscaceres)
-
Editorial: diversify currencies of examples w3c/payment-request#943 (2 comments by @ianbjacobs, @marcoscaceres)
-
w3c/secure-payment-confirmation
-
5 issues opened.
-
Allow enrollment outside of transaction flow w3c/secure-payment-confirmation#44, by @ianbjacobs.
-
Allow user to request that each instrument have its own credential w3c/secure-payment-confirmation#43, by @ianbjacobs.
-
Change payment amount from SPC call within a payment app? w3c/secure-payment-confirmation#42, by @ianbjacobs.
-
Unable to "decipher" sequence diagram w3c/secure-payment-confirmation#41, by @cyberphone.
-
2 issues closed.
-
. w3c/secure-payment-confirmation#45.
-
Test build w3c/secure-payment-confirmation#37.
-
-
4 issues received 5 new comments.
-
Change payment amount from SPC call within a payment app? w3c/secure-payment-confirmation#42 (2 comments by @danyao, @ianbjacobs)
-
Are Client-side Discoverable Credentials (aka Resident Keys) off the table in this proposal? w3c/secure-payment-confirmation#31 (1 comment by @ianbjacobs)
-
-
2 pull requests opened.
-
Update developer guide with origin trial information w3c/secure-payment-confirmation#47, by @nickburris.
-
Update developer guide w3c/secure-payment-confirmation#46, by @nickburris.
-
-
2 pull requests merged.
-
Update developer guide with origin trial information w3c/secure-payment-confirmation#47.
-
Update developer guide w3c/secure-payment-confirmation#46.
-
-
1 pull request received 1 new comment.
w3c/webpayments
-
2 issues closed.
-
Visual Identity for Web Payments w3c/webpayments#250.
-
Overview document figure 5 w3c/webpayments#171.
-
-
2 issues received 2 new comments.
-
1 pull request opened.
-
Fix some spelling mistakes w3c/webpayments#258, by @barseghyanartur.
-
-
1 pull request merged.
-
Fix some spelling mistakes w3c/webpayments#258.
-
-
1 pull request received 2 new comments.
w3c/payment-method-manifest
-
1 issue closed.
-
Renaming master branch w3c/payment-method-manifest#46.
-
-
1 issue received 1 new comment.
Participants
-
4 participants joined.
-
Sebastian Elfors (Yubico) joined.
-
Chris Wilson (Google LLC) joined.
-
Ishna Neamatullah (Google LLC) joined.
-
Vaishali Bulusu (American Express Company) joined.
-
-
1 participant left.
-
Anne Pouillard (Worldline) left.
-
GitHub
w3c/secure-payment-confirmation
-
3 issues opened.
-
Specification of the signature w3c/secure-payment-confirmation#40, by @tblachowicz.
-
Using PaymentCredential for vanilla WebAuthn authentication. w3c/secure-payment-confirmation#39, by @tblachowicz.
-
Similar functionality for transaction confirmation in online banking applications? w3c/secure-payment-confirmation#38, by @p-.
-
-
3 issues closed.
-
Who is the actual RP? w3c/secure-payment-confirmation#35.
-
Consider EMV for the Web w3c/secure-payment-confirmation#32.
-
Similar functionality for transaction confirmation in online banking applications? w3c/secure-payment-confirmation#38.
-
-
8 issues received 22 new comments.
-
Using PaymentCredential for vanilla WebAuthn authentication. w3c/secure-payment-confirmation#39 (12 comments by @btidor-stripe, @Goosth, @kenrb, @mountainhippo, @SensibleWood, @tblachowicz)
-
Similar functionality for transaction confirmation in online banking applications? w3c/secure-payment-confirmation#38 (3 comments by @Goosth, @ianbjacobs, @p-)
-
Specification of the signature w3c/secure-payment-confirmation#40 (2 comments by @btidor-stripe, @tblachowicz)
-
payment Method versus payment Instruments w3c/secure-payment-confirmation#33 (1 comment by @cyberphone)
-
Does the browser receive credential IDs or instrument IDs? w3c/secure-payment-confirmation#10 (1 comment by @tblachowicz)
-
w3c/payment-request
-
1 issue opened.
-
Split shipping address from Payment Request API 1.0 w3c/payment-request#939, by @danyao.
-
-
2 issues closed.
-
Provide better mapping between PaymentAddress and HTML5 autofill w3c/payment-request#505.
-
Spec is silent on its role in facilitating arbitrary communication between top level contexts w3c/payment-request#936.
-
-
5 issues received 6 new comments.
-
Allow user activation to be delegated to a child frame to trigger request.show() w3c/payment-request#917 (2 comments by @danyao, @mustaqahmed)
-
Provide better mapping between PaymentAddress and HTML5 autofill w3c/payment-request#505 (1 comment by @marcoscaceres)
-
Split shipping address from Payment Request API 1.0 w3c/payment-request#939 (1 comment by @marcoscaceres)
-
Spec is silent on its role in facilitating arbitrary communication between top level contexts w3c/payment-request#936 (1 comment by @Sauski)
-
-
1 pull request merged.
-
Added based on issue 936 w3c/payment-request#937.
-
w3c/payment-method-manifest
-
1 issue opened.
-
Renaming master branch w3c/payment-method-manifest#46, by @ianbjacobs.
-
-
1 issue received 1 new comment.
Participants
-
2 participants joined.
-
Huaqi Shan (China Mobile Communications Corporation) joined.
-
Song XU (China Mobile Communications Corporation) joined.
-
-
2 participants left.
-
Jules Renier (CANTON CONSULTING) left.
-
Sofiane Boumedine (CANTON CONSULTING) left.
-
-
1 organization left.
-
BlueSnap left.
-
GitHub
w3c/payment-request
-
1 issue opened.
-
Spec is silent on its role in facilitating arbitrary communication between top level contexts w3c/payment-request#936, by @Sauski.
-
-
2 issues received 18 new comments.
-
Spec is silent on its role in facilitating arbitrary communication between top level contexts w3c/payment-request#936 (16 comments by @danyao, @hofman-stripe, @ianbjacobs, @samuelweiler, @Sauski)
-
Richer negotiation re: address redaction? w3c/payment-request#842 (2 comments by @samuelweiler, @Sauski)
-
-
1 pull request opened.
-
Added based on issue 936 w3c/payment-request#937, by @ianbjacobs.
-
-
1 pull request received 2 new comments.
w3c/web-based-payment-handler
-
2 issues opened.
-
Restrict MIME types of Web Payment App navigation w3c/web-based-payment-handler#383, by @maxlgu.
-
Updates Timeline w3c/web-based-payment-handler#382, by @RomanKaliupin.
-
-
2 issues received 4 new comments.
-
Restrict MIME types of Web Payment App navigation w3c/web-based-payment-handler#383 (2 comments by @maxlgu, @rsolomakhin)
-
w3c/webpayments
-
1 issue received 1 new comment.