Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / w3c/webpayments-http-api issues and pull requests
#19 - Since no longer used, don't expose
Pull Request -
State: closed - Opened by ianbjacobs almost 2 years ago
#18 - Update spec status for Note publication
Pull Request -
State: closed - Opened by ianbjacobs about 7 years ago
#17 - Changed to NOTE.
Pull Request -
State: closed - Opened by halindrome about 7 years ago
#16 - Figure 1 (and details in section 3)
Issue -
State: open - Opened by halindrome over 8 years ago
#15 - Versioning
Issue -
State: open - Opened by mattsaxon over 8 years ago
#14 - Registration and payment are not tightly coupled
Issue -
State: open - Opened by adrianhopebailie over 8 years ago
#13 - What are the security and privacy implications of the HTTP API?
Issue -
State: open - Opened by msporny over 8 years ago
#12 - Push-based payments should be documented in the HTTP API
Issue -
State: open - Opened by msporny over 8 years ago
#11 - Should getting a PaymentRequest result in an extra round trip?
Issue -
State: open - Opened by msporny over 8 years ago
#10 - What other authentication schemes should be supported for Payment App registration?
Issue -
State: open - Opened by msporny over 8 years ago
#9 - Prefer new 'Payment' header instead of 402 response code?
Issue -
State: open - Opened by msporny over 8 years ago
#8 - What is the appropriate HTTP response code for a failed payment?
Issue -
State: open - Opened by msporny over 8 years ago
#7 - Further clarify the branching options for the payment flow
Issue -
State: open - Opened by msporny over 8 years ago
#6 - Payment App selection process should be in Payment App spec
Issue -
State: open - Opened by msporny over 8 years ago
#5 - Should PaymentRequest be returned via HTTP 402 response code?
Issue -
State: open - Opened by msporny over 8 years ago
- 3 comments
#4 - Overview diagram may be misleading
Issue -
State: open - Opened by msporny over 8 years ago
#3 - HTTP API terminology needs to be refined
Issue -
State: open - Opened by msporny over 8 years ago
#2 - Updates to HTTP API
Pull Request -
State: closed - Opened by adrianhopebailie over 8 years ago
- 1 comment
#1 - Need normative references
Issue -
State: open - Opened by halindrome over 8 years ago