Web Payments Working Group - Activity in 2017
No matches.
TR publications
-
3 documents published.
-
Payment Handler API published as a Working Draft. History of Payment Handler API
-
Payment Method Manifest published as a First Public Working Draft. History of Payment Method Manifest
-
Web Payments HTTP API 1.0 published as a Note. History of Web Payments HTTP API 1.0
-
GitHub
w3c/payment-request
-
6 issues opened.
-
Add equivalent of applepaypaymentmethodchanged w3c/payment-request#662, by @aestes.
-
Add Crypto Currency (BTC, ETH) as supported method w3c/payment-request#661, by @buhrmi.
-
Request: designated receiver for Payment Response w3c/payment-request#660, by @rektide.
-
ShippingAddressChange replaces address every time w3c/payment-request#659, by @marcoscaceres.
-
Is paypment request gated behind https? w3c/payment-request#658, by @jdalton.
-
updateWith accepts a details object? w3c/payment-request#657, by @jdalton.
-
-
5 issues closed.
-
Third-party payment handlers w3c/payment-request#640.
-
ShippingAddressChange replaces address every time w3c/payment-request#659.
-
Add Crypto Currency (BTC, ETH) as supported method w3c/payment-request#661.
-
updateWith accepts a details object? w3c/payment-request#657.
-
Is paypment request gated behind https? w3c/payment-request#658.
-
-
13 issues received 61 new comments.
-
Fine grained error recovery for fields w3c/payment-request#647 (12 comments by @marcoscaceres, @mnoorenberghe, @rsolomakhin)
-
Add type to PaymentItem w3c/payment-request#163 (12 comments by @adrianhopebailie, @marcoscaceres, @mnoorenberghe, @rsolomakhin)
-
redact full shipping address from event until payment response w3c/payment-request#648 (5 comments by @adrianhopebailie, @aestes, @marcoscaceres)
-
Request: designated receiver for Payment Response w3c/payment-request#660 (5 comments by @cyberphone, @ianbjacobs, @michelle, @rektide, @rsolomakhin)
-
Add equivalent of applepaypaymentmethodchanged w3c/payment-request#662 (4 comments by @aestes, @rsolomakhin)
-
Is paypment request gated behind https? w3c/payment-request#658 (4 comments by @jdalton, @marcoscaceres, @romandev, @rsolomakhin)
-
Require user gesture when `.show()` is called w3c/payment-request#651 (3 comments by @marcoscaceres, @rektide, @tantek)
-
ShippingAddressChange replaces address every time w3c/payment-request#659 (3 comments by @adrianhopebailie, @domenic, @marcoscaceres)
-
updateWith accepts a details object? w3c/payment-request#657 (2 comments by @marcoscaceres, @romandev)
-
Add Crypto Currency (BTC, ETH) as supported method w3c/payment-request#661 (1 comment by @ianbjacobs)
-
-
2 pull requests received 19 new comments.
-
add redactList for PaymentAddress (Part 1) w3c/payment-request#654 (17 comments by @domenic, @marcoscaceres)
-
show() must be triggered by user activation w3c/payment-request#655 (2 comments by @marcoscaceres, @rsolomakhin)
-
w3c/webpayments
-
1 issue received 11 new comments.
-
Should the WPWG develop a cryptocurrency payment method specification w3c/webpayments#232 (11 comments by @adrianhopebailie, @buhrmi, @cdecker, @ianbjacobs, @marcoscaceres, @stan-stripe, @webpayments)
-
-
2 pull requests opened.
-
Cleanup Readme w3c/webpayments#240, by @ianbjacobs.
-
Updates based on Wendy review w3c/webpayments#239, by @ianbjacobs.
-
-
3 pull requests merged.
-
Cleanup Readme w3c/webpayments#240.
-
Updates based on Wendy review w3c/webpayments#239.
-
Editorial around non-browser payments w3c/webpayments#238.
-
-
1 pull request received 1 new comment.
w3c/web-based-payment-handler
-
1 issue opened.
-
Does payment instrument registration imply a display order? w3c/web-based-payment-handler#243, by @ianbjacobs.
-
-
2 issues closed.
-
Recommended payment apps w3c/web-based-payment-handler#74.
-
Allow Payment instrument to respond with user data w3c/web-based-payment-handler#218.
-
-
6 issues received 46 new comments.
-
What happens when clearing site data? w3c/web-based-payment-handler#236 (16 comments by @adrianhopebailie, @annevk, @dlongley, @jakearchibald, @marcoscaceres, @romandev)
-
Share user data with Payment App w3c/web-based-payment-handler#123 (8 comments by @adrianhopebailie, @ianbjacobs, @Krystosterone, @rsolomakhin)
-
Does payment instrument registration imply a display order? w3c/web-based-payment-handler#243 (7 comments by @adrianhopebailie, @dezell, @ianbjacobs, @rsolomakhin)
-
User consent and permissions w3c/web-based-payment-handler#239 (7 comments by @adrianhopebailie, @dlongley, @ianbjacobs, @rsolomakhin)
-
Just-in-time payment handler install w3c/web-based-payment-handler#240 (6 comments by @ianbjacobs, @romandev, @rsolomakhin)
-
-
3 pull requests opened.
-
add a "public computing" section to security/privacy considerations w3c/web-based-payment-handler#244, by @ianbjacobs.
-
Edits regarding ordering based on 7 Dec WG teleconf w3c/web-based-payment-handler#242, by @ianbjacobs.
-
Make Origin and Instrument Display section non-normative. w3c/web-based-payment-handler#241, by @msporny.
-
-
2 pull requests merged.
-
Editorial: trim introduction w3c/web-based-payment-handler#227.
-
Editorial: trim/relocate conformance w3c/web-based-payment-handler#226.
-
-
2 pull requests closed.
-
Remove 'Origin and Instrument Display for Selection' sections w3c/web-based-payment-handler#229.
-
Make Origin and Instrument Display section non-normative. w3c/web-based-payment-handler#241.
-
-
1 pull request reopened.
-
Remove 'Origin and Instrument Display for Selection' sections w3c/web-based-payment-handler#229, by @ianbjacobs.
-
-
5 pull requests received 39 new comments.
-
Edits regarding ordering based on 7 Dec WG teleconf w3c/web-based-payment-handler#242 (18 comments by @ianbjacobs, @kmealey, @marcoscaceres, @msporny)
-
Remove 'Origin and Instrument Display for Selection' sections w3c/web-based-payment-handler#229 (11 comments by @adrianhopebailie, @ianbjacobs, @kmealey, @marcoscaceres, @msporny)
-
Make Origin and Instrument Display section non-normative. w3c/web-based-payment-handler#241 (5 comments by @ianbjacobs, @marcoscaceres, @msporny)
-
fix: PaymentInstruments.get not exceptional w3c/web-based-payment-handler#231 (3 comments by @marcoscaceres, @romandev)
-
w3c/payment-method-manifest
-
1 issue opened.
-
Relative URL for "default_applications" w3c/payment-method-manifest#25, by @rsolomakhin.
-
-
4 issues closed.
-
Clarify referrer policy w3c/payment-method-manifest#23.
-
Front matter needs adjusting for W3C FPWD w3c/payment-method-manifest#15.
-
Hosting on localhost w3c/payment-method-manifest#24.
-
Relative URL for "default_applications" w3c/payment-method-manifest#25.
-
-
4 issues received 12 new comments.
-
Clarify referrer policy w3c/payment-method-manifest#23 (5 comments by @domenic, @marcoscaceres, @rsolomakhin)
-
Matching payment apps and security in a world of payment method manifests w3c/payment-method-manifest#11 (3 comments by @adrianhopebailie, @domenic, @ianbjacobs)
-
Relative URL for "default_applications" w3c/payment-method-manifest#25 (3 comments by @domenic, @marcoscaceres, @rsolomakhin)
-
TR publications
-
2 documents published.
-
Payment Handler API published twice as a Working Draft. History of Payment Handler API
-
Participants
-
3 organizations joined.
-
Bread joined.
-
Abine Inc. joined.
-
Wiley joined.
-
GitHub
w3c/web-based-payment-handler
-
12 issues opened.
-
Just-in-time payment handler install w3c/web-based-payment-handler#240, by @rsolomakhin.
-
User consent and permissions w3c/web-based-payment-handler#239, by @rsolomakhin.
-
ImageObjects can now reference ImageResource w3c/web-based-payment-handler#238, by @marcoscaceres.
-
Image fetching does not seem to be defined w3c/web-based-payment-handler#237, by @annevk.
-
What happens when clearing site data? w3c/web-based-payment-handler#236, by @marcoscaceres.
-
"Convert image objects" trashes all images w3c/web-based-payment-handler#235, by @marcoscaceres.
-
retrieving the permission state w3c/web-based-payment-handler#234, by @marcoscaceres.
-
PaymentInstruments .set() and icons w3c/web-based-payment-handler#233, by @marcoscaceres.
-
PaymentInstruments' "the collection" needs an internal slot. w3c/web-based-payment-handler#232, by @marcoscaceres.
-
Trying to get a non-existing value is not exceptional w3c/web-based-payment-handler#230, by @marcoscaceres.
-
SW registration code unclear/incorrect w3c/web-based-payment-handler#223, by @ithinkihaveacat.
-
UI testing w3c/web-based-payment-handler#221, by @ebomcke-ingenico.
-
-
1 issue closed.
-
Trying to get a non-existing value is not exceptional w3c/web-based-payment-handler#230.
-
-
8 issues received 47 new comments.
-
What happens when clearing site data? w3c/web-based-payment-handler#236 (18 comments by @annevk, @dlongley, @marcoscaceres, @mikewest, @romandev, @rsolomakhin)
-
User consent and permissions w3c/web-based-payment-handler#239 (7 comments by @adrianhopebailie, @ianbjacobs, @romandev, @rsolomakhin)
-
Just-in-time payment handler install w3c/web-based-payment-handler#240 (6 comments by @adrianhopebailie, @jenan-stripe, @rsolomakhin)
-
PaymentInstruments .set() and icons w3c/web-based-payment-handler#233 (5 comments by @marcoscaceres, @rsolomakhin)
-
SW registration code unclear/incorrect w3c/web-based-payment-handler#223 (5 comments by @ianbjacobs, @jakearchibald, @romandev, @rsolomakhin)
-
"Convert image objects" trashes all images w3c/web-based-payment-handler#235 (3 comments by @marcoscaceres, @rsolomakhin)
-
Trying to get a non-existing value is not exceptional w3c/web-based-payment-handler#230 (1 comment by @marcoscaceres)
-
-
8 pull requests opened.
-
fix: PaymentInstruments.get not exceptional w3c/web-based-payment-handler#231, by @marcoscaceres.
-
Remove 'Origin and Instrument Display for Selection' sections w3c/web-based-payment-handler#229, by @marcoscaceres.
-
Editorial: small fixes, redundancies w3c/web-based-payment-handler#228, by @marcoscaceres.
-
Editorial: trim introduction w3c/web-based-payment-handler#227, by @marcoscaceres.
-
Editorial: trim/relocate conformance w3c/web-based-payment-handler#226, by @marcoscaceres.
-
Editorial: Simplify abstract w3c/web-based-payment-handler#225, by @marcoscaceres.
-
Only allows instrument.set() in active service worker w3c/web-based-payment-handler#224, by @romandev.
-
Per Tommy, mark him as former editor w3c/web-based-payment-handler#222, by @ianbjacobs.
-
-
4 pull requests merged.
-
fix: PaymentInstruments.get not exceptional w3c/web-based-payment-handler#231.
-
Editorial: small fixes, redundancies w3c/web-based-payment-handler#228.
-
Editorial: Simplify abstract w3c/web-based-payment-handler#225.
-
Per Tommy, mark him as former editor w3c/web-based-payment-handler#222.
-
-
6 pull requests received 34 new comments.
-
Add CanMakePaymentEvent. w3c/web-based-payment-handler#170 (9 comments by @marcoscaceres, @rsolomakhin)
-
fix: PaymentInstruments.get not exceptional w3c/web-based-payment-handler#231 (4 comments by @marcoscaceres, @rsolomakhin)
-
Remove 'Origin and Instrument Display for Selection' sections w3c/web-based-payment-handler#229 (3 comments by @adrianhopebailie, @marcoscaceres)
-
Editorial: trim/relocate conformance w3c/web-based-payment-handler#226 (2 comments by @marcoscaceres)
w3c/payment-request
-
10 issues opened.
-
Merchant-specified default shipping address w3c/payment-request#653, by @rsolomakhin.
-
Standardize phone number format w3c/payment-request#652, by @michelle.
-
Require user gesture when `.show()` is called w3c/payment-request#651, by @michelle.
-
Allow locale to be specified by the developer. w3c/payment-request#650, by @michelle.
-
updateWith(data) should merge with request.data w3c/payment-request#649, by @marcoscaceres.
-
redact full shipping address from event until payment response w3c/payment-request#648, by @marcoscaceres.
-
Fine grained error recovery for fields w3c/payment-request#647, by @marcoscaceres.
-
Add support for merchant validation w3c/payment-request#646, by @marcoscaceres.
-
Add way to update `total` and `displayItems` after `.show()` but before user interaction w3c/payment-request#645, by @jenan-stripe.
-
Make Payment Address construction into its own sub algorithm w3c/payment-request#643, by @marcoscaceres.
-
-
2 issues closed.
-
If a card payment fails, should we support exclusion of that card instrument from matching? w3c/payment-request#237.
-
Add way to update `total` and `displayItems` before `.show()` w3c/payment-request#639.
-
-
1 issue reopened.
-
Add type to PaymentItem w3c/payment-request#163, by @marcoscaceres.
-
-
13 issues received 69 new comments.
-
redact full shipping address from event until payment response w3c/payment-request#648 (13 comments by @adrianba, @ianbjacobs, @jenan-stripe, @lyverovski, @marcoscaceres, @michelle)
-
Allow locale to be specified by the developer. w3c/payment-request#650 (13 comments by @ianbjacobs, @marc-roberts-jg, @marcoscaceres, @michelle, @mnoorenberghe, @rsolomakhin)
-
Require user gesture when `.show()` is called w3c/payment-request#651 (11 comments by @cyberphone, @marcoscaceres, @michelle, @rsolomakhin, @zkoch)
-
Add type to PaymentItem w3c/payment-request#163 (7 comments by @asolove-stripe, @marcoscaceres, @michelle, @rsolomakhin)
-
Merchant-specified default shipping address w3c/payment-request#653 (6 comments by @jenan-stripe, @marcoscaceres, @sideshowbarker)
-
Add way to update `total` and `displayItems` after `.show()` but before user interaction w3c/payment-request#645 (6 comments by @marcoscaceres, @michelle, @rsolomakhin)
-
Standardize phone number format w3c/payment-request#652 (4 comments by @marcoscaceres, @mnoorenberghe, @rsolomakhin)
-
updateWith(data) should merge with request.data w3c/payment-request#649 (2 comments by @ianbjacobs, @marcoscaceres)
-
Should API support billing address capture (for tax computation)? w3c/payment-request#27 (2 comments by @michelle, @rsolomakhin)
-
Add support for merchant validation w3c/payment-request#646 (2 comments by @marcoscaceres, @rsolomakhin)
-
If a card payment fails, should we support exclusion of that card instrument from matching? w3c/payment-request#237 (1 comment by @ianbjacobs)
-
Add way to update `total` and `displayItems` before `.show()` w3c/payment-request#639 (1 comment by @jenan-stripe)
-
Describe how to implement PaymentAddress.languageCode w3c/payment-request#608 (1 comment by @jmacwhyte)
-
-
4 pull requests opened.
-
Add localization hint for payment sheet w3c/payment-request#656, by @marcoscaceres.
-
show() must be triggered by user activation w3c/payment-request#655, by @marcoscaceres.
-
add redactList for PaymentAddress (Part 1) w3c/payment-request#654, by @marcoscaceres.
-
Editorial: define create a PaymentAddress algo w3c/payment-request#644, by @marcoscaceres.
-
-
1 pull request merged.
-
Editorial: define create a PaymentAddress algo w3c/payment-request#644.
-
-
3 pull requests received 9 new comments.
-
add redactList for PaymentAddress (Part 1) w3c/payment-request#654 (4 comments by @marcoscaceres, @rsolomakhin)
-
Editorial: define create a PaymentAddress algo w3c/payment-request#644 (4 comments by @domenic, @marcoscaceres)
-
w3c/webpayments
-
1 issue received 5 new comments.
-
4 pull requests opened.
-
Editorial around non-browser payments w3c/webpayments#238, by @adrianhopebailie.
-
Chore: Added ref draft links w3c/webpayments#237, by @ianbjacobs.
-
More cleanup of draft charter and alignment with template w3c/webpayments#236, by @ianbjacobs.
-
Some categorization of new topics per NTR w3c/webpayments#235, by @ianbjacobs.
-
-
3 pull requests merged.
-
Chore: Added ref draft links w3c/webpayments#237.
-
More cleanup of draft charter and alignment with template w3c/webpayments#236.
-
Some categorization of new topics per NTR w3c/webpayments#235.
-
w3c/payment-method-manifest
-
3 issues opened.
-
Hosting on localhost w3c/payment-method-manifest#24, by @rsolomakhin.
-
Clarify referrer policy w3c/payment-method-manifest#23, by @marcoscaceres.
-
Fetches should probably use CORS w3c/payment-method-manifest#22, by @domenic.
-
-
3 issues closed.
-
Fetches should probably use CORS w3c/payment-method-manifest#22.
-
Should these fetches have a client? (impacts CSP, CORS, ...) w3c/payment-method-manifest#1.
-
Privacy considerations of retrieving a payment method manifest w3c/payment-method-manifest#7.
-
-
4 issues received 10 new comments.
-
Should these fetches have a client? (impacts CSP, CORS, ...) w3c/payment-method-manifest#1 (4 comments by @annevk, @domenic, @rsolomakhin)
-
Fetches should probably use CORS w3c/payment-method-manifest#22 (3 comments by @domenic, @marcoscaceres, @rsolomakhin)
-
Front matter needs adjusting for W3C FPWD w3c/payment-method-manifest#15 (2 comments by @domenic, @rsolomakhin)
-
Privacy considerations of retrieving a payment method manifest w3c/payment-method-manifest#7 (1 comment by @rsolomakhin)
-
-
2 pull requests opened.
-
Perform fetches with a supplied client w3c/payment-method-manifest#21, by @domenic.
-
Suggest how to deal with issue 7. w3c/payment-method-manifest#20, by @rsolomakhin.
-
-
2 pull requests merged.
-
Perform fetches with a supplied client w3c/payment-method-manifest#21.
-
Suggest how to deal with issue 7. w3c/payment-method-manifest#20.
-
-
2 pull requests received 10 new comments.
-
Suggest how to deal with issue 7. w3c/payment-method-manifest#20 (8 comments by @domenic, @rsolomakhin)
-
Perform fetches with a supplied client w3c/payment-method-manifest#21 (2 comments by @domenic, @rsolomakhin)
-
TR publications
-
2 documents published.
-
Payment Handler API published twice as a Working Draft. History of Payment Handler API
-
Participants
-
2 participants joined.
-
Lukasz Olejnik (W3C Invited Experts) joined.
-
Matthew de Ganon (W3C Invited Experts) joined.
-
-
2 organizations joined.
-
Visa joined.
-
SEEROO Information Co., Ltd joined.
-
-
1 organization left.
-
Gemalto SA left.
-
GitHub
w3c/payment-request
-
7 issues opened.
-
Is browser support for PR API configurable? w3c/payment-request#642, by @ianbjacobs.
-
Extract actionable items from @lknik's review w3c/payment-request#641, by @marcoscaceres.
-
Third-party payment handlers w3c/payment-request#640, by @KOLANICH.
-
Add way to update `total` and `displayItems` before `.show()` w3c/payment-request#639, by @jenan-stripe.
-
Allow default option for donation in PaymentShippingType w3c/payment-request#638, by @billhannah.
-
payment modifier brings error w3c/payment-request#637, by @arosiek.
-
Handling Digital Assets (i.e. Bitcoin and Ethereum) w3c/payment-request#635, by @paranoid-android.
-
-
3 issues closed.
-
Allow default option for donation in PaymentShippingType w3c/payment-request#638.
-
payment modifier brings error w3c/payment-request#637.
-
Handling Digital Assets (i.e. Bitcoin and Ethereum) w3c/payment-request#635.
-
-
1 issue reopened.
-
Unclear what happens when multiple PRs call show() w3c/payment-request#462, by @marcoscaceres.
-
-
12 issues received 47 new comments.
-
Dealing with name as returned by the API (i18n) w3c/payment-request#634 (9 comments by @adrianhopebailie, @chinnagogulapati, @ianbjacobs, @marcoscaceres, @r12a, @rsolomakhin, @sideshowbarker)
-
Is browser support for PR API configurable? w3c/payment-request#642 (6 comments by @dontcallmedom, @ianbjacobs, @marcoscaceres, @mnoorenberghe, @rsolomakhin)
-
Add way to update `total` and `displayItems` before `.show()` w3c/payment-request#639 (5 comments by @ianbjacobs, @jenan-stripe, @rsolomakhin)
-
Allow default option for donation in PaymentShippingType w3c/payment-request#638 (4 comments by @billhannah, @rsolomakhin)
-
Should API support billing address capture (for tax computation)? w3c/payment-request#27 (2 comments by @ianbjacobs, @michelle)
-
Extract actionable items from @lknik's review w3c/payment-request#641 (2 comments by @ianbjacobs, @lknik)
-
Unclear what happens when multiple PRs call show() w3c/payment-request#462 (1 comment by @marcoscaceres)
-
Handling Digital Assets (i.e. Bitcoin and Ethereum) w3c/payment-request#635 (1 comment by @ianbjacobs)
-
-
1 pull request opened.
-
Editorial: Reuse "digital goods" w3c/payment-request#636, by @ianbjacobs.
-
-
1 pull request merged.
-
Editorial: Reuse "digital goods" w3c/payment-request#636.
-
w3c/payment-method-manifest
-
1 issue opened.
-
Use "parse JSON from bytes" w3c/payment-method-manifest#18, by @annevk.
-
-
2 issues closed.
-
Suggest rephrasing language for web developers w3c/payment-method-manifest#17.
-
Use "parse JSON from bytes" w3c/payment-method-manifest#18.
-
-
1 pull request opened.
-
Allow localhost for testing and development. w3c/payment-method-manifest#19, by @rsolomakhin.
-
-
1 pull request closed.
-
Allow localhost for testing and development. w3c/payment-method-manifest#19.
-
-
1 pull request received 5 new comments.
-
Allow localhost for testing and development. w3c/payment-method-manifest#19 (5 comments by @domenic, @rsolomakhin)
-
w3c/web-based-payment-handler
-
3 issues closed.
-
"PaymentRequestEvent dictionary" makes no sense w3c/web-based-payment-handler#191.
-
respondWith behavior not specified w3c/web-based-payment-handler#190.
-
Add explicit permission call to allow payment app to handle payments w3c/web-based-payment-handler#94.
-
-
5 issues received 19 new comments.
-
Return origin of payment app in PaymentHandlerResponse data? w3c/web-based-payment-handler#217 (12 comments by @ianbjacobs, @marcoscaceres, @rsolomakhin)
-
Allow Payment instrument to respond with user data w3c/web-based-payment-handler#218 (4 comments by @ianbjacobs, @Krystosterone)
-
"PaymentRequestEvent dictionary" makes no sense w3c/web-based-payment-handler#191 (1 comment by @ianbjacobs)
-
Add explicit permission call to allow payment app to handle payments w3c/web-based-payment-handler#94 (1 comment by @ianbjacobs)
-
-
2 pull requests opened.
-
Fixed small things in the text and code example w3c/web-based-payment-handler#220, by @wonsuk73.
-
Clarification about data in PaymentRequestEvent w3c/web-based-payment-handler#219, by @ianbjacobs.
-
-
2 pull requests merged.
-
Fixed small things in the text and code example w3c/web-based-payment-handler#220.
-
Clarification about data in PaymentRequestEvent w3c/web-based-payment-handler#219.
-
-
2 pull requests received 6 new comments.
-
Add CanMakePaymentEvent. w3c/web-based-payment-handler#170 (5 comments by @ianbjacobs, @jenan-stripe, @rsolomakhin)
-
Clarification about data in PaymentRequestEvent w3c/web-based-payment-handler#219 (1 comment by @rsolomakhin)
-
w3c/webpayments
-
1 issue opened.
-
Adopt a "test as you commit" policy w3c/webpayments#234, by @rakuco.
-
-
1 issue received 3 new comments.
-
1 pull request merged.
-
Fix typo w3c/webpayments#233.
-
TR publications
-
15 documents published.
-
Payment Request API published twice as a Candidate Recommendation Snapshot. History of Payment Request API
-
Payment Method Identifiers published as a Candidate Recommendation Snapshot. History of Payment Method Identifiers
-
Payment Handler API published 4 times as a Working Draft. History of Payment Handler API
-
Payment Request API published 7 times as a Working Draft. History of Payment Request API
-
Payment Method Identifiers published as a Working Draft. History of Payment Method Identifiers
-
Participants
-
2 participants joined.
-
Francois Gaignard (W3C Invited Experts) joined.
-
Chris Marconi (W3C Invited Experts) joined.
-
-
2 participants left.
-
Peter van Leeuwen (W3C Invited Experts) left.
-
Lauren Jones (W3C Invited Experts) left.
-
GitHub
w3c/payment-request
-
24 issues opened.
-
Dealing with name as returned by the API (i18n) w3c/payment-request#634, by @dandv.
-
Pre Authorization w3c/payment-request#633, by @chadcampbell.
-
Regulatory Compliance Support w3c/payment-request#632, by @markalanrichards.
-
404 on some tests w3c/payment-request#630, by @marcoscaceres.
-
"Exposing available payment methods" is confusing given the existence of canMakePayment() w3c/payment-request#629, by @domenic.
-
Add support for crypto currencies w3c/payment-request#627, by @ghost.
-
Clarify the `displayItems` are not shared with payment handler w3c/payment-request#626, by @marcoscaceres.
-
Move to an incremental feature release model w3c/payment-request#625, by @marcoscaceres.
-
Are integer values for PaymentCurrencyAmount.value left as integers? w3c/payment-request#624, by @ianbjacobs.
-
Documentation error? 55 + 5 = 65 w3c/payment-request#622, by @edent.
-
.updateWith() example says "throws" w3c/payment-request#620, by @marcoscaceres.
-
Make iframe allowpaymentrequest normative w3c/payment-request#618, by @marcoscaceres.
-
Decide on currencySystem w3c/payment-request#617, by @marcoscaceres.
-
Pre-calculate shipping costs for available addresses w3c/payment-request#615, by @dandv.
-
Pre-filter shipping addresses, e.g. by country w3c/payment-request#614, by @dandv.
-
Pay method for testing environment w3c/payment-request#613, by @ghost.
-
Add Exposed= to IDL interfaces w3c/payment-request#611, by @marcoscaceres.
-
If requestShipping is false, pr.shippingOption should be null w3c/payment-request#609, by @marcoscaceres.
-
Describe how to implement PaymentAddress.languageCode w3c/payment-request#608, by @marcoscaceres.
-
PayerAddress.phone and PayerResponse.payerPhone w3c/payment-request#606, by @marcoscaceres.
-
Creation and assignment of PaymentAddress is underspecified w3c/payment-request#603, by @marcoscaceres.
-
PaymentAddress.languageCode lacking canonical form w3c/payment-request#602, by @marcoscaceres.
-
PaymentAddress attribute definition is wrong w3c/payment-request#601, by @marcoscaceres.
-
Integration with Feature Policy w3c/payment-request#600, by @marcoscaceres.
-
-
17 issues closed.
-
Are integer values for PaymentCurrencyAmount.value left as integers? w3c/payment-request#624.
-
Should user agent validate currency? w3c/payment-request#490.
-
Make iframe allowpaymentrequest normative w3c/payment-request#618.
-
Add support for crypto currencies w3c/payment-request#627.
-
Documentation error? 55 + 5 = 65 w3c/payment-request#622.
-
.updateWith() example says "throws" w3c/payment-request#620.
-
PaymentAddress attribute definition is wrong w3c/payment-request#601.
-
shippingOption description is misleading w3c/payment-request#534.
-
'Pull' Payment Bias in API spec w3c/payment-request#499.
-
Creation and assignment of PaymentAddress is underspecified w3c/payment-request#603.
-
.updateWith() should only be callable if event was canceled w3c/payment-request#589.
-
If requestShipping is false, pr.shippingOption should be null w3c/payment-request#609.
-
Add Exposed= to IDL interfaces w3c/payment-request#611.
-
PayerAddress.phone and PayerResponse.payerPhone w3c/payment-request#606.
-
PaymentAddress.languageCode lacking canonical form w3c/payment-request#602.
-
Duplicate shippingOptions lead to inconsistent `updateWith()` - should throw! w3c/payment-request#594.
-
CR check list w3c/payment-request#520.
-
-
6 issues reopened.
-
Pre Authorization w3c/payment-request#633, by @adrianhopebailie.
-
Should user agent validate currency? w3c/payment-request#490, by @adrianhopebailie.
-
Pay method for testing environment w3c/payment-request#613, by @adrianhopebailie.
-
Documentation error? 55 + 5 = 65 w3c/payment-request#622, by @marcoscaceres.
-
Pay method for testing environment w3c/payment-request#613, by @adrianhopebailie.
-
PaymentAddress attribute definition is wrong w3c/payment-request#601, by @ianbjacobs.
-
-
22 issues received 128 new comments.
-
Pay method for testing environment w3c/payment-request#613 (29 comments by @adrianhopebailie, @ghost, @ianbjacobs, @marcoscaceres, @rsolomakhin)
-
PaymentAddress attribute definition is wrong w3c/payment-request#601 (20 comments by @adrianhopebailie, @ianbjacobs, @marcoscaceres, @roubert, @rsolomakhin)
-
Should user agent validate currency? w3c/payment-request#490 (12 comments by @adrianhopebailie, @domenic, @ianbjacobs, @marcoscaceres)
-
Pre Authorization w3c/payment-request#633 (8 comments by @adrianhopebailie, @chadcampbell, @cyberphone, @ianbjacobs, @marcoscaceres, @rsolomakhin)
-
Are integer values for PaymentCurrencyAmount.value left as integers? w3c/payment-request#624 (8 comments by @ashokmisra, @ianbjacobs, @marcoscaceres, @rsolomakhin)
-
Clarify the `displayItems` are not shared with payment handler w3c/payment-request#626 (7 comments by @ianbjacobs, @marcoscaceres, @markalanrichards, @rsolomakhin)
-
Describe how to implement PaymentAddress.languageCode w3c/payment-request#608 (6 comments by @marcoscaceres, @rsolomakhin)
-
PayerAddress.phone and PayerResponse.payerPhone w3c/payment-request#606 (6 comments by @marcoscaceres, @rsolomakhin, @zkoch)
-
If requestShipping is false, pr.shippingOption should be null w3c/payment-request#609 (6 comments by @marcoscaceres, @rsolomakhin)
-
Regulatory Compliance Support w3c/payment-request#632 (5 comments by @ianbjacobs, @marcoscaceres, @markalanrichards)
-
Dealing with name as returned by the API (i18n) w3c/payment-request#634 (4 comments by @adrianhopebailie, @chinnagogulapati, @marcoscaceres, @rsolomakhin)
-
"Exposing available payment methods" is confusing given the existence of canMakePayment() w3c/payment-request#629 (4 comments by @ianbjacobs, @lknik, @marcoscaceres)
-
Make iframe allowpaymentrequest normative w3c/payment-request#618 (2 comments by @domenic, @marcoscaceres)
-
Pre-filter shipping addresses, e.g. by country w3c/payment-request#614 (2 comments by @dandv, @marcoscaceres)
-
-
13 pull requests opened.
-
UAs should not alter value string (addresses #624) w3c/payment-request#631, by @ianbjacobs.
-
Suggested emphasis of privacy protections w3c/payment-request#628, by @markalanrichards.
-
Auto publication no longer needed w3c/payment-request#621, by @deniak.
-
Chore: Minor link fix w3c/payment-request#619, by @ianbjacobs.
-
Editorial: removed extra "the" w3c/payment-request#616, by @ianbjacobs.
-
Editorial: explicitly Expose=Window IDL interface w3c/payment-request#612, by @marcoscaceres.
-
Only select shippingOption if asked to (closes #609) w3c/payment-request#610, by @marcoscaceres.
-
Construct and set attrs on PaymentAddress w3c/payment-request#607, by @marcoscaceres.
-
Canonicalize PaymentAddress.languageCode (closes #602) w3c/payment-request#605, by @marcoscaceres.
-
Fix PaymentAddress attr definition (closes #601) w3c/payment-request#604, by @marcoscaceres.
-
Less pull centric w3c/payment-request#599, by @ianbjacobs.
-
Clarify CR exit requirements w3c/payment-request#598, by @marcoscaceres.
-
-
14 pull requests merged.
-
UAs should not alter value string (addresses #624) w3c/payment-request#631.
-
Typo fix w3c/payment-request#623.
-
Auto publication no longer needed w3c/payment-request#621.
-
Chore: Minor link fix w3c/payment-request#619.
-
Editorial: removed extra "the" w3c/payment-request#616.
-
Construct and set attrs on PaymentAddress w3c/payment-request#607.
-
Dont block UI if .updateWith() not called (closes #589) w3c/payment-request#591.
-
Only select shippingOption if asked to (closes #609) w3c/payment-request#610.
-
Clarify CR exit requirements w3c/payment-request#598.
-
Editorial: explicitly Expose=Window IDL interface w3c/payment-request#612.
-
Fix PaymentAddress attr definition (closes #601) w3c/payment-request#604.
-
Canonicalize PaymentAddress.languageCode (closes #602) w3c/payment-request#605.
-
Throw on dup shippingOptions ids w3c/payment-request#596.
-
Less pull centric w3c/payment-request#599.
-
-
1 pull request closed.
-
editorial: Clarify wording to not imply 'pull' only payments w3c/payment-request#474.
-
-
12 pull requests received 53 new comments.
-
Suggested emphasis of privacy protections w3c/payment-request#628 (15 comments by @adrianhopebailie, @dlongley, @ianbjacobs, @marcoscaceres, @markalanrichards)
-
Construct and set attrs on PaymentAddress w3c/payment-request#607 (11 comments by @domenic, @marcoscaceres)
-
UAs should not alter value string (addresses #624) w3c/payment-request#631 (10 comments by @ianbjacobs, @marcoscaceres)
-
Dont block UI if .updateWith() not called (closes #589) w3c/payment-request#591 (4 comments by @marcoscaceres)
-
Canonicalize PaymentAddress.languageCode (closes #602) w3c/payment-request#605 (3 comments by @domenic, @marcoscaceres)
-
Only select shippingOption if asked to (closes #609) w3c/payment-request#610 (2 comments by @marcoscaceres)
-
Editorial: explicitly Expose=Window IDL interface w3c/payment-request#612 (2 comments by @marcoscaceres)
-
editorial: Clarify wording to not imply 'pull' only payments w3c/payment-request#474 (2 comments by @ianbjacobs, @marcoscaceres)
-
Do not show payment requests for non-fully-active documents w3c/payment-request#579 (1 comment by @marcoscaceres)
-
Fix PaymentAddress attr definition (closes #601) w3c/payment-request#604 (1 comment by @marcoscaceres)
-
w3c/web-based-payment-handler
-
4 issues opened.
-
Allow Payment instrument to respond with user data w3c/web-based-payment-handler#218, by @Krystosterone.
-
Return origin of payment app in PaymentHandlerResponse data? w3c/web-based-payment-handler#217, by @ianbjacobs.
-
Add [Exposed] to all interfaces w3c/web-based-payment-handler#215, by @annevk.
-
Clarification of "instrumentKey" language w3c/web-based-payment-handler#212, by @madmath.
-
-
4 issues closed.
-
Add [Exposed] to all interfaces w3c/web-based-payment-handler#215.
-
Suggestion: replace `PaymentWallets` with a property on `PaymentInstrument` w3c/web-based-payment-handler#153.
-
Ability to set default instrument for given handler w3c/web-based-payment-handler#173.
-
Clarification of "instrumentKey" language w3c/web-based-payment-handler#212.
-
-
6 issues received 13 new comments.
-
Return origin of payment app in PaymentHandlerResponse data? w3c/web-based-payment-handler#217 (5 comments by @adrianhopebailie, @ianbjacobs, @rsolomakhin)
-
Suggestion: replace `PaymentWallets` with a property on `PaymentInstrument` w3c/web-based-payment-handler#153 (3 comments by @ianbjacobs, @rsolomakhin)
-
Relation between merchant order of payment methods and payment app order of instruments w3c/web-based-payment-handler#116 (2 comments by @ianbjacobs, @kmealey)
-
Allow Payment instrument to respond with user data w3c/web-based-payment-handler#218 (1 comment by @adrianhopebailie)
-
Ability to set default instrument for given handler w3c/web-based-payment-handler#173 (1 comment by @ianbjacobs)
-
Clarification of "instrumentKey" language w3c/web-based-payment-handler#212 (1 comment by @rsolomakhin)
-
-
3 pull requests opened.
-
Add [Exposed] to PaymentInstruments interface. w3c/web-based-payment-handler#216, by @romandev.
-
Security addition w3c/web-based-payment-handler#214, by @ianbjacobs.
-
Removed section on instrument grouping with closure of issue 153 w3c/web-based-payment-handler#213, by @ianbjacobs.
-
-
7 pull requests merged.
-
Define PaymentRequestEvent.respondWith() behavior. w3c/web-based-payment-handler#194.
-
Make explicit which origin to use in conjunction with payment method manifest. w3c/web-based-payment-handler#209.
-
Security addition w3c/web-based-payment-handler#214.
-
Removed section on instrument grouping with closure of issue 153 w3c/web-based-payment-handler#213.
-
Add [Exposed] to PaymentInstruments interface. w3c/web-based-payment-handler#216.
-
Add userHint to PaymentManager w3c/web-based-payment-handler#206.
-
Clarify empty instrument key meaning. w3c/web-based-payment-handler#208.
-
-
4 pull requests received 14 new comments.
-
Add [Exposed] to PaymentInstruments interface. w3c/web-based-payment-handler#216 (4 comments by @marcoscaceres, @romandev, @rsolomakhin)
-
Define PaymentRequestEvent.respondWith() behavior. w3c/web-based-payment-handler#194 (2 comments by @ianbjacobs, @romandev)
-
Make explicit which origin to use in conjunction with payment method manifest. w3c/web-based-payment-handler#209 (2 comments by @rsolomakhin)
w3c/webpayments
-
1 issue opened.
-
Should the WPWG develop a cryptocurrency payment method specification w3c/webpayments#232, by @ianbjacobs.
-
-
1 pull request opened.
-
Fix typo w3c/webpayments#233, by @marcoscaceres.
-
w3c/payment-method-id
-
2 pull requests opened.
-
Auto publication no longer needed w3c/payment-method-id#51, by @deniak.
-
Clarify CR exit requirements w3c/payment-method-id#50, by @marcoscaceres.
-
-
2 pull requests merged.
-
Auto publication no longer needed w3c/payment-method-id#51.
-
Clarify CR exit requirements w3c/payment-method-id#50.
-
-
1 pull request received 3 new comments.
TR publications
-
18 documents published.
-
Payment Method Identifiers published 3 times as a Working Draft. History of Payment Method Identifiers
-
Payment Request API published 10 times as a Working Draft. History of Payment Request API
-
Payment Handler API published 5 times as a Working Draft. History of Payment Handler API
-
Participants
-
1 organization joined.
-
Merchant Advisory Group joined.
-
-
1 organization left.
-
360 left.
-
GitHub
w3c/payment-method-id
-
2 issues opened.
-
Better defined validity of standardized PMIs? w3c/payment-method-id#48, by @marcoscaceres.
-
w3c.github.io/payment-method-id/ is not in parity with the tests w3c/payment-method-id#46, by @mhahmadi.
-
-
4 issues closed.
-
Better defined validity of standardized PMIs? w3c/payment-method-id#48.
-
w3c.github.io/payment-method-id/ is not in parity with the tests w3c/payment-method-id#46.
-
CR checklist w3c/payment-method-id#39.
-
Reference manifest spec w3c/payment-method-id#33.
-
-
2 issues received 8 new comments.
-
w3c.github.io/payment-method-id/ is not in parity with the tests w3c/payment-method-id#46 (6 comments by @marcoscaceres, @mhahmadi, @rsolomakhin)
-
Better defined validity of standardized PMIs? w3c/payment-method-id#48 (2 comments by @marcoscaceres, @rsolomakhin)
-
-
4 pull requests opened.
-
Define syntax of standard PMI (closes #48) w3c/payment-method-id#49, by @marcoscaceres.
-
Other specs must define validity rules (closes #46) w3c/payment-method-id#47, by @marcoscaceres.
-
Editorial: final round of prep for CR (closes #39) w3c/payment-method-id#45, by @marcoscaceres.
-
Define generalized PMI validator w3c/payment-method-id#44, by @marcoscaceres.
-
-
6 pull requests merged.
-
Define syntax of standard PMI (closes #48) w3c/payment-method-id#49.
-
Other specs must define validity rules (closes #46) w3c/payment-method-id#47.
-
Editorial: final round of prep for CR (closes #39) w3c/payment-method-id#45.
-
Define generalized PMI validator w3c/payment-method-id#44.
-
make fetching URL-PMI optional (closes #33) w3c/payment-method-id#40.
-
editorial: add CR exit criteria w3c/payment-method-id#42.
-
-
6 pull requests received 14 new comments.
-
editorial: add CR exit criteria w3c/payment-method-id#42 (5 comments by @marcoscaceres, @sideshowbarker)
-
make fetching URL-PMI optional (closes #33) w3c/payment-method-id#40 (3 comments by @adrianhopebailie, @marcoscaceres)
-
Other specs must define validity rules (closes #46) w3c/payment-method-id#47 (1 comment by @marcoscaceres)
-
Editorial: final round of prep for CR (closes #39) w3c/payment-method-id#45 (1 comment by @marcoscaceres)
-
w3c/payment-request
-
16 issues opened.
-
https://www.w3.org/TR/payment-request/#conditional-modifications-to-payment-request w3c/payment-request#597, by @ghost.
-
Empty shippingOptions (ab)used as error w3c/payment-request#595, by @marcoscaceres.
-
Duplicate shippingOptions lead to inconsistent `updateWith()` - should throw! w3c/payment-request#594, by @marcoscaceres.
-
Third party Method not recognized- why w3c/payment-request#593, by @biseraivanovska.
-
Add a way of getting `details` from a `PaymentRequest` w3c/payment-request#592, by @marcoscaceres.
-
.updateWith() should only be callable if event was canceled w3c/payment-request#589, by @marcoscaceres.
-
Make paymentRequest.id a UUID a must w3c/payment-request#588, by @marcoscaceres.
-
Be more explicit that only alphabetic codes are supported for currency codes w3c/payment-request#585, by @marcoscaceres.
-
Show example of .complete("unknown") w3c/payment-request#584, by @marcoscaceres.
-
Dealing with "other" payment methods w3c/payment-request#580, by @cyberphone.
-
What about billet payment option? w3c/payment-request#577, by @mauricionr.
-
Need short example of serializing response w3c/payment-request#576, by @marcoscaceres.
-
details attribute is incorrect w3c/payment-request#575, by @marcoscaceres.
-
Support for "redirected" payment providers like PayPal, iDEAL/NL,Direktbetalning/SE etc w3c/payment-request#573, by @cyberphone.
-
Adding support for "encrypted basic card" w3c/payment-request#572, by @cyberphone.
-
PaymentItem.pending can be true, but transaction can "complete" w3c/payment-request#571, by @marcoscaceres.
-
-
19 issues closed.
-
Empty shippingOptions (ab)used as error w3c/payment-request#595.
-
Behavior for multiple modifiers for the same payment method is not defined w3c/payment-request#309.
-
validate supportedMethods w3c/payment-request#464.
-
https://www.w3.org/TR/payment-request/#conditional-modifications-to-payment-request w3c/payment-request#597.
-
Third party Method not recognized- why w3c/payment-request#593.
-
details attribute is incorrect w3c/payment-request#575.
-
Be more explicit that only alphabetic codes are supported for currency codes w3c/payment-request#585.
-
Need short example of serializing response w3c/payment-request#576.
-
Need to define the interaction of payment API with navigation and browsing context destruction w3c/payment-request#360.
-
Matching algo doesn't handle absence of filters w3c/payment-request#532.
-
Dealing with "other" payment methods w3c/payment-request#580.
-
What about billet payment option? w3c/payment-request#577.
-
PaymentItem.pending can be true, but transaction can "complete" w3c/payment-request#571.
-
Support for "redirected" payment providers like PayPal, iDEAL/NL,Direktbetalning/SE etc w3c/payment-request#573.
-
Considering allowing merchants to populate set of shipping addresses w3c/payment-request#565.
-
Adding support for "encrypted basic card" w3c/payment-request#572.
-
Descriptions of change events attributes are somewhat misleading w3c/payment-request#538.
-
Request `shippingType` attribute is not defined w3c/payment-request#472.
-
Initial values for internal slots w3c/payment-request#436.
-
-
25 issues received 67 new comments.
-
PaymentItem.pending can be true, but transaction can "complete" w3c/payment-request#571 (11 comments by @marcoscaceres, @rsolomakhin, @zkoch)
-
Need short example of serializing response w3c/payment-request#576 (6 comments by @dlongley, @marcoscaceres, @rsolomakhin)
-
Clarity required in section 21.2 regarding privacy w3c/payment-request#475 (5 comments by @ianbjacobs, @marcoscaceres)
-
Dealing with "other" payment methods w3c/payment-request#580 (4 comments by @cyberphone, @marcoscaceres, @webpayments-specs)
-
Support for "redirected" payment providers like PayPal, iDEAL/NL,Direktbetalning/SE etc w3c/payment-request#573 (4 comments by @cyberphone, @ianbjacobs, @rsolomakhin)
-
Add explicit extension point to matching algo w3c/payment-request#470 (4 comments by @ianbjacobs, @marcoscaceres)
-
Empty shippingOptions (ab)used as error w3c/payment-request#595 (3 comments by @adrianba, @marcoscaceres)
-
Third party Method not recognized- why w3c/payment-request#593 (3 comments by @cyberphone, @marcoscaceres, @rsolomakhin)
-
Drop array support for supported methods? w3c/payment-request#549 (3 comments by @marcoscaceres, @RByers)
-
Need to define the interaction of payment API with navigation and browsing context destruction w3c/payment-request#360 (3 comments by @domenic, @zkoch)
-
Matching algo doesn't handle absence of filters w3c/payment-request#532 (2 comments by @ianbjacobs, @zkoch)
-
canMakePayment() needs to match .show() w3c/payment-request#535 (2 comments by @marcoscaceres, @zkoch)
-
Adding support for "encrypted basic card" w3c/payment-request#572 (2 comments by @cyberphone, @marcoscaceres)
-
https://www.w3.org/TR/payment-request/#conditional-modifications-to-payment-request w3c/payment-request#597 (1 comment by @marcoscaceres)
-
Duplicate shippingOptions lead to inconsistent `updateWith()` - should throw! w3c/payment-request#594 (1 comment by @marcoscaceres)
-
.updateWith() should only be callable if event was canceled w3c/payment-request#589 (1 comment by @marcoscaceres)
-
Considering allowing merchants to populate set of shipping addresses w3c/payment-request#565 (1 comment by @marcoscaceres)
-
-
14 pull requests opened.
-
Throw on dup shippingOptions ids w3c/payment-request#596, by @marcoscaceres.
-
Dont block UI if .updateWith() not called (closes #589) w3c/payment-request#591, by @marcoscaceres.
-
Don't block UI if .updateWith() not called (closes #589) w3c/payment-request#590, by @marcoscaceres.
-
editorial: clarify currency member is alphabetic code w3c/payment-request#587, by @marcoscaceres.
-
editorial: rewrite pay response details attr w3c/payment-request#586, by @marcoscaceres.
-
editorial: add example of .toJSON()+fetch POST w3c/payment-request#583, by @marcoscaceres.
-
Add section on Payment Handler Matching w3c/payment-request#582, by @ianbjacobs.
-
Validate PMIs, ignore duplicates w3c/payment-request#581, by @marcoscaceres.
-
Do not show payment requests for non-fully-active documents w3c/payment-request#579, by @domenic.
-
remove matching .data text from .show() w3c/payment-request#578, by @marcoscaceres.
-
Editorial: change around payment handler language (closes #532) w3c/payment-request#574, by @ianbjacobs.
-
Editorial: test annotations w3c/payment-request#570, by @marcoscaceres.
-
editorial: s/Event/PaymentRequestUpdateEvent (closes #538) w3c/payment-request#569, by @marcoscaceres.
-
define PaymentRequest.shippingType attribute w3c/payment-request#568, by @marcoscaceres.
-
-
11 pull requests merged.
-
Validate PMIs, ignore duplicates w3c/payment-request#581.
-
editorial: rewrite pay response details attr w3c/payment-request#586.
-
editorial: clarify currency member is alphabetic code w3c/payment-request#587.
-
editorial: add example of .toJSON()+fetch POST w3c/payment-request#583.
-
Do not show payment requests for non-fully-active documents w3c/payment-request#579.
-
Add section on Payment Handler Matching w3c/payment-request#582.
-
remove matching .data text from .show() w3c/payment-request#578.
-
Editorial: test annotations w3c/payment-request#570.
-
validate PaymentCurrencyAmount.currency (closes #490) w3c/payment-request#567.
-
editorial: s/Event/PaymentRequestUpdateEvent (closes #538) w3c/payment-request#569.
-
define PaymentRequest.shippingType attribute w3c/payment-request#568.
-
-
4 pull requests closed.
-
l10n: adds Localizable dict + TextDirection enum w3c/payment-request#455.
-
Don't block UI if .updateWith() not called (closes #589) w3c/payment-request#590.
-
Use first matching PaymentDetailsModifier w3c/payment-request#541.
-
Editorial: change around payment handler language (closes #532) w3c/payment-request#574.
-
-
16 pull requests received 140 new comments.
-
Dont block UI if .updateWith() not called (closes #589) w3c/payment-request#591 (31 comments by @adrianba, @dlongley, @domenic, @marcoscaceres, @zkoch)
-
validate PaymentCurrencyAmount.currency (closes #490) w3c/payment-request#567 (26 comments by @domenic, @marcoscaceres)
-
Validate PMIs, ignore duplicates w3c/payment-request#581 (18 comments by @adrianhopebailie, @domenic, @dontcallmedom, @ianbjacobs, @marcoscaceres)
-
remove matching .data text from .show() w3c/payment-request#578 (18 comments by @adrianhopebailie, @dlongley, @dontcallmedom, @ianbjacobs, @marcoscaceres)
-
Editorial: change around payment handler language (closes #532) w3c/payment-request#574 (16 comments by @adrianhopebailie, @dlongley, @ianbjacobs, @marcoscaceres)
-
editorial: add example of .toJSON()+fetch POST w3c/payment-request#583 (7 comments by @domenic, @marcoscaceres)
-
Throw on dup shippingOptions ids w3c/payment-request#596 (6 comments by @adrianba, @ianbjacobs, @marcoscaceres)
-
Do not show payment requests for non-fully-active documents w3c/payment-request#579 (4 comments by @domenic, @marcoscaceres)
-
Use first matching PaymentDetailsModifier w3c/payment-request#541 (4 comments by @marcoscaceres, @zkoch)
-
BREAKING CHANGE: change `supportedMethods` to DOMString w3c/payment-request#551 (2 comments by @marcoscaceres, @zcorpan)
-
l10n: adds Localizable dict + TextDirection enum w3c/payment-request#455 (1 comment by @marcoscaceres)
-
Don't block UI if .updateWith() not called (closes #589) w3c/payment-request#590 (1 comment by @marcoscaceres)
-
w3c/web-based-payment-handler
-
5 issues opened.
-
Stop committing things without tests w3c/web-based-payment-handler#205, by @marcoscaceres.
-
Make explicit which origin to use in conjunction with payment method manifest w3c/web-based-payment-handler#203, by @ianbjacobs.
-
Change openWindow algorithm 14.1 to 'Resolve promise with null.' w3c/web-based-payment-handler#201, by @gogerald.
-
Registration example accesses `registration` before it is defined w3c/web-based-payment-handler#200, by @dlongley.
-
`requestPermission` is static in Web IDL but example is not w3c/web-based-payment-handler#198, by @dlongley.
-
-
5 issues closed.
-
Stop committing things without tests w3c/web-based-payment-handler#205.
-
Registration example accesses `registration` before it is defined w3c/web-based-payment-handler#200.
-
The Open Window Algorithm tries to access [[state]] of a request in a way that doesn't make sense w3c/web-based-payment-handler#192.
-
Change openWindow algorithm 14.1 to 'Resolve promise with null.' w3c/web-based-payment-handler#201.
-
`requestPermission` is static in Web IDL but example is not w3c/web-based-payment-handler#198.
-
-
10 issues received 22 new comments.
-
Change openWindow algorithm 14.1 to 'Resolve promise with null.' w3c/web-based-payment-handler#201 (6 comments by @dlongley, @gogerald, @ianbjacobs, @romandev)
-
The Open Window Algorithm tries to access [[state]] of a request in a way that doesn't make sense w3c/web-based-payment-handler#192 (5 comments by @gogerald, @mkruisselbrink, @rsolomakhin)
-
Registration example accesses `registration` before it is defined w3c/web-based-payment-handler#200 (4 comments by @dlongley, @ianbjacobs)
-
Revisiting Payment Method specific filter/capability matching w3c/web-based-payment-handler#157 (1 comment by @ianbjacobs)
-
Support for Abort() being delegated to Payment Handler w3c/web-based-payment-handler#117 (1 comment by @ianbjacobs)
-
Stop committing things without tests w3c/web-based-payment-handler#205 (1 comment by @adrianhopebailie)
-
Suggestion: replace `PaymentWallets` with a property on `PaymentInstrument` w3c/web-based-payment-handler#153 (1 comment by @ianbjacobs)
-
`requestPermission` is static in Web IDL but example is not w3c/web-based-payment-handler#198 (1 comment by @adrianhopebailie)
-
-
11 pull requests opened.
-
move dependency section down, as is done in PR API w3c/web-based-payment-handler#211, by @ianbjacobs.
-
Add link to payment handler test suite w3c/web-based-payment-handler#210, by @ianbjacobs.
-
Make explicit which origin to use in conjunction with payment method manifest. w3c/web-based-payment-handler#209, by @rsolomakhin.
-
Clarify empty instrument key meaning. w3c/web-based-payment-handler#208, by @rsolomakhin.
-
Add AbortPaymentEvent. w3c/web-based-payment-handler#207, by @rsolomakhin.
-
Add userHint to PaymentManager w3c/web-based-payment-handler#206, by @ianbjacobs.
-
Simplify Payment Handler Registration example. w3c/web-based-payment-handler#204, by @dlongley.
-
Resolve with null instead of reject with 'SecurityError' if PaymentRequestEvent.openWindow is opened in a different origin w3c/web-based-payment-handler#202, by @gogerald.
-
Fix a example for PaymentManager.requestPermission(). w3c/web-based-payment-handler#199, by @romandev.
-
Add "Validate Methods Algorithm" w3c/web-based-payment-handler#197, by @rsolomakhin.
-
Don't check PaymentRequest.[[state]] in openWindow() algorithm. w3c/web-based-payment-handler#196, by @rsolomakhin.
-
-
6 pull requests merged.
-
move dependency section down, as is done in PR API w3c/web-based-payment-handler#211.
-
Add link to payment handler test suite w3c/web-based-payment-handler#210.
-
Simplify Payment Handler Registration example. w3c/web-based-payment-handler#204.
-
Resolve with null instead of reject with 'SecurityError' if PaymentRequestEvent.openWindow is opened in a different origin w3c/web-based-payment-handler#202.
-
Fix a example for PaymentManager.requestPermission(). w3c/web-based-payment-handler#199.
-
Don't check PaymentRequest.[[state]] in openWindow() algorithm. w3c/web-based-payment-handler#196.
-
-
1 pull request closed.
-
Add "Validate Methods Algorithm" w3c/web-based-payment-handler#197.
-
-
10 pull requests received 57 new comments.
-
Add userHint to PaymentManager w3c/web-based-payment-handler#206 (27 comments by @dlongley, @ianbjacobs, @romandev, @rsolomakhin)
-
Resolve with null instead of reject with 'SecurityError' if PaymentRequestEvent.openWindow is opened in a different origin w3c/web-based-payment-handler#202 (9 comments by @gogerald, @romandev, @rsolomakhin)
-
Add "Validate Methods Algorithm" w3c/web-based-payment-handler#197 (6 comments by @ianbjacobs, @marcoscaceres, @rsolomakhin)
-
Add CanMakePaymentEvent. w3c/web-based-payment-handler#170 (5 comments by @adrianhopebailie, @ianbjacobs, @romandev, @rsolomakhin)
-
Add AbortPaymentEvent. w3c/web-based-payment-handler#207 (4 comments by @marcoscaceres, @romandev, @rsolomakhin)
-
Clarify empty instrument key meaning. w3c/web-based-payment-handler#208 (2 comments by @ianbjacobs, @rsolomakhin)
-
Define PaymentRequestEvent.respondWith() behavior. w3c/web-based-payment-handler#194 (1 comment by @romandev)
-
Make explicit which origin to use in conjunction with payment method manifest. w3c/web-based-payment-handler#209 (1 comment by @ianbjacobs)
-
Fix a example for PaymentManager.requestPermission(). w3c/web-based-payment-handler#199 (1 comment by @romandev)
-
Don't check PaymentRequest.[[state]] in openWindow() algorithm. w3c/web-based-payment-handler#196 (1 comment by @ianbjacobs)
-
w3c/payment-method-manifest
-
4 issues opened.
-
Suggest rephrasing language for web developers w3c/payment-method-manifest#17, by @ianbjacobs.
-
Updating references to other payments specs w3c/payment-method-manifest#16, by @ianbjacobs.
-
Front matter needs adjusting for W3C FPWD w3c/payment-method-manifest#15, by @ianbjacobs.
-
Reference URL in section on IANA considerations w3c/payment-method-manifest#13, by @ianbjacobs.
-
-
1 issue closed.
-
Updating references to other payments specs w3c/payment-method-manifest#16.
-
-
5 issues received 17 new comments.
-
Matching payment apps and security in a world of payment method manifests w3c/payment-method-manifest#11 (6 comments by @adrianhopebailie, @ianbjacobs, @rsolomakhin)
-
Front matter needs adjusting for W3C FPWD w3c/payment-method-manifest#15 (4 comments by @domenic, @ianbjacobs, @sideshowbarker, @tabatkins)
-
Reference URL in section on IANA considerations w3c/payment-method-manifest#13 (3 comments by @domenic, @ianbjacobs)
-
Suggest rephrasing language for web developers w3c/payment-method-manifest#17 (2 comments by @domenic, @ianbjacobs)
-
Updating references to other payments specs w3c/payment-method-manifest#16 (2 comments by @domenic, @ianbjacobs)
-
-
2 pull requests opened.
-
Ian edits to prepare for FPWD w3c/payment-method-manifest#14, by @ianbjacobs.
-
Converted from bikeshed to respec w3c/payment-method-manifest#12, by @ianbjacobs.
-
-
2 pull requests closed.
-
Ian edits to prepare for FPWD w3c/payment-method-manifest#14.
-
Converted from bikeshed to respec w3c/payment-method-manifest#12.
-
-
2 pull requests received 8 new comments.
-
Converted from bikeshed to respec w3c/payment-method-manifest#12 (5 comments by @domenic, @ianbjacobs)
-
w3c/payment-request-info
-
2 issues opened.
-
Um... Payment Method Practice doesn't provide any good best practice? w3c/payment-request-info#3, by @marcoscaceres.
-
PaymentMethodPractice -> Payment Method Practice w3c/payment-request-info#2, by @marcoscaceres.
-
TR publications
-
10 documents published.
-
Payment Request API published 5 times as a Working Draft. History of Payment Request API
-
Basic Card Payment published 3 times as a Working Draft. History of Basic Card Payment
-
Payment Handler API published as a Working Draft. History of Payment Handler API
-
Payment Method Identifiers published as a Working Draft. History of Payment Method Identifiers
-
Participants
-
1 participant left.
-
Olivier Yiptong (Airbnb Inc) left.
-
-
2 organizations joined.
-
PayCert joined.
-
Airbnb Inc joined.
-
GitHub
w3c/payment-request
-
3 issues opened.
-
Don't understand how to support outsourced payment providers using CNP + basic card w3c/payment-request#566, by @cyberphone.
-
Considering allowing merchants to populate set of shipping addresses w3c/payment-request#565, by @zkoch.
-
Populate implementation report w3c/payment-request#560, by @marcoscaceres.
-
-
6 issues closed.
-
Don't understand how to support outsourced payment providers using CNP + basic card w3c/payment-request#566.
-
Add Guidance Text for User Consent w3c/payment-request#229.
-
Reject acceptedPromise if payment method identifer is invalid w3c/payment-request#557.
-
Move examples to top of document w3c/payment-request#456.
-
RFC2119 keywords in informative sections w3c/payment-request#439.
-
UX guidance article w3c/payment-request#558.
-
-
12 issues received 27 new comments.
-
Populate implementation report w3c/payment-request#560 (4 comments by @marcoscaceres, @sideshowbarker)
-
Drop array support for supported methods? w3c/payment-request#549 (3 comments by @ianbjacobs, @marcoscaceres)
-
Don't understand how to support outsourced payment providers using CNP + basic card w3c/payment-request#566 (1 comment by @ianbjacobs)
-
Matching algo doesn't handle absence of filters w3c/payment-request#532 (1 comment by @adrianhopebailie)
-
Reject acceptedPromise if payment method identifer is invalid w3c/payment-request#557 (1 comment by @marcoscaceres)
-
Add dir/lang member on dictionaries whose content is displayed in browser UI w3c/payment-request#327 (1 comment by @marcoscaceres)
-
6 pull requests opened.
-
validate PaymentCurrencyAmount.currency (closes #490) w3c/payment-request#567, by @marcoscaceres.
-
chore: rename repo to match shortname w3c/payment-request#564, by @marcoscaceres.
-
editorial: fix CR exit date, add exit criteria w3c/payment-request#563, by @marcoscaceres.
-
editorial: set CR end date to 31st oct w3c/payment-request#562, by @marcoscaceres.
-
Make privacy section normative (closes #439) w3c/payment-request#561, by @marcoscaceres.
-
Editorial changes w3c/payment-request#559, by @ianbjacobs.
-
-
5 pull requests merged.
-
editorial: set CR end date to 31st oct w3c/payment-request#562.
-
chore: rename repo to match shortname w3c/payment-request#564.
-
Editorial: move+rework examples w3c/payment-request#553.
-
Make privacy section normative (closes #439) w3c/payment-request#561.
-
Editorial changes w3c/payment-request#559.
-
-
2 pull requests closed.
-
editorial: fix CR exit date, add exit criteria w3c/payment-request#563.
-
Remove 2119 language from privacy section. w3c/payment-request#511.
-
-
1 pull request reopened.
-
editorial: set CR end date to 31st oct w3c/payment-request#562, by @marcoscaceres.
-
-
10 pull requests received 45 new comments.
-
Editorial: move+rework examples w3c/payment-request#553 (13 comments by @bentian, @marcoscaceres, @zkoch)
-
chore: rename repo to match shortname w3c/payment-request#564 (5 comments by @domenic, @ianbjacobs, @marcoscaceres)
-
Use first matching PaymentDetailsModifier w3c/payment-request#541 (3 comments by @ianbjacobs, @marcoscaceres)
-
editorial: fix CR exit date, add exit criteria w3c/payment-request#563 (2 comments by @marcoscaceres)
-
validate PaymentCurrencyAmount.currency (closes #490) w3c/payment-request#567 (1 comment by @marcoscaceres)
-
editorial: Clarify wording to not imply 'pull' only payments w3c/payment-request#474 (1 comment by @marcoscaceres)
-
Editorial: consider removing merchant preference language w3c/payment-request#506 (1 comment by @ianbjacobs)
w3c/web-based-payment-handler
-
3 issues opened.
-
The Open Window Algorithm tries to access [[state]] of a request in a way that doesn't make sense w3c/web-based-payment-handler#192, by @mkruisselbrink.
-
"PaymentRequestEvent dictionary" makes no sense w3c/web-based-payment-handler#191, by @mkruisselbrink.
-
respondWith behavior not specified w3c/web-based-payment-handler#190, by @mkruisselbrink.
-
-
5 issues closed.
-
Add .clear() to map-likes w3c/web-based-payment-handler#129.
-
Multiple payment apps per origin w3c/web-based-payment-handler#98.
-
How to support communication with a payment app after initial PR API interaction? w3c/web-based-payment-handler#143.
-
Pictures would help! w3c/web-based-payment-handler#49.
-
Missing question mark, w3c/web-based-payment-handler#163.
-
-
1 issue reopened.
-
Add .clear() to map-likes w3c/web-based-payment-handler#129, by @ianbjacobs.
-
-
10 issues received 35 new comments.
-
Ability to set default instrument for given handler w3c/web-based-payment-handler#173 (11 comments by @adrianhopebailie, @ianbjacobs, @marcoscaceres, @rsolomakhin)
-
Relation between merchant order of payment methods and payment app order of instruments w3c/web-based-payment-handler#116 (7 comments by @adrianhopebailie, @ianbjacobs, @mattsaxon, @rsolomakhin)
-
Suggestion: replace `PaymentWallets` with a property on `PaymentInstrument` w3c/web-based-payment-handler#153 (6 comments by @ianbjacobs, @marcoscaceres, @rsolomakhin, @zkoch)
-
Add .clear() to map-likes w3c/web-based-payment-handler#129 (5 comments by @adrianhopebailie, @ianbjacobs, @marcoscaceres)
-
The Open Window Algorithm tries to access [[state]] of a request in a way that doesn't make sense w3c/web-based-payment-handler#192 (1 comment by @gogerald)
-
How to support communication with a payment app after initial PR API interaction? w3c/web-based-payment-handler#143 (1 comment by @ianbjacobs)
-
-
6 pull requests opened.
-
Chore: Removed duplicate issue 173 w3c/web-based-payment-handler#195, by @ianbjacobs.
-
Define PaymentRequestEvent.respondWith() behavior. w3c/web-based-payment-handler#194, by @romandev.
-
Add missing </section> after #188 PR. w3c/web-based-payment-handler#193, by @romandev.
-
Changed Jason to Andre per their request w3c/web-based-payment-handler#189, by @ianbjacobs.
-
Remove wallets, clean up issues w3c/web-based-payment-handler#188, by @adrianhopebailie.
-
PaymentRequestEvent.total should be PaymentCurrencyAmount. w3c/web-based-payment-handler#187, by @romandev.
-
-
5 pull requests merged.
-
Chore: Removed duplicate issue 173 w3c/web-based-payment-handler#195.
-
Changed Jason to Andre per their request w3c/web-based-payment-handler#189.
-
Add missing </section> after #188 PR. w3c/web-based-payment-handler#193.
-
Remove wallets, clean up issues w3c/web-based-payment-handler#188.
-
PaymentRequestEvent.total should be PaymentCurrencyAmount. w3c/web-based-payment-handler#187.
-
-
7 pull requests received 54 new comments.
-
Add CanMakePaymentEvent. w3c/web-based-payment-handler#170 (21 comments by @adamroach, @gogerald, @ianbjacobs, @romandev, @rsolomakhin, @webpayments-specs)
-
Remove wallets, clean up issues w3c/web-based-payment-handler#188 (10 comments by @adrianhopebailie, @ianbjacobs, @marcoscaceres)
-
Define PaymentRequestEvent.respondWith() behavior. w3c/web-based-payment-handler#194 (9 comments by @ianbjacobs, @mkruisselbrink, @romandev, @rsolomakhin)
-
Changed Jason to Andre per their request w3c/web-based-payment-handler#189 (6 comments by @ianbjacobs, @marcoscaceres)
-
Chore: Removed duplicate issue 173 w3c/web-based-payment-handler#195 (3 comments by @ianbjacobs, @marcoscaceres)
-
PaymentRequestEvent.total should be PaymentCurrencyAmount. w3c/web-based-payment-handler#187 (3 comments by @romandev, @rsolomakhin)
-
Add missing </section> after #188 PR. w3c/web-based-payment-handler#193 (2 comments by @ianbjacobs, @romandev)
-
w3c/payment-method-id
-
3 issues opened.
-
Auto-publishing failing on bad token w3c/payment-method-id#43, by @marcoscaceres.
-
CR checklist w3c/payment-method-id#39, by @marcoscaceres.
-
Rename repo payment-method-id w3c/payment-method-id#38, by @marcoscaceres.
-
-
3 issues closed.
-
Add ignore example w3c/payment-method-id#37.
-
Auto-publishing failing on bad token w3c/payment-method-id#43.
-
Rename repo payment-method-id w3c/payment-method-id#38.
-
-
1 issue reopened.
-
Rename repo payment-method-id w3c/payment-method-id#38, by @marcoscaceres.
-
-
3 issues received 16 new comments.
-
Auto-publishing failing on bad token w3c/payment-method-id#43 (4 comments by @deniak, @marcoscaceres)
-
3 pull requests opened.
-
editorial: add CR exit criteria w3c/payment-method-id#42, by @marcoscaceres.
-
Clarify validation of standardized PMIs w3c/payment-method-id#41, by @marcoscaceres.
-
make fetching URL-PMI optional (closes #33) w3c/payment-method-id#40, by @marcoscaceres.
-
-
1 pull request merged.
-
Clarify validation of standardized PMIs w3c/payment-method-id#41.
-
-
2 pull requests received 5 new comments.
-
make fetching URL-PMI optional (closes #33) w3c/payment-method-id#40 (3 comments by @adrianhopebailie, @ianbjacobs, @marcoscaceres)
-
Clarify validation of standardized PMIs w3c/payment-method-id#41 (2 comments by @marcoscaceres, @zkoch)
-
w3c/payment-method-manifest
-
1 issue opened.
-
Matching payment apps and security in a world of payment method manifests w3c/payment-method-manifest#11, by @ianbjacobs.
-
w3c/webpayments
-
2 pull requests opened.
-
Spec removed in favor of developer portal w3c/webpayments#230, by @ianbjacobs.
-
Tweaks w3c/webpayments#229, by @ianbjacobs.
-
-
2 pull requests merged.
-
Spec removed in favor of developer portal w3c/webpayments#230.
-
Tweaks w3c/webpayments#229.
-
w3c/payment-request-info
-
1 issue opened.
-
can we move this whole repo.... w3c/payment-request-info#1, by @marcoscaceres.
-
-
1 issue received 1 new comment.
TR publications
-
6 documents published.
-
Payment Request API published twice as a Working Draft. History of Payment Request API
-
Payment Handler API published 3 times as a Working Draft. History of Payment Handler API
-
Payment Method Identifiers published as a Working Draft. History of Payment Method Identifiers
-
Participants
-
2 participants joined.
-
Olivier Yiptong (Airbnb Inc) joined.
-
Peter van Leeuwen (W3C Invited Experts) joined.
-
-
2 participants left.
-
Michel Weksler (Airbnb Inc) left.
-
Olivier Yiptong (Airbnb Inc) left.
-
GitHub
w3c/payment-request
-
9 issues opened.
-
UX guidance article w3c/payment-request#558, by @mustafa-x.
-
Reject acceptedPromise if payment method identifer is invalid w3c/payment-request#557, by @adrianhopebailie.
-
WebIDL serializer has been deprecated in favor of toJSON operation w3c/payment-request#555, by @tobie.
-
A distinct invoice address should be supported w3c/payment-request#550, by @GSPP.
-
Drop array support for supported methods? w3c/payment-request#549, by @zkoch.
-
Adding custom fields next after shipping options have been added. w3c/payment-request#548, by @mustafa-x.
-
Unstrusted events can update PaymentRequest w3c/payment-request#546, by @marcoscaceres.
-
updateWith() "InvalidStateError" DOMException w3c/payment-request#544, by @marcoscaceres.
-
Editorial: PaymentRequestUpdateEvent constructor w3c/payment-request#543, by @marcoscaceres.
-
-
5 issues closed.
-
Drop array support for supported methods? w3c/payment-request#549.
-
WebIDL serializer has been deprecated in favor of toJSON operation w3c/payment-request#555.
-
Make text about CR phase into a note w3c/payment-request#542.
-
Unstrusted events can update PaymentRequest w3c/payment-request#546.
-
updateWith() "InvalidStateError" DOMException w3c/payment-request#544.
-
-
8 issues received 31 new comments.
-
Adding custom fields next after shipping options have been added. w3c/payment-request#548 (10 comments by @ianbjacobs, @mustafa-x, @rockeynebhwani, @rsolomakhin)
-
Drop array support for supported methods? w3c/payment-request#549 (6 comments by @dlongley, @domenic, @ianbjacobs, @marcoscaceres)
-
PaymentRequest does not handle the case of store pickup w3c/payment-request#389 (6 comments by @ianbjacobs, @marcoscaceres, @rockeynebhwani)
-
Shipping Address Validation - Suggest Alternate Address w3c/payment-request#537 (5 comments by @ktmitton, @marcoscaceres)
-
WebIDL serializer has been deprecated in favor of toJSON operation w3c/payment-request#555 (1 comment by @marcoscaceres)
-
-
7 pull requests opened.
-
Editorial: s/serializer/toJSON w3c/payment-request#556, by @marcoscaceres.
-
Typo in example Constructor code w3c/payment-request#554, by @nerdkid93.
-
Editorial: move+rework examples w3c/payment-request#553, by @marcoscaceres.
-
Editorial: add note about show() security CR experiments w3c/payment-request#552, by @marcoscaceres.
-
BREAKING CHANGE: change `supportedMethods` to DOMString w3c/payment-request#551, by @marcoscaceres.
-
throw if updateWith() is not trusted w3c/payment-request#547, by @marcoscaceres.
-
Remove dispatch flag check on .updateWith() w3c/payment-request#545, by @marcoscaceres.
-
-
8 pull requests merged.
-
Reject acceptedPromise if converting method data fails w3c/payment-request#536.
-
BREAKING CHANGE: change `supportedMethods` to DOMString w3c/payment-request#551.
-
Editorial: s/serializer/toJSON w3c/payment-request#556.
-
Editorial: add note about show() security CR experiments w3c/payment-request#552.
-
Typo in example Constructor code w3c/payment-request#554.
-
throw if updateWith() is not trusted w3c/payment-request#547.
-
Remove dispatch flag check on .updateWith() w3c/payment-request#545.
-
Cater for platform-specific limitations w3c/payment-request#540.
-
-
8 pull requests received 79 new comments.
-
Reject acceptedPromise if converting method data fails w3c/payment-request#536 (49 comments by @adrianba, @adrianhopebailie, @bentian, @dlongley, @domenic, @ianbjacobs, @madmath, @marcoscaceres, @patrickkettner, @rsolomakhin, @zkoch)
-
BREAKING CHANGE: change `supportedMethods` to DOMString w3c/payment-request#551 (15 comments by @marcoscaceres, @mnoorenberghe, @mollyd16, @zcorpan)
-
Use first matching PaymentDetailsModifier w3c/payment-request#541 (6 comments by @domenic, @marcoscaceres, @sideshowbarker)
-
Cater for platform-specific limitations w3c/payment-request#540 (2 comments by @marcoscaceres, @rsolomakhin)
-
w3c/web-based-payment-handler
-
6 issues opened.
-
PaymentRequestEvent.total should be PaymentCurrencyAmount. w3c/web-based-payment-handler#179, by @rsolomakhin.
-
Default handler icon? w3c/web-based-payment-handler#178, by @zkoch.
-
PaymentRequestEvent.total w3c/web-based-payment-handler#175, by @rsolomakhin.
-
Ability to set default instrument for given handler w3c/web-based-payment-handler#173, by @zkoch.
-
normative "A single payment handler should not be allowed to open more than one client window using this method." w3c/web-based-payment-handler#169, by @gogerald.
-
is PaymentRequestEvent.openWindow should check origin before navigation instead of after navigation w3c/web-based-payment-handler#168, by @gogerald.
-
-
7 issues closed.
-
normative "A single payment handler should not be allowed to open more than one client window using this method." w3c/web-based-payment-handler#169.
-
PaymentRequestEvent.total should be PaymentCurrencyAmount. w3c/web-based-payment-handler#179.
-
Different approaches to opening windows w3c/web-based-payment-handler#97.
-
PaymentRequestEvent.total w3c/web-based-payment-handler#175.
-
Image object is undefined w3c/web-based-payment-handler#125.
-
is PaymentRequestEvent.openWindow should check origin before navigation instead of after navigation w3c/web-based-payment-handler#168.
-
Dead link in an example w3c/web-based-payment-handler#166.
-
-
16 issues received 58 new comments.
-
Ability to set default instrument for given handler w3c/web-based-payment-handler#173 (18 comments by @adrianhopebailie, @ianbjacobs, @jnormore, @tommythorsen, @zkoch)
-
Share user data with Payment App w3c/web-based-payment-handler#123 (6 comments by @dlongley, @jnormore, @rsolomakhin, @tommythorsen)
-
normative "A single payment handler should not be allowed to open more than one client window using this method." w3c/web-based-payment-handler#169 (4 comments by @ianbjacobs, @romandev, @rsolomakhin)
-
Support for Abort() being delegated to Payment Handler w3c/web-based-payment-handler#117 (4 comments by @adrianhopebailie, @ianbjacobs, @rsolomakhin)
-
is PaymentRequestEvent.openWindow should check origin before navigation instead of after navigation w3c/web-based-payment-handler#168 (3 comments by @ianbjacobs, @romandev)
-
PaymentRequestEvent.total w3c/web-based-payment-handler#175 (3 comments by @ianbjacobs, @rakuco, @romandev)
-
PaymentRequestEvent.total should be PaymentCurrencyAmount. w3c/web-based-payment-handler#179 (2 comments by @ianbjacobs, @rsolomakhin)
-
Add explicit permission call to allow payment app to handle payments w3c/web-based-payment-handler#94 (2 comments by @ianbjacobs, @rsolomakhin)
-
Revisiting Payment Method specific filter/capability matching w3c/web-based-payment-handler#157 (2 comments by @rsolomakhin)
-
-
14 pull requests opened.
-
Change the patterns of returning promise to more readable patterns. w3c/web-based-payment-handler#186, by @romandev.
-
Fix aligns of examples for image.src. w3c/web-based-payment-handler#185, by @romandev.
-
Trying to figure out space issue and tidy w3c/web-based-payment-handler#184, by @ianbjacobs.
-
Add editors w3c/web-based-payment-handler#183, by @ianbjacobs.
-
Add .travis.yml w3c/web-based-payment-handler#182, by @ianbjacobs.
-
Added w3cid for autopublish w3c/web-based-payment-handler#181, by @ianbjacobs.
-
Define requestPermission() behavior. w3c/web-based-payment-handler#180, by @romandev.
-
The PaymentRequestEvent.total attribute should be |object| type. w3c/web-based-payment-handler#177, by @romandev.
-
Fix a link of PaymentRequestEvent.total. w3c/web-based-payment-handler#176, by @romandev.
-
Add ImageObject dictionary. w3c/web-based-payment-handler#174, by @romandev.
-
Link fix: Addresses #166; another reference link fix w3c/web-based-payment-handler#172, by @ianbjacobs.
-
Improve open window algorithm. w3c/web-based-payment-handler#171, by @romandev.
-
Add CanMakePaymentEvent. w3c/web-based-payment-handler#170, by @rsolomakhin.
-
Rename PaymentAppResponse with PaymentHandlerResponse. w3c/web-based-payment-handler#167, by @romandev.
-
-
14 pull requests merged.
-
Change the patterns of returning promise to more readable patterns. w3c/web-based-payment-handler#186.
-
Fix aligns of examples for image.src. w3c/web-based-payment-handler#185.
-
Define requestPermission() behavior. w3c/web-based-payment-handler#180.
-
Trying to figure out space issue and tidy w3c/web-based-payment-handler#184.
-
Add editors w3c/web-based-payment-handler#183.
-
Add .travis.yml w3c/web-based-payment-handler#182.
-
Added w3cid for autopublish w3c/web-based-payment-handler#181.
-
Add ImageObject dictionary. w3c/web-based-payment-handler#174.
-
Link fix: Addresses #166; another reference link fix w3c/web-based-payment-handler#172.
-
Fix a link of PaymentRequestEvent.total. w3c/web-based-payment-handler#176.
-
The PaymentRequestEvent.total attribute should be |object| type. w3c/web-based-payment-handler#177.
-
Improve open window algorithm. w3c/web-based-payment-handler#171.
-
Rename PaymentAppResponse with PaymentHandlerResponse. w3c/web-based-payment-handler#167.
-
Add a constructor of PaymentRequestEvent and PaymentRequestEventInit. w3c/web-based-payment-handler#162.
-
-
11 pull requests received 62 new comments.
-
Define requestPermission() behavior. w3c/web-based-payment-handler#180 (20 comments by @adrianhopebailie, @dlongley, @ianbjacobs, @romandev, @rsolomakhin)
-
Add ImageObject dictionary. w3c/web-based-payment-handler#174 (19 comments by @ianbjacobs, @romandev, @rsolomakhin)
-
Add CanMakePaymentEvent. w3c/web-based-payment-handler#170 (9 comments by @adrianhopebailie, @ianbjacobs, @jnormore, @rsolomakhin)
-
Added w3cid for autopublish w3c/web-based-payment-handler#181 (4 comments by @ianbjacobs, @rsolomakhin)
-
The PaymentRequestEvent.total attribute should be |object| type. w3c/web-based-payment-handler#177 (3 comments by @romandev, @rsolomakhin)
-
Rename PaymentAppResponse with PaymentHandlerResponse. w3c/web-based-payment-handler#167 (2 comments by @romandev)
-
Change the patterns of returning promise to more readable patterns. w3c/web-based-payment-handler#186 (1 comment by @romandev)
-
Link fix: Addresses #166; another reference link fix w3c/web-based-payment-handler#172 (1 comment by @ianbjacobs)
-
w3c/payment-method-id
-
1 issue opened.
-
Add ignore example w3c/payment-method-id#37, by @marcoscaceres.
-
-
11 issues closed.
-
Link to registry of W3C-published short strings w3c/payment-method-id#26.
-
Check what happens if URL parsing throws.... w3c/payment-method-id#27.
-
use of 'must' in section on Syntax of URLs as Payment Method Identifiers is suspicious w3c/payment-method-id#28.
-
Add Security Considerations and Privacy Considerations sections w3c/payment-method-id#7.
-
Identifier equivalence does not handle failure w3c/payment-method-id#8.
-
Circular dependency between PMI and PR specs w3c/payment-method-id#22.
-
Payment Method Identifier needs dfn w3c/payment-method-id#23.
-
[SECURE-CONTEXTS] should be a normative rather than informative reference w3c/payment-method-id#29.
-
citation to dated version of since-abandoned url spec fork is unusual w3c/payment-method-id#30.
-
"W3C String" is overly generic w3c/payment-method-id#32.
-
Remove "Conditional Matching Beyond Payment Method Identifier Matching" w3c/payment-method-id#34.
-
-
1 issue reopened.
-
Reference manifest spec w3c/payment-method-id#33, by @ianbjacobs.
-
-
4 issues received 7 new comments.
-
Check what happens if URL parsing throws.... w3c/payment-method-id#27 (2 comments by @marcoscaceres, @zcorpan)
-
Link to registry of W3C-published short strings w3c/payment-method-id#26 (1 comment by @marcoscaceres)
-
use of 'must' in section on Syntax of URLs as Payment Method Identifiers is suspicious w3c/payment-method-id#28 (1 comment by @marcoscaceres)
-
1 pull request merged.
-
feat: rewrite all the things w3c/payment-method-id#35.
-
-
2 pull requests closed.
-
editorial: rm 'Conditional Matching Beyond Payment Methods' section w3c/payment-method-id#36.
-
If URL parsing fails then always fail to match URLs. w3c/payment-method-id#31.
-
-
3 pull requests received 6 new comments.
-
If URL parsing fails then always fail to match URLs. w3c/payment-method-id#31 (2 comments by @marcoscaceres, @zcorpan)
-
editorial: rm 'Conditional Matching Beyond Payment Methods' section w3c/payment-method-id#36 (1 comment by @marcoscaceres)
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)
-
TR publications
-
5 documents published.
-
Payment Method Identifiers published twice as a Working Draft. History of Payment Method Identifiers
-
Basic Card Payment published as a Working Draft. History of Basic Card Payment
-
Payment Request API published as a Working Draft. History of Payment Request API
-
Payment Handler API published as a First Public Working Draft. History of Payment Handler API
-
Participants
-
1 participant joined.
-
Olivier Yiptong (Airbnb Inc) joined.
-
-
1 participant left.
-
Olivier Yiptong (Airbnb Inc) left.
-
GitHub
w3c/payment-request
-
10 issues opened.
-
Make text about CR phase into a note w3c/payment-request#542, by @marcoscaceres.
-
Show better examples of how to deal with change events w3c/payment-request#539, by @marcoscaceres.
-
Descriptions of change events attributes are somewhat misleading w3c/payment-request#538, by @marcoscaceres.
-
Shipping Address Validation - Suggest Alternate Address w3c/payment-request#537, by @ktmitton.
-
canMakePayment() needs to match .show() w3c/payment-request#535, by @marcoscaceres.
-
shippingOption description is misleading w3c/payment-request#534, by @marcoscaceres.
-
Matching algo doesn't handle absence of filters w3c/payment-request#532, by @adrianhopebailie.
-
Is PaymentResponse.details the result of a JSON.parse() w3c/payment-request#526, by @adrianhopebailie.
-
Change the value of currencySystem to an enum w3c/payment-request#521, by @marcoscaceres.
-
CR check list w3c/payment-request#520, by @marcoscaceres.
-
-
14 issues closed.
-
should .show() be user gated? w3c/payment-request#486.
-
Consider adding examples of payment matching algorithm w3c/payment-request#498.
-
Ambiguity in "Process payment methods:" w3c/payment-request#458.
-
DOMStrings don't contain "characters" w3c/payment-request#322.
-
Editorial: paymentResponse.complete() should return a rejected promise, not throw w3c/payment-request#509.
-
PaymentAddress and null values w3c/payment-request#495.
-
Standardize on "Payer" and "Payee" terms w3c/payment-request#493.
-
Reference to payment apps in Introduction needs updating w3c/payment-request#496.
-
Change the value of currencySystem to an enum w3c/payment-request#521.
-
Consider removing merchant preference language w3c/payment-request#481.
-
Web page and developer w3c/payment-request#437.
-
mark currencySystem as feature at risk w3c/payment-request#482.
-
Payment App or Payment Handler language w3c/payment-request#497.
-
Is PaymentResponse.details the result of a JSON.parse() w3c/payment-request#526.
-
-
12 issues received 29 new comments.
-
Change the value of currencySystem to an enum w3c/payment-request#521 (13 comments by @adamroach, @adrianhopebailie, @marcoscaceres)
-
"User accepts the payment request algorithm" needs to clarify where Payment Handlers are invoked w3c/payment-request#476 (4 comments by @marcoscaceres, @mattsaxon)
-
Consider adding examples of payment matching algorithm w3c/payment-request#498 (2 comments by @marcoscaceres, @mattsaxon)
-
Is PaymentResponse.details the result of a JSON.parse() w3c/payment-request#526 (2 comments by @marcoscaceres, @webpayments-specs)
-
Shipping Address Validation - Suggest Alternate Address w3c/payment-request#537 (1 comment by @marcoscaceres)
-
Reference to payment apps in Introduction needs updating w3c/payment-request#496 (1 comment by @marcoscaceres)
-
Consider removing merchant preference language w3c/payment-request#481 (1 comment by @marcoscaceres)
-
Add explicit extension point to matching algo w3c/payment-request#470 (1 comment by @adrianhopebailie)
-
-
14 pull requests opened.
-
Use first matching PaymentDetailsModifier w3c/payment-request#541, by @marcoscaceres.
-
Cater for platform-specific limitations w3c/payment-request#540, by @marcoscaceres.
-
Reject acceptedPromise if converting method data fails w3c/payment-request#536, by @marcoscaceres.
-
editorial: cleanup of updateWith() w3c/payment-request#533, by @marcoscaceres.
-
editorial: rephrase parse, rethrow, or null otherwise (closes #458) w3c/payment-request#531, by @marcoscaceres.
-
editorial: destructure tuple (closes #498) w3c/payment-request#530, by @marcoscaceres.
-
editorial: s/throw/reject in complete() (closes #509) w3c/payment-request#529, by @marcoscaceres.
-
editorial: s/characters/code points (closes #322) w3c/payment-request#528, by @marcoscaceres.
-
editorial: s/web page/developers w3c/payment-request#527, by @bentian.
-
editorial: s/payment app/payment handler w3c/payment-request#525, by @bentian.
-
editorial: fix reference to WebIDL spec w3c/payment-request#524, by @marcoscaceres.
-
editorial: document mandatory things needed for cr w3c/payment-request#523, by @marcoscaceres.
-
editorial: mark currencySystem at risk w3c/payment-request#522, by @marcoscaceres.
-
editorial: add link to test suite w3c/payment-request#519, by @marcoscaceres.
-
-
13 pull requests merged.
-
Reject with SecurityError if the UA rejects the call to show(). w3c/payment-request#512.
-
editorial: cleanup of updateWith() w3c/payment-request#533.
-
editorial: destructure tuple (closes #498) w3c/payment-request#530.
-
editorial: rephrase parse, rethrow, or null otherwise (closes #458) w3c/payment-request#531.
-
editorial: s/characters/code points (closes #322) w3c/payment-request#528.
-
editorial: s/throw/reject in complete() (closes #509) w3c/payment-request#529.
-
editorial: s/web page/developers w3c/payment-request#527.
-
Remove merchant preference language w3c/payment-request#518.
-
editorial: document mandatory things needed for cr w3c/payment-request#523.
-
editorial: mark currencySystem at risk w3c/payment-request#522.
-
editorial: add link to test suite w3c/payment-request#519.
-
editorial: fix reference to WebIDL spec w3c/payment-request#524.
-
editorial: s/payment app/payment handler w3c/payment-request#525.
-
-
2 pull requests closed.
-
Add extension point w3c/payment-request#492.
-
Section for A11Y Considerations w3c/payment-request#450.
-
-
14 pull requests received 82 new comments.
-
Reject acceptedPromise if converting method data fails w3c/payment-request#536 (15 comments by @adrianhopebailie, @domenic, @marcoscaceres)
-
editorial: s/web page/developers w3c/payment-request#527 (15 comments by @bentian, @dontcallmedom, @marcoscaceres)
-
Cater for platform-specific limitations w3c/payment-request#540 (10 comments by @domenic, @foolip, @marcoscaceres, @zcorpan)
-
Add extension point w3c/payment-request#492 (10 comments by @adrianba, @adrianhopebailie, @ianbjacobs, @marcoscaceres)
-
l10n: adds Localizable dict + TextDirection enum w3c/payment-request#455 (9 comments by @marcoscaceres, @tobie, @zcorpan)
-
Remove merchant preference language w3c/payment-request#518 (5 comments by @ianbjacobs, @marcoscaceres, @mattsaxon, @zkoch)
-
editorial: document mandatory things needed for cr w3c/payment-request#523 (4 comments by @adrianhopebailie, @ianbjacobs, @marcoscaceres)
-
editorial: destructure tuple (closes #498) w3c/payment-request#530 (3 comments by @adrianhopebailie, @marcoscaceres)
-
Reject with SecurityError if the UA rejects the call to show(). w3c/payment-request#512 (3 comments by @marcoscaceres)
-
editorial: mark currencySystem at risk w3c/payment-request#522 (3 comments by @domenic, @ianbjacobs, @marcoscaceres)
-
w3c/web-based-payment-handler
-
8 issues opened.
-
Dead link in an example w3c/web-based-payment-handler#166, by @tyoshino.
-
Missing question mark, w3c/web-based-payment-handler#163, by @gogerald.
-
Revisiting Payment Method specific filter/capability matching w3c/web-based-payment-handler#157, by @ianbjacobs.
-
Establish Editorial process w3c/web-based-payment-handler#156, by @marcoscaceres.
-
Suggestion: replace `PaymentWallets` with a property on `PaymentInstrument` w3c/web-based-payment-handler#153, by @dlongley.
-
Spec still talks about "payment app" w3c/web-based-payment-handler#151, by @marcoscaceres.
-
let 's App Pay w3c/web-based-payment-handler#148, by @Ezzzydoesit.
-
How to support communication with a payment app after initial PR API interaction? w3c/web-based-payment-handler#143, by @ianbjacobs.
-
-
3 issues closed.
-
let 's App Pay w3c/web-based-payment-handler#148.
-
Display may be subject to user and local policy (consider UA making security decisions etc) w3c/web-based-payment-handler#5.
-
Merge PaymentAppResponse and PaymentRequestEvent w3c/web-based-payment-handler#142.
-
-
11 issues received 54 new comments.
-
Missing question mark, w3c/web-based-payment-handler#163 (12 comments by @gogerald, @ianbjacobs, @romandev, @rsolomakhin)
-
How to support communication with a payment app after initial PR API interaction? w3c/web-based-payment-handler#143 (8 comments by @adrianhopebailie, @ianbjacobs, @mattsaxon, @msporny)
-
Establish Editorial process w3c/web-based-payment-handler#156 (7 comments by @adrianhopebailie, @ianbjacobs, @marcoscaceres, @msporny, @rsolomakhin)
-
Revisiting Payment Method specific filter/capability matching w3c/web-based-payment-handler#157 (6 comments by @ianbjacobs, @rsolomakhin)
-
Suggestion: replace `PaymentWallets` with a property on `PaymentInstrument` w3c/web-based-payment-handler#153 (5 comments by @adrianhopebailie, @dlongley, @ianbjacobs, @msporny)
-
Spec still talks about "payment app" w3c/web-based-payment-handler#151 (5 comments by @adrianhopebailie, @ianbjacobs, @marcoscaceres, @msporny)
-
Add .clear() to map-likes w3c/web-based-payment-handler#129 (4 comments by @ianbjacobs, @marcoscaceres)
-
Support for Abort() being delegated to Payment Handler w3c/web-based-payment-handler#117 (2 comments by @ianbjacobs, @rsolomakhin)
-
Display may be subject to user and local policy (consider UA making security decisions etc) w3c/web-based-payment-handler#5 (1 comment by @ianbjacobs)
-
Merge PaymentAppResponse and PaymentRequestEvent w3c/web-based-payment-handler#142 (1 comment by @ianbjacobs)
-
-
16 pull requests opened.
-
chore: tidy up w3c/web-based-payment-handler#165, by @marcoscaceres.
-
chore(.pr-preview): enable pull request previews w3c/web-based-payment-handler#164, by @marcoscaceres.
-
Add a constructor of PaymentRequestEvent and PaymentRequestEventInit. w3c/web-based-payment-handler#162, by @romandev.
-
Added "github" param for respec w3c/web-based-payment-handler#161, by @ianbjacobs.
-
Link fixes w3c/web-based-payment-handler#160, by @ianbjacobs.
-
link fixes w3c/web-based-payment-handler#159, by @ianbjacobs.
-
Link fixes w3c/web-based-payment-handler#158, by @ianbjacobs.
-
Pre FPWD tweaks w3c/web-based-payment-handler#155, by @ianbjacobs.
-
Update README.md w3c/web-based-payment-handler#154, by @ianbjacobs.
-
docs(README): reflect recent name change w3c/web-based-payment-handler#152, by @marcoscaceres.
-
editorial: fix references + don't show mailing list details w3c/web-based-payment-handler#150, by @marcoscaceres.
-
editorial: make shortname... shorter. w3c/web-based-payment-handler#149, by @marcoscaceres.
-
Fix wrt group charter w3c/web-based-payment-handler#147, by @ianbjacobs.
-
Update LICENSE.md w3c/web-based-payment-handler#146, by @ianbjacobs.
-
Fix to prevent duplicate ids by respec w3c/web-based-payment-handler#145, by @ianbjacobs.
-
Merge PaymentAppRequest and PaymentRequestEvent w3c/web-based-payment-handler#144, by @adrianhopebailie.
-
-
14 pull requests merged.
-
chore(.pr-preview): enable pull request previews w3c/web-based-payment-handler#164.
-
chore: tidy up w3c/web-based-payment-handler#165.
-
Added "github" param for respec w3c/web-based-payment-handler#161.
-
Link fixes w3c/web-based-payment-handler#160.
-
link fixes w3c/web-based-payment-handler#159.
-
Link fixes w3c/web-based-payment-handler#158.
-
Pre FPWD tweaks w3c/web-based-payment-handler#155.
-
Update README.md w3c/web-based-payment-handler#154.
-
editorial: make shortname... shorter. w3c/web-based-payment-handler#149.
-
editorial: fix references + don't show mailing list details w3c/web-based-payment-handler#150.
-
Update LICENSE.md w3c/web-based-payment-handler#146.
-
Fix wrt group charter w3c/web-based-payment-handler#147.
-
Fix to prevent duplicate ids by respec w3c/web-based-payment-handler#145.
-
Merge PaymentAppRequest and PaymentRequestEvent w3c/web-based-payment-handler#144.
-
-
1 pull request closed.
-
docs(README): reflect recent name change w3c/web-based-payment-handler#152.
-
-
6 pull requests received 25 new comments.
-
Add a constructor of PaymentRequestEvent and PaymentRequestEventInit. w3c/web-based-payment-handler#162 (18 comments by @marcoscaceres, @romandev)
-
Fix to prevent duplicate ids by respec w3c/web-based-payment-handler#145 (3 comments by @adrianhopebailie, @ianbjacobs, @marcoscaceres)
-
chore(.pr-preview): enable pull request previews w3c/web-based-payment-handler#164 (1 comment by @marcoscaceres)
-
docs(README): reflect recent name change w3c/web-based-payment-handler#152 (1 comment by @ianbjacobs)
-
w3c/payment-method-manifest
-
2 issues opened.
-
reconsider extra level of indirection for retrieving a manifest? w3c/payment-method-manifest#10, by @dbaron.
-
"Unicode serialization" definition has been removed w3c/payment-method-manifest#9, by @dbaron.
-
-
1 issue closed.
-
"Unicode serialization" definition has been removed w3c/payment-method-manifest#9.
-
-
2 issues received 3 new comments.
-
reconsider extra level of indirection for retrieving a manifest? w3c/payment-method-manifest#10 (2 comments by @dbaron, @zkoch)
-
Privacy considerations of retrieving a payment method manifest w3c/payment-method-manifest#7 (1 comment by @zkoch)
-
-
1 pull request opened.
-
Update Repository that the document lives in. w3c/payment-method-manifest#8, by @dbaron.
-
-
1 pull request merged.
-
Update Repository that the document lives in. w3c/payment-method-manifest#8.
-
-
1 pull request received 2 new comments.
-
Update Repository that the document lives in. w3c/payment-method-manifest#8 (2 comments by @dbaron, @domenic)
-
w3c/webpayments
-
1 issue closed.
-
[Tokenized Card Payment] Replace usage of 'last4' with 'suffix' w3c/webpayments#211.
-
-
1 issue received 1 new comment.
-
[Tokenized Card Payment] Replace usage of 'last4' with 'suffix' w3c/webpayments#211 (1 comment by @ianbjacobs)
-
-
1 pull request opened.
-
Updated tokenization (moved) and payment method practice w3c/webpayments#228, by @ianbjacobs.
-
-
1 pull request merged.
-
Updated tokenization (moved) and payment method practice w3c/webpayments#228.
-
w3c/payment-method-id
-
1 pull request received 1 new comment.
TR publications
-
2 documents published.
-
Payment Request API published twice as a Working Draft. History of Payment Request API
-
Participants
-
2 organizations joined.
-
Unify joined.
-
Mastercard Incorporated joined.
-
GitHub
w3c/payment-method-manifest
-
6 issues opened.
-
Privacy considerations of retrieving a payment method manifest w3c/payment-method-manifest#7, by @triblondon.
-
Migrate to a W3C org? w3c/payment-method-manifest#5, by @RByers.
-
Don't forget to do the IANA link relation registration dance w3c/payment-method-manifest#4, by @domenic.
-
Use the first Link header if multiple match our requirements w3c/payment-method-manifest#3, by @domenic.
-
Link URLs should be parsed relative w3c/payment-method-manifest#2, by @domenic.
-
Should these fetches have a client? (impacts CSP, CORS, ...) w3c/payment-method-manifest#1, by @domenic.
-
-
4 issues closed.
-
Migrate to a W3C org? w3c/payment-method-manifest#5.
-
Don't forget to do the IANA link relation registration dance w3c/payment-method-manifest#4.
-
Use the first Link header if multiple match our requirements w3c/payment-method-manifest#3.
-
Link URLs should be parsed relative w3c/payment-method-manifest#2.
-
-
2 issues received 20 new comments.
-
Should these fetches have a client? (impacts CSP, CORS, ...) w3c/payment-method-manifest#1 (14 comments by @annevk, @domenic, @rsolomakhin)
-
Migrate to a W3C org? w3c/payment-method-manifest#5 (6 comments by @domenic, @ianbjacobs, @RByers, @zkoch)
-
-
1 pull request opened.
-
Minor editorial suggestions w3c/payment-method-manifest#6, by @ianbjacobs.
-
-
1 pull request closed.
-
Minor editorial suggestions w3c/payment-method-manifest#6.
-
-
1 pull request received 2 new comments.
w3c/payment-method-id
-
6 issues opened.
-
Remove "Conditional Matching Beyond Payment Method Identifier Matching" w3c/payment-method-id#34, by @marcoscaceres.
-
Reference manifest spec w3c/payment-method-id#33, by @marcoscaceres.
-
"W3C String" is overly generic w3c/payment-method-id#32, by @marcoscaceres.
-
citation to dated version of since-abandoned url spec fork is unusual w3c/payment-method-id#30, by @dbaron.
-
[SECURE-CONTEXTS] should be a normative rather than informative reference w3c/payment-method-id#29, by @dbaron.
-
use of 'must' in section on Syntax of URLs as Payment Method Identifiers is suspicious w3c/payment-method-id#28, by @dbaron.
-
-
2 issues closed.
-
SRI on manifest w3c/payment-method-id#18.
-
Why are payment ids restricted to [a-z0-9]? w3c/payment-method-id#20.
-
-
8 issues received 41 new comments.
-
Link to registry of W3C-published short strings w3c/payment-method-id#26 (17 comments by @adrianhopebailie, @ianbjacobs, @marcoscaceres, @zkoch)
-
Reference manifest spec w3c/payment-method-id#33 (9 comments by @ianbjacobs, @marcoscaceres, @zkoch)
-
[SECURE-CONTEXTS] should be a normative rather than informative reference w3c/payment-method-id#29 (7 comments by @dbaron, @ianbjacobs, @marcoscaceres)
-
citation to dated version of since-abandoned url spec fork is unusual w3c/payment-method-id#30 (3 comments by @ianbjacobs, @marcoscaceres, @zkoch)
-
Remove "Conditional Matching Beyond Payment Method Identifier Matching" w3c/payment-method-id#34 (2 comments by @ianbjacobs, @marcoscaceres)
-
-
3 pull requests opened.
-
editorial: rm 'Conditional Matching Beyond Payment Methods' section w3c/payment-method-id#36, by @marcoscaceres.
-
feat: rewrite all the things w3c/payment-method-id#35, by @marcoscaceres.
-
If URL parsing fails then always fail to match URLs. w3c/payment-method-id#31, by @adrianba.
-
-
2 pull requests received 53 new comments.
-
feat: rewrite all the things w3c/payment-method-id#35 (49 comments by @annevk, @domenic, @ianbjacobs, @marcoscaceres, @zkoch)
-
If URL parsing fails then always fail to match URLs. w3c/payment-method-id#31 (4 comments by @annevk, @marcoscaceres)
-
w3c/payment-request
-
16 issues opened.
-
Editorial: event `.target` attribute should be relatedTarget w3c/payment-request#513, by @marcoscaceres.
-
Editorial: paymentResponse.complete() should return a rejected promise, not throw w3c/payment-request#509, by @domenic.
-
"User accepts payment request" algorithm should timeout without .complete(). w3c/payment-request#508, by @rsolomakhin.
-
Define expected behavior when no 'shippingaddresschange ' event listener is defined w3c/payment-request#507, by @gauntface.
-
Provide better mapping between PaymentAddress and HTML5 autofill w3c/payment-request#505, by @marcoscaceres.
-
Missing (normative) reference to BPC-47 (language code) w3c/payment-request#503, by @ianbjacobs.
-
Links to some HTML definitions are broken w3c/payment-request#502, by @npdoty.
-
Clarify use of API in (or not in) Secure Contexts w3c/payment-request#501, by @ianbjacobs.
-
State change issues in updateWith() w3c/payment-request#500, by @mattsaxon.
-
'Pull' Payment Bias in API spec w3c/payment-request#499, by @mattsaxon.
-
Consider adding examples of payment matching algorithm w3c/payment-request#498, by @mattsaxon.
-
Payment App or Payment Handler language w3c/payment-request#497, by @mattsaxon.
-
Reference to payment apps in Introduction needs updating w3c/payment-request#496, by @mattsaxon.
-
PaymentAddress and null values w3c/payment-request#495, by @marcoscaceres.
-
Add postMessage() and addMessageListener() for enabling "in-bound" communication w3c/payment-request#494, by @cyberphone.
-
Standardize on "Payer" and "Payee" terms w3c/payment-request#493, by @adrianhopebailie.
-
-
10 issues closed.
-
Editorial: event `.target` attribute should be relatedTarget w3c/payment-request#513.
-
'Interactive' Bias in API w3c/payment-request#467.
-
"User accepts payment request" algorithm should timeout without .complete(). w3c/payment-request#508.
-
Define expected behavior when no 'shippingaddresschange ' event listener is defined w3c/payment-request#507.
-
Missing (normative) reference to BPC-47 (language code) w3c/payment-request#503.
-
Supplement QuoteExceededError with NotAllowedError for canMakePayments w3c/payment-request#485.
-
State change issues in updateWith() w3c/payment-request#500.
-
Links to some HTML definitions are broken w3c/payment-request#502.
-
Clarify use of API in (or not in) Secure Contexts w3c/payment-request#501.
-
Add postMessage() and addMessageListener() for enabling "in-bound" communication w3c/payment-request#494.
-
-
26 issues received 114 new comments.
-
Define expected behavior when no 'shippingaddresschange ' event listener is defined w3c/payment-request#507 (11 comments by @domenic, @gauntface, @marcoscaceres, @nickjshearer, @rsolomakhin, @zkoch)
-
should .show() be user gated? w3c/payment-request#486 (10 comments by @adrianba, @dlongley, @marcoscaceres, @nickjshearer, @rvm4, @zkoch)
-
"User accepts payment request" algorithm should timeout without .complete(). w3c/payment-request#508 (10 comments by @domenic, @marcoscaceres, @romandev, @rsolomakhin)
-
Should user agent validate currency? w3c/payment-request#490 (9 comments by @adrianhopebailie, @delapuente, @marcoscaceres, @rsolomakhin)
-
Standardize on "Payer" and "Payee" terms w3c/payment-request#493 (9 comments by @adrianhopebailie, @ianbjacobs, @marcoscaceres, @mattsaxon)
-
Links to some HTML definitions are broken w3c/payment-request#502 (8 comments by @domenic, @marcoscaceres)
-
canMakePayment() might be in the wrong place? w3c/payment-request#403 (7 comments by @Edouard-chin, @rsolomakhin)
-
Should API support billing address capture (for tax computation)? w3c/payment-request#27 (7 comments by @burdges, @ghost, @marcoscaceres, @zkoch)
-
Provide better mapping between PaymentAddress and HTML5 autofill w3c/payment-request#505 (7 comments by @lararennie, @marcoscaceres, @rsolomakhin, @zkoch)
-
Clarify use of API in (or not in) Secure Contexts w3c/payment-request#501 (4 comments by @ianbjacobs, @marcoscaceres)
-
Add postMessage() and addMessageListener() for enabling "in-bound" communication w3c/payment-request#494 (4 comments by @adrianhopebailie, @cyberphone, @ianbjacobs, @marcoscaceres)
-
"User accepts the payment request algorithm" needs to clarify where Payment Handlers are invoked w3c/payment-request#476 (3 comments by @ianbjacobs, @mattsaxon, @mattsaxonwp)
-
Editors to figure out text on line items w3c/payment-request#477 (2 comments by @ianbjacobs, @zkoch)
-
Reference to payment apps in Introduction needs updating w3c/payment-request#496 (2 comments by @ianbjacobs, @marcoscaceres)
-
Payment App or Payment Handler language w3c/payment-request#497 (2 comments by @ianbjacobs, @mattsaxon)
-
maybe add `DisplayItem` dictionary w3c/payment-request#457 (2 comments by @adrianhopebailie, @marcoscaceres)
-
Editorial: event `.target` attribute should be relatedTarget w3c/payment-request#513 (1 comment by @marcoscaceres)
-
Unclear what happens when multiple PRs call show() w3c/payment-request#462 (1 comment by @marcoscaceres)
-
Consider adding examples of payment matching algorithm w3c/payment-request#498 (1 comment by @marcoscaceres)
-
Add explicit extension point to matching algo w3c/payment-request#470 (1 comment by @adrianhopebailie)
-
-
11 pull requests opened.
-
Remove merchant preference language w3c/payment-request#518, by @ianbjacobs.
-
editorial: s/target/request in updateWith() algo w3c/payment-request#517, by @marcoscaceres.
-
editorial: s/target/request in updateWith() algo w3c/payment-request#516, by @marcoscaceres.
-
editorial: use DOM relatedTarget instead of .target (closes #513) w3c/payment-request#515, by @marcoscaceres.
-
editorial: xref EventInit in DOM spec w3c/payment-request#514, by @marcoscaceres.
-
Reject with SecurityError if the UA rejects the call to show(). w3c/payment-request#512, by @adrianba.
-
Remove 2119 language from privacy section. w3c/payment-request#511, by @adrianba.
-
Added BCP ref w3c/payment-request#510, by @mollyd16.
-
Editorial: consider removing merchant preference language w3c/payment-request#506, by @ianbjacobs.
-
fix: broken links to HTML (closes #502) w3c/payment-request#504, by @marcoscaceres.
-
Add extension point w3c/payment-request#492, by @adrianhopebailie.
-
-
6 pull requests merged.
-
editorial: s/target/request in updateWith() algo w3c/payment-request#517.
-
editorial: xref EventInit in DOM spec w3c/payment-request#514.
-
Added BCP ref w3c/payment-request#510.
-
Use "NotAllowedError" instead of "QuotaExceededError" w3c/payment-request#488.
-
fix: broken links to HTML (closes #502) w3c/payment-request#504.
-
Adding legal entity types for consistency w3c/payment-request#491.
-
-
3 pull requests closed.
-
Editorial: consider removing merchant preference language w3c/payment-request#506.
-
editorial: use DOM relatedTarget instead of .target (closes #513) w3c/payment-request#515.
-
editorial: s/target/request in updateWith() algo w3c/payment-request#516.
-
-
9 pull requests received 37 new comments.
-
Editorial: consider removing merchant preference language w3c/payment-request#506 (15 comments by @ianbjacobs, @marcoscaceres, @mattsaxon, @mountainhippo, @zkoch)
-
Add extension point w3c/payment-request#492 (8 comments by @adrianhopebailie, @ianbjacobs, @marcoscaceres)
-
Remove 2119 language from privacy section. w3c/payment-request#511 (5 comments by @adrianba, @domenic, @ianbjacobs, @marcoscaceres)
-
editorial: use DOM relatedTarget instead of .target (closes #513) w3c/payment-request#515 (2 comments by @domenic, @marcoscaceres)
-
Reject with SecurityError if the UA rejects the call to show(). w3c/payment-request#512 (1 comment by @domenic)
-
editorial: s/target/request in updateWith() algo w3c/payment-request#516 (1 comment by @marcoscaceres)
-
w3c/webpayments
-
2 issues closed.
-
Payment Method Manifest spec - should enable country specific app discovery w3c/webpayments#224.
-
Fingerprint and version metadata (in Web App Manifest spec) w3c/webpayments#225.
-
-
3 issues received 22 new comments.
-
Fingerprint and version metadata (in Web App Manifest spec) w3c/webpayments#225 (19 comments by @adrianhopebailie, @dlongley, @domenic, @marcoscaceres, @mgiuca, @RByers, @rsolomakhin, @zkoch)
-
Payment Method Manifest spec - should enable country specific app discovery w3c/webpayments#224 (2 comments by @kayakalan, @marcoscaceres)
-
-
2 pull requests opened.
-
Use of filters w3c/webpayments#227, by @ianbjacobs.
-
Updates to Interledger Payment Method spec w3c/webpayments#226, by @adrianhopebailie.
-
-
2 pull requests merged.
-
Use of filters w3c/webpayments#227.
-
Updates to Interledger Payment Method spec w3c/webpayments#226.
-
w3c/web-based-payment-handler
-
8 issues opened.
-
Merge PaymentAppResponse and PaymentRequestEvent w3c/web-based-payment-handler#142, by @adrianhopebailie.
-
Passing modifiers to payment apps w3c/web-based-payment-handler#139, by @rsolomakhin.
-
Define event handler before payment manager w3c/web-based-payment-handler#134, by @adrianhopebailie.
-
Add .clear() to map-likes w3c/web-based-payment-handler#129, by @marcoscaceres.
-
Revisit Examples 4 and 5 w3c/web-based-payment-handler#128, by @ianbjacobs.
-
Do we need "Payment Manager" and "Payment Handler"? w3c/web-based-payment-handler#127, by @ianbjacobs.
-
Image object is undefined w3c/web-based-payment-handler#125, by @ianbjacobs.
-
[Privacy] Clarify what information user agents forget at various moments w3c/web-based-payment-handler#124, by @ianbjacobs.
-
-
10 issues closed.
-
Do we need "Payment Manager" and "Payment Handler"? w3c/web-based-payment-handler#127.
-
Define event handler before payment manager w3c/web-based-payment-handler#134.
-
Passing modifiers to payment apps w3c/web-based-payment-handler#139.
-
Origin should include iframe(s) w3c/web-based-payment-handler#120.
-
[Editorial] Clean up respec errors w3c/web-based-payment-handler#122.
-
Renaming PaymentApp* classes w3c/web-based-payment-handler#109.
-
What is a Payment App? w3c/web-based-payment-handler#105.
-
[Privacy] Clarify what information user agents forget at various moments w3c/web-based-payment-handler#124.
-
What does "icon" mean? w3c/web-based-payment-handler#69.
-
`appRequest` attribute should not be a dictionary w3c/web-based-payment-handler#111.
-
-
2 issues reopened.
-
Do we need "Payment Manager" and "Payment Handler"? w3c/web-based-payment-handler#127, by @mattsaxon.
-
Multiple payment apps per origin w3c/web-based-payment-handler#98, by @ianbjacobs.
-
-
20 issues received 43 new comments.
-
Do we need "Payment Manager" and "Payment Handler"? w3c/web-based-payment-handler#127 (9 comments by @adrianhopebailie, @mattsaxon, @rsolomakhin)
-
[Privacy] Clarify what information user agents forget at various moments w3c/web-based-payment-handler#124 (4 comments by @ianbjacobs, @marcoscaceres)
-
Origin should include iframe(s) w3c/web-based-payment-handler#120 (3 comments by @ianbjacobs, @rsolomakhin)
-
Share user data with Payment App w3c/web-based-payment-handler#123 (3 comments by @adrianhopebailie, @marcoscaceres)
-
Passing modifiers to payment apps w3c/web-based-payment-handler#139 (2 comments by @ianbjacobs, @rsolomakhin)
-
Define event handler before payment manager w3c/web-based-payment-handler#134 (2 comments by @adrianhopebailie, @ianbjacobs)
-
Renaming PaymentApp* classes w3c/web-based-payment-handler#109 (2 comments by @ianbjacobs, @tommythorsen)
-
Relation between merchant order of payment methods and payment app order of instruments w3c/web-based-payment-handler#116 (2 comments by @ianbjacobs, @kmealey)
-
Image object is undefined w3c/web-based-payment-handler#125 (2 comments by @marcoscaceres, @rsolomakhin)
-
Support for Abort() being delegated to Payment Handler w3c/web-based-payment-handler#117 (2 comments by @adrianhopebailie, @mattsaxon)
-
Merge PaymentAppResponse and PaymentRequestEvent w3c/web-based-payment-handler#142 (1 comment by @ianbjacobs)
-
`appRequest` attribute should not be a dictionary w3c/web-based-payment-handler#111 (1 comment by @rsolomakhin)
-
Display may be subject to user and local policy (consider UA making security decisions etc) w3c/web-based-payment-handler#5 (1 comment by @ianbjacobs)
-
-
11 pull requests opened.
-
respec fix w3c/web-based-payment-handler#141, by @ianbjacobs.
-
Improve payment app arch image w3c/web-based-payment-handler#140, by @ianbjacobs.
-
Editorial changes for FPWD w3c/web-based-payment-handler#138, by @adrianhopebailie.
-
Tidy w3c/web-based-payment-handler#137, by @ianbjacobs.
-
Updated short name and URL for new repo name w3c/web-based-payment-handler#136, by @ianbjacobs.
-
Update README.md to link to new repo w3c/web-based-payment-handler#135, by @adrianhopebailie.
-
Issue marker cleanup w3c/web-based-payment-handler#133, by @ianbjacobs.
-
Diagrams w3c/web-based-payment-handler#132, by @ianbjacobs.
-
WebIDL fix w3c/web-based-payment-handler#131, by @ianbjacobs.
-
Add support for topLevelOrigin and paymentRequestOrigin w3c/web-based-payment-handler#130, by @ianbjacobs.
-
Respec fixes w3c/web-based-payment-handler#126, by @ianbjacobs.
-
-
12 pull requests merged.
-
respec fix w3c/web-based-payment-handler#141.
-
Improve payment app arch image w3c/web-based-payment-handler#140.
-
Editorial changes for FPWD w3c/web-based-payment-handler#138.
-
Tidy w3c/web-based-payment-handler#137.
-
Updated short name and URL for new repo name w3c/web-based-payment-handler#136.
-
Update README.md to link to new repo w3c/web-based-payment-handler#135.
-
Diagrams w3c/web-based-payment-handler#132.
-
Issue marker cleanup w3c/web-based-payment-handler#133.
-
WebIDL fix w3c/web-based-payment-handler#131.
-
Add support for topLevelOrigin and paymentRequestOrigin w3c/web-based-payment-handler#130.
-
Respec fixes w3c/web-based-payment-handler#126.
-
The instrumnets/wallets attributes should be readonly and [SameObject]. w3c/web-based-payment-handler#121.
-
-
7 pull requests received 101 new comments.
-
Editorial changes for FPWD w3c/web-based-payment-handler#138 (16 comments by @adrianhopebailie, @dlongley, @ianbjacobs)
-
Issue marker cleanup w3c/web-based-payment-handler#133 (8 comments by @adrianhopebailie, @ianbjacobs, @marcoscaceres)
-
Diagrams w3c/web-based-payment-handler#132 (8 comments by @adrianhopebailie, @ianbjacobs, @marcoscaceres)
-
The instrumnets/wallets attributes should be readonly and [SameObject]. w3c/web-based-payment-handler#121 (6 comments by @adamroach, @ianbjacobs, @marcoscaceres, @romandev)
-
Add support for topLevelOrigin and paymentRequestOrigin w3c/web-based-payment-handler#130 (2 comments by @frank-hoffmann, @ianbjacobs)
TR publications
-
12 documents published.
-
Payment Request API published 10 times as a Working Draft. History of Payment Request API
-
Payment Method Identifiers published as a Working Draft. History of Payment Method Identifiers
-
Basic Card Payment published as a Working Draft. History of Basic Card Payment
-
GitHub
w3c/payment-request
-
26 issues opened.
-
Should user agent validate currency? w3c/payment-request#490, by @perja12.
-
should .show() be user gated? w3c/payment-request#486, by @marcoscaceres.
-
Supplement QuoteExceededError with NotAllowedError for canMakePayments w3c/payment-request#485, by @nickjshearer.
-
complete() does not match all payment apps w3c/payment-request#484, by @cyberphone.
-
Should the user agent generate the `id` when it's empty? w3c/payment-request#483, by @rsolomakhin.
-
mark currencySystem as feature at risk w3c/payment-request#482, by @marcos-travel.
-
Consider removing merchant preference language w3c/payment-request#481, by @zkoch.
-
Does PR API need to include text around matching to take payment method manifest into account? w3c/payment-request#478, by @ianbjacobs.
-
Editors to figure out text on line items w3c/payment-request#477, by @zkoch.
-
"User accepts the payment request algorithm" needs to clarify where Payment Handlers are invoked w3c/payment-request#476, by @mattsaxon.
-
Clarity required in section 21.2 regarding privacy w3c/payment-request#475, by @mattsaxon.
-
Aborting of in-progress push payments w3c/payment-request#473, by @mattsaxon.
-
Request `shippingType` attribute is not defined w3c/payment-request#472, by @marcos-travel.
-
Recipient and payerName are lacking i18n support w3c/payment-request#471, by @nickjshearer.
-
Add explicit extension point to matching algo w3c/payment-request#470, by @zkoch.
-
'Interactive' Bias in API w3c/payment-request#467, by @mattsaxon.
-
Why are two sections non-normative? w3c/payment-request#466, by @ianbjacobs.
-
validate supportedMethods w3c/payment-request#464, by @marcoscaceres.
-
Unclear what happens when multiple PRs call show() w3c/payment-request#462, by @marcoscaceres.
-
show() method lacks developer guidance w3c/payment-request#461, by @marcoscaceres.
-
Badness in constructor... w3c/payment-request#459, by @marcoscaceres.
-
Ambiguity in "Process payment methods:" w3c/payment-request#458, by @marcoscaceres.
-
maybe add `DisplayItem` dictionary w3c/payment-request#457, by @marcoscaceres.
-
Move examples to top of document w3c/payment-request#456, by @marcoscaceres.
-
NotSupportedError in private browsing mode w3c/payment-request#448, by @rsolomakhin.
-
API assumes Issuer communication is OOB w3c/payment-request#447, by @cyberphone.
-
-
32 issues closed.
-
Group payment dictionaries into a section w3c/payment-request#427.
-
markup issues w3c/payment-request#441.
-
Why are two sections non-normative? w3c/payment-request#466.
-
Does PR API need to include text around matching to take payment method manifest into account? w3c/payment-request#478.
-
complete() does not match all payment apps w3c/payment-request#484.
-
Recipient and payerName are lacking i18n support w3c/payment-request#471.
-
Should the user agent generate the `id` when it's empty? w3c/payment-request#483.
-
updateWith will silently ignore data in hard-to-debug ways w3c/payment-request#350.
-
PaymentRequest type checks (valid non-negative monetary value) w3c/payment-request#306.
-
maybe add `DisplayItem` dictionary w3c/payment-request#457.
-
Addition of flag on PaymentMethodData to indicate that line items should be shared with apps w3c/payment-request#446.
-
Badness in constructor... w3c/payment-request#459.
-
NotSupportedError in private browsing mode w3c/payment-request#448.
-
valid decimal monetary value maybe overly restrictive w3c/payment-request#304.
-
How can a user agent not accept a payment method? w3c/payment-request#273.
-
What does it mean to "accept the payment"? w3c/payment-request#278.
-
Should values for supportedNetworks be defined in Basic Card or separately? w3c/payment-request#325.
-
PaymentApp fails to abort payment flow w3c/payment-request#384.
-
Supporting push payment methods w3c/payment-request#224.
-
PaymentResponse attributes should be separate sections w3c/payment-request#442.
-
Introductory explanations of methods should be non-normative notes w3c/payment-request#379.
-
Fix markup errors that broke autopublishing w3c/payment-request#444.
-
PaymentDetails should include a transaction ID w3c/payment-request#287.
-
PaymentRequestID initialization w3c/payment-request#412.
-
It is never stated how the payment request ID is used w3c/payment-request#415.
-
Providing/Generating paymentRequestID during construction w3c/payment-request#388.
-
PaymentDetails "total" member should be required w3c/payment-request#320.
-
Why does PaymentRequest constructor throw on details.error w3c/payment-request#302.
-
API assumes Issuer communication is OOB w3c/payment-request#447.
-
`PaymentInstrument.complete(result)` wording w3c/payment-request#402.
-
Spec talks about dictionary fields instead of dictionary members w3c/payment-request#424.
-
"Shown" should be "presented" in prose w3c/payment-request#428.
-
-
1 issue reopened.
-
Add Guidance Text for User Consent w3c/payment-request#229, by @ianbjacobs.
-
-
38 issues received 138 new comments.
-
validate supportedMethods w3c/payment-request#464 (13 comments by @domenic, @ianbjacobs, @marcoscaceres, @zkoch)
-
Should user agent validate currency? w3c/payment-request#490 (12 comments by @domenic, @ianbjacobs, @marcoscaceres, @perja12, @rsolomakhin)
-
Unclear what happens when multiple PRs call show() w3c/payment-request#462 (12 comments by @domenic, @marcoscaceres, @rsolomakhin, @zkoch)
-
should .show() be user gated? w3c/payment-request#486 (10 comments by @dlongley, @ianbjacobs, @marcoscaceres, @mattsaxon, @mnoorenberghe, @nickjshearer, @rsolomakhin, @zkoch)
-
Add dir/lang member on dictionaries whose content is displayed in browser UI w3c/payment-request#327 (9 comments by @aphillips, @ianbjacobs, @marcoscaceres, @r12a)
-
Fix markup errors that broke autopublishing w3c/payment-request#444 (8 comments by @ianbjacobs, @marcoscaceres, @sideshowbarker)
-
Consider removing merchant preference language w3c/payment-request#481 (6 comments by @ianbjacobs, @nickjshearer, @weksler, @zkoch)
-
API assumes Issuer communication is OOB w3c/payment-request#447 (6 comments by @bentian, @cyberphone, @ianbjacobs, @marcoscaceres)
-
NotSupportedError in private browsing mode w3c/payment-request#448 (5 comments by @domenic, @marcoscaceres, @rsolomakhin)
-
valid decimal monetary value maybe overly restrictive w3c/payment-request#304 (4 comments by @marcoscaceres, @rsolomakhin)
-
Ambiguity in "Process payment methods:" w3c/payment-request#458 (4 comments by @domenic, @marcoscaceres, @rsolomakhin)
-
Add Guidance Text for User Consent w3c/payment-request#229 (4 comments by @chaals, @ianbjacobs, @zkoch)
-
Why are two sections non-normative? w3c/payment-request#466 (3 comments by @domenic, @marcoscaceres)
-
Supplement QuoteExceededError with NotAllowedError for canMakePayments w3c/payment-request#485 (3 comments by @domenic, @rsolomakhin, @zkoch)
-
Should values for supportedNetworks be defined in Basic Card or separately? w3c/payment-request#325 (3 comments by @ianbjacobs, @zkoch)
-
PaymentRequest does not handle the case of store pickup w3c/payment-request#389 (3 comments by @adrianhopebailie, @zkoch)
-
Initial values for internal slots w3c/payment-request#436 (3 comments by @domenic, @marcoscaceres, @zkoch)
-
Behavior for multiple modifiers for the same payment method is not defined w3c/payment-request#309 (2 comments by @domenic, @zkoch)
-
Recipient and payerName are lacking i18n support w3c/payment-request#471 (2 comments by @marcoscaceres, @nickjshearer)
-
Need to define the interaction of payment API with navigation and browsing context destruction w3c/payment-request#360 (2 comments by @bzbarsky, @marcoscaceres)
-
PaymentRequest type checks (valid non-negative monetary value) w3c/payment-request#306 (2 comments by @marcoscaceres, @zkoch)
-
Does PR API need to include text around matching to take payment method manifest into account? w3c/payment-request#478 (1 comment by @marcoscaceres)
-
"User accepts the payment request algorithm" needs to clarify where Payment Handlers are invoked w3c/payment-request#476 (1 comment by @marcoscaceres)
-
Should the user agent generate the `id` when it's empty? w3c/payment-request#483 (1 comment by @domenic)
-
Addition of flag on PaymentMethodData to indicate that line items should be shared with apps w3c/payment-request#446 (1 comment by @zkoch)
-
PaymentDetails should include a transaction ID w3c/payment-request#287 (1 comment by @marcoscaceres)
-
It is never stated how the payment request ID is used w3c/payment-request#415 (1 comment by @marcoscaceres)
-
-
18 pull requests opened.
-
Adding legal entity types for consistency w3c/payment-request#491, by @abatishchev.
-
fix: change Events section to normative (closes #466) w3c/payment-request#489, by @marcoscaceres.
-
Use "NotAllowedError" instead of "QuotaExceededError" w3c/payment-request#488, by @domenic.
-
Disallow multiple showing payment requests per user agent w3c/payment-request#487, by @domenic.
-
editorial: grouped payment details dictionaries into section w3c/payment-request#479, by @kayakalan.
-
editorial: Clarify wording to not imply 'pull' only payments w3c/payment-request#474, by @mattsaxon.
-
editorial: remove redundant event declaration w3c/payment-request#469, by @marcos-travel.
-
fix(complete): bugus result value will have thrown already w3c/payment-request#468, by @marcos-travel.
-
Editorial changes w3c/payment-request#465, by @ianbjacobs.
-
fix: make supportedMethod conforming w3c/payment-request#463, by @marcoscaceres.
-
editorial(constructor): remove redundant line (closes #459) w3c/payment-request#460, by @marcoscaceres.
-
l10n: adds Localizable dict + TextDirection enum w3c/payment-request#455, by @marcoscaceres.
-
Changes to show() and canMakePayment() to take into account w3c/payment-request#454, by @ianbjacobs.
-
Remove trailing comma from IDL enums w3c/payment-request#453, by @zcorpan.
-
Fix constructor handling of shippingType w3c/payment-request#452, by @domenic.
-
Make updateWith() reject the show() promise on validation failures w3c/payment-request#451, by @domenic.
-
Section for A11Y Considerations w3c/payment-request#450, by @halindrome.
-
Specify how to abort a payment request w3c/payment-request#449, by @domenic.
-
-
19 pull requests merged.
-
Disallow multiple showing payment requests per user agent w3c/payment-request#487.
-
editorial: grouped payment details dictionaries into section w3c/payment-request#479.
-
fix: change Events section to normative (closes #466) w3c/payment-request#489.
-
fix(complete): bugus result value will have thrown already w3c/payment-request#468.
-
editorial: remove redundant event declaration w3c/payment-request#469.
-
Make updateWith() reject the show() promise on validation failures w3c/payment-request#451.
-
Editorial changes w3c/payment-request#465.
-
editorial(constructor): remove redundant line (closes #459) w3c/payment-request#460.
-
Fix constructor handling of shippingType w3c/payment-request#452.
-
Changes to show() and canMakePayment() to take into account w3c/payment-request#454.
-
Remove trailing comma from IDL enums w3c/payment-request#453.
-
Specify how to abort a payment request w3c/payment-request#449.
-
editorial: attr/method intros are notes (closes #379) w3c/payment-request#438.
-
feat: put request id in details dictionary w3c/payment-request#426.
-
fix: delegate total and error member checks to WebIDL w3c/payment-request#425.
-
fix: s/user interaction/transaction (closes #402) w3c/payment-request#432.
-
editorial: s/fields/members + xref fixes (closes #424) w3c/payment-request#443.
-
editorial: s/shown/presented (closes #428) w3c/payment-request#435.
-
Create pr-preview config file. w3c/payment-request#445.
-
-
4 pull requests closed.
-
fix: make supportedMethod conforming w3c/payment-request#463.
-
Add billing shipping type w3c/payment-request#409.
-
Define payment option filtering algorithm. w3c/payment-request#420.
-
Make updateWith() return a promise signaling any update failures w3c/payment-request#418.
-
-
22 pull requests received 127 new comments.
-
l10n: adds Localizable dict + TextDirection enum w3c/payment-request#455 (14 comments by @annevk, @domenic, @ianbjacobs, @marcoscaceres, @tobie, @zcorpan)
-
Section for A11Y Considerations w3c/payment-request#450 (13 comments by @chaals, @halindrome, @ianbjacobs, @marcoscaceres)
-
fix: change Events section to normative (closes #466) w3c/payment-request#489 (12 comments by @domenic, @marcoscaceres)
-
Make updateWith() reject the show() promise on validation failures w3c/payment-request#451 (11 comments by @domenic, @marcoscaceres, @rsolomakhin, @zkoch)
-
feat: put request id in details dictionary w3c/payment-request#426 (10 comments by @domenic, @marcoscaceres)
-
fix: delegate total and error member checks to WebIDL w3c/payment-request#425 (10 comments by @bentian, @domenic, @marcoscaceres)
-
Fix constructor handling of shippingType w3c/payment-request#452 (9 comments by @domenic, @marcoscaceres, @rsolomakhin, @zkoch)
-
Create pr-preview config file. w3c/payment-request#445 (7 comments by @marcoscaceres, @sideshowbarker, @tobie)
-
editorial: attr/method intros are notes (closes #379) w3c/payment-request#438 (6 comments by @domenic, @marcoscaceres)
-
editorial: grouped payment details dictionaries into section w3c/payment-request#479 (5 comments by @kayakalan, @marcos-travel, @marcoscaceres)
-
editorial: s/fields/members + xref fixes (closes #424) w3c/payment-request#443 (5 comments by @marcoscaceres, @tobie, @zkoch)
-
Define payment option filtering algorithm. w3c/payment-request#420 (3 comments by @adrianhopebailie, @ianbjacobs, @zkoch)
-
Changes to show() and canMakePayment() to take into account w3c/payment-request#454 (3 comments by @domenic, @ianbjacobs)
-
editorial: Clarify wording to not imply 'pull' only payments w3c/payment-request#474 (2 comments by @ianbjacobs, @marcoscaceres)
-
Make updateWith() return a promise signaling any update failures w3c/payment-request#418 (2 comments by @domenic, @marcoscaceres)
-
fix: s/user interaction/transaction (closes #402) w3c/payment-request#432 (2 comments by @marcoscaceres, @zkoch)
-
editorial(constructor): remove redundant line (closes #459) w3c/payment-request#460 (1 comment by @marcoscaceres)
-
w3c/webpayments
-
4 issues opened.
-
Fingerprint and version metadata (in Web App Manifest spec) w3c/webpayments#225, by @mgiuca.
-
Payment Method Manifest spec - should enable country specific app discovery w3c/webpayments#224, by @kayakalan.
-
Sepamail WebIDL syntax and algorithms w3c/webpayments#219, by @rsolomakhin.
-
3D secure support w3c/webpayments#217, by @Abacaxi-Nelson.
-
-
1 issue closed.
-
3D secure support w3c/webpayments#217.
-
-
6 issues received 33 new comments.
-
Fingerprint and version metadata (in Web App Manifest spec) w3c/webpayments#225 (17 comments by @cyberphone, @domenic, @marcoscaceres, @mgiuca, @rsolomakhin, @zkoch)
-
Payment Method Manifest spec - should enable country specific app discovery w3c/webpayments#224 (7 comments by @ianbjacobs, @rsolomakhin)
-
Sepamail WebIDL syntax and algorithms w3c/webpayments#219 (3 comments by @ianbjacobs, @marcoscaceres, @rsolomakhin)
-
-
7 pull requests opened.
-
Update sepamail.html w3c/webpayments#223, by @CYV.
-
issue #12 / what happens if supportedNetwork & supportedTypes are empty fields w3c/webpayments#222, by @CYV.
-
Small tweaks for sepamail w3c/webpayments#218, by @ianbjacobs.
-
Sepamail w3c/webpayments#216, by @ianbjacobs.
-
New sepamail payment method spec from Cyril w3c/webpayments#215, by @ianbjacobs.
-
-
6 pull requests merged.
-
Update sepamail.html w3c/webpayments#223.
-
issue #12 / what happens if supportedNetwork & supportedTypes are empty fields w3c/webpayments#222.
-
issue #12 w3c/webpayments#221.
-
Small tweaks for sepamail w3c/webpayments#218.
-
Sepamail w3c/webpayments#216.
-
New sepamail payment method spec from Cyril w3c/webpayments#215.
-
-
1 pull request closed.
-
issue #12 w3c/webpayments#220.
-
w3c/web-based-payment-handler
-
10 issues opened.
-
Share user data with Payment App w3c/web-based-payment-handler#123, by @frank-hoffmann.
-
[Editorial] Clean up respec errors w3c/web-based-payment-handler#122, by @ianbjacobs.
-
Origin should include iframe(s) w3c/web-based-payment-handler#120, by @frank-hoffmann.
-
PaymentRequestEvent incompatible with DOM events w3c/web-based-payment-handler#119, by @marcoscaceres.
-
Should `modifiers` be passed to the payment handler? w3c/web-based-payment-handler#118, by @rsolomakhin.
-
Support for Abort() being delegated to Payment Handler w3c/web-based-payment-handler#117, by @mattsaxon.
-
Relation between merchant order of payment methods and payment app order of instruments w3c/web-based-payment-handler#116, by @ianbjacobs.
-
Open Window Algorithm w3c/web-based-payment-handler#115, by @tommythorsen.
-
`appRequest` attribute should not be a dictionary w3c/web-based-payment-handler#111, by @rsolomakhin.
-
Renaming PaymentApp* classes w3c/web-based-payment-handler#109, by @tommythorsen.
-
-
7 issues closed.
-
Should `modifiers` be passed to the payment handler? w3c/web-based-payment-handler#118.
-
Revisiting payment app filtering w3c/web-based-payment-handler#96.
-
Use PaymentRequest and PaymentResponse w3c/web-based-payment-handler#99.
-
Need to specify behavior for Clients.openWindow w3c/web-based-payment-handler#73.
-
Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete() w3c/web-based-payment-handler#95.
-
How can we optimize user experience when there is only one match? w3c/web-based-payment-handler#14.
-
How does the payee provide information about recommended payment apps? w3c/web-based-payment-handler#79.
-
-
18 issues received 68 new comments.
-
Add explicit permission call to allow payment app to handle payments w3c/web-based-payment-handler#94 (13 comments by @adrianhopebailie, @dlongley, @ianbjacobs, @marcoscaceres)
-
`appRequest` attribute should not be a dictionary w3c/web-based-payment-handler#111 (10 comments by @adamroach, @marcoscaceres)
-
Why does a Payment App need to see the line items? w3c/web-based-payment-handler#91 (10 comments by @adrianhopebailie, @frank-hoffmann, @ianbjacobs, @marcoscaceres, @msporny, @zkoch)
-
Renaming PaymentApp* classes w3c/web-based-payment-handler#109 (8 comments by @adamroach, @adrianhopebailie, @ianbjacobs, @pjbazin, @rsolomakhin, @tommythorsen)
-
Origin should include iframe(s) w3c/web-based-payment-handler#120 (7 comments by @dlongley, @frank-hoffmann, @marcoscaceres, @rsolomakhin)
-
Different approaches to opening windows w3c/web-based-payment-handler#97 (4 comments by @dlongley, @marcoscaceres, @tommythorsen)
-
Should `modifiers` be passed to the payment handler? w3c/web-based-payment-handler#118 (2 comments by @rsolomakhin)
-
Support for Abort() being delegated to Payment Handler w3c/web-based-payment-handler#117 (2 comments by @mattsaxon, @rsolomakhin)
-
Use PaymentRequest and PaymentResponse w3c/web-based-payment-handler#99 (2 comments by @adamroach, @ianbjacobs)
-
What is a Payment App? w3c/web-based-payment-handler#105 (2 comments by @adrianhopebailie, @tommythorsen)
-
Need to specify behavior for Clients.openWindow w3c/web-based-payment-handler#73 (1 comment by @ianbjacobs)
-
Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete() w3c/web-based-payment-handler#95 (1 comment by @ianbjacobs)
-
How can we optimize user experience when there is only one match? w3c/web-based-payment-handler#14 (1 comment by @ianbjacobs)
-
How does the payee provide information about recommended payment apps? w3c/web-based-payment-handler#79 (1 comment by @ianbjacobs)
-
-
8 pull requests opened.
-
The instrumnets/wallets attributes should be readonly and [SameObject]. w3c/web-based-payment-handler#121, by @romandev.
-
Small fixes w3c/web-based-payment-handler#114, by @ianbjacobs.
-
Updates for F2F meeting w3c/web-based-payment-handler#113, by @adamroach.
-
Merging from main branch w3c/web-based-payment-handler#112, by @adamroach.
-
Per 16 March teleconf [1], displayItems are not handed to the payment app w3c/web-based-payment-handler#110, by @ianbjacobs.
-
Run the spec through HTML5-Tidy. w3c/web-based-payment-handler#108, by @tommythorsen.
-
Structural changes based on task force discussion w3c/web-based-payment-handler#107, by @ianbjacobs.
-
Change from clients.openWindow to event.openWindow. w3c/web-based-payment-handler#106, by @tommythorsen.
-
-
6 pull requests merged.
-
Change from clients.openWindow to event.openWindow. w3c/web-based-payment-handler#106.
-
Small fixes w3c/web-based-payment-handler#114.
-
Per 16 March teleconf [1], displayItems are not handed to the payment app w3c/web-based-payment-handler#110.
-
Updates for F2F meeting w3c/web-based-payment-handler#113.
-
Run the spec through HTML5-Tidy. w3c/web-based-payment-handler#108.
-
Structural changes based on task force discussion w3c/web-based-payment-handler#107.
-
-
1 pull request closed.
-
Merging from main branch w3c/web-based-payment-handler#112.
-
-
4 pull requests received 81 new comments.
-
Change from clients.openWindow to event.openWindow. w3c/web-based-payment-handler#106 (71 comments by @adrianhopebailie, @dlongley, @ianbjacobs, @marcoscaceres, @sideshowbarker, @tommythorsen)
-
Proposed changes for #95 (and #96) w3c/web-based-payment-handler#104 (5 comments by @adrianhopebailie, @dlongley, @ianbjacobs, @tommythorsen)
-
Structural changes based on task force discussion w3c/web-based-payment-handler#107 (3 comments by @ianbjacobs, @marcoscaceres)
-
w3c/payment-method-id
-
3 issues opened.
-
Check what happens if URL parsing throws.... w3c/payment-method-id#27, by @marcos-travel.
-
Link to registry of W3C-published short strings w3c/payment-method-id#26, by @ianbjacobs.
-
Add marcoscaceres as collaborator w3c/payment-method-id#24, by @marcoscaceres.
-
-
1 issue closed.
-
Add marcoscaceres as collaborator w3c/payment-method-id#24.
-
-
2 issues received 2 new comments.
-
1 pull request opened.
-
chore: tidy w3c/payment-method-id#25, by @marcoscaceres.
-
-
1 pull request merged.
-
chore: tidy w3c/payment-method-id#25.
-
TR publications
-
1 document published.
-
Payment Method Identifiers published as a Working Draft. History of Payment Method Identifiers
-
Participants
-
1 participant joined.
-
Michel Weksler (Airbnb Inc) joined.
-
-
2 organizations joined.
-
Telenor joined.
-
International Forecourt Standards Forum joined.
-
GitHub
w3c/web-based-payment-handler
-
3 issues opened.
-
What is a Payment App? w3c/web-based-payment-handler#105, by @tommythorsen.
-
Don't send display items to payment handler w3c/web-based-payment-handler#103, by @marcoscaceres.
-
Recovery of a failed Push Payment w3c/web-based-payment-handler#102, by @conorbot.
-
-
6 issues closed.
-
Don't send display items to payment handler w3c/web-based-payment-handler#103.
-
Example 3 does not work w3c/web-based-payment-handler#82.
-
Payment app identifier to manifest filename mapping w3c/web-based-payment-handler#48.
-
Clarification on Payment App "Options" w3c/web-based-payment-handler#90.
-
payment-manifest.json and canHandle function w3c/web-based-payment-handler#83.
-
Recovery of a failed Push Payment w3c/web-based-payment-handler#102.
-
-
1 issue reopened.
-
Why does a Payment App need to see the line items? w3c/web-based-payment-handler#91, by @marcoscaceres.
-
-
15 issues received 103 new comments.
-
Multiple payment apps per origin w3c/web-based-payment-handler#98 (38 comments by @adamroach, @adrianhopebailie, @dlongley, @ianbjacobs, @jakearchibald, @marcoscaceres, @tommythorsen)
-
Revisiting payment app filtering w3c/web-based-payment-handler#96 (16 comments by @adamroach, @adrianhopebailie, @ianbjacobs, @marcoscaceres, @nickjshearer, @rsolomakhin, @tommythorsen)
-
What is a Payment App? w3c/web-based-payment-handler#105 (15 comments by @adrianhopebailie, @delapuente, @dlongley, @ianbjacobs, @tommythorsen)
-
Why does a Payment App need to see the line items? w3c/web-based-payment-handler#91 (7 comments by @adrianhopebailie, @ianbjacobs, @marcoscaceres, @msporny)
-
Payment app identifier to manifest filename mapping w3c/web-based-payment-handler#48 (6 comments by @ianbjacobs, @marcoscaceres, @tommythorsen)
-
Use PaymentRequest and PaymentResponse w3c/web-based-payment-handler#99 (5 comments by @adamroach, @adrianhopebailie, @ianbjacobs, @marcoscaceres)
-
Recommended payment apps w3c/web-based-payment-handler#74 (3 comments by @ianbjacobs, @marcoscaceres, @tommythorsen)
-
Different approaches to opening windows w3c/web-based-payment-handler#97 (3 comments by @ianbjacobs, @marcoscaceres)
-
Recovery of a failed Push Payment w3c/web-based-payment-handler#102 (2 comments by @conorbot, @tommythorsen)
-
Don't send display items to payment handler w3c/web-based-payment-handler#103 (1 comment by @marcoscaceres)
-
Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete() w3c/web-based-payment-handler#95 (1 comment by @ianbjacobs)
-
Need to specify behavior for Clients.openWindow w3c/web-based-payment-handler#73 (1 comment by @ianbjacobs)
-
payment-manifest.json and canHandle function w3c/web-based-payment-handler#83 (1 comment by @ianbjacobs)
-
-
2 pull requests opened.
-
Proposed changes for #95 (and #96) w3c/web-based-payment-handler#104, by @adamroach.
-
Simplify Example 3 as per issue #82 w3c/web-based-payment-handler#101, by @tommythorsen.
-
-
2 pull requests merged.
-
Proposed changes for #95 (and #96) w3c/web-based-payment-handler#104.
-
Simplify Example 3 as per issue #82 w3c/web-based-payment-handler#101.
-
-
1 pull request received 7 new comments.
-
Proposed changes for #95 (and #96) w3c/web-based-payment-handler#104 (7 comments by @adamroach, @bentian, @tommythorsen)
-
w3c/webpayments
-
3 issues opened.
-
[Tokenized Card Payment] TokenCardRequest should inherit from BasicCardRequest w3c/webpayments#212, by @nickjshearer.
-
[Tokenized Card Payment] Replace usage of 'last4' with 'suffix' w3c/webpayments#211, by @nickjshearer.
-
European market - Security concerns w3c/webpayments#210, by @Abacaxi-Nelson.
-
-
1 issue closed.
-
[Tokenized Card Payment] TokenCardRequest should inherit from BasicCardRequest w3c/webpayments#212.
-
-
3 issues received 18 new comments.
-
European market - Security concerns w3c/webpayments#210 (8 comments by @Abacaxi-Nelson, @adamroach, @adrianhopebailie, @cyberphone, @ianbjacobs, @marcoscaceres)
-
[Tokenized Card Payment] Replace usage of 'last4' with 'suffix' w3c/webpayments#211 (7 comments by @adrianhopebailie, @doodi-v1, @ianbjacobs, @kphfb, @nickjshearer)
-
[Tokenized Card Payment] TokenCardRequest should inherit from BasicCardRequest w3c/webpayments#212 (3 comments by @ianbjacobs, @kphfb, @webpayments)
-
-
2 pull requests opened.
-
Editorial adjustments w3c/webpayments#214, by @ianbjacobs.
-
Update to tokenized card spec to include more examples and additional… w3c/webpayments#213, by @kphfb.
-
-
2 pull requests merged.
-
Editorial adjustments w3c/webpayments#214.
-
Update to tokenized card spec to include more examples and additional… w3c/webpayments#213.
-
-
1 pull request received 2 new comments.
-
Update to tokenized card spec to include more examples and additional… w3c/webpayments#213 (2 comments by @ianbjacobs, @webpayments)
-
w3c/payment-request
-
16 issues opened.
-
Addition of flag on PaymentMethodData to indicate that line items should be shared with apps w3c/payment-request#446, by @adrianhopebailie.
-
Fix markup errors that broke autopublishing w3c/payment-request#444, by @sideshowbarker.
-
PaymentResponse attributes should be separate sections w3c/payment-request#442, by @marcoscaceres.
-
markup issues w3c/payment-request#441, by @marcoscaceres.
-
Authors are not conformance classes w3c/payment-request#440, by @marcoscaceres.
-
RFC2119 keywords in informative sections w3c/payment-request#439, by @marcoscaceres.
-
Web page and developer w3c/payment-request#437, by @marcoscaceres.
-
Initial values for internal slots w3c/payment-request#436, by @marcoscaceres.
-
`country` vs `sortingCode` w3c/payment-request#434, by @agektmr.
-
"Shown" should be "presented" in prose w3c/payment-request#428, by @marcoscaceres.
-
Group payment dictionaries into a section w3c/payment-request#427, by @marcoscaceres.
-
Spec talks about dictionary fields instead of dictionary members w3c/payment-request#424, by @marcoscaceres.
-
It is never stated how the payment request ID is used w3c/payment-request#415, by @domenic.
-
paymentRequestID is spelled wrong :( w3c/payment-request#414, by @domenic.
-
PaymentRequestID initialization w3c/payment-request#412, by @rvm4.
-
Introduction is aspirational, but misleading w3c/payment-request#410, by @marcoscaceres.
-
-
20 issues closed.
-
Making this API work with HTML Forms w3c/payment-request#330.
-
firing an event is not done correctly w3c/payment-request#401.
-
`country` vs `sortingCode` w3c/payment-request#434.
-
Is 'currencySystem' required? w3c/payment-request#408.
-
Drop redundant reference to secure context + other redefinitions w3c/payment-request#399.
-
Collect Privacy and Security considerations w3c/payment-request#331.
-
What is the mechanism for limiting repeated calls to canMakePayments ? w3c/payment-request#367.
-
How are currency systems expected to be implemented in practice? w3c/payment-request#343.
-
Throwing exceptions rather than permitting broken usage w3c/payment-request#275.
-
Editorial: define and link to the different states w3c/payment-request#376.
-
Editorial: Add missing xrefs to various specs w3c/payment-request#400.
-
Editorial: don't capitalize RFC 2119 terms w3c/payment-request#377.
-
PaymentAddress should be a dictionary w3c/payment-request#299.
-
Dynamic Currency Conversion requirements w3c/payment-request#289.
-
PaymentOptions seems overly verbose/overlaps with HTML w3c/payment-request#326.
-
Response/Request semantics and cancellation w3c/payment-request#298.
-
What is the shippingAddress/shippingOption of a PaymentResponse if requestShipping was false? w3c/payment-request#352.
-
paymentRequestID is spelled wrong :( w3c/payment-request#414.
-
Why is the "shippingType" member of PaymentOptions not a PaymentShippingType? w3c/payment-request#337.
-
Introduction is aspirational, but misleading w3c/payment-request#410.
-
-
1 issue reopened.
-
PaymentAddress should be a dictionary w3c/payment-request#299, by @adrianhopebailie.
-
-
23 issues received 43 new comments.
-
PaymentAddress should be a dictionary w3c/payment-request#299 (8 comments by @adrianhopebailie, @dlongley, @ianbjacobs, @marcoscaceres, @msporny, @tommythorsen, @zcorpan)
-
Add dir/lang member on dictionaries whose content is displayed in browser UI w3c/payment-request#327 (3 comments by @aphillips, @marcoscaceres)
-
`country` vs `sortingCode` w3c/payment-request#434 (3 comments by @agektmr, @marcoscaceres, @rsolomakhin)
-
Fix markup errors that broke autopublishing w3c/payment-request#444 (2 comments by @ianbjacobs, @marcoscaceres)
-
What is the mechanism for limiting repeated calls to canMakePayments ? w3c/payment-request#367 (2 comments by @ianbjacobs, @marcoscaceres)
-
Throwing exceptions rather than permitting broken usage w3c/payment-request#275 (2 comments by @marcoscaceres)
-
updateWith will silently ignore data in hard-to-debug ways w3c/payment-request#350 (2 comments by @domenic, @marcoscaceres)
-
How are digital signatures supported for Payment Requests? w3c/payment-request#291 (1 comment by @cyberphone)
-
PaymentRequest does not handle the case of store pickup w3c/payment-request#389 (1 comment by @marcoscaceres)
-
How are currency systems expected to be implemented in practice? w3c/payment-request#343 (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)
-
PaymentOptions seems overly verbose/overlaps with HTML w3c/payment-request#326 (1 comment by @marcoscaceres)
-
Why is the "shippingType" member of PaymentOptions not a PaymentShippingType? w3c/payment-request#337 (1 comment by @zkoch)
-
-
21 pull requests opened.
-
Create pr-preview config file. w3c/payment-request#445, by @tobie.
-
editorial: s/fields/members + xref fixes (closes #424) w3c/payment-request#443, by @marcoscaceres.
-
editorial: attr/method intros are notes (closes #379) w3c/payment-request#438, by @marcoscaceres.
-
editorial: s/shown/presented (closes #428) w3c/payment-request#435, by @marcoscaceres.
-
Editorial: firing event not done correctly (closes #401) w3c/payment-request#433, by @marcoscaceres.
-
fix: s/user interaction/transaction (closes #402) w3c/payment-request#432, by @marcoscaceres.
-
editorial: IDL dictates what is/isn't required (closes #408) w3c/payment-request#431, by @marcoscaceres.
-
editorial: don't redefine WebIDL things (closes #399) w3c/payment-request#430, by @marcoscaceres.
-
editorial: dfn payment request states as strings (closes #376) w3c/payment-request#429, by @marcoscaceres.
-
feat: put request id in details dictionary w3c/payment-request#426, by @rvm4.
-
fix: delegate total and error member checks to WebIDL w3c/payment-request#425, by @marcoscaceres.
-
editorial: fix linking to various specs w3c/payment-request#423, by @marcoscaceres.
-
Editorial fixes and xrefs w3c/payment-request#422, by @marcoscaceres.
-
editorial: s/character/code unit/ (closes #322) w3c/payment-request#421, by @marcoscaceres.
-
Define payment option filtering algorithm. w3c/payment-request#420, by @rsolomakhin.
-
BREAKING CHANGE: s/paymentRequestID/paymentRequestId (closes #414) w3c/payment-request#419, by @marcoscaceres.
-
Make updateWith() return a promise signaling any update failures w3c/payment-request#418, by @domenic.
-
Set all the attributes of PaymentResponse when creating it w3c/payment-request#417, by @domenic.
-
Update the shippingType option to not allow invalid strings w3c/payment-request#416, by @domenic.
-
Take paymentRequestID in constructor w3c/payment-request#413, by @rvm4.
-
editorial(intro): drop hyperbolic statements (closes #410) w3c/payment-request#411, by @marcoscaceres.
-
-
10 pull requests merged.
-
Editorial: firing event not done correctly (closes #401) w3c/payment-request#433.
-
editorial: IDL dictates what is/isn't required (closes #408) w3c/payment-request#431.
-
editorial: don't redefine WebIDL things (closes #399) w3c/payment-request#430.
-
editorial: dfn payment request states as strings (closes #376) w3c/payment-request#429.
-
editorial: fix linking to various specs w3c/payment-request#423.
-
Editorial fixes and xrefs w3c/payment-request#422.
-
Set all the attributes of PaymentResponse when creating it w3c/payment-request#417.
-
BREAKING CHANGE: s/paymentRequestID/paymentRequestId (closes #414) w3c/payment-request#419.
-
Update the shippingType option to not allow invalid strings w3c/payment-request#416.
-
editorial(intro): drop hyperbolic statements (closes #410) w3c/payment-request#411.
-
-
2 pull requests closed.
-
Take paymentRequestID in constructor w3c/payment-request#413.
-
editorial: s/character/code unit/ (closes #322) w3c/payment-request#421.
-
-
14 pull requests received 125 new comments.
-
feat: put request id in details dictionary w3c/payment-request#426 (29 comments by @domenic, @marcoscaceres, @rsolomakhin)
-
Take paymentRequestID in constructor w3c/payment-request#413 (23 comments by @domenic, @marcoscaceres, @rsolomakhin, @rvm4, @zkoch)
-
fix: delegate total and error member checks to WebIDL w3c/payment-request#425 (21 comments by @bentian, @domenic, @marcoscaceres)
-
Make updateWith() return a promise signaling any update failures w3c/payment-request#418 (13 comments by @domenic, @marcoscaceres, @mollyd16, @rsolomakhin, @zcorpan)
-
editorial: attr/method intros are notes (closes #379) w3c/payment-request#438 (10 comments by @adrianhopebailie, @domenic, @marcoscaceres)
-
Define payment option filtering algorithm. w3c/payment-request#420 (8 comments by @adamroach, @domenic, @ianbjacobs, @rsolomakhin)
-
editorial: s/character/code unit/ (closes #322) w3c/payment-request#421 (7 comments by @domenic, @marcoscaceres, @zcorpan)
-
editorial: IDL dictates what is/isn't required (closes #408) w3c/payment-request#431 (4 comments by @ianbjacobs, @marcoscaceres)
-
editorial: fix linking to various specs w3c/payment-request#423 (2 comments by @domenic, @marcoscaceres)
-
editorial: s/fields/members + xref fixes (closes #424) w3c/payment-request#443 (1 comment by @marcoscaceres)
-
Editorial: firing event not done correctly (closes #401) w3c/payment-request#433 (1 comment by @marcoscaceres)
-
editorial: dfn payment request states as strings (closes #376) w3c/payment-request#429 (1 comment by @marcoscaceres)
-
BREAKING CHANGE: s/paymentRequestID/paymentRequestId (closes #414) w3c/payment-request#419 (1 comment by @zcorpan)
-
w3c/payment-method-id
-
2 issues opened.
-
Payment Method Identifier needs dfn w3c/payment-method-id#23, by @marcoscaceres.
-
Circular dependency between PMI and PR specs w3c/payment-method-id#22, by @adrianhopebailie.
-
-
2 issues closed.
-
Support for PMI's with schemes other than https? w3c/payment-method-id#17.
-
How should we address payment method manifest files? w3c/payment-method-id#19.
-
-
4 issues received 5 new comments.
-
Support for PMI's with schemes other than https? w3c/payment-method-id#17 (1 comment by @ianbjacobs)
-
How should we address payment method manifest files? w3c/payment-method-id#19 (1 comment by @ianbjacobs)
-
1 pull request merged.
-
Changes to address Action #40 w3c/payment-method-id#21.
-
-
2 pull requests closed.
-
update pmi spec with apen and proprietary payment method identifiers w3c/payment-method-id#10.
-
slight rewording w3c/payment-method-id#6.
-
-
3 pull requests received 7 new comments.
-
Changes to address Action #40 w3c/payment-method-id#21 (5 comments by @adrianhopebailie, @ianbjacobs)
-
update pmi spec with apen and proprietary payment method identifiers w3c/payment-method-id#10 (1 comment by @adrianhopebailie)
-
TR publications
-
3 documents published.
-
Basic Card Payment published as a Working Draft. History of Basic Card Payment
-
Payment Request API published twice as a Working Draft. History of Payment Request API
-
Participants
-
1 participant left.
-
Doug Schepers (W3C) left.
-
-
1 organization joined.
-
BarrierBreak Solutions Private Limited joined.
-
GitHub
w3c/web-based-payment-handler
-
13 issues opened.
-
Use PaymentRequest and PaymentResponse w3c/web-based-payment-handler#99, by @marcoscaceres.
-
Multiple payment apps per origin w3c/web-based-payment-handler#98, by @adamroach.
-
Different approaches to opening windows w3c/web-based-payment-handler#97, by @adamroach.
-
Revisiting payment app filtering w3c/web-based-payment-handler#96, by @adamroach.
-
Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete() w3c/web-based-payment-handler#95, by @adamroach.
-
Add explicit permission call to allow payment app to handle payments w3c/web-based-payment-handler#94, by @adamroach.
-
Payment App Decline w3c/web-based-payment-handler#92, by @rvm4.
-
Why does a Payment App need to see the line items? w3c/web-based-payment-handler#91, by @zkoch.
-
Clarification on Payment App "Options" w3c/web-based-payment-handler#90, by @zkoch.
-
payment-manifest.json and canHandle function w3c/web-based-payment-handler#83, by @conorbot.
-
Example 3 does not work w3c/web-based-payment-handler#82, by @tommythorsen.
-
We need a PaymentAppResponseData dictionary w3c/web-based-payment-handler#81, by @tommythorsen.
-
How does the payee provide information about recommended payment apps? w3c/web-based-payment-handler#79, by @ianbjacobs.
-
-
8 issues closed.
-
Payment App Decline w3c/web-based-payment-handler#92.
-
We need a PaymentAppResponseData dictionary w3c/web-based-payment-handler#81.
-
What is matching and display behavior for various scenarios of recommended apps, enabled apps, non-enabled apps, etc.? w3c/web-based-payment-handler#38.
-
Should we allow payment providers to issue queries about their installed payment apps (match on origin) w3c/web-based-payment-handler#6.
-
Versioning w3c/web-based-payment-handler#45.
-
Section 6 steps 1-5 seem to avoid selecting a payment option / payment method w3c/web-based-payment-handler#56.
-
Split out enabled and supported methods w3c/web-based-payment-handler#7.
-
Should payment apps implement payment method-specific filters? w3c/web-based-payment-handler#63.
-
-
22 issues received 244 new comments.
-
Revisiting payment app filtering w3c/web-based-payment-handler#96 (47 comments by @adamroach, @adrianhopebailie, @ianbjacobs, @jakearchibald, @marcoscaceres, @rsolomakhin, @tommythorsen)
-
Payment app identifier to manifest filename mapping w3c/web-based-payment-handler#48 (43 comments by @adamroach, @adrianhopebailie, @dlongley, @ianbjacobs, @jakearchibald, @msporny, @rsolomakhin, @tommythorsen)
-
Multiple payment apps per origin w3c/web-based-payment-handler#98 (39 comments by @adamroach, @adrianhopebailie, @conorbot, @delapuente, @dlongley, @ianbjacobs, @jakearchibald, @marcoscaceres, @tommythorsen)
-
Use PaymentRequest and PaymentResponse w3c/web-based-payment-handler#99 (26 comments by @adamroach, @adrianhopebailie, @delapuente, @dlongley, @ianbjacobs, @marcoscaceres, @zkoch)
-
Payment App Decline w3c/web-based-payment-handler#92 (22 comments by @dlongley, @ianbjacobs, @marcoscaceres, @rsolomakhin, @rvm4, @tommythorsen)
-
Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete() w3c/web-based-payment-handler#95 (22 comments by @adamroach, @adrianhopebailie, @ianbjacobs, @jakearchibald, @madmath, @marcoscaceres, @tommythorsen)
-
Need to specify behavior for Clients.openWindow w3c/web-based-payment-handler#73 (9 comments by @ianbjacobs, @jenan-stripe, @marcoscaceres, @tommythorsen)
-
Example 3 does not work w3c/web-based-payment-handler#82 (6 comments by @adamroach, @dlongley, @marcoscaceres, @rsolomakhin, @tommythorsen)
-
Different approaches to opening windows w3c/web-based-payment-handler#97 (6 comments by @adamroach, @dlongley, @jakearchibald, @marcoscaceres)
-
payment-manifest.json and canHandle function w3c/web-based-payment-handler#83 (5 comments by @adamroach, @conorbot, @ianbjacobs, @rsolomakhin)
-
We need a PaymentAppResponseData dictionary w3c/web-based-payment-handler#81 (4 comments by @ianbjacobs, @tommythorsen)
-
Add explicit permission call to allow payment app to handle payments w3c/web-based-payment-handler#94 (3 comments by @jakearchibald, @marcoscaceres)
-
Clarification on Payment App "Options" w3c/web-based-payment-handler#90 (2 comments by @ianbjacobs, @zkoch)
-
How does the payee provide information about recommended payment apps? w3c/web-based-payment-handler#79 (2 comments by @ianbjacobs)
-
Why does a Payment App need to see the line items? w3c/web-based-payment-handler#91 (1 comment by @ianbjacobs)
-
What is matching and display behavior for various scenarios of recommended apps, enabled apps, non-enabled apps, etc.? w3c/web-based-payment-handler#38 (1 comment by @ianbjacobs)
-
Should we allow payment providers to issue queries about their installed payment apps (match on origin) w3c/web-based-payment-handler#6 (1 comment by @ianbjacobs)
-
Section 6 steps 1-5 seem to avoid selecting a payment option / payment method w3c/web-based-payment-handler#56 (1 comment by @ianbjacobs)
-
Should payment apps implement payment method-specific filters? w3c/web-based-payment-handler#63 (1 comment by @ianbjacobs)
-
-
9 pull requests opened.
-
Add sentence on display of payment app origin w3c/web-based-payment-handler#100, by @ianbjacobs.
-
* updates around payment app registration, more clarity wrt user cons… w3c/web-based-payment-handler#93, by @ianbjacobs.
-
Updates around display of windows w3c/web-based-payment-handler#89, by @ianbjacobs.
-
Small fixes + displayItems w3c/web-based-payment-handler#88, by @ianbjacobs.
-
Security note adjustment w3c/web-based-payment-handler#87, by @ianbjacobs.
-
security note moved w3c/web-based-payment-handler#86, by @ianbjacobs.
-
Move secure context note from intro to where the requirement is listed. w3c/web-based-payment-handler#85, by @ianbjacobs.
-
Introduce the PaymentAppResponseData dictionary w3c/web-based-payment-handler#84, by @tommythorsen.
-
Edits based on recent discussions and decisions w3c/web-based-payment-handler#80, by @ianbjacobs.
-
-
9 pull requests merged.
-
Add sentence on display of payment app origin w3c/web-based-payment-handler#100.
-
* updates around payment app registration, more clarity wrt user cons… w3c/web-based-payment-handler#93.
-
Updates around display of windows w3c/web-based-payment-handler#89.
-
Small fixes + displayItems w3c/web-based-payment-handler#88.
-
Introduce the PaymentAppResponseData dictionary w3c/web-based-payment-handler#84.
-
Security note adjustment w3c/web-based-payment-handler#87.
-
Edits based on recent discussions and decisions w3c/web-based-payment-handler#80.
-
(Deleted this edit by mistake before merged) w3c/web-based-payment-handler#78.
-
Lambda functions for app matching w3c/web-based-payment-handler#76.
-
-
2 pull requests closed.
-
Move secure context note from intro to where the requirement is listed. w3c/web-based-payment-handler#85.
-
security note moved w3c/web-based-payment-handler#86.
-
-
1 pull request reopened.
-
Move secure context note from intro to where the requirement is listed. w3c/web-based-payment-handler#85, by @ianbjacobs.
-
-
3 pull requests received 6 new comments.
-
Introduce the PaymentAppResponseData dictionary w3c/web-based-payment-handler#84 (3 comments by @dlongley, @ianbjacobs, @tommythorsen)
-
Small fixes + displayItems w3c/web-based-payment-handler#88 (2 comments by @adrianhopebailie, @ianbjacobs)
-
Edits based on recent discussions and decisions w3c/web-based-payment-handler#80 (1 comment by @ianbjacobs)
-
w3c/payment-request
-
11 issues opened.
-
Is 'currencySystem' required? w3c/payment-request#408, by @rsolomakhin.
-
canMakePayment() might be in the wrong place? w3c/payment-request#403, by @marcoscaceres.
-
`PaymentInstrument.complete(result)` wording w3c/payment-request#402, by @rsolomakhin.
-
firing an event is not done correctly w3c/payment-request#401, by @domenic.
-
Editorial: Add missing xrefs to various specs w3c/payment-request#400, by @marcoscaceres.
-
Drop redundant reference to secure context + other redefinitions w3c/payment-request#399, by @marcoscaceres.
-
[WebIDL] reference is wrong w3c/payment-request#394, by @domenic.
-
Internal slots vs. attributes w3c/payment-request#393, by @tommythorsen.
-
Phone number format w3c/payment-request#390, by @rsolomakhin.
-
PaymentRequest does not handle the case of store pickup w3c/payment-request#389, by @sanjoypal.
-
Providing/Generating paymentRequestID during construction w3c/payment-request#388, by @sanjoypal.
-
-
24 issues closed.
-
Is section 3.4 informative or normative? w3c/payment-request#342.
-
The myth of JSON-serializable object w3c/payment-request#307.
-
The "data" member of PaymentDetailsModifier doesn't seem to be used for anything w3c/payment-request#346.
-
waitForUpdate is not defined w3c/payment-request#371.
-
Setting internal slots of objects from asynchronous steps is not OK w3c/payment-request#339.
-
The shipping address/option changed algorithms should not be synchronously poking internal slots w3c/payment-request#351.
-
canMakePayment() might be in the wrong place? w3c/payment-request#403.
-
Phone number format w3c/payment-request#390.
-
Editorial: use new language for DOMExceptions w3c/payment-request#375.
-
DOMExceptions are now in WebIDL w3c/payment-request#314.
-
Internal slots vs. attributes w3c/payment-request#393.
-
[WebIDL] reference is wrong w3c/payment-request#394.
-
Security hole in payment API when a constructor from a no longer active document is invoked w3c/payment-request#361.
-
The "data" member of PaymentMethodData doesn't seem to actually be used for anything w3c/payment-request#338.
-
Ambiguous conformance requirement in constructor w3c/payment-request#354.
-
Serializer behavior w3c/payment-request#385.
-
Examples in the spec w3c/payment-request#274.
-
"contains a value for" isn't defined for dictionaries w3c/payment-request#321.
-
A `PaymentItem` can't be a "valid decimal monetary value" w3c/payment-request#334.
-
A PaymentDetailsModifier may not have an additionalDisplayItems value present w3c/payment-request#335.
-
PaymentRequest constructor validation ordering does not match Blink at all w3c/payment-request#373.
-
-
1 issue reopened.
-
The myth of JSON-serializable object w3c/payment-request#307, by @zkoch.
-
-
20 issues received 59 new comments.
-
[WebIDL] reference is wrong w3c/payment-request#394 (11 comments by @domenic, @marcoscaceres, @tobie)
-
Providing/Generating paymentRequestID during construction w3c/payment-request#388 (7 comments by @ianbjacobs, @marcoscaceres, @rsolomakhin)
-
Phone number format w3c/payment-request#390 (5 comments by @ianbjacobs, @marcoscaceres, @nickjshearer, @rsolomakhin)
-
Is 'currencySystem' required? w3c/payment-request#408 (4 comments by @ianbjacobs, @marcoscaceres, @romandev, @tommythorsen)
-
canMakePayment() might be in the wrong place? w3c/payment-request#403 (4 comments by @domenic, @marcoscaceres, @rsolomakhin)
-
Internal slots vs. attributes w3c/payment-request#393 (4 comments by @domenic, @marcoscaceres, @tommythorsen)
-
Editorial: don't capitalize RFC 2119 terms w3c/payment-request#377 (3 comments by @domenic, @marcoscaceres)
-
PaymentRequest does not handle the case of store pickup w3c/payment-request#389 (3 comments by @ianbjacobs, @rsolomakhin)
-
Why is the "shippingType" member of PaymentOptions not a PaymentShippingType? w3c/payment-request#337 (2 comments by @domenic, @ianbjacobs)
-
The "data" member of PaymentDetailsModifier doesn't seem to be used for anything w3c/payment-request#346 (2 comments by @domenic, @rsolomakhin)
-
"contains a value for" isn't defined for dictionaries w3c/payment-request#321 (2 comments by @domenic, @sideshowbarker)
-
Need to define the interaction of payment API with navigation and browsing context destruction w3c/payment-request#360 (1 comment by @domenic)
-
Drop redundant reference to secure context + other redefinitions w3c/payment-request#399 (1 comment by @domenic)
-
Editorial: refer to methods with parentheses for clarity, and spell out their params in their definition w3c/payment-request#378 (1 comment by @marcoscaceres)
-
-
11 pull requests opened.
-
Add billing shipping type w3c/payment-request#409, by @rvm4.
-
Define [[waitForUpdate]] and make it clear where it lives w3c/payment-request#407, by @domenic.
-
Move state transitions diagram into a note w3c/payment-request#406, by @domenic.
-
Queue tasks to change developer-visible properties w3c/payment-request#405, by @domenic.
-
State how payment details modifier data is serialized and used w3c/payment-request#404, by @domenic.
-
Editorial: refer to methods with parentheses (closes #378) w3c/payment-request#398, by @marcoscaceres.
-
Editorial: use new language for DOMExceptions (close #375) w3c/payment-request#397, by @marcoscaceres.
-
feat(payment resp algo): phone# SHOULD be E.164 (closes #390) w3c/payment-request#396, by @marcoscaceres.
-
Remove confusing IDL comments w3c/payment-request#395, by @marcoscaceres.
-
style(index.html): cleanup markup w3c/payment-request#392, by @marcoscaceres.
-
fix(payment request algo): set attributes to null if not given (closes #385) w3c/payment-request#391, by @marcoscaceres.
-
-
13 pull requests merged.
-
Move state transitions diagram into a note w3c/payment-request#406.
-
State how payment details modifier data is serialized and used w3c/payment-request#404.
-
Define [[waitForUpdate]] and make it clear where it lives w3c/payment-request#407.
-
Queue tasks to change developer-visible properties w3c/payment-request#405.
-
feat(payment resp algo): phone# SHOULD be E.164 (closes #390) w3c/payment-request#396.
-
Editorial: refer to methods with parentheses (closes #378) w3c/payment-request#398.
-
Remove confusing IDL comments w3c/payment-request#395.
-
Editorial: use new language for DOMExceptions (close #375) w3c/payment-request#397.
-
fix(payment request algo): set attributes to null if not given (closes #385) w3c/payment-request#391.
-
style(index.html): cleanup markup w3c/payment-request#392.
-
Invoke "allowed to use" always w3c/payment-request#383.
-
Straighten out the payment method data flow w3c/payment-request#382.
-
Various fixes to the PaymentRequest constructor w3c/payment-request#374.
-
-
2 pull requests closed.
-
an event to providing standards for push payment methods w3c/payment-request#223.
-
Add `enableLegacyCheckout` option to PaymentOptions. w3c/payment-request#365.
-
-
14 pull requests received 69 new comments.
-
Editorial: refer to methods with parentheses (closes #378) w3c/payment-request#398 (23 comments by @domenic, @marcoscaceres)
-
Add billing shipping type w3c/payment-request#409 (10 comments by @dlongley, @domenic, @ianbjacobs, @marcoscaceres, @rsolomakhin, @rvm4)
-
Straighten out the payment method data flow w3c/payment-request#382 (8 comments by @adrianba, @domenic, @marcoscaceres)
-
Move state transitions diagram into a note w3c/payment-request#406 (4 comments by @domenic, @marcoscaceres)
-
Queue tasks to change developer-visible properties w3c/payment-request#405 (4 comments by @domenic, @marcoscaceres)
-
Editorial: use new language for DOMExceptions (close #375) w3c/payment-request#397 (4 comments by @marcoscaceres)
-
fix(payment request algo): set attributes to null if not given (closes #385) w3c/payment-request#391 (3 comments by @domenic, @marcoscaceres)
-
State how payment details modifier data is serialized and used w3c/payment-request#404 (2 comments by @marcoscaceres)
-
feat(payment resp algo): phone# SHOULD be E.164 (closes #390) w3c/payment-request#396 (2 comments by @marcoscaceres, @rsolomakhin)
-
an event to providing standards for push payment methods w3c/payment-request#223 (1 comment by @marcoscaceres)
-
Add `enableLegacyCheckout` option to PaymentOptions. w3c/payment-request#365 (1 comment by @marcoscaceres)
-
w3c/payment-method-id
-
1 issue opened.
-
Why are payment ids restricted to [a-z0-9]? w3c/payment-method-id#20, by @stevenatkin.
-
-
3 issues received 8 new comments.
-
How should we address payment method manifest files? w3c/payment-method-id#19 (6 comments by @adrianhopebailie, @ianbjacobs, @mnot, @rsolomakhin)
-
-
1 pull request opened.
-
Changes to address Action #40 w3c/payment-method-id#21, by @adrianhopebailie.
-
w3c/webpayments
-
8 pull requests opened.
-
Removed billing address w3c/webpayments#209, by @ianbjacobs.
-
markup fix w3c/webpayments#208, by @ianbjacobs.
-
Mostly editorial based on discussion today. w3c/webpayments#207, by @ianbjacobs.
-
Small fixes w3c/webpayments#206, by @ianbjacobs.
-
new direct debit w3c/webpayments#205, by @ianbjacobs.
-
Updating token card spec to align better with basic card spec and cov… w3c/webpayments#204, by @kphfb.
-
deleted unused section w3c/webpayments#203, by @ianbjacobs.
-
Add section on merchantID w3c/webpayments#202, by @ianbjacobs.
-
-
7 pull requests merged.
-
Removed billing address w3c/webpayments#209.
-
markup fix w3c/webpayments#208.
-
Mostly editorial based on discussion today. w3c/webpayments#207.
-
Updating token card spec to align better with basic card spec and cov… w3c/webpayments#204.
-
Small fixes w3c/webpayments#206.
-
new direct debit w3c/webpayments#205.
-
Add section on merchantID w3c/webpayments#202.
-
-
1 pull request closed.
-
deleted unused section w3c/webpayments#203.
-
-
1 pull request received 2 new comments.
-
Updating token card spec to align better with basic card spec and cov… w3c/webpayments#204 (2 comments by @rvm4)
-