[w3c/webpayments] Fix payment options references + proposal on recommended apps (#150)
FTF meeting attendance is full
Review ready Core Messages and HTTP API specs
PROPOSED: No meeting this week
Updated Web Payments Architecture Summary
[w3c/webpayments] Include the IG terminology document (#149)
[Minutes] Web Payments WG meeting 2016-06-23
AGENDA
[w3c/webpayments] Api shape and payment options (#148)
- Re: [w3c/webpayments] Api shape and payment options (#148)
- Re: [w3c/webpayments] Api shape and payment options (#148)
- Re: [w3c/webpayments] Api shape and payment options (#148)
[w3c/webpayments] Update conformance (#147)
- Re: [w3c/webpayments] Update conformance (#147)
- Re: [w3c/webpayments] Update conformance (#147)
- Re: [w3c/webpayments] Update conformance (#147)
- Re: [w3c/webpayments] Update conformance (#147)
- Re: [w3c/webpayments] Update conformance (#147)
- Re: [w3c/webpayments] Update conformance (#147)
[w3c/webpayments] Adding issues to payment app specification (#146)
- Re: [w3c/webpayments] Adding issues to payment app specification (#146)
- Re: [w3c/webpayments] Adding issues to payment app specification (#146)
Re: [WICG/historical-web-payments-browser-api] Status update (#8)
[w3c/webpayments] Moved notes and issues into markers to distinguish from spec text (#145)
[w3c/webpayments] Use notes and issues more consistently (#144)
- Re: [w3c/webpayments] Use notes and issues more consistently (#144)
- Re: [w3c/webpayments] Use notes and issues more consistently (#144)
[w3c/webpayments] How should third-party payment apps be displayed by the browser? (#143)
- Re: [w3c/webpayments] How should third-party payment apps be displayed by the browser? (#143)
- Re: [w3c/webpayments] How should third-party payment apps be displayed by the browser? (#143)
- Re: [w3c/webpayments] How should third-party payment apps be displayed by the browser? (#143)
- Re: [w3c/webpayments] How should third-party payment apps be displayed by the browser? (#143)
- Re: [w3c/webpayments] How should third-party payment apps be displayed by the browser? (#143)
[w3c/webpayments] Registration: Should payment instrument details be included? (#142)
Re: [w3c/webpayments] Registration: How is registration information updated? (#111)
- Re: [w3c/webpayments] Registration: How is registration information updated? (#111)
- Re: [w3c/webpayments] Registration: How is registration information updated? (#111)
- Re: [w3c/webpayments] Registration: How is registration information updated? (#111)
- Re: [w3c/webpayments] Registration: How is registration information updated? (#111)
Help Required on Issues
Reminder - Interledger Workshop - 6 July - London
Re: [w3c/webpayments] Choosing between javascript and http communication. (#131)
[w3c/webpayments] What happens if there’s a failure before the payment response promise resolves? (#141)
[w3c/webpayments] More info about UX around app recommendation and selection (#140)
- Re: [w3c/webpayments] More info about UX around app recommendation and selection (#140)
- Re: [w3c/webpayments] More info about UX around app recommendation and selection; network failures (#140)
- Re: [w3c/webpayments] More info about UX around app recommendation and selection; network failures (#140)
- Re: [w3c/webpayments] More info about UX around app recommendation and selection; network failures (#140)
[WICG/web-payments-browser-api] Status update (#8)
[WICG/paymentrequest] Web Payments WG relation to this repo (#71)
- Re: [WICG/paymentrequest] Web Payments WG relation to this repo (#71)
- Re: [WICG/paymentrequest] Web Payments WG relation to this repo (#71)
- Re: [WICG/paymentrequest] Web Payments WG relation to this repo (#71)
- Re: [WICG/paymentrequest] Web Payments WG relation to this repo (#71)
- Re: [WICG/paymentrequest] Web Payments WG relation to this repo (#71)
- Re: [WICG/paymentrequest] Web Payments WG relation to this repo (#71)
- Re: [WICG/paymentrequest] Web Payments WG relation to this repo (#71)
- Re: [WICG/paymentrequest] Web Payments WG relation to this repo (#71)
[WICG/web-payments-browser-api] Web Payments WG relation to this repo (#7)
Re: Call for reviews of HTTP API and Core Messages proposals
Re: 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
- Re: comments on web payment HTTP API and core message components
New Web Payments Architecture document proposal
- Re: New Web Payments Architecture document proposal
- Re: New Web Payments Architecture document proposal
- Re: New Web Payments Architecture document proposal
[Minutes] 16 June WPWG teleconference
Re: [w3c/webpayments] Registration: Should we support payee knowing user has payee-controlled payment app? (#112)
[w3c/webpayments] Editorial changes for more context (#139)
- Re: [w3c/webpayments] Editorial changes for more context (#139)
- Re: [w3c/webpayments] Editorial changes for more context (#139)
[w3c/webpayments] Gh pages (#138)
Agenda
[w3c/webpayments] Should the browser pass user data it has collected (email etc) to the payment app? (#137)
[w3c/webpayments] Some edits on @ianbjacobs refactoring (#136)
Apple Pay on the Web
WPWG meeting minutes for 2016-06-09
Agenda for WG call tomorrow
[Minutes] 2 June 2016 WPWG teleconference
AGENDA - 2 June
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)