Web Payments Working Group - Activity in 2015
No matches.
Participants
-
1 participant joined.
-
Sam Sugimoto (W3C) joined.
-
-
3 organizations joined.
-
China Mobile Communications Corporation joined.
-
China Mobile Communications Corporation joined.
-
China Mobile Communications Corporation joined.
-
-
2 organizations left.
-
China Mobile Communications Corporation left.
-
China Mobile Communications Corporation left.
-
GitHub
w3c/webpayments
-
26 issues opened.
-
How are third-party native wallets integrated? w3c/webpayments#42, by @cyberphone.
-
Should we expose status change events in the browser API? w3c/webpayments#41, by @msporny.
-
Expression of monetary amounts w3c/webpayments#40, by @msporny.
-
Should a Payment Request API have shipping address APIs? w3c/webpayments#39, by @msporny.
-
Should the payment request contain line item details? w3c/webpayments#38, by @msporny.
-
Should list of accepted payment methods be strings or objects? w3c/webpayments#37, by @msporny.
-
Should a payment request be just data, or a programmable object? w3c/webpayments#36, by @msporny.
-
Is tracking payment request state necessary? w3c/webpayments#35, by @msporny.
-
Confining the definition of user agents to browsers w3c/webpayments#34, by @msporny.
-
Should Payment Method Identifiers and Messages be expressed using a Linked Data Vocabulary? w3c/webpayments#29, by @msporny.
-
What gets registered - apps, wallets, or payment instruments? w3c/webpayments#28, by @msporny.
-
Should we have separate specifications for payment and registration of payment apps? w3c/webpayments#26, by @msporny.
-
Payment Method Identifier Registry should have oversight / formal structure w3c/webpayments#25, by @msporny.
-
Document relationship diagrams? w3c/webpayments#24, by @msporny.
-
Payment Request Architecture glossary should include IG glossary w3c/webpayments#23, by @msporny.
-
Merge Payment Request Architecture with Capabilities Document w3c/webpayments#22, by @msporny.
-
Should we be concerned about the use of the Browser API in a non-HTTPS environment? w3c/webpayments#20, by @msporny.
-
How do organizations layer additional information in the core messages? w3c/webpayments#18, by @msporny.
-
Should we be publishing a specification for an HTTP API? w3c/webpayments#17, by @msporny.
-
How are cloud-based payment apps supported? w3c/webpayments#16, by @msporny.
-
How are payment apps shared between different browser brands? w3c/webpayments#15, by @msporny.
-
How are payment apps registered? w3c/webpayments#14, by @msporny.
-
-
4 issues closed.
-
Confining the definition of user agents to browsers w3c/webpayments#34.
-
Abstract payment architecture w3c/webpayments#11.
-
No proprietary binary files, please w3c/webpayments#7.
-
26 issues received 220 new comments.
-
[Architecture] Payment App is a term used in EMV to describe the applet stored in SC w3c/webpayments#31 (22 comments by @adrianhopebailie, @dlongley, @halindrome, @ianbjacobs, @shepazu, @webpayments)
-
What gets registered - apps, wallets, or payment instruments? w3c/webpayments#28 (17 comments by @adrianhopebailie, @burdges, @dlongley, @msporny, @webpayments)
-
Payment Method Identifier Registry should have oversight / formal structure w3c/webpayments#25 (15 comments by @adrianhopebailie, @dlongley, @halindrome, @ianbjacobs, @webpayments, @zkoch)
-
How are payment apps registered? w3c/webpayments#14 (14 comments by @adrianhopebailie, @dlongley, @ianbjacobs, @mattsaxon, @msporny, @rsolomakhin, @webpayments)
-
Should the payment request contain line item details? w3c/webpayments#38 (13 comments by @adrianhopebailie, @dlongley, @mattsaxon, @mountainhippo, @msporny, @vkuntz, @webpayments, @zkoch)
-
Should a Payment Request API have shipping address APIs? w3c/webpayments#39 (13 comments by @adrianhopebailie, @burdges, @dlongley, @ianbjacobs, @msporny, @zkoch)
-
How are cloud-based payment apps supported? w3c/webpayments#16 (13 comments by @adrianhopebailie, @burdges, @cyberphone, @dlongley, @mattsaxon, @mountainhippo, @msporny, @rsolomakhin)
-
Expression of monetary amounts w3c/webpayments#40 (12 comments by @adrianhopebailie, @davidlehn, @dezell, @dlongley, @mattsaxon, @msporny, @vkuntz)
-
Abstract payment architecture w3c/webpayments#11 (12 comments by @adrianhopebailie, @dlongley, @ianbjacobs, @mattsaxon, @webpayments)
-
How do we ensure that the payment request from the merchant is not tampered with before it gets to the payment app? w3c/webpayments#19 (12 comments by @adrianhopebailie, @burdges, @CYV, @dlongley, @ianbjacobs, @mattsaxon, @mountainhippo, @msporny)
-
Should we expose status change events in the browser API? w3c/webpayments#41 (10 comments by @adrianhopebailie, @dlongley, @msporny, @zkoch)
-
How are payment apps shared between different browser brands? w3c/webpayments#15 (9 comments by @adrianhopebailie, @dlongley, @ianbjacobs, @mattsaxon, @mountainhippo, @msporny)
-
How are third-party native wallets integrated? w3c/webpayments#42 (7 comments by @cyberphone, @rsolomakhin)
-
Should we be concerned about the use of the Browser API in a non-HTTPS environment? w3c/webpayments#20 (7 comments by @adrianhopebailie, @halindrome, @ianbjacobs, @mountielee, @msporny)
-
Should we be publishing a specification for an HTTP API? w3c/webpayments#17 (6 comments by @adrianhopebailie, @dlongley, @mattsaxon, @mountainhippo, @msporny)
-
Should a payment method identifier (URL) resolve to a machine readable resource that describes the payment method? w3c/webpayments#30 (6 comments by @adrianhopebailie, @dlongley, @halindrome, @ianbjacobs, @msporny)
-
How do organizations layer additional information in the core messages? w3c/webpayments#18 (5 comments by @adrianhopebailie, @dlongley, @msporny)
-
Should Payment Method Identifiers and Messages be expressed using a Linked Data Vocabulary? w3c/webpayments#29 (5 comments by @adrianhopebailie, @halindrome, @ianbjacobs, @msporny)
-
Should list of accepted payment methods be strings or objects? w3c/webpayments#37 (4 comments by @adrianhopebailie, @dlongley, @msporny, @webpayments)
-
Payment Request Architecture glossary should include IG glossary w3c/webpayments#23 (4 comments by @halindrome, @ianbjacobs, @msporny)
-
Should a payment request be just data, or a programmable object? w3c/webpayments#36 (3 comments by @burdges, @dlongley, @msporny)
-
Confining the definition of user agents to browsers w3c/webpayments#34 (2 comments by @ianbjacobs, @msporny)
-
Merge Payment Request Architecture with Capabilities Document w3c/webpayments#22 (2 comments by @adrianhopebailie, @ianbjacobs)
-
-
5 pull requests opened.
-
Added Apple Pay w3c/webpayments#44, by @mattsaxon.
-
SDD one off e-mandate w3c/webpayments#43, by @fredMeignien.
-
Refined SEPA Credit Transfer to add the web interactions w3c/webpayments#33, by @mattsaxon.
-
Added PSP Hosted Card Payment w3c/webpayments#32, by @mattsaxon.
-
Uploaded Credit Transfer files for Cyril w3c/webpayments#21, by @mattsaxon.
-
-
5 pull requests merged.
-
Added Apple Pay w3c/webpayments#44.
-
SDD one off e-mandate w3c/webpayments#43.
-
Refined SEPA Credit Transfer to add the web interactions w3c/webpayments#33.
-
Added PSP Hosted Card Payment w3c/webpayments#32.
-
Uploaded Credit Transfer files for Cyril w3c/webpayments#21.
-
-
2 pull requests received 4 new comments.
-
Refined SEPA Credit Transfer to add the web interactions w3c/webpayments#33 (3 comments by @ianbjacobs, @mattsaxon, @webpayments)
-
Participants
-
2 participants joined.
-
Xueyuan Jia (W3C) joined.
-
Natasha Rooney (W3C Invited Experts) joined.
-
-
5 organizations joined.
-
GROUPE BPCE joined.
-
Fundacion CTIC joined.
-
Deque Systems, Inc. joined.
-
Alibaba Group joined.
-
HM Government joined.
-
-
1 organization left.
-
Fundacion CTIC left.
-
GitHub
w3c/webpayments
-
4 issues opened.
-
Abstract payment architecture w3c/webpayments#11, by @msporny.
-
Confusion over payment flow w3c/webpayments#10, by @zkoch.
-
Please enable issues to be reflected on the mailing list w3c/webpayments#9, by @webpayments.
-
No proprietary binary files, please w3c/webpayments#7, by @msporny.
-
-
1 issue closed.
-
Please enable issues to be reflected on the mailing list w3c/webpayments#9.
-
-
4 issues received 49 new comments.
-
Please enable issues to be reflected on the mailing list w3c/webpayments#9 (22 comments by @adrianhopebailie, @halindrome, @msporny, @shepazu, @webpayments)
-
Abstract payment architecture w3c/webpayments#11 (13 comments by @adrianhopebailie, @dlongley, @LaurentCastillo, @mattsaxon, @msporny)
-
No proprietary binary files, please w3c/webpayments#7 (9 comments by @adrianhopebailie, @davidlehn, @halindrome, @mattsaxon, @msporny)
-
Confusion over payment flow w3c/webpayments#10 (5 comments by @adrianhopebailie, @halindrome, @LaurentCastillo, @mattsaxon)
-
-
6 pull requests opened.
-
Adding Masterpass Standard Checkout Payment Flow diagram w3c/webpayments#13, by @LaurentCastillo.
-
Added Tokenisation Coniderations w3c/webpayments#12, by @mattsaxon.
-
Removed docx and spaces w3c/webpayments#8, by @mattsaxon.
-
Renamed Push to Redirect w3c/webpayments#6, by @mattsaxon.
-
Gh pages w3c/webpayments#5, by @mattsaxon.
-
Added APM current flow w3c/webpayments#4, by @mattsaxon.
-
-
6 pull requests merged.
-
Adding Masterpass Standard Checkout Payment Flow diagram w3c/webpayments#13.
-
Added Tokenisation Coniderations w3c/webpayments#12.
-
Removed docx and spaces w3c/webpayments#8.
-
Renamed Push to Redirect w3c/webpayments#6.
-
Gh pages w3c/webpayments#5.
-
Added APM current flow w3c/webpayments#4.
-
Lifecycle
-
1 charter started.
-
Chartered until 31 December 2017. Participants had to rejoin under this charter.
-
Participants
-
3 participants joined.
-
Doug Schepers (W3C) joined.
-
Wendy Seltzer (W3C) joined.
-
Ian Jacobs (W3C) joined.
-
-
19 organizations joined.
-
Knowbility joined.
-
CANTON CONSULTING joined.
-
Conexxus joined.
-
Inria joined.
-
Bloomberg joined.
-
Digital Bazaar joined.
-
Inswave Co., Ltd. joined.
-
Orange joined.
-
PayGate joined.
-
ISO 20022 Registration Authority joined.
-
IBM Corporation joined.
-
Worldpay - FIS joined.
-
360 joined.
-
Google LLC joined.
-
Mozilla Foundation joined.
-
Microsoft Corporation joined.
-
Ripple joined.
-
TPGi joined.
-
Opera Software AS joined.
-
GitHub
w3c/webpayments
-
3 pull requests opened.
-
Move docs into folder w3c/webpayments#3, by @mattsaxon.
-
Added pml files (raw uml text) w3c/webpayments#2, by @mattsaxon.
-
Initial Commit of Payment Flows w3c/webpayments#1, by @mattsaxon.
-
-
3 pull requests merged.
-
Move docs into folder w3c/webpayments#3.
-
Added pml files (raw uml text) w3c/webpayments#2.
-
Initial Commit of Payment Flows w3c/webpayments#1.
-