GitHub updates and new repos
[w3c/webpayments] Terminology across all Web Payments documents should be aligned (#135)
- Re: [w3c/webpayments] Terminology across all Web Payments documents should be aligned (#135)
- Re: [w3c/webpayments] Terminology across all Web Payments documents should be aligned (#135)
- Re: [w3c/webpayments] Terminology across all Web Payments documents should be aligned (#135)
- Re: [w3c/webpayments] Terminology across all Web Payments documents should be aligned (#135)
- Re: [w3c/webpayments] Terminology across all Web Payments documents should be aligned (#135)
[w3c/webpayments] PROPOSAL: A new document structure for this API (#134)
[w3c/webpayments] Should payment method specifications contain WebIDL? (#133)
- Re: [w3c/webpayments] Should payment method specifications contain WebIDL? (#133)
- Re: [w3c/webpayments] Should payment method specifications contain WebIDL? (#133)
- Re: [w3c/webpayments] Should payment method specifications contain WebIDL? (#133)
[w3c/webpayments] Clarify the concepts of enabled vs. supported (#132)
- Re: [w3c/webpayments] Clarify the concepts of enabled vs. supported (#132)
- Re: [w3c/webpayments] Clarify the concepts of enabled vs. supported (#132)
- Re: [w3c/webpayments] Clarify the concepts of enabled vs. supported (#132)
- Re: [w3c/webpayments] Clarify the concepts of enabled vs. supported (#132)
- Re: [w3c/webpayments] Clarify the concepts of enabled vs. supported (#132)
- Re: [w3c/webpayments] Clarify the concepts of enabled vs. supported (#132)
- Re: [w3c/webpayments] Clarify the concepts of enabled vs. supported (#132)
- Re: [w3c/webpayments] Clarify the concepts of enabled vs. supported (#132)
[Minutes] 26 May 2016 WPWG teleconference
Re: [w3c/webpayments] Registration: App supports method but user has no instrument for that method (#110)
- Re: [w3c/webpayments] Registration: App supports method but user has no instrument for that method (#110)
- Re: [w3c/webpayments] Registration: App supports method but user has no instrument for that method (#110)
- Re: [w3c/webpayments] Registration: App supports method but user has no instrument for that method (#110)
- Re: [w3c/webpayments] Registration: App supports method but user has no instrument for that method (#110)
- Re: [w3c/webpayments] Registration: App supports method but user has no instrument for that method (#110)
New ISO standards for mobile payments
Agenda - 26 May
Web Payments Demo
The WebPayment API vs Personal Payment Terminal
Google I/O talk about PaymentRequest
[Minutes] 19 May 2016 WPWG Teleconference
Re: [w3c/webpayments] How can a Web Based Payment App cancel the payment flow? (#128)
AGENDA - Web Payments WG call - 19 May
[w3c/webpayments] Choosing between javascript and http communication. (#131)
- Re: [w3c/webpayments] Choosing between javascript and http communication. (#131)
- Re: [w3c/webpayments] Choosing between javascript and http communication. (#131)
- Re: [w3c/webpayments] Choosing between javascript and http communication. (#131)
[w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130)
- Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130)
- Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130)
- Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130)
- Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130)
- Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130)
- Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130)
- Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130)
- Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130)
- Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130)
- Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130)
- Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130)
- Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130)
- Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130)
- Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130)
- Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130)
- Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130)
- Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130)
- Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130)
- Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130)
- Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130)
- Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130)
- Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130)
- Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130)
New payment apps proposal
Re: [w3c/webpayments] Update reference labels to match other docs (#117)
[web-payments/web-payments-http-api] Issues point to the wrong repo (#2)
- Re: [web-payments/web-payments-http-api] Issues point to the wrong repo (#2)
- Re: [web-payments/web-payments-http-api] Issues point to the wrong repo (#2)
- Re: [web-payments/web-payments-http-api] Issues point to the wrong repo (#2)
[web-payments/web-payments-http-api] Source points to the wrong repo (#1)
- Re: [web-payments/web-payments-http-api] Source points to the wrong repo (#1)
- Re: [web-payments/web-payments-http-api] Source points to the wrong repo (#1)
- Re: [web-payments/web-payments-http-api] Source points to the wrong repo (#1)
[w3c/webpayments] Payment Apps (#129)
- Re: [w3c/webpayments] Payment Apps (#129)
- Re: [w3c/webpayments] Payment Apps (#129)
- Re: [w3c/webpayments] Payment Apps (#129)
- Re: [w3c/webpayments] Payment Apps (#129)
- Re: [w3c/webpayments] Payment Apps (#129)
- Re: [w3c/webpayments] Payment Apps (#129)
- Re: [w3c/webpayments] Payment Apps (#129)
- Re: [w3c/webpayments] Payment Apps (#129)
[Minutes] 12 May 2016 WPWG teleconference
TechCrunch article on Wallets
Issues for today's call
Agenda for our call tomorrow
Hardware Security CG
Regrets for the next two weeks
Updates to Payment Apps wiki page
- Re: Updates to Payment Apps wiki page
July 2016 Face-to-face meetings for Web Payments Interest and Working Group
Experiences with Native wallet Web shop integration
Re: Spec-Ops Comments on Web Payments Core Messages 1.0
Editor's Drafts for Web Payments Core Messages and HTTP API
Request for 2 new repositories
RE: Review of Payment Apps Proposal
Dealing with Wallets
[Minutes] 5 May 2016 WPWG teleconference
Agenda for today?
Re: Spec-Ops comments on Web Payments HTTP API 1.0
Summary of feedback on proposed adoption of Core Messages/HTTP API
Undiscussed (?) issues in Payments API
- RE: Undiscussed (?) issues in Payments API
- User Consent and Addresses
- Re: User Consent and Addresses
Suggestions on API change
Re: [w3c/webpayments] New Architecture Proposal (#125)
Re: Review of Payment Apps Proposal
Payment Method Identifiers
comments on web payment HTTP API and core message components
- Re: comments on web payment HTTP API and core message components
- RE: comments on web payment HTTP API and core message components
- FW: comments on web payment HTTP API and core message components
New repos for specs
RE: Call for reviews of HTTP API and Core Messages proposals
- Re: Call for reviews of HTTP API and Core Messages proposals
Re: Call for reviews of HTTP API and Core Messages proposals
- Re: Call for reviews of HTTP API and Core Messages proposals
- Re: Call for reviews of HTTP API and Core Messages proposals