Web Payments Working Group - Activity in 2018
No matches.
TR publications
-
1 document published.
-
Payment Method: Basic Card published as a Working Draft. History of Payment Method: Basic Card
-
GitHub
w3c/payment-request
-
3 issues opened.
-
Clarification question for `show()` algorithm w3c/payment-request#820, by @rsolomakhin.
-
Support for language the form is served w3c/payment-request#819, by @kennanseno.
-
Extensibility of PaymentResponse.complete(result) w3c/payment-request#817, by @adrianhopebailie.
-
-
2 issues closed.
-
Clarify the behavior of calling PaymentResponse.complete() while [[retryPromise]] is pending w3c/payment-request#795.
-
Should we validate nonsense payer error properties? w3c/payment-request#793.
-
-
3 issues received 6 new comments.
-
Support for language the form is served w3c/payment-request#819 (4 comments by @cyberphone, @ianbjacobs, @marcoscaceres, @rsolomakhin)
-
consider requiring an error (non-empty dict) for .retry()? w3c/payment-request#792 (1 comment by @mnoorenberghe)
-
Extensibility of PaymentResponse.complete(result) w3c/payment-request#817 (1 comment by @rsolomakhin)
-
-
1 pull request opened.
-
Fix: WebIDL link for converting an ECMAScript value to a dictionary w3c/payment-request#818, by @wonsuk73.
-
-
3 pull requests merged.
-
Fix: WebIDL link for converting an ECMAScript value to a dictionary w3c/payment-request#818.
-
fix: while retrying complete() returns a rejected promise w3c/payment-request#808.
-
Warn when errorFields don't match request[[options]] w3c/payment-request#807.
-
-
2 pull requests received 5 new comments.
-
fix: while retrying complete() returns a rejected promise w3c/payment-request#808 (4 comments by @marcoscaceres, @romandev, @rsolomakhin)
-
Fix: WebIDL link for converting an ECMAScript value to a dictionary w3c/payment-request#818 (1 comment by @marcoscaceres)
-
w3c/web-based-payment-handler
-
1 issue closed.
-
Drop PaymentInstrument in favor of MethodCapability w3c/web-based-payment-handler#302.
-
-
1 issue received 1 new comment.
-
Drop PaymentInstrument in favor of MethodCapability w3c/web-based-payment-handler#302 (1 comment by @ianbjacobs)
-
-
1 pull request opened.
-
chore: move former editors to the right place w3c/web-based-payment-handler#328, by @marcoscaceres.
-
-
1 pull request received 5 new comments.
-
HTTPS considerations. w3c/web-based-payment-handler#283 (5 comments by @domenic, @marcoscaceres, @rsolomakhin)
-
TR publications
-
4 documents published.
-
Payment Method: Basic Card published 4 times as a Working Draft. History of Payment Method: Basic Card
-
Participants
-
1 participant joined.
-
Didier Martin (W3C Invited Experts) joined.
-
-
2 participants left.
-
Robert Wozniak (W3C Invited Experts) left.
-
Francois Gaignard (W3C Invited Experts) left.
-
-
1 organization joined.
-
Rakuten Group, Inc. joined.
-
-
1 organization left.
-
GROUPE BPCE left.
-
GitHub
w3c/payment-request
-
6 issues opened.
-
Should we put `regionCode` attribute at risk? w3c/payment-request#816, by @marcoscaceres.
-
Include payment handler information in response w3c/payment-request#815, by @ianbjacobs.
-
De-dup "user aborts the payment request" and "abort the update" w3c/payment-request#814, by @marcoscaceres.
-
Should PaymentMethodData be converted at construction time? w3c/payment-request#813, by @marcoscaceres.
-
Rethink "payment request is showing" boolean w3c/payment-request#809, by @marcoscaceres.
-
retry(errorFields) should be optional w3c/payment-request#804, by @marcoscaceres.
-
-
5 issues closed.
-
Should API support billing address capture (for tax computation)? w3c/payment-request#27.
-
Treat scroll as a user gesture for PaymentRequest.show() w3c/payment-request#797.
-
Follow up on APA Comments on Web Payments FPWDs w3c/payment-request#735.
-
Meaning of canMakePayment() w3c/payment-request#800.
-
retry(errorFields) should be optional w3c/payment-request#804.
-
-
12 issues received 51 new comments.
-
Rethink "payment request is showing" boolean w3c/payment-request#809 (13 comments by @adrianhopebailie, @domenic, @ianbjacobs, @marcoscaceres, @mnoorenberghe, @rsolomakhin)
-
Clarify when the user can abort the payment request algorithm w3c/payment-request#796 (10 comments by @aestes, @marcoscaceres, @mnoorenberghe, @rsolomakhin)
-
Should PaymentMethodData be converted at construction time? w3c/payment-request#813 (9 comments by @aestes, @marcoscaceres, @rsolomakhin, @zouhir)
-
Treat scroll as a user gesture for PaymentRequest.show() w3c/payment-request#797 (5 comments by @danyao, @ianbjacobs, @marcoscaceres)
-
Should we put `regionCode` attribute at risk? w3c/payment-request#816 (3 comments by @marcoscaceres, @mnoorenberghe, @rsolomakhin)
-
Way of detecting if can make payment with some instrument w3c/payment-request#801 (3 comments by @ianbjacobs, @marcoscaceres)
-
Consider specifying a testing IDL for a mock payment UI w3c/payment-request#799 (2 comments by @ianbjacobs, @rsolomakhin)
-
consider requiring an error (non-empty dict) for .retry()? w3c/payment-request#792 (1 comment by @marcoscaceres)
-
Should API support billing address capture (for tax computation)? w3c/payment-request#27 (1 comment by @marcoscaceres)
-
Clarify the behavior of calling PaymentResponse.complete() while [[retryPromise]] is pending w3c/payment-request#795 (1 comment by @marcoscaceres)
-
-
7 pull requests opened.
-
fix: convert PaymentMethodData.data w3c/payment-request#812, by @marcoscaceres.
-
Attach 'payment request is showing boolean' to top-level browsing context w3c/payment-request#811, by @marcoscaceres.
-
Clarify when the user can abort the payment request algorithm w3c/payment-request#810, by @marcoscaceres.
-
fix: while retrying complete() returns a rejected promise w3c/payment-request#808, by @marcoscaceres.
-
Warn when errorFields don't match request[[options]] w3c/payment-request#807, by @marcoscaceres.
-
Change what canMakePayment() means w3c/payment-request#806, by @marcoscaceres.
-
fix: retry()'s errorFields should be optional per WebIDL w3c/payment-request#805, by @marcoscaceres.
-
-
4 pull requests merged.
-
Support requesting billing address w3c/payment-request#749.
-
Added section and paragraph on accessibility considerations w3c/payment-request#802.
-
Change what canMakePayment() means w3c/payment-request#806.
-
fix: retry()'s errorFields should be optional per WebIDL w3c/payment-request#805.
-
-
13 pull requests received 64 new comments.
-
Attach 'payment request is showing boolean' to top-level browsing context w3c/payment-request#811 (14 comments by @domenic, @ianbjacobs, @marcoscaceres, @rsolomakhin)
-
Support requesting billing address w3c/payment-request#749 (9 comments by @marcoscaceres, @rsolomakhin, @snez)
-
Warn when errorFields don't match request[[options]] w3c/payment-request#807 (8 comments by @domenic, @marcoscaceres)
-
Change what canMakePayment() means w3c/payment-request#806 (8 comments by @marcoscaceres, @rsolomakhin)
-
Clarify when the user can abort the payment request algorithm w3c/payment-request#810 (5 comments by @domenic, @marcoscaceres)
-
Add PaymentResponse.prototype.onpayerdetailchange w3c/payment-request#724 (5 comments by @aestes, @marcoscaceres, @romandev)
-
fix: retry()'s errorFields should be optional per WebIDL w3c/payment-request#805 (5 comments by @aestes, @marcoscaceres)
-
fix: convert PaymentMethodData.data w3c/payment-request#812 (3 comments by @domenic, @marcoscaceres)
-
fix: while retrying complete() returns a rejected promise w3c/payment-request#808 (3 comments by @marcoscaceres)
-
Added section and paragraph on accessibility considerations w3c/payment-request#802 (1 comment by @michael-n-cooper)
-
Add paymentMethodErrors, payerErrors, to PaymentDetailsUpdate w3c/payment-request#768 (1 comment by @aestes)
-
w3c/web-based-payment-handler
-
1 issue closed.
-
Return origin of payment app in PaymentHandlerResponse data? w3c/web-based-payment-handler#217.
-
-
1 issue received 10 new comments.
-
Return origin of payment app in PaymentHandlerResponse data? w3c/web-based-payment-handler#217 (10 comments by @adrianhopebailie, @ianbjacobs, @rsolomakhin)
-
-
1 pull request received 5 new comments.
-
Cross-origin iframes and feature policy. w3c/web-based-payment-handler#282 (5 comments by @ianbjacobs, @marcoscaceres, @rsolomakhin)
-
TR publications
-
3 documents published.
-
Payment Method: Basic Card published 3 times as a Working Draft. History of Payment Method: Basic Card
-
Participants
-
2 participants left.
-
Michael[tm] Smith (sideshowbarker) (W3C) left.
-
Sam Sugimoto (W3C) left.
-
-
2 organizations joined.
-
Verizon joined.
-
Reach joined.
-
-
1 organization left.
-
Shift4 Corporation left.
-
GitHub
w3c/payment-request
-
10 issues opened.
-
Way of detecting if can make payment with some instrument w3c/payment-request#801, by @marcoscaceres.
-
Meaning of canMakePayment() w3c/payment-request#800, by @marcoscaceres.
-
Consider specifying a testing IDL for a mock payment UI w3c/payment-request#799, by @aestes.
-
Make Basic Card Payment Method Spec an informative reference w3c/payment-request#798, by @adrianhopebailie.
-
Treat scroll as a user gesture for PaymentRequest.show() w3c/payment-request#797, by @danyao.
-
Clarify when the user can abort the payment request algorithm w3c/payment-request#796, by @aestes.
-
Clarify the behavior of calling PaymentResponse.complete() while [[retryPromise]] is pending w3c/payment-request#795, by @aestes.
-
Should we validate nonsense payer error properties? w3c/payment-request#793, by @marcoscaceres.
-
consider requiring an error (non-empty dict) for .retry()? w3c/payment-request#792, by @marcoscaceres.
-
test suite that checks whether shipping options can be updated w3c/payment-request#791, by @adimallikarjunareddy.
-
-
5 issues closed.
-
Make Basic Card Payment Method Spec an informative reference w3c/payment-request#798.
-
Describe how to implement PaymentAddress.languageCode w3c/payment-request#608.
-
Sensible defaults for dictionary members w3c/payment-request#780.
-
Guidance on shipping options (mostly for devs) w3c/payment-request#680.
-
Rename `PayerErrorFields` to be like `AddressErrors` and `BasicCardErrors` w3c/payment-request#782.
-
-
9 issues received 43 new comments.
-
consider requiring an error (non-empty dict) for .retry()? w3c/payment-request#792 (16 comments by @aestes, @marcoscaceres, @mnoorenberghe, @romandev, @rsolomakhin)
-
To address branded button issues and improve privacy, add browser support for payment method selection before the sheet w3c/payment-request#777 (6 comments by @adrianhopebailie, @ianbjacobs)
-
Clarify the behavior of calling PaymentResponse.complete() while [[retryPromise]] is pending w3c/payment-request#795 (4 comments by @aestes, @marcoscaceres)
-
Guidance on shipping options (mostly for devs) w3c/payment-request#680 (4 comments by @aestes, @marcoscaceres, @rsolomakhin)
-
Should we validate nonsense payer error properties? w3c/payment-request#793 (4 comments by @aestes, @marcoscaceres, @romandev, @rsolomakhin)
-
Make Basic Card Payment Method Spec an informative reference w3c/payment-request#798 (3 comments by @ianbjacobs, @marcoscaceres)
-
test suite that checks whether shipping options can be updated w3c/payment-request#791 (3 comments by @adimallikarjunareddy, @marcoscaceres)
-
Consider specifying a testing IDL for a mock payment UI w3c/payment-request#799 (2 comments by @aestes, @ianbjacobs)
-
-
3 pull requests opened.
-
Added section and paragraph on accessibility considerations w3c/payment-request#802, by @ianbjacobs.
-
Remove PaymentItem.type w3c/payment-request#794, by @marcoscaceres.
-
Editorial: fixed grammatical errors w3c/payment-request#790, by @wonsuk73.
-
-
4 pull requests merged.
-
Remove PaymentAddress' languageCode w3c/payment-request#765.
-
Remove PaymentItem.type w3c/payment-request#794.
-
Rename `PayerErrorFields` to `PayerErrors` w3c/payment-request#789.
-
Editorial: fixed grammatical errors w3c/payment-request#790.
-
-
6 pull requests received 20 new comments.
-
Rename `PayerErrorFields` to `PayerErrors` w3c/payment-request#789 (9 comments by @akansha2608, @marcoscaceres, @romandev)
-
Remove PaymentAddress' languageCode w3c/payment-request#765 (4 comments by @marcoscaceres, @rsolomakhin)
-
Added section and paragraph on accessibility considerations w3c/payment-request#802 (1 comment by @marcoscaceres)
-
w3c/web-based-payment-handler
-
2 issues closed.
-
Use payment method manifest for registration-time validation? w3c/web-based-payment-handler#248.
-
SW registration code unclear/incorrect w3c/web-based-payment-handler#223.
-
-
3 issues received 8 new comments.
-
interaction with payment methods doesn't appear to be defined w3c/web-based-payment-handler#249 (3 comments by @ianbjacobs, @rsolomakhin)
-
SW registration code unclear/incorrect w3c/web-based-payment-handler#223 (3 comments by @ianbjacobs, @romandev, @rsolomakhin)
-
Use payment method manifest for registration-time validation? w3c/web-based-payment-handler#248 (2 comments by @ianbjacobs, @rsolomakhin)
-
-
1 pull request opened.
-
Removed conflicts from Jake Archibald pull request w3c/web-based-payment-handler#327, by @ianbjacobs.
-
-
2 pull requests merged.
-
Removed conflicts from Jake Archibald pull request w3c/web-based-payment-handler#327.
-
Only allows instrument.set() in active service worker w3c/web-based-payment-handler#224.
-
-
1 pull request closed.
-
Simplifying functional event handling w3c/web-based-payment-handler#305.
-
-
3 pull requests received 11 new comments.
-
Removed conflicts from Jake Archibald pull request w3c/web-based-payment-handler#327 (7 comments by @ianbjacobs, @rsolomakhin)
-
Only allows instrument.set() in active service worker w3c/web-based-payment-handler#224 (2 comments by @romandev)
-
w3c/payment-method-manifest
-
1 issue opened.
-
Redesign of "extract header list values" expected w3c/payment-method-manifest#30, by @annevk.
-
w3c/webpayments
-
1 issue received 1 new comment.
w3c/payment-method-id
-
1 pull request opened.
-
Editorial: Fixed duplication of url and spec name to sync with linked doc w3c/payment-method-id#57, by @wonsuk73.
-
-
1 pull request merged.
-
Editorial: Fixed duplication of url and spec name to sync with linked doc w3c/payment-method-id#57.
-
-
1 pull request received 4 new comments.
-
Editorial: Fixed duplication of url and spec name to sync with linked doc w3c/payment-method-id#57 (4 comments by @marcoscaceres, @wonsuk73)
-
TR publications
-
1 document published.
-
Payment Method: Basic Card published as a Working Draft. History of Payment Method: Basic Card
-
Participants
-
1 participant joined.
-
Mayra Sciarrillo (W3C Invited Experts) joined.
-
-
1 organization joined.
-
The Clearing House joined.
-
GitHub
w3c/payment-method-id
-
2 issues opened.
-
Prepare for Proposed Recommendation w3c/payment-method-id#56, by @marcoscaceres.
-
Generate an implementation report w3c/payment-method-id#54, by @marcoscaceres.
-
-
1 issue closed.
-
What can I do with a URL-based payment method identifier? w3c/payment-method-id#52.
-
-
1 issue received 19 new comments.
-
Generate an implementation report w3c/payment-method-id#54 (19 comments by @ianbjacobs, @marcoscaceres, @yatri1609)
-
-
2 pull requests opened.
-
Updated the link to the test-suit w3c/payment-method-id#55, by @yatri1609.
-
Editorial: describe relationship to pay manifest w3c/payment-method-id#53, by @marcoscaceres.
-
-
2 pull requests merged.
-
Updated the link to the test-suit w3c/payment-method-id#55.
-
Editorial: describe relationship to pay manifest w3c/payment-method-id#53.
-
-
2 pull requests received 10 new comments.
-
Updated the link to the test-suit w3c/payment-method-id#55 (9 comments by @marcoscaceres, @yatri1609)
-
Editorial: describe relationship to pay manifest w3c/payment-method-id#53 (1 comment by @marcoscaceres)
-
w3c/payment-request
-
11 issues opened.
-
Fix the links to the `data-tests` in the spec w3c/payment-request#787, by @Sylvia23.
-
"data-test" should be changed to "data-tests" in spec w3c/payment-request#785, by @Sylvia23.
-
Rename `PayerErrorFields` to be like `AddressErrors` and `BasicCardErrors` w3c/payment-request#782, by @mnoorenberghe.
-
Sensible defaults for dictionary members w3c/payment-request#780, by @marcoscaceres.
-
Confirm tests and specs align w3c/payment-request#779, by @marcoscaceres.
-
Not able to add shipping options dynamically for apple pay w3c/payment-request#778, by @Siddeshwaraswamy.
-
Do we need to identify payment method in MerchantValidationEvent? w3c/payment-request#775, by @ianbjacobs.
-
Some clarifications with Payment Request API w3c/payment-request#774, by @adimallikarjunareddy.
-
Make billing address optional w3c/payment-request#773, by @agektmr.
-
Extract actionable items from Shopify study w3c/payment-request#772, by @marcoscaceres.
-
-
9 issues closed.
-
Fix the links to the `data-tests` in the spec w3c/payment-request#787.
-
"data-test" should be changed to "data-tests" in spec w3c/payment-request#785.
-
PaymentDetailsUpdate needs to include payerErrors w3c/payment-request#766.
-
Not able to add shipping options dynamically for apple pay w3c/payment-request#778.
-
Do we need to identify payment method in MerchantValidationEvent? w3c/payment-request#775.
-
Make billing address optional w3c/payment-request#773.
-
Add link to SecureContext test w3c/payment-request#697.
-
Populate implementation report w3c/payment-request#560.
-
Can PaymentMethodChangeEventInit really have a required member? w3c/payment-request#770.
-
-
16 issues received 70 new comments.
-
Some clarifications with Payment Request API w3c/payment-request#774 (27 comments by @adimallikarjunareddy, @aestes, @agektmr, @asolove-stripe, @ianbjacobs, @marcoscaceres, @rsolomakhin)
-
Integration with Feature Policy w3c/payment-request#600 (9 comments by @clelland, @loonybear, @marcoscaceres, @rsolomakhin)
-
To address branded button issues and improve privacy, add browser support for payment method selection before the sheet w3c/payment-request#777 (7 comments by @asolove-stripe, @dlongley, @ianbjacobs, @Krystosterone)
-
Not able to add shipping options dynamically for apple pay w3c/payment-request#778 (6 comments by @marcoscaceres, @Siddeshwaraswamy)
-
Confirm tests and specs align w3c/payment-request#779 (5 comments by @ianbjacobs, @marcoscaceres, @Sylvia23)
-
Rename `PayerErrorFields` to be like `AddressErrors` and `BasicCardErrors` w3c/payment-request#782 (3 comments by @akansha2608, @marcoscaceres)
-
Make billing address optional w3c/payment-request#773 (3 comments by @agektmr, @marcoscaceres, @romandev)
-
Describe how to implement PaymentAddress.languageCode w3c/payment-request#608 (2 comments by @ianbjacobs, @stpeter)
-
"data-test" should be changed to "data-tests" in spec w3c/payment-request#785 (1 comment by @marcoscaceres)
-
Modifiers and [[serializedModifierData]] not actually used anywhere. w3c/payment-request#753 (1 comment by @ianbjacobs)
-
Should API support billing address capture (for tax computation)? w3c/payment-request#27 (1 comment by @snez)
-
-
7 pull requests opened.
-
Rename `PayerErrorFields` to `PayerErrors` w3c/payment-request#789, by @akansha2608.
-
Fix #787 : Fix the links to the `data-tests` in the spec w3c/payment-request#788, by @Sylvia23.
-
Fix #785 : data-test should be changed to data-tests in spec w3c/payment-request#786, by @Sylvia23.
-
Fix #779 : Confirm test and specs align w3c/payment-request#784, by @Sylvia23.
-
Editorial: fix link to basic card error dictionary in examples w3c/payment-request#783, by @mnoorenberghe.
-
fix: give dictionary members sensible defaults w3c/payment-request#781, by @marcoscaceres.
-
Add MerchantValidationEvent.prototype.methodName w3c/payment-request#776, by @marcoscaceres.
-
-
6 pull requests merged.
-
Fix #787 : Fix the links to the `data-tests` in the spec w3c/payment-request#788.
-
Fix #785 : data-test should be changed to data-tests in spec w3c/payment-request#786.
-
Editorial: fix link to basic card error dictionary in examples w3c/payment-request#783.
-
Add paymentMethodErrors, payerErrors, to PaymentDetailsUpdate w3c/payment-request#768.
-
Add MerchantValidationEvent.prototype.methodName w3c/payment-request#776.
-
fix: give PaymentMethodChangeEventInit defaults w3c/payment-request#771.
-
-
2 pull requests closed.
-
fix: give dictionary members sensible defaults w3c/payment-request#781.
-
Fix #779 : Confirm test and specs align w3c/payment-request#784.
-
-
12 pull requests received 37 new comments.
-
Add paymentMethodErrors, payerErrors, to PaymentDetailsUpdate w3c/payment-request#768 (7 comments by @marcoscaceres, @romandev)
-
Add MerchantValidationEvent.prototype.methodName w3c/payment-request#776 (7 comments by @domenic, @marcoscaceres, @romandev)
-
editorial: mark languageCode at risk w3c/payment-request#764 (7 comments by @aphillips, @marcoscaceres, @stpeter)
-
Remove PaymentAddress' languageCode w3c/payment-request#765 (6 comments by @adrianhopebailie, @aestes, @ianbjacobs, @marcoscaceres)
-
Fix #787 : Fix the links to the `data-tests` in the spec w3c/payment-request#788 (2 comments by @marcoscaceres, @Sylvia23)
-
fix: give PaymentMethodChangeEventInit defaults w3c/payment-request#771 (2 comments by @marcoscaceres)
-
fix: give dictionary members sensible defaults w3c/payment-request#781 (1 comment by @marcoscaceres)
-
Fix #785 : data-test should be changed to data-tests in spec w3c/payment-request#786 (1 comment by @marcoscaceres)
-
Editorial: fix link to basic card error dictionary in examples w3c/payment-request#783 (1 comment by @marcoscaceres)
-
w3c/web-based-payment-handler
-
3 issues opened.
-
Update Open Window Algorithm w3c/web-based-payment-handler#321, by @ianbjacobs.
-
Link for "fetching image object" is broken w3c/web-based-payment-handler#317, by @Ms2ger.
-
Examples involving storedInstrument seem broken w3c/web-based-payment-handler#316, by @Ms2ger.
-
-
10 issues closed.
-
Proposal: Remove requestPermission() w3c/web-based-payment-handler#246.
-
What should payees validate? w3c/web-based-payment-handler#310.
-
Examples involving storedInstrument seem broken w3c/web-based-payment-handler#316.
-
Open Window Algorithm w3c/web-based-payment-handler#115.
-
How would iDeal work? w3c/web-based-payment-handler#251.
-
Links to terms and common terminology w3c/web-based-payment-handler#50.
-
Link for "fetching image object" is broken w3c/web-based-payment-handler#317.
-
Payment Handler window `.focused` field w3c/web-based-payment-handler#307.
-
What mechanism allows enforcing payment handler authenticity? w3c/web-based-payment-handler#308.
-
Add support for communicating billing address to merchant (e.g., for VAT computation) w3c/web-based-payment-handler#314.
-
-
11 issues received 27 new comments.
-
Suggest changing a shape of openWindow() w3c/web-based-payment-handler#300 (7 comments by @romandev, @rsolomakhin)
-
PaymentManager behavior unclear w3c/web-based-payment-handler#253 (6 comments by @ianbjacobs, @jmpas, @rsolomakhin)
-
Payment Handler window `.focused` field w3c/web-based-payment-handler#307 (2 comments by @ianbjacobs, @rsolomakhin)
-
Normative what happens when users closing the window opened by PaymentRequestEvent.openWindow w3c/web-based-payment-handler#299 (2 comments by @ianbjacobs, @rsolomakhin)
-
Support for Abort() being delegated to Payment Handler w3c/web-based-payment-handler#117 (1 comment by @ianbjacobs)
-
What mechanism allows enforcing payment handler authenticity? w3c/web-based-payment-handler#308 (1 comment by @ianbjacobs)
-
Drop PaymentInstrument in favor of MethodCapability w3c/web-based-payment-handler#302 (1 comment by @rsolomakhin)
-
-
8 pull requests opened.
-
Code of Conduct w3c/web-based-payment-handler#326, by @plehegar.
-
[WIP] showPaymentUI() method w3c/web-based-payment-handler#325, by @romandev.
-
(Editorial) Clarify validation expectation w3c/web-based-payment-handler#324, by @ianbjacobs.
-
(Editorial) fix storedInstrument per issue 316 w3c/web-based-payment-handler#323, by @ianbjacobs.
-
(Editorial) link fix for issue 317 w3c/web-based-payment-handler#322, by @ianbjacobs.
-
Added more security implementation notes from Rouslan; non-normative w3c/web-based-payment-handler#320, by @ianbjacobs.
-
Fix Web IDL typo: bool → boolean w3c/web-based-payment-handler#319, by @foolip.
-
Notify merchant that payment method (possibly including the billing address) changed in payment handler. w3c/web-based-payment-handler#318, by @rsolomakhin.
-
-
8 pull requests merged.
-
Code of Conduct w3c/web-based-payment-handler#326.
-
Remove requestPermission() w3c/web-based-payment-handler#277.
-
(Editorial) Clarify validation expectation w3c/web-based-payment-handler#324.
-
(Editorial) fix storedInstrument per issue 316 w3c/web-based-payment-handler#323.
-
(Editorial) link fix for issue 317 w3c/web-based-payment-handler#322.
-
Added more security implementation notes from Rouslan; non-normative w3c/web-based-payment-handler#320.
-
Fix Web IDL typo: bool → boolean w3c/web-based-payment-handler#319.
-
Notify merchant that payment method (possibly including the billing address) changed in payment handler. w3c/web-based-payment-handler#318.
-
-
2 pull requests closed.
-
Remove link to issue 157 w3c/web-based-payment-handler#292.
-
Add AbortPaymentEvent. w3c/web-based-payment-handler#207.
-
-
10 pull requests received 37 new comments.
-
Notify merchant that payment method (possibly including the billing address) changed in payment handler. w3c/web-based-payment-handler#318 (11 comments by @foolip, @ianbjacobs, @romandev, @rsolomakhin)
-
[WIP] showPaymentUI() method w3c/web-based-payment-handler#325 (9 comments by @dlongley, @ianbjacobs, @romandev, @rsolomakhin, @webpayments-specs)
-
Simplifying functional event handling w3c/web-based-payment-handler#305 (9 comments by @jakearchibald, @marcoscaceres, @rsolomakhin)
-
Update Example6 and Example7 w3c/web-based-payment-handler#290 (2 comments by @romandev, @rsolomakhin)
-
Cross-origin iframes and feature policy. w3c/web-based-payment-handler#282 (1 comment by @rsolomakhin)
-
Only allows instrument.set() in active service worker w3c/web-based-payment-handler#224 (1 comment by @rsolomakhin)
-
w3c/webpayments
-
1 issue received 2 new comments.
-
Should the WPWG develop a cryptocurrency payment method specification w3c/webpayments#232 (2 comments by @Sjors, @webpayments)
-
TR publications
-
5 documents published.
-
Payment Request API published 5 times as a Candidate Recommendation Snapshot. History of Payment Request API
-
Participants
-
1 participant joined.
-
Robert Wozniak (W3C Invited Experts) joined.
-
-
3 organizations joined.
-
NACHA - The Electronic Payments Association joined.
-
Barclays Bank PLC joined.
-
Bank of America joined.
-
GitHub
w3c/payment-request
-
8 issues opened.
-
Can PaymentMethodChangeEventInit really have a required member? w3c/payment-request#770, by @cdumez.
-
Section 3.11 (onpaymentmethodchange attribute) mentions the wrong event interface w3c/payment-request#769, by @aestes.
-
Update spec to use "event constructing steps" w3c/payment-request#767, by @marcoscaceres.
-
PaymentDetailsUpdate needs to include payerErrors w3c/payment-request#766, by @marcoscaceres.
-
Proposal to add more details to shopping cart contents and shipping option descriptions w3c/payment-request#761, by @rsolomakhin.
-
Should the PaymentRequest ID be passed to canMakePayment? w3c/payment-request#760, by @rvm4.
-
Drop support for "Push Payments" w3c/payment-request#759, by @adrianhopebailie.
-
bless() is racy with document.body w3c/payment-request#758, by @marcoscaceres.
-
-
5 issues closed.
-
Add support for merchant validation w3c/payment-request#646.
-
Section 3.11 (onpaymentmethodchange attribute) mentions the wrong event interface w3c/payment-request#769.
-
bless() is racy with document.body w3c/payment-request#758.
-
Signaling payment handler details errors w3c/payment-request#727.
-
Add generic `error` member for `.retry()` w3c/payment-request#729.
-
-
10 issues received 58 new comments.
-
Should API support billing address capture (for tax computation)? w3c/payment-request#27 (18 comments by @adrianhopebailie, @ianbjacobs, @marcoscaceres, @rsolomakhin)
-
Modifiers and [[serializedModifierData]] not actually used anywhere. w3c/payment-request#753 (16 comments by @adrianhopebailie, @ianbjacobs, @Krystosterone, @marcoscaceres, @mountainhippo, @rsolomakhin, @stpeter)
-
Describe how to implement PaymentAddress.languageCode w3c/payment-request#608 (8 comments by @aphillips, @marcoscaceres, @rsolomakhin, @stpeter)
-
Can PaymentMethodChangeEventInit really have a required member? w3c/payment-request#770 (4 comments by @cdumez, @domenic, @marcoscaceres)
-
bless() is racy with document.body w3c/payment-request#758 (4 comments by @adrianhopebailie, @domenic, @marcoscaceres, @stpeter)
-
Drop support for "Push Payments" w3c/payment-request#759 (3 comments by @ianbjacobs, @marcoscaceres)
-
Should the PaymentRequest ID be passed to canMakePayment? w3c/payment-request#760 (2 comments by @ianbjacobs, @rsolomakhin)
-
Section 3.11 (onpaymentmethodchange attribute) mentions the wrong event interface w3c/payment-request#769 (1 comment by @marcoscaceres)
-
Proposal to add more details to shopping cart contents and shipping option descriptions w3c/payment-request#761 (1 comment by @marcoscaceres)
-
Providing an `AbortSignal` instead of calling .abort() w3c/payment-request#757 (1 comment by @adrianhopebailie)
-
-
4 pull requests opened.
-
fix: give PaymentMethodChangeEventInit defaults w3c/payment-request#771, by @marcoscaceres.
-
Add paymentMethodErrors, payerErrors, to PaymentDetailsUpdate w3c/payment-request#768, by @marcoscaceres.
-
Remove PaymentAddress' languageCode w3c/payment-request#765, by @marcoscaceres.
-
editorial: mark languageCode at risk w3c/payment-request#764, by @marcoscaceres.
-
-
4 pull requests merged.
-
Add support for merchant validation w3c/payment-request#751.
-
editorial: mark languageCode at risk w3c/payment-request#764.
-
Support fine-grained errors for payment methods w3c/payment-request#752.
-
Add error member to PaymentValidationErrors w3c/payment-request#747.
-
-
1 pull request closed.
-
Add error reporting billing address w3c/payment-request#750.
-
-
2 pull requests reopened.
-
Add error reporting billing address w3c/payment-request#750, by @marcoscaceres.
-
Support requesting billing address w3c/payment-request#749, by @marcoscaceres.
-
-
11 pull requests received 89 new comments.
-
Support requesting billing address w3c/payment-request#749 (36 comments by @adrianhopebailie, @asolove-stripe, @domenic, @ianbjacobs, @marcoscaceres, @rsolomakhin, @stpeter)
-
Add support for merchant validation w3c/payment-request#751 (24 comments by @adrianhopebailie, @domenic, @marcoscaceres)
-
editorial: mark languageCode at risk w3c/payment-request#764 (7 comments by @marcoscaceres, @rsolomakhin, @stpeter)
-
Remove PaymentAddress' languageCode w3c/payment-request#765 (6 comments by @marcoscaceres, @rsolomakhin)
-
Add paymentMethodErrors, payerErrors, to PaymentDetailsUpdate w3c/payment-request#768 (5 comments by @marcoscaceres, @romandev)
-
fix: give PaymentMethodChangeEventInit defaults w3c/payment-request#771 (3 comments by @aestes, @marcoscaceres)
-
Support fine-grained errors for payment methods w3c/payment-request#752 (1 comment by @marcoscaceres)
-
fine-grained errors reporting for PaymentAddress w3c/payment-request#712 (1 comment by @marcoscaceres)
-
w3c/web-based-payment-handler
-
2 issues opened.
-
Add support for communicating billing address to merchant (e.g., for VAT computation) w3c/web-based-payment-handler#314, by @ianbjacobs.
-
Add paymentRequestID to CanMakePaymentEvent? w3c/web-based-payment-handler#312, by @ianbjacobs.
-
-
2 issues closed.
-
Remove modifiers from CanMakePaymentEvent? w3c/web-based-payment-handler#289.
-
Need normative text for checking the origin of the SW scope against "supported_origins". w3c/web-based-payment-handler#309.
-
-
4 issues received 6 new comments.
-
Remove modifiers from CanMakePaymentEvent? w3c/web-based-payment-handler#289 (2 comments by @ianbjacobs)
-
Payment Handler window `.focused` field w3c/web-based-payment-handler#307 (2 comments by @adrianhopebailie, @ianbjacobs)
-
Normative what happens when users closing the window opened by PaymentRequestEvent.openWindow w3c/web-based-payment-handler#299 (1 comment by @adrianhopebailie)
-
Add support for PaymentValidationErrors w3c/web-based-payment-handler#306 (1 comment by @ianbjacobs)
-
-
3 pull requests opened.
-
Remove modifiers from CanMakePaymentEvent. w3c/web-based-payment-handler#315, by @rsolomakhin.
-
Incorporate the canMakePayment algorithm of the payment method good practices doc. w3c/web-based-payment-handler#313, by @rsolomakhin.
-
Removed note on payment method manifest and added reference to it w3c/web-based-payment-handler#311, by @ianbjacobs.
-
-
3 pull requests merged.
-
Remove modifiers from CanMakePaymentEvent. w3c/web-based-payment-handler#315.
-
Incorporate the canMakePayment algorithm of the payment method good practices doc. w3c/web-based-payment-handler#313.
-
Removed note on payment method manifest and added reference to it w3c/web-based-payment-handler#311.
-
-
3 pull requests received 12 new comments.
-
Incorporate the canMakePayment algorithm of the payment method good practices doc. w3c/web-based-payment-handler#313 (8 comments by @ianbjacobs, @rsolomakhin)
-
Remove modifiers from CanMakePaymentEvent. w3c/web-based-payment-handler#315 (2 comments by @ianbjacobs, @rsolomakhin)
-
Cross-origin iframes and feature policy. w3c/web-based-payment-handler#282 (2 comments by @marcoscaceres, @rsolomakhin)
-
w3c/payment-method-manifest
-
1 issue opened.
-
Regular expressions for "supported_origins" w3c/payment-method-manifest#29, by @rsolomakhin.
-
w3c/webpayments
-
1 issue received 5 new comments.
-
Visual Identity for Web Payments w3c/webpayments#250 (5 comments by @ianbjacobs, @marcoscaceres, @webpayments)
-
TR publications
-
4 documents published.
-
Payment Request API published 4 times as a Candidate Recommendation Snapshot. History of Payment Request API
-
Participants
-
1 participant joined.
-
Nick Telford-Reed (W3C) joined.
-
-
2 participants left.
-
Chris Marconi (W3C Invited Experts) left.
-
Matthew de Ganon (W3C Invited Experts) left.
-
-
1 organization joined.
-
Coil Technologies, Inc. joined.
-
-
2 organizations left.
-
Yandex left.
-
Unify left.
-
GitHub
w3c/payment-method-id
-
1 issue opened.
-
What can I do with a URL-based payment method identifier? w3c/payment-method-id#52, by @rsolomakhin.
-
-
1 issue received 7 new comments.
-
What can I do with a URL-based payment method identifier? w3c/payment-method-id#52 (7 comments by @ianbjacobs, @rsolomakhin, @stpeter)
-
w3c/web-based-payment-handler
-
5 issues opened.
-
What should payees validate? w3c/web-based-payment-handler#310, by @rsolomakhin.
-
Need normative text for checking the origin of the SW scope against "supported_origins". w3c/web-based-payment-handler#309, by @rsolomakhin.
-
What mechanism allows enforcing payment handler authenticity? w3c/web-based-payment-handler#308, by @rsolomakhin.
-
Payment Handler window `.focused` field w3c/web-based-payment-handler#307, by @rsolomakhin.
-
Add support for PaymentValidationErrors w3c/web-based-payment-handler#306, by @ianbjacobs.
-
-
2 issues received 11 new comments.
-
Payment Handler window `.focused` field w3c/web-based-payment-handler#307 (10 comments by @ianbjacobs, @rsolomakhin)
-
ImageObjects can now reference ImageResource w3c/web-based-payment-handler#238 (1 comment by @dbaron)
-
w3c/payment-request
-
2 issues opened.
-
Providing an `AbortSignal` instead of calling .abort() w3c/payment-request#757, by @marcoscaceres.
-
Modifiers and [[serializedModifierData]] not actually used anywhere. w3c/payment-request#753, by @marcoscaceres.
-
-
6 issues closed.
-
Do we need "doc is fully active" checks on `response.complete()`? w3c/payment-request#731.
-
[NewObject] annotation w3c/payment-request#743.
-
Drop `*Error` from error things ... and `payer*` w3c/payment-request#736.
-
Document privacy and security mitigations w3c/payment-request#675.
-
Retrying a payment w3c/payment-request#705.
-
EventTarget is used by never linked to w3c/payment-request#744.
-
-
1 issue reopened.
-
Signaling payment handler details errors w3c/payment-request#727, by @marcoscaceres.
-
-
9 issues received 27 new comments.
-
Should API support billing address capture (for tax computation)? w3c/payment-request#27 (9 comments by @domenic, @ianbjacobs, @marcoscaceres, @rsolomakhin)
-
Modifiers and [[serializedModifierData]] not actually used anywhere. w3c/payment-request#753 (8 comments by @domenic, @marcoscaceres, @rsolomakhin, @stpeter)
-
Define handling of multiple applicable modifiers w3c/payment-request#684 (3 comments by @ianbjacobs, @marcoscaceres, @stpeter)
-
-
11 pull requests opened.
-
Editorial: fix grammatical error w3c/payment-request#756, by @christianliebel.
-
Rename AddressErrorFields -> AddressErrors w3c/payment-request#755, by @marcoscaceres.
-
fix: state was not closed w3c/payment-request#754, by @marcoscaceres.
-
Support fine-grained errors for payment methods w3c/payment-request#752, by @marcoscaceres.
-
Add support for merchant validation w3c/payment-request#751, by @marcoscaceres.
-
Add error reporting billing address w3c/payment-request#750, by @marcoscaceres.
-
Support requesting billing address w3c/payment-request#749, by @marcoscaceres.
-
Check doc fully active during response.complete() w3c/payment-request#748, by @marcoscaceres.
-
Add error member to PaymentValidationErrors w3c/payment-request#747, by @marcoscaceres.
-
Add [NewObject] annotations to methods w3c/payment-request#746, by @marcoscaceres.
-
Drop prefixes, suffixes from error field members w3c/payment-request#745, by @marcoscaceres.
-
-
12 pull requests merged.
-
Editorial: fix grammatical error w3c/payment-request#756.
-
Check doc fully active during response.complete() w3c/payment-request#748.
-
fix: state was not closed w3c/payment-request#754.
-
Rename AddressErrorFields -> AddressErrors w3c/payment-request#755.
-
Add [NewObject] annotations to methods w3c/payment-request#746.
-
Drop prefixes, suffixes from error field members w3c/payment-request#745.
-
Add secure origin section to security considerations w3c/payment-request#742.
-
iframe usage security subsection w3c/payment-request#741.
-
document show() protections under security considerations w3c/payment-request#740.
-
Added canMakePayment() section to privacy considerations w3c/payment-request#739.
-
Added information about redactList to privacy consideration w3c/payment-request#738.
-
Add PaymentResponse.prototype.onpayerdetailchange w3c/payment-request#724.
-
-
2 pull requests closed.
-
Editorial: use internal slots w3c/payment-request#726.
-
Editorial: describe security mitigations #675 w3c/payment-request#683.
-
-
16 pull requests received 50 new comments.
-
Support fine-grained errors for payment methods w3c/payment-request#752 (16 comments by @domenic, @marcoscaceres, @rsolomakhin, @stpeter)
-
Drop prefixes, suffixes from error field members w3c/payment-request#745 (4 comments by @domenic, @marcoscaceres)
-
Editorial: fix grammatical error w3c/payment-request#756 (3 comments by @christianliebel, @marcoscaceres)
-
Check doc fully active during response.complete() w3c/payment-request#748 (2 comments by @domenic, @marcoscaceres)
-
Add PaymentResponse.prototype.onpayerdetailchange w3c/payment-request#724 (2 comments by @marcoscaceres)
-
Define PaymentResponse.prototype.retry() method w3c/payment-request#720 (1 comment by @marcoscaceres)
-
w3c/webpayments
-
1 issue received 6 new comments.
-
Visual Identity for Web Payments w3c/webpayments#250 (6 comments by @agektmr, @ianbjacobs, @marcoscaceres, @webpayments)
-
TR publications
-
1 document published.
-
Payment Request API published as a Candidate Recommendation Snapshot. History of Payment Request API
-
GitHub
w3c/payment-request
-
10 issues opened.
-
EventTarget is used by never linked to w3c/payment-request#744, by @marcoscaceres.
-
[NewObject] annotation w3c/payment-request#743, by @marcoscaceres.
-
Response timeout could leave page/user in confused state. w3c/payment-request#737, by @marcoscaceres.
-
Drop `*Error` from error things ... and `payer*` w3c/payment-request#736, by @marcoscaceres.
-
Follow up on APA Comments on Web Payments FPWDs w3c/payment-request#735, by @marcoscaceres.
-
Do we need "doc is fully active" checks on `response.complete()`? w3c/payment-request#731, by @marcoscaceres.
-
Always requiring CVV? w3c/payment-request#730, by @marcoscaceres.
-
Add generic `error` member for `.retry()` w3c/payment-request#729, by @marcoscaceres.
-
Update state diagram to include retry() w3c/payment-request#728, by @ianbjacobs.
-
Signaling payment handler details errors w3c/payment-request#727, by @marcoscaceres.
-
-
5 issues closed.
-
Update state diagram to include retry() w3c/payment-request#728.
-
Add equivalent of applepaypaymentmethodchanged w3c/payment-request#662.
-
Always requiring CVV? w3c/payment-request#730.
-
Add explicit extension point to matching algo w3c/payment-request#470.
-
Fine grained error recovery for fields w3c/payment-request#647.
-
-
10 issues received 31 new comments.
-
Signaling payment handler details errors w3c/payment-request#727 (8 comments by @ianbjacobs, @marcoscaceres)
-
Should API support billing address capture (for tax computation)? w3c/payment-request#27 (7 comments by @ianbjacobs, @Krystosterone, @marcoscaceres, @tricky456)
-
Response timeout could leave page/user in confused state. w3c/payment-request#737 (4 comments by @adrianhopebailie, @ianbjacobs, @marcoscaceres)
-
Drop `*Error` from error things ... and `payer*` w3c/payment-request#736 (2 comments by @domenic, @marcoscaceres)
-
Do we need "doc is fully active" checks on `response.complete()`? w3c/payment-request#731 (2 comments by @domenic, @marcoscaceres)
-
Follow up on APA Comments on Web Payments FPWDs w3c/payment-request#735 (2 comments by @ianbjacobs, @marcoscaceres)
-
-
15 pull requests opened.
-
Add secure origin section to security considerations w3c/payment-request#742, by @ianbjacobs.
-
iframe usage security subsection w3c/payment-request#741, by @ianbjacobs.
-
document show() protections under security considerations w3c/payment-request#740, by @ianbjacobs.
-
Added canMakePayment() section to privacy considerations w3c/payment-request#739, by @ianbjacobs.
-
Added information about redactList to privacy consideration w3c/payment-request#738, by @ianbjacobs.
-
editorial: add retry() to state diagram w3c/payment-request#734, by @marcoscaceres.
-
Fix a small bug in `abort`'s error handling. w3c/payment-request#733, by @mrbkap.
-
fix: complete() returns rejected promise w3c/payment-request#732, by @marcoscaceres.
-
Editorial: use internal slots w3c/payment-request#726, by @marcoscaceres.
-
Update test-plan.md after web-platform-tests repo move w3c/payment-request#725, by @foolip.
-
Add PaymentResponse.prototype.onpayerdetailchange w3c/payment-request#724, by @marcoscaceres.
-
Retry request abort the update w3c/payment-request#723, by @marcoscaceres.
-
chore(PULL_REQUEST_TEMPLATE.md): note impact on payment handler w3c/payment-request#722, by @Kronik-Lilus.
-
teach retry() about payerErrors w3c/payment-request#721, by @marcoscaceres.
-
Define PaymentResponse.prototype.retry() method w3c/payment-request#720, by @marcoscaceres.
-
-
9 pull requests merged.
-
Retry request abort the update w3c/payment-request#723.
-
fix: complete() returns rejected promise w3c/payment-request#732.
-
teach retry() about payerErrors w3c/payment-request#721.
-
editorial: add retry() to state diagram w3c/payment-request#734.
-
Define PaymentResponse.prototype.retry() method w3c/payment-request#720.
-
add paymentmethodchange event w3c/payment-request#695.
-
Fix a small bug in `abort`'s error handling. w3c/payment-request#733.
-
Update test-plan.md after web-platform-tests repo move w3c/payment-request#725.
-
fine-grained errors reporting for PaymentAddress w3c/payment-request#712.
-
-
3 pull requests closed.
-
chore(PULL_REQUEST_TEMPLATE.md): note impact on payment handler w3c/payment-request#722.
-
Teach retry() about payerErrors w3c/payment-request#716.
-
Define PaymentResponse.retry() method w3c/payment-request#715.
-
-
11 pull requests received 98 new comments.
-
Add PaymentResponse.prototype.onpayerdetailchange w3c/payment-request#724 (27 comments by @DannyRussellWP, @domenic, @ianbjacobs, @marcoscaceres, @stpeter, @wanli)
-
Define PaymentResponse.prototype.retry() method w3c/payment-request#720 (19 comments by @domenic, @ianbjacobs, @marcoscaceres)
-
fine-grained errors reporting for PaymentAddress w3c/payment-request#712 (7 comments by @domenic, @ianbjacobs, @marcoscaceres)
-
editorial: add retry() to state diagram w3c/payment-request#734 (3 comments by @ianbjacobs, @marcoscaceres)
-
Added information about redactList to privacy consideration w3c/payment-request#738 (2 comments by @ianbjacobs, @marcoscaceres)
-
w3c/webpayments
-
1 issue opened.
-
Visual Identity for Web Payments w3c/webpayments#250, by @ianbjacobs.
-
-
1 issue received 2 new comments.
w3c/web-based-payment-handler
-
1 issue closed.
-
Just in time installation of Payment Handler w3c/web-based-payment-handler#303.
-
-
1 issue received 1 new comment.
-
Just in time installation of Payment Handler w3c/web-based-payment-handler#303 (1 comment by @ianbjacobs)
-
-
1 pull request opened.
-
Simplifying functional event handling w3c/web-based-payment-handler#305, by @jakearchibald.
-
w3c/payment-method-manifest
-
2 issues received 3 new comments.
-
Should this be a part of web app manifest? w3c/payment-method-manifest#27 (2 comments by @adrianhopebailie, @cvan)
-
reconsider extra level of indirection for retrieving a manifest? w3c/payment-method-manifest#10 (1 comment by @cvan)
-
TR publications
-
3 documents published.
-
Payment Request API published twice as a Candidate Recommendation Snapshot. History of Payment Request API
-
Payment Method: Basic Card published as a Working Draft. History of Payment Method: Basic Card
-
Participants
-
1 organization joined.
-
Capital One Discover Network joined.
-
GitHub
w3c/payment-request
-
5 issues opened.
-
Applying "Detached" JWS Signatures to PaymentRequest w3c/payment-request#714, by @cyberphone.
-
Clarify that empty region/regionCode is ok for some locales w3c/payment-request#710, by @marcoscaceres.
-
canMakePayment always return false w3c/payment-request#708, by @cozohar.
-
UX Idea: Favicon in the sheet? w3c/payment-request#707, by @ianbjacobs.
-
Retrying a payment w3c/payment-request#705, by @marcoscaceres.
-
-
11 issues closed.
-
PaymentShippingOption as a subclass of DisplayItem w3c/payment-request#681.
-
Regulatory Compliance Support w3c/payment-request#632.
-
Show better examples of how to deal with change events w3c/payment-request#539.
-
Add contact info / support URL to show() method? w3c/payment-request#687.
-
Applying "Detached" JWS Signatures to PaymentRequest w3c/payment-request#714.
-
Clarify that empty region/regionCode is ok for some locales w3c/payment-request#710.
-
"User accepts the payment request algorithm" needs to clarify where Payment Handlers are invoked w3c/payment-request#476.
-
canMakePayment always return false w3c/payment-request#708.
-
UX Idea: Favicon in the sheet? w3c/payment-request#707.
-
Verifying the total w3c/payment-request#702.
-
Decide on currencySystem w3c/payment-request#617.
-
-
18 issues received 100 new comments.
-
Support for gift cards and discount codes w3c/payment-request#145 (24 comments by @adrianhopebailie, @domenic, @ianbjacobs, @Krystosterone, @marcoscaceres, @mnoorenberghe, @n3o77, @stpeter)
-
Applying "Detached" JWS Signatures to PaymentRequest w3c/payment-request#714 (17 comments by @adrianhopebailie, @cyberphone, @marcoscaceres, @stpeter)
-
Disable Payment Request API in CSP/iframe sandbox w3c/payment-request#698 (10 comments by @clelland, @devd, @ianbjacobs, @shhnjk, @stpeter)
-
UX Idea: Favicon in the sheet? w3c/payment-request#707 (9 comments by @domenic, @ianbjacobs, @marcoscaceres, @stpeter)
-
canMakePayment always return false w3c/payment-request#708 (8 comments by @cozohar, @ianbjacobs, @marcoscaceres, @n3o77)
-
Fine grained error recovery for fields w3c/payment-request#647 (7 comments by @domenic, @marcoscaceres, @mnoorenberghe, @stpeter)
-
Is browser support for PR API configurable? w3c/payment-request#642 (2 comments by @719media, @ianbjacobs)
-
"User accepts the payment request algorithm" needs to clarify where Payment Handlers are invoked w3c/payment-request#476 (2 comments by @ianbjacobs, @marcoscaceres)
-
PaymentShippingOption as a subclass of DisplayItem w3c/payment-request#681 (1 comment by @marcoscaceres)
-
Show better examples of how to deal with change events w3c/payment-request#539 (1 comment by @marcoscaceres)
-
Add contact info / support URL to show() method? w3c/payment-request#687 (1 comment by @marcoscaceres)
-
Alternative 'Pay' button wording options for Browser UI (the button in the sheet) w3c/payment-request#701 (1 comment by @marcoscaceres)
-
-
12 pull requests opened.
-
editorial: small non-normative bug fixes w3c/payment-request#719, by @marcoscaceres.
-
editorial: use ReSpec auto-pluralizer w3c/payment-request#718, by @marcoscaceres.
-
editorial: fix a broken reference w3c/payment-request#717, by @sidvishnoi.
-
Teach retry() about payerErrors w3c/payment-request#716, by @marcoscaceres.
-
Define PaymentResponse.retry() method w3c/payment-request#715, by @marcoscaceres.
-
editorial: relocate Algorithms section w3c/payment-request#713, by @marcoscaceres.
-
fine-grained errors reporting for PaymentAddress w3c/payment-request#712, by @marcoscaceres.
-
editorial: note about inputting regions w3c/payment-request#711, by @marcoscaceres.
-
chore(PULL_REQUEST_TEMPLATE.md): note impact on payment handler w3c/payment-request#709, by @marcoscaceres.
-
editorial: fix "concpet" typo w3c/payment-request#706, by @DrewML.
-
Editorial: devs verify total w3c/payment-request#704, by @marcoscaceres.
-
Editorial: devs verify total w3c/payment-request#703, by @marcoscaceres.
-
-
11 pull requests merged.
-
editorial: small non-normative bug fixes w3c/payment-request#719.
-
editorial: use ReSpec auto-pluralizer w3c/payment-request#718.
-
editorial: fix a broken reference w3c/payment-request#717.
-
editorial: relocate Algorithms section w3c/payment-request#713.
-
editorial: note about inputting regions w3c/payment-request#711.
-
Add regionCode attribute w3c/payment-request#690.
-
chore(PULL_REQUEST_TEMPLATE.md): note impact on payment handler w3c/payment-request#709.
-
editorial: better payment handler integration w3c/payment-request#700.
-
editorial: fix "concpet" typo w3c/payment-request#706.
-
Editorial: devs verify total w3c/payment-request#704.
-
remove currencySystem member w3c/payment-request#694.
-
-
1 pull request closed.
-
Editorial: devs verify total w3c/payment-request#703.
-
-
11 pull requests received 55 new comments.
-
Add regionCode attribute w3c/payment-request#690 (11 comments by @domenic, @ianbjacobs, @marcoscaceres, @stpeter)
-
editorial: better payment handler integration w3c/payment-request#700 (9 comments by @domenic, @marcoscaceres)
-
fine-grained errors reporting for PaymentAddress w3c/payment-request#712 (8 comments by @marcoscaceres, @msujaws)
-
Define PaymentResponse.retry() method w3c/payment-request#715 (6 comments by @marcoscaceres, @stpeter)
-
w3c/web-based-payment-handler
-
3 issues opened.
-
Remove PaymentRequestEvent and CanMakePaymentEvent from ServiceWorker Scope? w3c/web-based-payment-handler#304, by @gogerald.
-
Just in time installation of Payment Handler w3c/web-based-payment-handler#303, by @majaybabu.
-
Drop PaymentInstrument in favor of MethodCapability w3c/web-based-payment-handler#302, by @ianbjacobs.
-
-
3 issues closed.
-
Remove PaymentRequestEvent and CanMakePaymentEvent from ServiceWorker Scope? w3c/web-based-payment-handler#304.
-
Popup messages w3c/web-based-payment-handler#297.
-
topLevelOrigin is a weird name w3c/web-based-payment-handler#259.
-
-
1 issue reopened.
-
Remove PaymentRequestEvent and CanMakePaymentEvent from ServiceWorker Scope? w3c/web-based-payment-handler#304, by @gogerald.
-
-
5 issues received 25 new comments.
-
Suggest changing a shape of openWindow() w3c/web-based-payment-handler#300 (8 comments by @dlongley, @gogerald, @romandev)
-
Remove PaymentRequestEvent and CanMakePaymentEvent from ServiceWorker Scope? w3c/web-based-payment-handler#304 (7 comments by @gogerald, @marcoscaceres, @romandev)
-
Drop PaymentInstrument in favor of MethodCapability w3c/web-based-payment-handler#302 (6 comments by @anthonyvd, @dlongley)
-
Just in time installation of Payment Handler w3c/web-based-payment-handler#303 (3 comments by @gogerald, @majaybabu)
-
-
1 pull request opened.
-
BREAKING CHANGE: Change topLevelOrigin to topOrigin w3c/web-based-payment-handler#301, by @ianbjacobs.
-
-
1 pull request merged.
-
BREAKING CHANGE: Change topLevelOrigin to topOrigin w3c/web-based-payment-handler#301.
-
-
1 pull request received 6 new comments.
-
BREAKING CHANGE: Change topLevelOrigin to topOrigin w3c/web-based-payment-handler#301 (6 comments by @ianbjacobs, @marcoscaceres)
-
w3c/webpayments
-
1 issue opened.
-
Just a question, curious w3c/webpayments#249, by @jehan96.
-
-
1 issue closed.
-
Just a question, curious w3c/webpayments#249.
-
-
1 issue received 1 new comment.
w3c/payment-method-manifest
-
1 issue received 4 new comments.
-
Allow following redirects when requesting payment method ‘HEAD’ w3c/payment-method-manifest#28 (4 comments by @adrianhopebailie, @domenic, @madmath)
-
Participants
-
1 organization joined.
-
Consensys joined.
-
GitHub
w3c/payment-request
-
2 issues opened.
-
Verifying the total w3c/payment-request#702, by @stpeter.
-
Alternative 'Pay' button wording options for Browser UI (the button in the sheet) w3c/payment-request#701, by @hexalys.
-
-
1 issue closed.
-
canMakePayment() needs to match .show() w3c/payment-request#535.
-
-
12 issues received 36 new comments.
-
Alternative 'Pay' button wording options for Browser UI (the button in the sheet) w3c/payment-request#701 (10 comments by @adrianhopebailie, @hexalys, @ianbjacobs, @marcoscaceres, @stpeter)
-
A distinct invoice address should be supported w3c/payment-request#550 (5 comments by @GSPP, @ianbjacobs, @marcoscaceres, @mattsaxon, @mnoorenberghe)
-
Disable Payment Request API in CSP/iframe sandbox w3c/payment-request#698 (3 comments by @clelland, @domenic, @shhnjk)
-
Add support for merchant validation w3c/payment-request#646 (3 comments by @marcoscaceres, @riking, @rsolomakhin)
-
Merchant-specified default shipping address w3c/payment-request#653 (3 comments by @marcoscaceres, @mnoorenberghe)
-
Describe how to implement PaymentAddress.languageCode w3c/payment-request#608 (2 comments by @riking, @stpeter)
-
updateWith(data) should merge with request.data w3c/payment-request#649 (2 comments by @marcoscaceres, @rsolomakhin)
-
PaymentRequest does not handle the case of store pickup w3c/payment-request#389 (1 comment by @Bailey520)
-
-
1 pull request opened.
-
editorial: better payment handler integration w3c/payment-request#700, by @marcoscaceres.
-
-
1 pull request merged.
-
Editorial: align show() and canMakePayment() w3c/payment-request#682.
-
-
5 pull requests received 45 new comments.
-
remove currencySystem member w3c/payment-request#694 (16 comments by @adrianhopebailie, @ianbjacobs, @marcoscaceres)
-
editorial: better payment handler integration w3c/payment-request#700 (14 comments by @domenic, @ianbjacobs, @marcoscaceres)
-
Add regionCode attribute w3c/payment-request#690 (7 comments by @domenic, @marcoscaceres, @mnoorenberghe)
-
Editorial: describe security mitigations #675 w3c/payment-request#683 (2 comments by @ianbjacobs, @stpeter)
-
w3c/web-based-payment-handler
-
13 issues opened.
-
Suggest changing a shape of openWindow() w3c/web-based-payment-handler#300, by @romandev.
-
Normative what happens when users closing the window opened by PaymentRequestEvent.openWindow w3c/web-based-payment-handler#299, by @gogerald.
-
Define the feature policy for the Payment Handler content w3c/web-based-payment-handler#298, by @anthonyvd.
-
Popup messages w3c/web-based-payment-handler#297, by @majaybabu.
-
Need to specify CanMakePaymentEvent.respondWith() behavior w3c/web-based-payment-handler#295, by @romandev.
-
Remove modifiers from CanMakePaymentEvent? w3c/web-based-payment-handler#289, by @rsolomakhin.
-
Call out the need for merchants to validate payment responses w3c/web-based-payment-handler#288, by @rsolomakhin.
-
Need to reuse web app manifest ImageResource better. w3c/web-based-payment-handler#287, by @rsolomakhin.
-
HEAD request for supportedMethods not getting triggered w3c/web-based-payment-handler#286, by @kishoretulsiani.
-
Should PaymentInstruments.set() be immutable? w3c/web-based-payment-handler#285, by @alexshalamov.
-
Found some typos in the wiki w3c/web-based-payment-handler#284, by @mattijsbliek.
-
Block payment handler in iframes by default w3c/web-based-payment-handler#281, by @rsolomakhin.
-
window.open not working from paymentrequest eventlistener w3c/web-based-payment-handler#280, by @majaybabu.
-
-
6 issues closed.
-
Need to reuse web app manifest ImageResource better. w3c/web-based-payment-handler#287.
-
HEAD request for supportedMethods not getting triggered w3c/web-based-payment-handler#286.
-
Establish Editorial process w3c/web-based-payment-handler#156.
-
Revisiting Payment Method specific filter/capability matching w3c/web-based-payment-handler#157.
-
Found some typos in the wiki w3c/web-based-payment-handler#284.
-
Payment manifest supporting multiple payments apps from different providers? w3c/web-based-payment-handler#270.
-
-
22 issues received 77 new comments.
-
window.open not working from paymentrequest eventlistener w3c/web-based-payment-handler#280 (14 comments by @majaybabu, @romandev, @rsolomakhin)
-
topLevelOrigin is a weird name w3c/web-based-payment-handler#259 (9 comments by @adrianhopebailie, @anthonyvd, @domenic, @rsolomakhin)
-
HEAD request for supportedMethods not getting triggered w3c/web-based-payment-handler#286 (9 comments by @ianbjacobs, @majaybabu, @rsolomakhin)
-
ImageObjects can now reference ImageResource w3c/web-based-payment-handler#238 (6 comments by @domenic, @ianbjacobs, @kenchris, @rsolomakhin)
-
Open Window Algorithm w3c/web-based-payment-handler#115 (5 comments by @dlongley, @ianbjacobs, @romandev, @rsolomakhin)
-
Need to reuse web app manifest ImageResource better. w3c/web-based-payment-handler#287 (4 comments by @domenic, @ianbjacobs, @kenchris, @rsolomakhin)
-
Consider explaining the connection with payment method manifests sooner w3c/web-based-payment-handler#269 (3 comments by @anthonyvd, @ianbjacobs, @marcoscaceres)
-
Call out the need for merchants to validate payment responses w3c/web-based-payment-handler#288 (3 comments by @rsolomakhin, @stpeter)
-
Block payment handler in iframes by default w3c/web-based-payment-handler#281 (3 comments by @ianbjacobs, @rsolomakhin)
-
Suggest changing a shape of openWindow() w3c/web-based-payment-handler#300 (2 comments by @gogerald, @ianbjacobs)
-
interaction with payment methods doesn't appear to be defined w3c/web-based-payment-handler#249 (2 comments by @marcoscaceres, @rsolomakhin)
-
Remove modifiers from CanMakePaymentEvent? w3c/web-based-payment-handler#289 (2 comments by @ianbjacobs, @rsolomakhin)
-
Should PaymentInstruments.set() be immutable? w3c/web-based-payment-handler#285 (2 comments by @alexshalamov, @romandev)
-
Found some typos in the wiki w3c/web-based-payment-handler#284 (2 comments by @ianbjacobs, @mattijsbliek)
-
Normative what happens when users closing the window opened by PaymentRequestEvent.openWindow w3c/web-based-payment-handler#299 (1 comment by @gogerald)
-
Define the feature policy for the Payment Handler content w3c/web-based-payment-handler#298 (1 comment by @marcoscaceres)
-
Need to specify CanMakePaymentEvent.respondWith() behavior w3c/web-based-payment-handler#295 (1 comment by @stpeter)
-
Revisiting Payment Method specific filter/capability matching w3c/web-based-payment-handler#157 (1 comment by @ianbjacobs)
-
Payment manifest supporting multiple payments apps from different providers? w3c/web-based-payment-handler#270 (1 comment by @ianbjacobs)
-
-
10 pull requests opened.
-
Define CanMakePaymentEvent.respondWith() behavior w3c/web-based-payment-handler#296, by @romandev.
-
Should throw InvalidStateError if PaymentRequestEvent is not trusted w3c/web-based-payment-handler#294, by @romandev.
-
Add [SameObject] to paymentManager attribute w3c/web-based-payment-handler#293, by @romandev.
-
Remove link to issue 157 w3c/web-based-payment-handler#292, by @romandev.
-
Throws NotAllowedError instead of InvalidAccessError w3c/web-based-payment-handler#291, by @romandev.
-
Update Example6 and Example7 w3c/web-based-payment-handler#290, by @romandev.
-
HTTPS considerations. w3c/web-based-payment-handler#283, by @rsolomakhin.
-
Cross-origin iframes and feature policy. w3c/web-based-payment-handler#282, by @rsolomakhin.
-
Link ot issue 115 that supersedes issue 97 w3c/web-based-payment-handler#279, by @rsolomakhin.
-
Consistent use of quotes. w3c/web-based-payment-handler#278, by @rsolomakhin.
-
-
6 pull requests merged.
-
Add [SameObject] to paymentManager attribute w3c/web-based-payment-handler#293.
-
Throws NotAllowedError instead of InvalidAccessError w3c/web-based-payment-handler#291.
-
Should throw InvalidStateError if PaymentRequestEvent is not trusted w3c/web-based-payment-handler#294.
-
Consistent use of quotes. w3c/web-based-payment-handler#278.
-
Link ot issue 115 that supersedes issue 97 w3c/web-based-payment-handler#279.
-
Replace 'enabledMethods' array with 'method' string. w3c/web-based-payment-handler#276.
-
-
9 pull requests received 29 new comments.
-
Cross-origin iframes and feature policy. w3c/web-based-payment-handler#282 (5 comments by @marcoscaceres, @rsolomakhin)
-
Throws NotAllowedError instead of InvalidAccessError w3c/web-based-payment-handler#291 (4 comments by @romandev, @rsolomakhin)
-
Add [SameObject] to paymentManager attribute w3c/web-based-payment-handler#293 (4 comments by @romandev, @rsolomakhin)
-
Should throw InvalidStateError if PaymentRequestEvent is not trusted w3c/web-based-payment-handler#294 (4 comments by @romandev, @rsolomakhin)
-
Replace 'enabledMethods' array with 'method' string. w3c/web-based-payment-handler#276 (4 comments by @ianbjacobs, @rsolomakhin)
-
Remove link to issue 157 w3c/web-based-payment-handler#292 (3 comments by @marcoscaceres, @rsolomakhin)
-
Define CanMakePaymentEvent.respondWith() behavior w3c/web-based-payment-handler#296 (2 comments by @romandev, @rsolomakhin)
-
Link ot issue 115 that supersedes issue 97 w3c/web-based-payment-handler#279 (1 comment by @rsolomakhin)
-
w3c/payment-method-manifest
-
2 issues opened.
-
Allow following redirects when requesting payment method ‘HEAD’ w3c/payment-method-manifest#28, by @gogerald.
-
Should this be a part of web app manifest? w3c/payment-method-manifest#27, by @rsolomakhin.
-
-
2 issues received 5 new comments.
-
Allow following redirects when requesting payment method ‘HEAD’ w3c/payment-method-manifest#28 (3 comments by @domenic, @gogerald)
-
Should this be a part of web app manifest? w3c/payment-method-manifest#27 (2 comments by @kenchris, @RByers)
-
w3c/webpayments
-
9 issues closed.
-
ISO20022 terminology adoption w3c/webpayments#93.
-
Synonym Mapping from Web Environment Terminology to ISO 20022 Terminonogy w3c/webpayments#95.
-
Sepamail WebIDL syntax and algorithms w3c/webpayments#219.
-
Adopt a "test as you commit" policy w3c/webpayments#234.
-
propose to add encoding attribute to data set w3c/webpayments#181.
-
Terminology across all Web Payments documents should be aligned w3c/webpayments#135.
-
What happens if there’s a failure before the payment response promise resolves? w3c/webpayments#141.
-
Should the WPWG develop a cryptocurrency payment method specification w3c/webpayments#232.
-
-
9 issues received 13 new comments.
-
Synonym Mapping from Web Environment Terminology to ISO 20022 Terminonogy w3c/webpayments#95 (2 comments by @ianbjacobs, @webpayments)
-
propose to add encoding attribute to data set w3c/webpayments#181 (2 comments by @ianbjacobs, @webpayments)
-
Terminology across all Web Payments documents should be aligned w3c/webpayments#135 (1 comment by @ianbjacobs)
-
What happens if there’s a failure before the payment response promise resolves? w3c/webpayments#141 (1 comment by @ianbjacobs)
-
Propose a payment method specification that includes an example of field level security w3c/webpayments#179 (1 comment by @ianbjacobs)
-
Should the WPWG develop a cryptocurrency payment method specification w3c/webpayments#232 (1 comment by @ianbjacobs)
w3c/payment-request-info
-
1 issue closed.
-
Work with MDN w3c/payment-request-info#4.
-
-
1 issue received 4 new comments.
Lifecycle
-
1 charter started.
-
Chartered until 31 December 2019.
-
TR publications
-
3 documents published.
-
Payment Request API published twice as a Candidate Recommendation Snapshot. History of Payment Request API
-
Payment Method: Basic Card published as a Working Draft. History of Payment Method: Basic Card
-
Participants
-
2 organizations joined.
-
Groupement des Cartes Bancaires joined.
-
BlueSnap joined.
-
GitHub
w3c/payment-request
-
4 issues opened.
-
support of VAT w3c/payment-request#699, by @repalogic.
-
Disable Payment Request API in CSP/iframe sandbox w3c/payment-request#698, by @shhnjk.
-
Add link to SecureContext test w3c/payment-request#697, by @marcoscaceres.
-
When "pay" happens, PaymentAddress request and response should match. w3c/payment-request#692, by @marcoscaceres.
-
-
7 issues closed.
-
Unknown currencySystem should throw w3c/payment-request#686.
-
404 on some tests w3c/payment-request#630.
-
When "pay" happens, PaymentAddress request and response should match. w3c/payment-request#692.
-
Clarify addressLine definition w3c/payment-request#676.
-
Make Payment Address construction into its own sub algorithm w3c/payment-request#643.
-
redact full shipping address from event until payment response w3c/payment-request#648.
-
Require user gesture when `.show()` is called w3c/payment-request#651.
-
-
13 issues received 32 new comments.
-
Disable Payment Request API in CSP/iframe sandbox w3c/payment-request#698 (5 comments by @ianbjacobs, @marcoscaceres, @rsolomakhin)
-
Add contact info / support URL to show() method? w3c/payment-request#687 (5 comments by @ianbjacobs, @marcoscaceres, @stpeter)
-
Add equivalent of applepaypaymentmethodchanged w3c/payment-request#662 (3 comments by @marcoscaceres, @rsolomakhin, @stpeter)
-
Should API support billing address capture (for tax computation)? w3c/payment-request#27 (3 comments by @ianbjacobs, @rsolomakhin, @stpeter)
-
"User accepts the payment request algorithm" needs to clarify where Payment Handlers are invoked w3c/payment-request#476 (3 comments by @rsolomakhin, @stpeter)
-
A distinct invoice address should be supported w3c/payment-request#550 (2 comments by @ianbjacobs, @repalogic)
-
When "pay" happens, PaymentAddress request and response should match. w3c/payment-request#692 (2 comments by @hsivonen, @marcoscaceres)
-
Describe how to implement PaymentAddress.languageCode w3c/payment-request#608 (2 comments by @marcoscaceres, @rsolomakhin)
-
Make Payment Address construction into its own sub algorithm w3c/payment-request#643 (1 comment by @marcoscaceres)
-
Add way to update `total` and `displayItems` after `.show()` but before user interaction w3c/payment-request#645 (1 comment by @rsolomakhin)
-
-
7 pull requests opened.
-
PaymentOptions.shippingType definition should link to PaymentShippingType, not to itself w3c/payment-request#696, by @dbaron.
-
add paymentmethodchange event w3c/payment-request#695, by @marcoscaceres.
-
remove currencySystem member w3c/payment-request#694, by @marcoscaceres.
-
test: show() triggered by user activation w3c/payment-request#693, by @marcoscaceres.
-
editorial: fix links to tests w3c/payment-request#691, by @marcoscaceres.
-
Add regionCode attribute w3c/payment-request#690, by @marcoscaceres.
-
fix: unknown currencySystem throws w3c/payment-request#689, by @marcoscaceres.
-
-
6 pull requests merged.
-
PaymentOptions.shippingType definition should link to PaymentShippingType, not to itself w3c/payment-request#696.
-
test: show() triggered by user activation w3c/payment-request#693.
-
fix: unknown currencySystem throws w3c/payment-request#689.
-
editorial: fix links to tests w3c/payment-request#691.
-
add redactList for PaymentAddress (Part 1) w3c/payment-request#654.
-
show() must be triggered by user activation w3c/payment-request#655.
-
-
9 pull requests received 97 new comments.
-
add redactList for PaymentAddress (Part 1) w3c/payment-request#654 (34 comments by @domenic, @marcoscaceres, @rsolomakhin)
-
Add regionCode attribute w3c/payment-request#690 (28 comments by @domenic, @marcoscaceres, @mnoorenberghe, @rsolomakhin, @sebsg)
-
remove currencySystem member w3c/payment-request#694 (16 comments by @adrianhopebailie, @domenic, @ianbjacobs, @marcoscaceres, @rsolomakhin, @stpeter, @webpayments-specs)
-
show() must be triggered by user activation w3c/payment-request#655 (7 comments by @marcoscaceres, @rsolomakhin)
-
w3c/web-based-payment-handler
-
20 issues opened.
-
Review userHint w3c/web-based-payment-handler#273, by @ianbjacobs.
-
Payment manifest supporting multiple payments apps from different providers? w3c/web-based-payment-handler#270, by @arisc097.
-
Consider explaining the connection with payment method manifests sooner w3c/web-based-payment-handler#269, by @domenic.
-
Normative MUSTs inside a non-normative note w3c/web-based-payment-handler#268, by @domenic.
-
Inconsistent DOMException styles w3c/web-based-payment-handler#267, by @domenic.
-
"Dispatch e to global" should link w3c/web-based-payment-handler#266, by @domenic.
-
Structured clone usage seems wrong w3c/web-based-payment-handler#265, by @domenic.
-
Editorial tweaks to " MethodData Population Algorithm" w3c/web-based-payment-handler#264, by @domenic.
-
Origin definitions are imprecise w3c/web-based-payment-handler#263, by @domenic.
-
Move normative requirements on PaymentRequestEvent to the processing model w3c/web-based-payment-handler#262, by @domenic.
-
Get rid of normative requirements inside dictionary member definitions w3c/web-based-payment-handler#261, by @domenic.
-
Use the correct origin serialization w3c/web-based-payment-handler#260, by @domenic.
-
topLevelOrigin is a weird name w3c/web-based-payment-handler#259, by @domenic.
-
Integrate better with the payment request spec w3c/web-based-payment-handler#258, by @domenic.
-
Do not use "context object" w3c/web-based-payment-handler#257, by @domenic.
-
PaymentInstruments internal storage could be clearer w3c/web-based-payment-handler#256, by @domenic.
-
PaymentInstruments is missing values() and entries() w3c/web-based-payment-handler#255, by @domenic.
-
Incorrect destructing in example w3c/web-based-payment-handler#254, by @domenic.
-
PaymentManager behavior unclear w3c/web-based-payment-handler#253, by @domenic.
-
How would iDeal work? w3c/web-based-payment-handler#251, by @bdewater.
-
-
4 issues closed.
-
Move normative requirements on PaymentRequestEvent to the processing model w3c/web-based-payment-handler#262.
-
Use the correct origin serialization w3c/web-based-payment-handler#260.
-
Inconsistent DOMException styles w3c/web-based-payment-handler#267.
-
Incorrect destructing in example w3c/web-based-payment-handler#254.
-
-
10 issues received 34 new comments.
-
Payment manifest supporting multiple payments apps from different providers? w3c/web-based-payment-handler#270 (14 comments by @adrianhopebailie, @gogerald, @ianbjacobs, @majaybabu, @majaybabupayment, @rsolomakhin)
-
How would iDeal work? w3c/web-based-payment-handler#251 (10 comments by @adrianhopebailie, @arisc097, @bdewater, @glelouarn, @ianbjacobs, @rsolomakhin)
-
Image fetching does not seem to be defined w3c/web-based-payment-handler#237 (3 comments by @annevk, @domenic)
-
Normative MUSTs inside a non-normative note w3c/web-based-payment-handler#268 (1 comment by @rsolomakhin)
-
Consider explaining the connection with payment method manifests sooner w3c/web-based-payment-handler#269 (1 comment by @rsolomakhin)
-
Editorial tweaks to " MethodData Population Algorithm" w3c/web-based-payment-handler#264 (1 comment by @domenic)
-
ImageObjects can now reference ImageResource w3c/web-based-payment-handler#238 (1 comment by @domenic)
-
-
7 pull requests opened.
-
Remove requestPermission() w3c/web-based-payment-handler#277, by @rsolomakhin.
-
Replace 'enabledMethods' array with 'method' string. w3c/web-based-payment-handler#276, by @rsolomakhin.
-
Use the correct origin serialization w3c/web-based-payment-handler#275, by @romandev.
-
chore: tidy up w3c/web-based-payment-handler#274, by @romandev.
-
Fix incorrect destructing in example w3c/web-based-payment-handler#272, by @romandev.
-
Editorial: Fix inconsistent DOMException styles w3c/web-based-payment-handler#271, by @romandev.
-
chore(PULL_REQUEST_TEMPLATE): add pull request template w3c/web-based-payment-handler#252, by @marcoscaceres.
-
-
6 pull requests merged.
-
Use the correct origin serialization w3c/web-based-payment-handler#275.
-
chore: tidy up w3c/web-based-payment-handler#274.
-
Add CanMakePaymentEvent. w3c/web-based-payment-handler#170.
-
Editorial: Fix inconsistent DOMException styles w3c/web-based-payment-handler#271.
-
Fix incorrect destructing in example w3c/web-based-payment-handler#272.
-
chore(PULL_REQUEST_TEMPLATE): add pull request template w3c/web-based-payment-handler#252.
-
-
1 pull request closed.
-
work in progress: simplification of various things w3c/web-based-payment-handler#247.
-
-
6 pull requests received 18 new comments.
-
Add CanMakePaymentEvent. w3c/web-based-payment-handler#170 (12 comments by @ianbjacobs, @marcoscaceres, @rsolomakhin)
-
work in progress: simplification of various things w3c/web-based-payment-handler#247 (2 comments by @marcoscaceres, @rsolomakhin)
-
Replace 'enabledMethods' array with 'method' string. w3c/web-based-payment-handler#276 (1 comment by @ianbjacobs)
-
Fix incorrect destructing in example w3c/web-based-payment-handler#272 (1 comment by @marcoscaceres)
-
w3c/webpayments
-
1 pull request opened.
-
specific IL-RFC versions in Interledger readme w3c/webpayments#248, by @michielbdejong.
-
-
1 pull request closed.
-
specific IL-RFC versions in Interledger readme w3c/webpayments#248.
-
-
1 pull request received 5 new comments.
-
specific IL-RFC versions in Interledger readme w3c/webpayments#248 (5 comments by @adrianhopebailie, @michielbdejong)
-
TR publications
-
1 document published.
-
Payment Request API published as a Candidate Recommendation Snapshot. History of Payment Request API
-
Participants
-
1 organization left.
-
Camara Interbancaria de Pagamentos (CIP) left.
-
GitHub
w3c/payment-request
-
6 issues opened.
-
Add contact info / support URL to show() method? w3c/payment-request#687, by @stpeter.
-
Unknown currencySystem should throw w3c/payment-request#686, by @marcoscaceres.
-
Define handling of multiple applicable modifiers w3c/payment-request#684, by @mnoorenberghe.
-
PaymentShippingOption as a subclass of DisplayItem w3c/payment-request#681, by @marcoscaceres.
-
Guidance on shipping options (mostly for devs) w3c/payment-request#680, by @marcoscaceres.
-
-
4 issues closed.
-
Add way to update `total` and `displayItems` after `.show()` but before user interaction w3c/payment-request#645.
-
Add type to PaymentItem w3c/payment-request#163.
-
Standardize phone number format w3c/payment-request#652.
-
FR: 3DS w3c/payment-request#685.
-
-
1 issue reopened.
-
Define handling of multiple applicable modifiers w3c/payment-request#684, by @rsolomakhin.
-
-
13 issues received 44 new comments.
-
Define handling of multiple applicable modifiers w3c/payment-request#684 (16 comments by @adrianhopebailie, @ianbjacobs, @marcoscaceres, @mnoorenberghe, @rsolomakhin, @stpeter)
-
Guidance on shipping options (mostly for devs) w3c/payment-request#680 (7 comments by @domenic, @marcoscaceres, @mnoorenberghe, @rsolomakhin)
-
PaymentShippingOption as a subclass of DisplayItem w3c/payment-request#681 (5 comments by @domenic, @marcoscaceres, @mnoorenberghe)
-
Merchant-specified default shipping address w3c/payment-request#653 (3 comments by @ianbjacobs, @marcoscaceres)
-
Is paypment request gated behind https? w3c/payment-request#658 (3 comments by @ianbjacobs, @rsolomakhin)
-
Document privacy and security mitigations w3c/payment-request#675 (2 comments by @ianbjacobs, @marcoscaceres)
-
Add contact info / support URL to show() method? w3c/payment-request#687 (1 comment by @rsolomakhin)
-
"User accepts the payment request algorithm" needs to clarify where Payment Handlers are invoked w3c/payment-request#476 (1 comment by @ianbjacobs)
-
Add way to update `total` and `displayItems` after `.show()` but before user interaction w3c/payment-request#645 (1 comment by @aestes)
-
-
3 pull requests opened.
-
test: link to shipping option test w3c/payment-request#688, by @marcoscaceres.
-
Editorial: describe security mitigations #675 w3c/payment-request#683, by @ianbjacobs.
-
Editorial: align show() and canMakePayment() w3c/payment-request#682, by @ianbjacobs.
-
-
4 pull requests merged.
-
Feat: allow show() to take optional detailsPromise w3c/payment-request#672.
-
test: link to shipping option test w3c/payment-request#688.
-
Feat: adds PaymentItemType enum and PaymentItem.type w3c/payment-request#666.
-
Add localization hint for payment sheet w3c/payment-request#656.
-
-
5 pull requests received 45 new comments.
-
Editorial: describe security mitigations #675 w3c/payment-request#683 (17 comments by @ianbjacobs, @marcoscaceres, @stpeter)
-
Editorial: align show() and canMakePayment() w3c/payment-request#682 (10 comments by @ianbjacobs, @marcoscaceres)
-
add redactList for PaymentAddress (Part 1) w3c/payment-request#654 (8 comments by @marcoscaceres, @rsolomakhin)
-
Feat: allow show() to take optional detailsPromise w3c/payment-request#672 (5 comments by @ianbjacobs, @marcoscaceres)
-
Feat: adds PaymentItemType enum and PaymentItem.type w3c/payment-request#666 (5 comments by @adrianba, @ianbjacobs, @marcoscaceres, @stpeter)
-
w3c/web-based-payment-handler
-
3 issues opened.
-
Indicate to the payment handler whether the user agent showed payment sheet? w3c/web-based-payment-handler#250, by @rsolomakhin.
-
interaction with payment methods doesn't appear to be defined w3c/web-based-payment-handler#249, by @dbaron.
-
Use payment method manifest for registration-time validation? w3c/web-based-payment-handler#248, by @ianbjacobs.
-
-
6 issues received 25 new comments.
-
What happens when clearing site data? w3c/web-based-payment-handler#236 (10 comments by @annevk, @ianbjacobs, @marcoscaceres, @rsolomakhin)
-
Indicate to the payment handler whether the user agent showed payment sheet? w3c/web-based-payment-handler#250 (5 comments by @adrianhopebailie, @ianbjacobs, @rsolomakhin, @stpeter)
-
Proposal: Remove requestPermission() w3c/web-based-payment-handler#246 (5 comments by @ianbjacobs, @marcoscaceres, @mgiuca, @rsolomakhin)
-
Use payment method manifest for registration-time validation? w3c/web-based-payment-handler#248 (3 comments by @ianbjacobs, @rsolomakhin)
-
interaction with payment methods doesn't appear to be defined w3c/web-based-payment-handler#249 (1 comment by @ianbjacobs)
-
-
1 pull request opened.
-
work in progress: simplification of various things w3c/web-based-payment-handler#247, by @marcoscaceres.
-
-
1 pull request merged.
-
Editorial: Replace site with origin; mark as informative w3c/web-based-payment-handler#245.
-
-
1 pull request received 4 new comments.
-
Only allows instrument.set() in active service worker w3c/web-based-payment-handler#224 (4 comments by @ianbjacobs, @marcoscaceres, @romandev)
-
w3c/payment-method-manifest
-
1 issue opened.
-
Terms and conditions text to be displayed near Pay button w3c/payment-method-manifest#26, by @ianbjacobs.
-
w3c/webpayments
-
3 pull requests opened.
-
Remove localBiblio from Interledger spec w3c/webpayments#247, by @adrianhopebailie.
-
refer to specific versions of IL-RFCs w3c/webpayments#246, by @michielbdejong.
-
Interledger Payment Method w3c/webpayments#245, by @adrianhopebailie.
-
-
2 pull requests merged.
-
Remove localBiblio from Interledger spec w3c/webpayments#247.
-
Interledger Payment Method w3c/webpayments#245.
-
-
1 pull request closed.
-
refer to specific versions of IL-RFCs w3c/webpayments#246.
-
-
2 pull requests received 11 new comments.
-
refer to specific versions of IL-RFCs w3c/webpayments#246 (10 comments by @adrianhopebailie, @marcoscaceres, @michielbdejong)
-
w3c/payment-request-info
-
1 issue received 10 new comments.
-
Work with MDN w3c/payment-request-info#4 (10 comments by @chrisdavidmills, @ianbjacobs, @poshaughnessy, @rsolomakhin)
-
TR publications
-
2 documents published.
-
Payment Request API published as a Candidate Recommendation Snapshot. History of Payment Request API
-
Payment Handler API published as a Working Draft. History of Payment Handler API
-
Participants
-
1 organization joined.
-
Discover Financial Services LLC joined.
-
GitHub
w3c/payment-method-manifest
-
1 issue received 1 new comment.
-
reconsider extra level of indirection for retrieving a manifest? w3c/payment-method-manifest#10 (1 comment by @triblondon)
-
w3c/web-based-payment-handler
-
1 issue opened.
-
Proposal: Remove requestPermission() w3c/web-based-payment-handler#246, by @rsolomakhin.
-
-
4 issues closed.
-
User consent and permissions w3c/web-based-payment-handler#239.
-
Just-in-time payment handler install w3c/web-based-payment-handler#240.
-
Relation between merchant order of payment methods and payment app order of instruments w3c/web-based-payment-handler#116.
-
Does payment instrument registration imply a display order? w3c/web-based-payment-handler#243.
-
-
6 issues received 24 new comments.
-
Just-in-time payment handler install w3c/web-based-payment-handler#240 (13 comments by @domenic, @gogerald, @ianbjacobs, @rsolomakhin)
-
Proposal: Remove requestPermission() w3c/web-based-payment-handler#246 (6 comments by @mgiuca, @romandev, @rsolomakhin)
-
Relation between merchant order of payment methods and payment app order of instruments w3c/web-based-payment-handler#116 (1 comment by @ianbjacobs)
-
Does payment instrument registration imply a display order? w3c/web-based-payment-handler#243 (1 comment by @ianbjacobs)
-
-
1 pull request opened.
-
Editorial: Replace site with origin; mark as informative w3c/web-based-payment-handler#245, by @ianbjacobs.
-
-
1 pull request merged.
-
Edits regarding ordering based on 7 Dec WG teleconf w3c/web-based-payment-handler#242.
-
-
1 pull request closed.
-
add a "public computing" section to security/privacy considerations w3c/web-based-payment-handler#244.
-
-
2 pull requests received 10 new comments.
-
Edits regarding ordering based on 7 Dec WG teleconf w3c/web-based-payment-handler#242 (5 comments by @ianbjacobs, @kmealey, @marcoscaceres, @msporny)
-
add a "public computing" section to security/privacy considerations w3c/web-based-payment-handler#244 (5 comments by @ianbjacobs, @marcoscaceres)
-
w3c/payment-request
-
2 issues opened.
-
Clarify addressLine definition w3c/payment-request#676, by @stpeter.
-
Document privacy and security mitigations w3c/payment-request#675, by @marcoscaceres.
-
-
19 issues closed.
-
Editorial: PaymentRequestUpdateEvent constructor w3c/payment-request#543.
-
"Exposing available payment methods" is confusing given the existence of canMakePayment() w3c/payment-request#629.
-
Authors are not conformance classes w3c/payment-request#440.
-
Clarity required in section 21.2 regarding privacy w3c/payment-request#475.
-
Move to an incremental feature release model w3c/payment-request#625.
-
Clarify the `displayItems` are not shared with payment handler w3c/payment-request#626.
-
Unclear what happens when multiple PRs call show() w3c/payment-request#462.
-
Dealing with name as returned by the API (i18n) w3c/payment-request#634.
-
Is browser support for PR API configurable? w3c/payment-request#642.
-
Use HTML's (or infra) definition of “valid decimal monetary value”, once available w3c/payment-request#301.
-
How are digital signatures supported for Payment Requests? w3c/payment-request#291.
-
Should the web page be able to provide status information before calling complete() w3c/payment-request#5.
-
API Data Integrity w3c/payment-request#31.
-
Should the API support field validation? w3c/payment-request#225.
-
show() method lacks developer guidance w3c/payment-request#461.
-
Editors to figure out text on line items w3c/payment-request#477.
-
updateWith(data) should merge with request.data w3c/payment-request#649.
-
Make paymentRequest.id a UUID a must w3c/payment-request#588.
-
Request: designated receiver for Payment Response w3c/payment-request#660.
-
-
1 issue reopened.
-
Standardize phone number format w3c/payment-request#652, by @marcoscaceres.
-
-
27 issues received 72 new comments.
-
Add equivalent of applepaypaymentmethodchanged w3c/payment-request#662 (7 comments by @aestes, @marcoscaceres, @mnoorenberghe)
-
Standardize phone number format w3c/payment-request#652 (7 comments by @asolove-stripe, @marcoscaceres, @rsolomakhin, @stpeter)
-
"User accepts the payment request algorithm" needs to clarify where Payment Handlers are invoked w3c/payment-request#476 (6 comments by @ianbjacobs, @marcoscaceres)
-
Authors are not conformance classes w3c/payment-request#440 (6 comments by @domenic, @dontcallmedom, @ianbjacobs, @marcoscaceres)
-
updateWith(data) should merge with request.data w3c/payment-request#649 (6 comments by @domenic, @marcoscaceres, @rsolomakhin)
-
Clarify addressLine definition w3c/payment-request#676 (5 comments by @ianbjacobs, @marcoscaceres, @stpeter)
-
Allow locale to be specified by the developer. w3c/payment-request#650 (4 comments by @domenic, @marcoscaceres, @stpeter)
-
Add way to update `total` and `displayItems` after `.show()` but before user interaction w3c/payment-request#645 (4 comments by @marcoscaceres, @michelle)
-
redact full shipping address from event until payment response w3c/payment-request#648 (4 comments by @aestes, @ianbjacobs, @marcoscaceres)
-
"Exposing available payment methods" is confusing given the existence of canMakePayment() w3c/payment-request#629 (3 comments by @domenic, @marcoscaceres)
-
How are digital signatures supported for Payment Requests? w3c/payment-request#291 (2 comments by @adrianhopebailie, @marcoscaceres)
-
Clarify the `displayItems` are not shared with payment handler w3c/payment-request#626 (2 comments by @cyberphone, @marcoscaceres)
-
Request: designated receiver for Payment Response w3c/payment-request#660 (2 comments by @marcoscaceres)
-
Add dir/lang member on dictionaries whose content is displayed in browser UI w3c/payment-request#327 (1 comment by @marcoscaceres)
-
Unclear what happens when multiple PRs call show() w3c/payment-request#462 (1 comment by @marcoscaceres)
-
Pre-filter shipping addresses, e.g. by country w3c/payment-request#614 (1 comment by @marcoscaceres)
-
Dealing with name as returned by the API (i18n) w3c/payment-request#634 (1 comment by @marcoscaceres)
-
Use HTML's (or infra) definition of “valid decimal monetary value”, once available w3c/payment-request#301 (1 comment by @marcoscaceres)
-
How do the payer and payee agree on the payment obligation as part of the flow? w3c/payment-request#113 (1 comment by @marcoscaceres)
-
Should the web page be able to provide status information before calling complete() w3c/payment-request#5 (1 comment by @marcoscaceres)
-
-
12 pull requests opened.
-
Editorial: Call out payment handlers in abort() w3c/payment-request#679, by @ianbjacobs.
-
Call out payment handlers in abort() w3c/payment-request#678, by @ianbjacobs.
-
Editorial: PaymentRequestUpdateEvent ctor algo w3c/payment-request#674, by @marcoscaceres.
-
Editorial fixes w3c/payment-request#673, by @marcoscaceres.
-
Feat: allow show() to take optional detailsPromise w3c/payment-request#672, by @marcoscaceres.
-
Editorial: define update a PaymentRequest's details algo w3c/payment-request#671, by @marcoscaceres.
-
privacy: dont share line items w3c/payment-request#670, by @marcoscaceres.
-
Spread resolved `data` on updateWith() w3c/payment-request#669, by @marcoscaceres.
-
wip: allow show() to take optional promise w3c/payment-request#668, by @marcoscaceres.
-
Editorial: fixup updateWith() example w3c/payment-request#667, by @marcoscaceres.
-
Feat: adds PaymentItemType enum and PaymentItem.type w3c/payment-request#666, by @marcoscaceres.
-
Assure PaymentRequest.id is a UUID (closes #588) w3c/payment-request#665, by @marcoscaceres.
-
-
7 pull requests merged.
-
Editorial: Call out payment handlers in abort() w3c/payment-request#679.
-
Editorial: PaymentRequestUpdateEvent ctor algo w3c/payment-request#674.
-
Editorial fixes w3c/payment-request#673.
-
Editorial: define update a PaymentRequest's details algo w3c/payment-request#671.
-
privacy: dont share line items w3c/payment-request#670.
-
Assure PaymentRequest.id is a UUID (closes #588) w3c/payment-request#665.
-
Editorial: fixup updateWith() example w3c/payment-request#667.
-
-
4 pull requests closed.
-
Call out payment handlers in abort() w3c/payment-request#678.
-
Suggested emphasis of privacy protections w3c/payment-request#628.
-
wip: allow show() to take optional promise w3c/payment-request#668.
-
Spread resolved `data` on updateWith() w3c/payment-request#669.
-
-
14 pull requests received 74 new comments.
-
Feat: adds PaymentItemType enum and PaymentItem.type w3c/payment-request#666 (19 comments by @adrianhopebailie, @domenic, @marcoscaceres, @mnoorenberghe, @rsolomakhin, @stpeter, @zkoch)
-
add redactList for PaymentAddress (Part 1) w3c/payment-request#654 (10 comments by @domenic, @marcoscaceres, @stpeter)
-
Add localization hint for payment sheet w3c/payment-request#656 (9 comments by @domenic, @marcoscaceres, @stpeter)
-
wip: allow show() to take optional promise w3c/payment-request#668 (9 comments by @domenic, @marcoscaceres)
-
Editorial: fixup updateWith() example w3c/payment-request#667 (7 comments by @ianbjacobs, @marcoscaceres)
-
Spread resolved `data` on updateWith() w3c/payment-request#669 (4 comments by @domenic, @marcoscaceres)
-
Editorial: Call out payment handlers in abort() w3c/payment-request#679 (3 comments by @ianbjacobs, @marcoscaceres)
-
Feat: allow show() to take optional detailsPromise w3c/payment-request#672 (2 comments by @domenic, @marcoscaceres)
-
Editorial: define update a PaymentRequest's details algo w3c/payment-request#671 (1 comment by @marcoscaceres)
-
w3c/payment-request-info
-
1 issue opened.
-
Work with MDN w3c/payment-request-info#4, by @marcoscaceres.
-
-
1 issue received 16 new comments.
-
Work with MDN w3c/payment-request-info#4 (16 comments by @chrisdavidmills, @dontcallmedom, @ianbjacobs, @marcoscaceres, @poshaughnessy)
-
w3c/webpayments
-
4 pull requests opened.
-
More link fixes w3c/webpayments#244, by @ianbjacobs.
-
link fixes in draft charter w3c/webpayments#243, by @ianbjacobs.
-
Remove BASE w3c/webpayments#242, by @ianbjacobs.
-
Add BASE to fix broken links w3c/webpayments#241, by @ianbjacobs.
-
-
4 pull requests merged.
-
More link fixes w3c/webpayments#244.
-
link fixes in draft charter w3c/webpayments#243.
-
Remove BASE w3c/webpayments#242.
-
Add BASE to fix broken links w3c/webpayments#241.
-