Tuesday, 31 May 2016
- Re: GitHub updates and new repos
- Re: [w3c/webpayments] PROPOSAL: A new document structure for this API (#134)
- Re: GitHub updates and new repos
- 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] Terminology across all Web Payments documents should be aligned (#135)
- Re: [w3c/webpayments] Terminology across all Web Payments documents should be aligned (#135)
- GitHub updates and new repos
- 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)
- 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] 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)
Saturday, 28 May 2016
- Re: Web Payments Demo
- Re: [w3c/webpayments] Clarify the concepts of enabled vs. supported (#132)
- Re: [w3c/webpayments] Registration: App supports method but user has no instrument for that method (#110)
- Re: Web Payments Demo
Friday, 27 May 2016
- 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] Registration: App supports method but user has no instrument for that method (#110)
- Re: Web Payments Demo
- RE: Web Payments Demo
- Re: [w3c/webpayments] Clarify the concepts of enabled vs. supported (#132)
- Re: [w3c/webpayments] Registration: App supports method but user has no instrument for that method (#110)
- Re: Web Payments Demo
- Re: Web Payments Demo
- Re: Google I/O talk about PaymentRequest
- [w3c/webpayments] Clarify the concepts of enabled vs. supported (#132)
- Re: [w3c/webpayments] Registration: App supports method but user has no instrument for that method (#110)
- Re: Web Payments Demo
- Re: Web Payments Demo
Thursday, 26 May 2016
- [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)
- New ISO standards for mobile payments
- Re: Web Payments Demo
Wednesday, 25 May 2016
Monday, 23 May 2016
- RE: Google I/O talk about PaymentRequest
- Re: Google I/O talk about PaymentRequest
- Re: Google I/O talk about PaymentRequest
- Re: Google I/O talk about PaymentRequest
- Re: Google I/O talk about PaymentRequest
- Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130)
- Re: Google I/O talk about PaymentRequest
Sunday, 22 May 2016
- Re: The WebPayment API vs Personal Payment Terminal
- Re: The WebPayment API vs Personal Payment Terminal
- Re: Google I/O talk about PaymentRequest
- The WebPayment API vs Personal Payment Terminal
Saturday, 21 May 2016
Friday, 20 May 2016
- Google I/O talk about PaymentRequest
- 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)
Thursday, 19 May 2016
- [Minutes] 19 May 2016 WPWG Teleconference
- 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] How can a Web Based Payment App cancel the payment flow? (#128)
- 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: AGENDA - Web Payments WG call - 19 May
- AGENDA - Web Payments WG call - 19 May
- Re: [w3c/webpayments] Choosing between javascript and http communication. (#131)
Wednesday, 18 May 2016
- Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130)
- Re: [w3c/webpayments] Choosing between javascript and http communication. (#131)
- Re: [w3c/webpayments] Choosing between javascript and http communication. (#131)
- Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130)
- [w3c/webpayments] Choosing between javascript and http communication. (#131)
- Re: Updates to Payment Apps wiki page
- Re: Updates to Payment Apps wiki page
- Re: Updates to Payment Apps wiki page
- 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: Updates to Payment Apps wiki page
- [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)
- Re: [w3c/webpayments] Update reference labels to match other docs (#117)
- Re: [w3c/webpayments] Payment Apps (#129)
- Re: Updates to Payment Apps wiki page
Tuesday, 17 May 2016
- 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] 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] Issues point to the wrong repo (#2)
- [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)
Monday, 16 May 2016
- 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)
Saturday, 14 May 2016
Friday, 13 May 2016
- Re: [w3c/webpayments] Payment Apps (#129)
- [w3c/webpayments] Payment Apps (#129)
- Re: Updates to Payment Apps wiki page
- Re: Updates to Payment Apps wiki page
Thursday, 12 May 2016
- [Minutes] 12 May 2016 WPWG teleconference
- Re: Updates to Payment Apps wiki page
- Re: Agenda for our call tomorrow
- TechCrunch article on Wallets
- Re: Agenda for our call tomorrow
- Issues for today's call
Wednesday, 11 May 2016
- Agenda for our call tomorrow
- Re: Updates to Payment Apps wiki page
- Re: Updates to Payment Apps wiki page
- Re: Updates to Payment Apps wiki page
- Re: Updates to Payment Apps wiki page
- Re: User Consent and Addresses
- Re: User Consent and Addresses
- Re: User Consent and Addresses
Tuesday, 10 May 2016
- Re: User Consent and Addresses
- Re: User Consent and Addresses
- Re: User Consent and Addresses
- Re: User Consent and Addresses
- Re: User Consent and Addresses
- Re: User Consent and Addresses
- Re: User Consent and Addresses
- Re: Updates to Payment Apps wiki page
- RE: Updates to Payment Apps wiki page
- Re: User Consent and Addresses
- Re: User Consent and Addresses
- Re: User Consent and Addresses
- Re: User Consent and Addresses
- Re: User Consent and Addresses
- Re: User Consent and Addresses
- Re: User Consent and Addresses
- Re: User Consent and Addresses
- Re: User Consent and Addresses
- Re: User Consent and Addresses
- Re: Updates to Payment Apps wiki page
- RE: Hardware Security CG
- Re: Updates to Payment Apps wiki page
- Re: Updates to Payment Apps wiki page
- Re: Updates to Payment Apps wiki page
- Re: Updates to Payment Apps wiki page
- Re: Updates to Payment Apps wiki page
- Hardware Security CG
- Re: Updates to Payment Apps wiki page
- RE: Updates to Payment Apps wiki page
Monday, 9 May 2016
- Re: Updates to Payment Apps wiki page
- Re: User Consent and Addresses
- Regrets for the next two weeks
- Updates to Payment Apps wiki page
- July 2016 Face-to-face meetings for Web Payments Interest and Working Group
Sunday, 8 May 2016
Saturday, 7 May 2016
Friday, 6 May 2016
- RE: User Consent and Addresses
- User Consent and Addresses
- Editor's Drafts for Web Payments Core Messages and HTTP API
- Re: Request for 2 new repositories
- Re: Request for 2 new repositories
- Re: Request for 2 new repositories
- Re: Request for 2 new repositories
- RE: Request for 2 new repositories
- Request for 2 new repositories
- RE: Review of Payment Apps Proposal
- Re: Dealing with Wallets
- Re: Dealing with Wallets
- Re: Dealing with Wallets
- Dealing with Wallets
Thursday, 5 May 2016
- [Minutes] 5 May 2016 WPWG teleconference
- Re: Call for reviews of HTTP API and Core Messages proposals
- Re: comments on web payment HTTP API and core message components
- Re: Call for reviews of HTTP API and Core Messages proposals
- Re: Agenda for today?
- Agenda for today?
- Re: Call for reviews of HTTP API and Core Messages proposals
- Re: Spec-Ops comments on Web Payments HTTP API 1.0
- Re: Payment Method Identifiers
- Summary of feedback on proposed adoption of Core Messages/HTTP API
- RE: Undiscussed (?) issues in Payments API
Wednesday, 4 May 2016
- Re: Payment Method Identifiers
- Undiscussed (?) issues in Payments API
- Re: Payment Method Identifiers
- Re: Payment Method Identifiers
- Re: Payment Method Identifiers
- RE: Payment Method Identifiers
- Re: Payment Method Identifiers
- Re: New repos for specs
- Re: [Suggestions on API change
- Suggestions on API change
- Re: [w3c/webpayments] New Architecture Proposal (#125)
- Re: Payment Method Identifiers
- FW: comments on web payment HTTP API and core message components
- RE: New repos for specs
- RE: comments on web payment HTTP API and core message components
- Re: Payment Method Identifiers
- Re: Call for reviews of HTTP API and Core Messages proposals
- Re: Review of Payment Apps Proposal
- Re: Payment Method Identifiers
- Payment Method Identifiers
Tuesday, 3 May 2016
- Re: New repos for specs
- Re: New repos for specs
- Re: comments on web payment HTTP API and core message components
- 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
Monday, 2 May 2016
- 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
- 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
- Basic implementation of Payment App, Payment Mediator, and Merchant App (HTTP API)