Web Payments Working Group - Activity in 2020
No matches.
TR publications
-
2 documents published.
-
Payment Request API published as a Candidate Recommendation Snapshot. History of Payment Request API
-
The MerchantValidationEvent interface published as a Note. History of The MerchantValidationEvent interface
-
Participants
-
1 participant joined.
-
Babu Muttineni (Yahoo Holdings Inc.) joined.
-
-
1 organization joined.
-
Verizon joined.
-
GitHub
w3c/web-based-payment-handler
-
3 issues opened.
-
Payment Instrument architecture clarification w3c/web-based-payment-handler#381, by @RomanKaliupin.
-
Require user gesture before installation payment app that supports a standardized payment method? w3c/web-based-payment-handler#380, by @ianbjacobs.
-
Basic-credit security issue w3c/web-based-payment-handler#379, by @RomanKaliupin.
-
-
2 issues received 29 new comments.
-
Payment Instrument architecture clarification w3c/web-based-payment-handler#381 (16 comments by @ianbjacobs, @RomanKaliupin, @rsolomakhin)
-
Basic-credit security issue w3c/web-based-payment-handler#379 (13 comments by @ianbjacobs, @RomanKaliupin, @rsolomakhin)
-
w3c/webpayments
-
1 issue opened.
-
QR use cases w3c/webpayments#257, by @mountainhippo.
-
-
1 issue received 2 new comments.
w3c/payment-request
-
1 issue opened.
-
Google Pay disappears from payment methods list w3c/payment-request#935, by @kersov.
-
-
2 issues received 7 new comments.
-
Google Pay disappears from payment methods list w3c/payment-request#935 (6 comments by @danyao, @ianbjacobs, @kersov, @rsolomakhin)
-
w3c/secure-payment-confirmation
-
1 issue received 1 new comment.
Participants
-
2 participants joined.
-
Lauren Jones (Huawei) joined.
-
Shuxin Ouyang (Huawei) joined.
-
GitHub
w3c/secure-payment-confirmation
-
1 issue opened.
-
Test build w3c/secure-payment-confirmation#37, by @yackermann.
-
-
1 issue closed.
-
Allow the original RP of a PaymentCredential to update the payment instrument details w3c/secure-payment-confirmation#27.
-
-
4 issues received 13 new comments.
-
How to handle stale displayName and icon? w3c/secure-payment-confirmation#14 (5 comments by @adrianhopebailie, @btidor-stripe, @danyao, @Goosth)
-
Suggestion to enable Frictionless Flows w3c/secure-payment-confirmation#34 (5 comments by @danyao, @Goosth, @ianbjacobs)
-
Allow the original RP of a PaymentCredential to update the payment instrument details w3c/secure-payment-confirmation#27 (2 comments by @danyao, @ianbjacobs)
-
-
1 pull request opened.
-
FAQ: Can the party that calls SPC validate the assertion even if not the RP? w3c/secure-payment-confirmation#36, by @ianbjacobs.
-
-
1 pull request received 3 new comments.
-
FAQ: Can the party that calls SPC validate the assertion even if not the RP? w3c/secure-payment-confirmation#36 (3 comments by @danyao, @ianbjacobs)
-
w3c/payment-request
-
1 issue opened.
-
Permissible data changes during a retry w3c/payment-request#933, by @SECtim.
-
-
1 issue closed.
-
Permissible data changes during a retry w3c/payment-request#933.
-
-
1 issue received 2 new comments.
-
Permissible data changes during a retry w3c/payment-request#933 (2 comments by @marcoscaceres, @SECtim)
-
-
1 pull request opened.
-
Editorial: describe purpose of retry() w3c/payment-request#934, by @marcoscaceres.
-
-
1 pull request merged.
-
Editorial: describe purpose of retry() w3c/payment-request#934.
-
-
1 pull request received 3 new comments.
-
Editorial: describe purpose of retry() w3c/payment-request#934 (3 comments by @ianbjacobs, @marcoscaceres, @SECtim)
-
w3c/web-based-payment-handler
-
1 issue opened.
-
Leftovers regarding modifiers in CanMakePaymentEvents w3c/web-based-payment-handler#378, by @SECtim.
-
Participants
-
5 participants joined.
-
Chris Wood (W3C Invited Experts) joined.
-
Ryan Cliffford (Fiserv) joined.
-
Krish Yallam (Barclays Bank PLC) joined.
-
Lawrence Cheng (Barclays Bank PLC) joined.
-
Aanchal Malhotra (Ripple) joined.
-
-
1 participant left.
-
Adam Solove (Stripe) left.
-
-
2 organizations joined.
-
Barclays Bank PLC joined.
-
Ripple joined.
-
GitHub
w3c/secure-payment-confirmation
-
7 issues opened.
-
Who is the actual RP? w3c/secure-payment-confirmation#35, by @cyberphone.
-
Suggestion to enable Frictionless Flows w3c/secure-payment-confirmation#34, by @Goosth.
-
payment Method versus payment Instruments w3c/secure-payment-confirmation#33, by @cyberphone.
-
Consider EMV for the Web w3c/secure-payment-confirmation#32, by @cyberphone.
-
Are Client-side Discoverable Credentials (aka Resident Keys) off the table in this proposal? w3c/secure-payment-confirmation#31, by @SensibleWood.
-
Provide support for Out of Band Authentication to a secondary device w3c/secure-payment-confirmation#30, by @Goosth.
-
How can SPC be used in conjunction with a frictionless 3DS flow? w3c/secure-payment-confirmation#29, by @ianbjacobs.
-
-
2 issues closed.
-
Instrument ID should never leave the payment handler or browser w3c/secure-payment-confirmation#22.
-
payment Method versus payment Instruments w3c/secure-payment-confirmation#33.
-
-
3 issues received 6 new comments.
-
How can SPC be used in conjunction with a frictionless 3DS flow? w3c/secure-payment-confirmation#29 (3 comments by @Goosth, @ianbjacobs)
-
payment Method versus payment Instruments w3c/secure-payment-confirmation#33 (2 comments by @ianbjacobs)
-
PROPOSAL: Alternative Secure Payment Confirmation Flow w3c/secure-payment-confirmation#15 (1 comment by @Goosth)
-
-
1 pull request closed.
-
Payment Handlers w3c/secure-payment-confirmation#9.
-
-
1 pull request received 1 new comment.
w3c/payment-request
-
2 issues closed.
-
show() should consume user activation w3c/payment-request#886.
-
Mark hasEnrolledInstrument() at risk? w3c/payment-request#926.
-
-
1 issue received 3 new comments.
-
Richer negotiation re: address redaction? w3c/payment-request#842 (3 comments by @EricMwobobia, @ianbjacobs, @pes10k)
-
-
1 pull request opened.
-
Add hasEnrolledInstrument() again w3c/payment-request#931, by @marcoscaceres.
-
-
2 pull requests merged.
-
Consume user activation w3c/payment-request#916.
-
Remove hasEnrolledInstrument() from version 1.0 w3c/payment-request#930.
-
-
2 pull requests received 3 new comments.
-
Remove hasEnrolledInstrument() from version 1.0 w3c/payment-request#930 (2 comments by @marcoscaceres)
-
Participants
-
2 participants joined.
-
Liam Kennedy (Fiserv) joined.
-
Marcos Caceres (Apple Inc.) joined.
-
-
1 participant left.
-
Adam Roach (Mozilla Foundation) left.
-
GitHub
w3c/payment-request
-
3 issues opened.
-
What should we do with MerchantValidationEvent? w3c/payment-request#927, by @marcoscaceres.
-
Mark hasEnrolledInstrument() at risk? w3c/payment-request#926, by @marcoscaceres.
-
Proposal: drop `allowpaymentrequest` attribute w3c/payment-request#925, by @marcoscaceres.
-
-
3 issues closed.
-
What should we do with MerchantValidationEvent? w3c/payment-request#927.
-
How do the payer and payee agree on the payment obligation as part of the flow? w3c/payment-request#113.
-
Proposal: drop `allowpaymentrequest` attribute w3c/payment-request#925.
-
-
1 issue reopened.
-
Richer negotiation re: address redaction? w3c/payment-request#842, by @ianbjacobs.
-
-
7 issues received 13 new comments.
-
What should we do with MerchantValidationEvent? w3c/payment-request#927 (3 comments by @cyberphone, @ianbjacobs)
-
Proposal: drop `allowpaymentrequest` attribute w3c/payment-request#925 (3 comments by @danyao, @ianbjacobs)
-
How do the payer and payee agree on the payment obligation as part of the flow? w3c/payment-request#113 (2 comments by @adrianhopebailie, @ianbjacobs)
-
Add dir/lang member on dictionaries whose content is displayed in browser UI w3c/payment-request#327 (2 comments by @ianbjacobs, @r12a)
-
Allow user activation to be delegated to a child frame to trigger request.show() w3c/payment-request#917 (1 comment by @mustaqahmed)
-
-
4 pull requests opened.
-
Remove hasEnrolledInstrument() from version 1.0 w3c/payment-request#930, by @marcoscaceres.
-
Remove merchant validation w3c/payment-request#929, by @marcoscaceres.
-
Deprecate allowpaymentrequest attribute w3c/payment-request#928, by @marcoscaceres.
-
Create azure.yml w3c/payment-request#924, by @johnuno11.
-
-
2 pull requests merged.
-
Remove merchant validation w3c/payment-request#929.
-
Deprecate allowpaymentrequest attribute w3c/payment-request#928.
-
-
1 pull request closed.
-
Create azure.yml w3c/payment-request#924.
-
-
4 pull requests received 17 new comments.
-
Deprecate allowpaymentrequest attribute w3c/payment-request#928 (7 comments by @clelland, @danyao, @ianbjacobs, @marcoscaceres)
-
Remove hasEnrolledInstrument() from version 1.0 w3c/payment-request#930 (4 comments by @danyao, @michael-n-cooper)
-
w3c/secure-payment-confirmation
-
3 issues opened.
-
Clarify security properties of the cryptogram w3c/secure-payment-confirmation#28, by @btidor-stripe.
-
Allow the original RP of a PaymentCredential to update the payment instrument details w3c/secure-payment-confirmation#27, by @danyao.
-
SPC should not constrain how WebAuthn nonce is created w3c/secure-payment-confirmation#26, by @ianbjacobs.
-
-
1 issue received 1 new comment.
-
Clarify cardinality between PaymentCredential and payment instruments w3c/secure-payment-confirmation#13 (1 comment by @erhardbrand)
-
-
1 pull request opened.
-
Update API and examples w3c/secure-payment-confirmation#25, by @nickburris.
-
-
1 pull request merged.
-
Update API and examples w3c/secure-payment-confirmation#25.
-
w3c/web-based-payment-handler
-
1 issue received 1 new comment.
-
Collecting use cases that require payment handler window to be 1P context w3c/web-based-payment-handler#370 (1 comment by @ianbjacobs)
-
Participants
-
2 participants joined.
-
Leigh Garner (Discover Financial Services LLC) joined.
-
Robert Martin (Capital One Discover Network) joined.
-
-
1 participant left.
-
Marcos Caceres (Apple Inc.) left.
-
-
1 organization joined.
-
Kodansha, Publishers, Ltd. joined.
-
GitHub
w3c/payment-request
-
1 issue opened.
-
Payment sheet open in new tab when internet connection disconnect w3c/payment-request#923, by @ankushsapkal.
-
-
1 issue closed.
-
Payment sheet open in new tab when internet connection disconnect w3c/payment-request#923.
-
-
1 issue received 6 new comments.
-
Payment sheet open in new tab when internet connection disconnect w3c/payment-request#923 (6 comments by @ankushsapkal, @ianbjacobs, @rsolomakhin)
-
-
1 pull request opened.
-
Editorial: Align with Web IDL specification w3c/payment-request#922, by @autokagami.
-
-
2 pull requests merged.
-
Editorial: Align with Web IDL specification w3c/payment-request#922.
-
Editorial: clarify what sorting code is a bit more w3c/payment-request#921.
-
w3c/secure-payment-confirmation
-
7 issues opened.
-
The instrument ID should not be easily usable by the merchant to track the user w3c/secure-payment-confirmation#24, by @ianbjacobs.
-
How to include the transaction details in the FIDO/WebAuthn assertion w3c/secure-payment-confirmation#23, by @rlin1.
-
Instrument ID should never leave the payment handler or browser w3c/secure-payment-confirmation#22, by @danyao.
-
Include a field for the RP to provide routing information w3c/secure-payment-confirmation#21, by @danyao.
-
PROPOSAL 2: No Payment Handler Flow w3c/secure-payment-confirmation#17, by @adrianhopebailie.
-
Linking PaymentCredentialInstrument with PaymentInstrument/Payment Handler w3c/secure-payment-confirmation#16, by @tblachowicz.
-
PROPOSAL: Alternative Secure Payment Confirmation Flow w3c/secure-payment-confirmation#15, by @adrianhopebailie.
-
-
2 issues closed.
-
What is the purpose of SecurePaymentConfirmationAction? w3c/secure-payment-confirmation#5.
-
Linking PaymentCredentialInstrument with PaymentInstrument/Payment Handler w3c/secure-payment-confirmation#16.
-
-
9 issues received 13 new comments.
-
PROPOSAL 2: No Payment Handler Flow w3c/secure-payment-confirmation#17 (4 comments by @adrianhopebailie, @ianbjacobs, @tblachowicz)
-
Instrument ID should never leave the payment handler or browser w3c/secure-payment-confirmation#22 (2 comments by @ianbjacobs)
-
How to include the transaction details in the FIDO/WebAuthn assertion w3c/secure-payment-confirmation#23 (1 comment by @danyao)
-
The instrument ID should not be easily usable by the merchant to track the user w3c/secure-payment-confirmation#24 (1 comment by @ianbjacobs)
-
PROPOSAL: Alternative Secure Payment Confirmation Flow w3c/secure-payment-confirmation#15 (1 comment by @ianbjacobs)
-
Multiple versions of card art icon? (E.g. to support dark mode) w3c/secure-payment-confirmation#1 (1 comment by @marcoscaceres)
-
How to handle stale displayName and icon? w3c/secure-payment-confirmation#14 (1 comment by @adrianhopebailie)
-
Clarify cardinality between PaymentCredential and payment instruments w3c/secure-payment-confirmation#13 (1 comment by @adrianhopebailie)
-
What is the purpose of SecurePaymentConfirmationAction? w3c/secure-payment-confirmation#5 (1 comment by @adrianhopebailie)
-
-
3 pull requests opened.
-
Update enrollment sequence to match latest API proposal w3c/secure-payment-confirmation#20, by @danyao.
-
Upload sequence diagrams. w3c/secure-payment-confirmation#19, by @danyao.
-
Add a security and privacy questionnaire for TAG review. w3c/secure-payment-confirmation#18, by @danyao.
-
-
3 pull requests merged.
-
Update enrollment sequence to match latest API proposal w3c/secure-payment-confirmation#20.
-
Upload sequence diagrams. w3c/secure-payment-confirmation#19.
-
Add a security and privacy questionnaire for TAG review. w3c/secure-payment-confirmation#18.
-
-
1 pull request received 2 new comments.
w3c/web-based-payment-handler
-
1 pull request opened.
-
Editorial: Align with Web IDL specification w3c/web-based-payment-handler#377, by @autokagami.
-
TR publications
-
1 document published.
-
Web Payments HTTP Messages 1.0 published as a Note. History of Web Payments HTTP Messages 1.0
-
Participants
-
4 participants joined.
-
James Evans-Rong (Fiserv) joined.
-
Matt Lockyer (Fiserv) joined.
-
Anne Pouillard (Worldline) joined.
-
Lucian Lauritz (Fiserv) joined.
-
-
2 organizations joined.
-
Pundi X joined.
-
Fiserv joined.
-
GitHub
w3c/secure-payment-confirmation
-
8 issues opened.
-
How to handle stale displayName and icon? w3c/secure-payment-confirmation#14, by @danyao.
-
Clarify cardinality between PaymentCredential and payment instruments w3c/secure-payment-confirmation#13, by @danyao.
-
Supporting roaming authenticators w3c/secure-payment-confirmation#12, by @jcjones.
-
Does the browser receive credential IDs or instrument IDs? w3c/secure-payment-confirmation#10, by @danyao.
-
Can a merchant ensure that SPC will be used before invoking PR API? w3c/secure-payment-confirmation#8, by @adrianhopebailie.
-
What is the purpose of SecurePaymentConfirmationAction? w3c/secure-payment-confirmation#5, by @adrianhopebailie.
-
Is an issuer hosted payment handler necessary for secure-payment-confirmation flow? w3c/secure-payment-confirmation#4, by @danyao.
-
Multiple versions of card art icon? (E.g. to support dark mode) w3c/secure-payment-confirmation#1, by @danyao.
-
-
6 issues received 12 new comments.
-
Does the browser receive credential IDs or instrument IDs? w3c/secure-payment-confirmation#10 (4 comments by @adrianhopebailie, @btidor-stripe, @danyao)
-
Is an issuer hosted payment handler necessary for secure-payment-confirmation flow? w3c/secure-payment-confirmation#4 (3 comments by @adrianhopebailie, @btidor-stripe)
-
Multiple versions of card art icon? (E.g. to support dark mode) w3c/secure-payment-confirmation#1 (2 comments by @adrianhopebailie, @danyao)
-
Can a merchant ensure that SPC will be used before invoking PR API? w3c/secure-payment-confirmation#8 (1 comment by @danyao)
-
What is the purpose of SecurePaymentConfirmationAction? w3c/secure-payment-confirmation#5 (1 comment by @danyao)
-
-
6 pull requests opened.
-
Typo fix: Sequence, Intentionally w3c/secure-payment-confirmation#11, by @jcjones.
-
Payment Handlers w3c/secure-payment-confirmation#9, by @adrianhopebailie.
-
Add some privacy commentary w3c/secure-payment-confirmation#7, by @adrianhopebailie.
-
Background & multiple instruments w3c/secure-payment-confirmation#6, by @adrianhopebailie.
-
Add API sketch and clarify data structures. w3c/secure-payment-confirmation#3, by @danyao.
-
Add API sketch and clarify data structures. w3c/secure-payment-confirmation#2, by @danyao.
-
-
3 pull requests merged.
-
Add some privacy commentary w3c/secure-payment-confirmation#7.
-
Typo fix: Sequence, Intentionally w3c/secure-payment-confirmation#11.
-
Add API sketch and clarify data structures. w3c/secure-payment-confirmation#3.
-
-
1 pull request closed.
-
Add API sketch and clarify data structures. w3c/secure-payment-confirmation#2.
-
-
4 pull requests received 25 new comments.
-
Add API sketch and clarify data structures. w3c/secure-payment-confirmation#3 (15 comments by @btidor-stripe, @danyao, @marcoscaceres, @rsolomakhin)
-
Background & multiple instruments w3c/secure-payment-confirmation#6 (3 comments by @btidor-stripe, @danyao)
-
Add API sketch and clarify data structures. w3c/secure-payment-confirmation#2 (2 comments by @danyao)
-
w3c/payment-request
-
1 issue opened.
-
check out w3c/payment-request#918, by @deltaone33usa3.
-
-
1 issue closed.
-
check out w3c/payment-request#918.
-
-
1 issue received 3 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)
-
-
3 pull requests opened.
-
Editorial: clarify what sorting code is a bit more w3c/payment-request#921, by @marcoscaceres.
-
Editorial: use 'this' + new syntax w3c/payment-request#920, by @marcoscaceres.
-
Editorial: Feature Policy now Permissions Policy w3c/payment-request#919, by @marcoscaceres.
-
-
2 pull requests merged.
-
Editorial: use 'this' + new syntax w3c/payment-request#920.
-
Editorial: Feature Policy now Permissions Policy w3c/payment-request#919.
-
w3c/web-based-payment-handler
-
2 issues opened.
-
Specify how to construct PaymentRequestDetailsUpdate from PaymentDetailsUpdate w3c/web-based-payment-handler#376, by @danyao.
-
Make Marcos repo admin w3c/web-based-payment-handler#373, by @marcoscaceres.
-
-
2 issues closed.
-
The "triggered by user activation" link is incorrect w3c/web-based-payment-handler#358.
-
Make Marcos repo admin w3c/web-based-payment-handler#373.
-
-
2 issues received 3 new comments.
-
Make Marcos repo admin w3c/web-based-payment-handler#373 (2 comments by @ianbjacobs, @marcoscaceres)
-
Specify how to construct PaymentRequestDetailsUpdate from PaymentDetailsUpdate w3c/web-based-payment-handler#376 (1 comment by @sahel-sh)
-
-
3 pull requests opened.
-
Remove triggered by user activation w3c/web-based-payment-handler#375, by @marcoscaceres.
-
chore: switch to ReSpec auto-publish w3c/web-based-payment-handler#374, by @marcoscaceres.
-
fix: use sequence, not FrozenArray w3c/web-based-payment-handler#372, by @marcoscaceres.
-
-
3 pull requests merged.
-
chore: switch to ReSpec auto-publish w3c/web-based-payment-handler#374.
-
Remove triggered by user activation w3c/web-based-payment-handler#375.
-
fix: use sequence, not FrozenArray w3c/web-based-payment-handler#372.
-
-
2 pull requests received 3 new comments.
-
fix: use sequence, not FrozenArray w3c/web-based-payment-handler#372 (2 comments by @marcoscaceres, @romandev)
-
Participants
-
3 participants joined.
-
Xin Kang (Huawei) joined.
-
Gavin Shenker (Visa) joined.
-
Arvind Santhanaraman (Visa) joined.
-
-
1 participant left.
-
Alan Marshall (Samsung Electronics Co., Ltd.) left.
-
-
1 organization joined.
-
Huawei joined.
-
GitHub
w3c/payment-method-manifest
-
1 issue received 3 new comments.
-
Allow additional properties in manifest w3c/payment-method-manifest#43 (3 comments by @danyao, @marcoscaceres, @rsolomakhin)
-
w3c/webpayments
-
1 pull request opened.
-
Adrianhopebailie patch 1 w3c/webpayments#256, by @deltaone33usa3.
-
-
1 pull request closed.
-
Adrianhopebailie patch 1 w3c/webpayments#256.
-
w3c/payment-request
-
1 issue opened.
-
Allow user activation to be delegated to a child frame to trigger request.show() w3c/payment-request#917, by @danyao.
-
-
1 issue closed.
-
Proposal to make the amount field in PaymentShippingOption optional w3c/payment-request#901.
-
-
2 issues received 3 new comments.
-
Allow user activation to be delegated to a child frame to trigger request.show() w3c/payment-request#917 (2 comments by @danyao, @marcoscaceres)
-
Proposal to make the amount field in PaymentShippingOption optional w3c/payment-request#901 (1 comment by @sahel-sh)
-
-
1 pull request opened.
-
Consume user activation w3c/payment-request#916, by @marcoscaceres.
-
-
1 pull request received 1 new comment.
Participants
-
2 participants joined.
-
Nick Telford-Reed (W3C) joined.
-
Merwan Rodriguez (The Washington Post) joined.
-
-
2 participants left.
-
Merwan Rodriguez (The Washington Post) left.
-
Nick Telford-Reed (W3C) left.
-
-
1 organization joined.
-
The Washington Post joined.
-
-
1 organization left.
-
The Washington Post left.
-
GitHub
w3c/web-based-payment-handler
-
1 issue opened.
-
Remove "instrument" concept from PaymentManager w3c/web-based-payment-handler#371, by @danyao.
-
-
4 issues received 10 new comments.
-
Remove "instrument" concept from PaymentManager w3c/web-based-payment-handler#371 (6 comments by @danyao, @rsolomakhin, @tblachowicz)
-
Specify just-in-time installation behavior? w3c/web-based-payment-handler#346 (2 comments by @ianbjacobs, @tblachowicz)
-
Collecting use cases that require payment handler window to be 1P context w3c/web-based-payment-handler#370 (1 comment by @tblachowicz)
-
Creating a "Wallet" using PaymentHandler? w3c/web-based-payment-handler#368 (1 comment by @cyberphone)
-
w3c/payment-request
-
2 issues opened.
-
Refactoring PaymentRequest w3c/payment-request#914, by @cyberphone.
-
Make "total" and "details" optional w3c/payment-request#912, by @maxlgu.
-
-
6 issues closed.
-
Disallow ambiguous methodData declarations? w3c/payment-request#905.
-
Improve error codes w3c/payment-request#871.
-
Consider adding "national identifier" and "birthdate" as billing fields w3c/payment-request#859.
-
Clarification on payment handler selection in spec w3c/payment-request#904.
-
Refactoring PaymentRequest w3c/payment-request#914.
-
Passing a transaction id to a payment request w3c/payment-request#911.
-
-
9 issues received 24 new comments.
-
Make "total" and "details" optional w3c/payment-request#912 (11 comments by @adrianhopebailie, @ianbjacobs, @marcoscaceres, @maxlgu, @mgiuca, @rsolomakhin)
-
Passing a transaction id to a payment request w3c/payment-request#911 (3 comments by @agektmr, @danyao, @ianbjacobs)
-
Disallow ambiguous methodData declarations? w3c/payment-request#905 (2 comments by @danyao, @marcoscaceres)
-
Consider adding "national identifier" and "birthdate" as billing fields w3c/payment-request#859 (1 comment by @marcoscaceres)
-
-
1 pull request opened.
-
Informative note about role of id attribute w3c/payment-request#913, by @ianbjacobs.
-
-
3 pull requests merged.
-
fix: disallow duplicate PMIs when creating request w3c/payment-request#908.
-
Editorial: Add [[handler]] slot to PaymentRequest w3c/payment-request#909.
-
Informative note about role of id attribute w3c/payment-request#913.
-
-
1 pull request closed.
-
chore: Prepare PR branch w3c/payment-request#860.
-
-
4 pull requests received 15 new comments.
-
fix: disallow duplicate PMIs when creating request w3c/payment-request#908 (6 comments by @danyao, @marcoscaceres, @rsolomakhin)
-
Informative note about role of id attribute w3c/payment-request#913 (5 comments by @ianbjacobs, @marcoscaceres)
-
Add optional description to PaymentShippingOption w3c/payment-request#910 (3 comments by @marcoscaceres, @rsolomakhin)
-
w3c/webpayments
-
1 pull request received 1 new comment.
w3c/payment-method-manifest
-
1 issue closed.
-
Remove "*" functionality for supported_origins w3c/payment-method-manifest#42.
-
-
1 pull request opened.
-
Remove "*" functionality for supported_origins w3c/payment-method-manifest#45, by @danyao.
-
-
1 pull request merged.
-
Remove "*" functionality for supported_origins w3c/payment-method-manifest#45.
-
-
1 pull request received 3 new comments.
-
Remove "*" functionality for supported_origins w3c/payment-method-manifest#45 (3 comments by @danyao, @rsolomakhin)
-
Participants
-
5 participants joined.
-
Paul Madsen (Hedera Hashgraph) joined.
-
Brett McDowell (Hedera Hashgraph) joined.
-
Erhard Brand (Entersekt) joined.
-
Arno Van Der Merwe (Entersekt) joined.
-
Rolf Lindemann (OneSpan) joined.
-
-
1 organization joined.
-
OneSpan joined.
-
GitHub
w3c/web-based-payment-handler
-
4 issues opened.
-
Collecting use cases that require payment handler window to be 1P context w3c/web-based-payment-handler#370, by @danyao.
-
Require user interaction before payment handler response returned w3c/web-based-payment-handler#369, by @ianbjacobs.
-
Creating a "Wallet" using PaymentHandler? w3c/web-based-payment-handler#368, by @cyberphone.
-
Rename canmakepayment event to hasenrolledinstrument event w3c/web-based-payment-handler#364, by @danyao.
-
-
2 issues closed.
-
Rename canMakePayment* hasEnrolledInstrument w3c/web-based-payment-handler#332.
-
Creating a "Wallet" using PaymentHandler? w3c/web-based-payment-handler#368.
-
-
6 issues received 15 new comments.
-
Open Window Algorithm and tracking through 1ps w3c/web-based-payment-handler#351 (8 comments by @cyberphone, @danyao, @ianbjacobs, @pes10k)
-
Collecting use cases that require payment handler window to be 1P context w3c/web-based-payment-handler#370 (2 comments by @adrianhopebailie, @marcoscaceres)
-
Creating a "Wallet" using PaymentHandler? w3c/web-based-payment-handler#368 (2 comments by @cyberphone, @ianbjacobs)
-
Require user interaction before payment handler response returned w3c/web-based-payment-handler#369 (1 comment by @danyao)
-
Rename canMakePayment* hasEnrolledInstrument w3c/web-based-payment-handler#332 (1 comment by @ianbjacobs)
-
Rename canmakepayment event to hasenrolledinstrument event w3c/web-based-payment-handler#364 (1 comment by @danyao)
-
-
3 pull requests opened.
-
chore: tidy w3c/web-based-payment-handler#367, by @marcoscaceres.
-
Security consideration: more awareness about cross-origin sharing w3c/web-based-payment-handler#366, by @ianbjacobs.
-
Security consideration: user consent before payment w3c/web-based-payment-handler#365, by @ianbjacobs.
-
-
4 pull requests merged.
-
Security consideration: more awareness about cross-origin sharing w3c/web-based-payment-handler#366.
-
Security consideration: user consent before payment w3c/web-based-payment-handler#365.
-
chore: tidy w3c/web-based-payment-handler#367.
-
Updated examples.md - Formatting w3c/web-based-payment-handler#357.
-
-
3 pull requests received 19 new comments.
-
Security consideration: user consent before payment w3c/web-based-payment-handler#365 (9 comments by @danyao, @ianbjacobs, @marcoscaceres, @romandev)
-
Security consideration: more awareness about cross-origin sharing w3c/web-based-payment-handler#366 (8 comments by @danyao, @ianbjacobs, @marcoscaceres)
-
Shipping Address and Payer's Contact info Delegation w3c/web-based-payment-handler#349 (2 comments by @marcoscaceres, @sahel-sh)
-
w3c/payment-request
-
6 issues opened.
-
Passing a transaction id to a payment request w3c/payment-request#911, by @agektmr.
-
Fix typo in code sample. w3c/payment-request#907, by @rsolomakhin.
-
Privacy considerations concerning shipping cost calculation w3c/payment-request#906, by @crowgames.
-
Disallow ambiguous methodData declarations? w3c/payment-request#905, by @crowgames.
-
Clarification on payment handler selection in spec w3c/payment-request#904, by @crowgames.
-
Discuss findings of security analysis w3c/payment-request#903, by @crowgames.
-
-
5 issues closed.
-
Privacy considerations concerning shipping cost calculation w3c/payment-request#906.
-
Expected behaviours: paymentmethodchange event updates with a rejection w3c/payment-request#898.
-
Move PaymentAddress string defaults to AddressInit w3c/payment-request#853.
-
Fix typo in code sample. w3c/payment-request#907.
-
Discuss findings of security analysis w3c/payment-request#903.
-
-
8 issues received 20 new comments.
-
Expected behaviours: paymentmethodchange event updates with a rejection w3c/payment-request#898 (5 comments by @marcoscaceres, @maxlgu, @rsolomakhin)
-
Discuss findings of security analysis w3c/payment-request#903 (4 comments by @crowgames, @cyberphone, @ianbjacobs, @marcoscaceres)
-
Disallow ambiguous methodData declarations? w3c/payment-request#905 (3 comments by @ianbjacobs, @marcoscaceres)
-
Privacy considerations concerning shipping cost calculation w3c/payment-request#906 (2 comments by @crowgames, @marcoscaceres)
-
Passing a transaction id to a payment request w3c/payment-request#911 (2 comments by @agektmr, @ianbjacobs)
-
Proposal to add optional "description" string field to PaymentShippingOption dictionary w3c/payment-request#902 (2 comments by @marcoscaceres)
-
Proposal to make the amount field in PaymentShippingOption optional w3c/payment-request#901 (1 comment by @marcoscaceres)
-
-
3 pull requests opened.
-
Add optional description to PaymentShippingOption w3c/payment-request#910, by @marcoscaceres.
-
Editorial: Add [[handler]] slot to PaymentRequest w3c/payment-request#909, by @marcoscaceres.
-
fix: disallow duplicate PMIs when creating request w3c/payment-request#908, by @marcoscaceres.
-
-
1 pull request merged.
-
Give AddressInit's members defaults w3c/payment-request#852.
-
-
1 pull request received 1 new comment.
w3c/webpayments
-
1 pull request opened.
-
Add mention of private browsing as insufficient w3c/webpayments#253, by @ianbjacobs.
-
-
1 pull request received 3 new comments.
-
Add mention of private browsing as insufficient w3c/webpayments#253 (3 comments by @danyao, @ianbjacobs)
-
w3c/payment-method-manifest
-
3 issues opened.
-
Spec cleanup for "default_applications" w3c/payment-method-manifest#44, by @rsolomakhin.
-
Allow additional properties in manifest w3c/payment-method-manifest#43, by @adrianhopebailie.
-
Remove "*" functionality for supported_origins w3c/payment-method-manifest#42, by @danyao.
-
-
3 issues received 5 new comments.
-
Spec cleanup for "default_applications" w3c/payment-method-manifest#44 (3 comments by @domenic, @rsolomakhin)
-
Remove "*" functionality for supported_origins w3c/payment-method-manifest#42 (1 comment by @danyao)
-
Participants
-
4 participants joined.
-
Jorge Barboza (Airbnb Inc) joined.
-
Jules Renier (CANTON CONSULTING) joined.
-
Duy-Tung LUU (CANTON CONSULTING) joined.
-
Tomasz Blachowicz (Mastercard Incorporated) joined.
-
-
3 participants left.
-
Antoine Roulin (CANTON CONSULTING) left.
-
Nicolas ANCOT (CANTON CONSULTING) left.
-
Matthew Lockyer (Worldpay - FIS) left.
-
-
1 organization joined.
-
Hedera Hashgraph joined.
-
GitHub
w3c/payment-request
-
2 issues opened.
-
Proposal to add optional "description" string field to PaymentShippingOption dictionary w3c/payment-request#902, by @sahel-sh.
-
Proposal to make the amount field in PaymentShippingOption optional w3c/payment-request#901, by @sahel-sh.
-
-
2 issues received 5 new comments.
-
Proposal to make the amount field in PaymentShippingOption optional w3c/payment-request#901 (3 comments by @ianbjacobs, @marcoscaceres, @sahel-sh)
-
Proposal to add optional "description" string field to PaymentShippingOption dictionary w3c/payment-request#902 (2 comments by @marcoscaceres, @sahel-sh)
-
-
1 pull request opened.
-
Update index.html w3c/payment-request#900, by @Sdussault.
-
-
1 pull request merged.
-
Update index.html w3c/payment-request#900.
-
-
1 pull request received 1 new comment.
w3c/web-based-payment-handler
-
2 issues received 5 new comments.
-
Specify just-in-time installation behavior? w3c/web-based-payment-handler#346 (4 comments by @ianbjacobs, @marcoscaceres)
-
Add support for PaymentValidationErrors w3c/web-based-payment-handler#306 (1 comment by @ianbjacobs)
-
TR publications
-
2 documents published.
-
Payment Method: Basic Card published twice as a Working Draft. History of Payment Method: Basic Card
-
Participants
-
11 participants joined.
-
Claire Thompson (Airbnb Inc) joined.
-
Jonathan Grossar (Mastercard Incorporated) joined.
-
Mathieu Hofman (W3C Invited Experts) joined.
-
Marco Medina (Netflix Inc.) joined.
-
Yun Cho (Airbnb Inc) joined.
-
Dirk Balfanz (Google LLC) joined.
-
John Carrier (International Forecourt Standards Forum) joined.
-
Ian Brown (International Forecourt Standards Forum) joined.
-
Andrey Bannikov (Meta) joined.
-
Keiko Itakura (Rakuten Group, Inc.) joined.
-
Frank Hoffman (Klarna) joined.
-
-
65 participants left.
-
Jenan Wise (Stripe) left.
-
Stanislas Polu (Stripe) left.
-
Robert Martin (Capital One Discover Network) left.
-
Tomasz Blachowicz (Mastercard Incorporated) left.
-
Swapnil Deshmukh (Certus Cybersecurity Solutions LLC) left.
-
Young Yang (Wells Fargo Bank N.A.) left.
-
Hideki Akashika (Rakuten Group, Inc.) left.
-
Elizabeth Koumpan (IBM Corporation) left.
-
Laurence Masson (PayCert) left.
-
Ryan McDonough (Verizon) left.
-
Jennifer Sheridan (Bank of America) left.
-
Charmaine Jones (Bank of America) left.
-
Tony England (Visa) left.
-
Luis Guzman (NACHA - The Electronic Payments Association) left.
-
Andrés Rapela (Federal Reserve Bank of Minneapolis) left.
-
Russell Kendall (Bank of America) left.
-
Ganesh Annan (Digital Bazaar) left.
-
Jonathan Grossar (Mastercard Incorporated) left.
-
Chris Marconi (Capital One Discover Network) left.
-
Brian Piel (Mastercard Incorporated) left.
-
William Vanobberghen (Groupement des Cartes Bancaires) left.
-
Shay Dotan (BlueSnap) left.
-
Andrew Sudbury (Abine Inc.) left.
-
ELENI LIALIAMOU (Wiley) left.
-
Ludovic Verecque (PayCert) left.
-
eric seong (LG Electronics) left.
-
Ahuja Sachin (Mastercard Incorporated) left.
-
Mike McCarthy (Mastercard Incorporated) left.
-
Holger Kunkat (Mastercard Incorporated) left.
-
Guy Berg (Federal Reserve Bank of Minneapolis) left.
-
Todd Albers (Federal Reserve Bank of Minneapolis) left.
-
Michiel de Jong (Ripple) left.
-
Adam Lake (Digital Bazaar) left.
-
John Carrier (International Forecourt Standards Forum) left.
-
Ian Brown (International Forecourt Standards Forum) left.
-
Frank Hoffman (Klarna) left.
-
Peter Orton (Department of Human Services) left.
-
CHAO GUO (Tencent) left.
-
crest xu (Tencent) left.
-
Diogo Cortiz (NIC.br - Brazilian Network Information Center) left.
-
Florian Dold (Inria) left.
-
Jun Yang (Alibaba Group) left.
-
Dapeng(Max) Liu (Alibaba Group) left.
-
Shane McCarron (Spec-Ops) left.
-
Kevin Hurley (Meta) left.
-
Yanhua Mao (Meta) left.
-
Wonsuk Lee (Electronics and Telecommunications Research Institute (ETRI)) left.
-
Kangchan Lee (Electronics and Telecommunications Research Institute (ETRI)) left.
-
Roy McElmurry (Meta) left.
-
Jungkee Song (Microsoft Corporation) left.
-
Klaus-Peter Hofmann (Deutsche Telekom AG) left.
-
Patrick Adler (Federal Reserve Bank of Minneapolis) left.
-
Xueyuan Jia (W3C) left.
-
Sailesh Panchang (Deque Systems, Inc.) left.
-
Zephyr Tuan (Alibaba Group) left.
-
Kepeng Li (Alibaba Group) left.
-
Jeffrey Burdges (Inria) left.
-
Manu Sporny (Digital Bazaar) left.
-
Dave Longley (Digital Bazaar) left.
-
David Lehn (Digital Bazaar) left.
-
Matthew Collier (Digital Bazaar) left.
-
Wooglae Kim (Inswave Co., Ltd.) left.
-
Nitin Gaur (IBM Corporation) left.
-
Wendy Seltzer (W3C) left.
-
Matt Pisut (Microsoft Corporation) left.
-
-
8 organizations joined.
-
Mastercard Incorporated joined.
-
Meta joined.
-
International Forecourt Standards Forum joined.
-
Rakuten Group, Inc. joined.
-
Capital One Discover Network joined.
-
Klarna joined.
-
NACHA - The Electronic Payments Association joined.
-
BlueSnap joined.
-
GitHub
w3c/web-based-payment-handler
-
2 issues opened.
-
Permission model w3c/web-based-payment-handler#363, by @marcoscaceres.
-
See W3C TAG review comments w3c/web-based-payment-handler#362, by @ianbjacobs.
-
-
1 issue received 3 new comments.
-
Permission model w3c/web-based-payment-handler#363 (3 comments by @dlongley, @marcoscaceres, @msporny)
-
w3c/payment-method-manifest
-
2 issues opened.
-
"serviceworker" member no longer a thing w3c/payment-method-manifest#41, by @marcoscaceres.
-
Manifest's (c|s)hould be optional for payment handlers w3c/payment-method-manifest#40, by @cyberphone.
-
w3c/payment-request
-
2 issues opened.
-
Expected behaviours: paymentmethodchange event updates with a rejection w3c/payment-request#898, by @maxlgu.
-
Payment Method - BasicCardErrors.paymentMethod errors not being displayed w3c/payment-request#897, by @rrigoni.
-
-
3 issues closed.
-
the user interface's language should not be derived from `the body element` w3c/payment-request#895.
-
Payment Method - BasicCardErrors.paymentMethod errors not being displayed w3c/payment-request#897.
-
-
3 issues received 6 new comments.
-
Expected behaviours: paymentmethodchange event updates with a rejection w3c/payment-request#898 (3 comments by @maxlgu, @rsolomakhin)
-
Payment Method - BasicCardErrors.paymentMethod errors not being displayed w3c/payment-request#897 (2 comments by @marcoscaceres, @rsolomakhin)
-
-
1 pull request opened.
-
Editorial: Use respec shorthands instead of `data-lt` w3c/payment-request#899, by @janiceshiu.
-
-
3 pull requests merged.
-
Editorial: Use respec shorthands instead of `data-lt` w3c/payment-request#899.
-
Remove recommendation to localize sheet based on body element w3c/payment-request#896.
-
Editorial: Export terms for payment method basic card spec w3c/payment-request#894.
-
-
2 pull requests received 16 new comments.
-
Editorial: Use respec shorthands instead of `data-lt` w3c/payment-request#899 (13 comments by @janiceshiu, @marcoscaceres)
-
Remove recommendation to localize sheet based on body element w3c/payment-request#896 (3 comments by @marcoscaceres)
-
TR publications
-
1 document published.
-
Payment Method: Basic Card published as a Working Draft. History of Payment Method: Basic Card
-
Participants
-
5 participants joined.
-
Sahel Sharify (Google LLC) joined.
-
Masateru Mashita (JCB CO., LTD.) joined.
-
Mercia le Roux (Entersekt) joined.
-
Gerhard Oosthuizen (Entersekt) joined.
-
Jay Patel (American Express Company) joined.
-
-
2 participants left.
-
Norie Ozawa (JCB CO., LTD.) left.
-
Eric Kauz (GS1) left.
-
-
24 organizations joined.
-
Netflix Inc. joined.
-
Google LLC joined.
-
Apple Inc. joined.
-
Mozilla Foundation joined.
-
Amazon joined.
-
CANTON CONSULTING joined.
-
Entersekt joined.
-
Discover Financial Services LLC joined.
-
JCB CO., LTD. joined.
-
Knowbility joined.
-
Coil Technologies, Inc. joined.
-
The Clearing House joined.
-
Merchant Advisory Group joined.
-
Shopify joined.
-
American Express Company joined.
-
Lyra Network joined.
-
Samsung Electronics Co., Ltd. joined.
-
ISO 20022 Registration Authority joined.
-
Visa joined.
-
Brave Software Inc. joined.
-
Conexxus joined.
-
China Mobile Communications Corporation joined.
-
Airbnb Inc joined.
-
Yubico joined.
-
GitHub
w3c/web-based-payment-handler
-
3 issues opened.
-
PaymentRequestEvent.OpenWindow() could fail in two different ways w3c/web-based-payment-handler#361, by @maxlgu.
-
Add informative mention of native payment handlers w3c/web-based-payment-handler#360, by @ianbjacobs.
-
iDeal test payment- TRXID is not requested in my webpage's URL w3c/web-based-payment-handler#359, by @muzammilmuzamil.
-
-
1 issue closed.
-
iDeal test payment- TRXID is not requested in my webpage's URL w3c/web-based-payment-handler#359.
-
-
3 issues received 3 new comments.
-
PaymentRequestEvent.OpenWindow() could fail in two different ways w3c/web-based-payment-handler#361 (1 comment by @rsolomakhin)
-
iDeal test payment- TRXID is not requested in my webpage's URL w3c/web-based-payment-handler#359 (1 comment by @rsolomakhin)
-
w3c/payment-request
-
4 issues opened.
-
the user interface's language should not be derived from `the body element` w3c/payment-request#895, by @janiceshiu.
-
ISP managed "micropayments" as alternative to advertisement based funding for web content creators. w3c/payment-request#893, by @keenla.
-
Missing definition of retrying a payment as a concept w3c/payment-request#889, by @marcoscaceres.
-
-
1 issue closed.
-
ISP managed "micropayments" as alternative to advertisement based funding for web content creators. w3c/payment-request#893.
-
-
1 issue reopened.
-
Allow locale to be specified by the developer. w3c/payment-request#650, by @marcoscaceres.
-
-
4 issues received 9 new comments.
-
Payment Method Basic Card spec uses various Payment Request definitions that Payment Request does not yet export w3c/payment-request#890 (4 comments by @danyao, @janiceshiu)
-
the user interface's language should not be derived from `the body element` w3c/payment-request#895 (3 comments by @marcoscaceres)
-
Use Case: 3DS 1.0 flows and invoking PR API from inside an iFrame w3c/payment-request#881 (1 comment by @ianbjacobs)
-
ISP managed "micropayments" as alternative to advertisement based funding for web content creators. w3c/payment-request#893 (1 comment by @ianbjacobs)
-
-
4 pull requests opened.
-
Remove recommendation to localize sheet based on body element w3c/payment-request#896, by @marcoscaceres.
-
Editorial: Export terms for payment method basic card spec w3c/payment-request#894, by @janiceshiu.
-
Updated link to PR API test suite w3c/payment-request#892, by @ianbjacobs.
-
Editorial: Update links to respec definitions w3c/payment-request#891, by @janiceshiu.
-
-
2 pull requests merged.
-
Editorial: Update links to respec definitions w3c/payment-request#891.
-
Updated link to PR API test suite w3c/payment-request#892.
-
-
3 pull requests received 27 new comments.
-
Editorial: Export terms for payment method basic card spec w3c/payment-request#894 (14 comments by @ianbjacobs, @janiceshiu, @marcoscaceres)
-
Remove recommendation to localize sheet based on body element w3c/payment-request#896 (7 comments by @janiceshiu, @marcoscaceres)
-
Editorial: Update links to respec definitions w3c/payment-request#891 (6 comments by @ianbjacobs, @janiceshiu, @marcoscaceres)
-