Friday, 30 September 2016
- Re: Web Payments Overview prepped for CfC
- Call for Consensus on Publishing Web Payments Overview 1.0 as a Working Group Note - RESPONSE REQUESTED
- Web Payments Overview prepped for CfC
- Re: Preparing CFC for Payments Overview document
- Re: Preparing CFC for Payments Overview document
Thursday, 29 September 2016
- [Agenda] 6 October WPWG teleconf - please look at action items inline to prepare!
- Preparing CFC for Payments Overview document
- Web Payments WG teleconf canceled today (29 Sep 2016) - next meeting 6 October
Wednesday, 28 September 2016
Tuesday, 27 September 2016
Monday, 26 September 2016
- [Draft] Minutes from 19-20 September WPWG FTF in Lisbon
- [Press about WPWG] New York Times: What if ‘One Click’ Buying Were Internetwide?
- Questions about Native App GUI integration
Friday, 23 September 2016
- Re: [w3c/webpayments] propose to add encoding attribute to data set (#181)
- Re: [w3c/webpayments] propose to add encoding attribute to data set (#181)
- Re: [w3c/webpayments] propose to add encoding attribute to data set (#181)
- Re: [w3c/webpayments] propose to add encoding attribute to data set (#181)
- Re: [w3c/webpayments] propose to add encoding attribute to data set (#181)
- [w3c/webpayments] Added 360Pay Payment Method link (#182)
- Re: [w3c/webpayments] propose to add encoding attribute to data set (#181)
- Re: [w3c/webpayments] propose to add encoding attribute to data set (#181)
- Re: [w3c/webpayments] propose to add encoding attribute to data set (#181)
- Re: [w3c/webpayments] propose to add encoding attribute to data set (#181)
- Re: [w3c/webpayments] propose to add encoding attribute to data set (#181)
- Re: [w3c/webpayments] propose to add encoding attribute to data set (#181)
- Re: [w3c/webpayments] propose to add encoding attribute to data set (#181)
- Re: [w3c/webpayments] propose to add encoding attribute to data set (#181)
- Re: [w3c/webpayments] propose to add encoding attribute to data set (#181)
- [w3c/webpayments] propose to add encoding attribute to data set (#181)
Wednesday, 21 September 2016
Tuesday, 20 September 2016
Monday, 19 September 2016
- Updated TPAC Agenda
- wpwg-ACTION-36: Revise the tokenization specification based on today's feedback
- wpwg-ACTION-35: Organize review of tokenization spec from emv perspective
- Re: wpwg-ACTION-34: Remove the diagram from basic card
- wpwg-ACTION-34: Remove the diagram from basic card
- wpwg-ACTION-33: Propose text about why the api can reduce need; without any recommendations
- wpwg-ACTION-32: Write a pull request on what might change around error handling re: addresses
- Re: Taler HTTP API
- Antitrust/competition guidance
Saturday, 17 September 2016
- Re: WPWG agenda tweaks to accommodate a logistics request re: lunch
- Re: Service-worker-based payment app proposal
- Re: Service-worker-based payment app proposal
Friday, 16 September 2016
- Service-worker-based payment app proposal
- Update of Web Payments Overview doc
- Re: [w3c/webpayments] Create tokenized_cards.html (#180)
- Re: [w3c/webpayments] Create tokenized_cards.html (#180)
- WPWG agenda tweaks to accommodate a logistics request re: lunch
- Re: Payment Method Spec for Card Issuer Tokens
- Re: Payment Method Spec for Card Issuer Tokens
- Re: Payment Method Spec for Card Issuer Tokens
- Re: Payment Method Spec for Card Issuer Tokens
- Call for Exclusions: Web Payments HTTP Messages 1.0; Web Payments HTTP API 1.0
Thursday, 15 September 2016
- Re: Payment Method Spec for Card Issuer Tokens
- [w3c/webpayments] Create tokenized_cards.html (#180)
- Minutes [Was: [Agenda] 15 September WPWG meeting]
- Re: Payment Method Spec for Card Issuer Tokens
- Re: Payment Method Spec for Card Issuer Tokens
- Feedback on Roy's document on Push Payments
- wpwg-ACTION-31: Update the spec to mention care in multi-line handling with careof as an example.
- Re: FPWD-ready Web Payments HTTP API and HTTP Messages specs
- Two Web Payments FPWDs published
- Re: FPWD-ready Web Payments HTTP API and HTTP Messages specs
- Re: Payment Method Spec for Card Issuer Tokens
- Re: Payment Method Spec for Card Issuer Tokens
- Re: Payment Method Spec for Card Issuer Tokens
- Re: FPWD-ready Web Payments HTTP API and HTTP Messages specs
- Re: Payment Method Spec for Card Issuer Tokens
Wednesday, 14 September 2016
- Payment Method Spec for Card Issuer Tokens
- [Agenda] 15 September WPWG meeting
- Re: [Agenda] 14 September Payment Apps task force meeting
Tuesday, 13 September 2016
- Re: [Agenda] 14 September Payment Apps task force meeting
- [Agenda] 14 September Payment Apps task force meeting
Monday, 12 September 2016
- Re: FPWD-ready Web Payments HTTP API and HTTP Messages specs
- RE: W3C TPAC WhatsApp Group
- Re: W3C TPAC WhatsApp Group
- W3C TPAC WhatsApp Group
- Re: Taler HTTP API
- Re: FPWD-ready Web Payments HTTP API and HTTP Messages specs
- Taler HTTP API
- [w3c/webpayments] Propose a payment method specification that includes an example of field level security (#179)
- Re: FPWD-ready Web Payments HTTP API and HTTP Messages specs
Saturday, 10 September 2016
Friday, 9 September 2016
- Re: FPWD-ready Web Payments HTTP API and HTTP Messages specs
- Re: FPWD-ready Web Payments HTTP API and HTTP Messages specs
- FPWD-ready Web Payments HTTP API and HTTP Messages specs
Thursday, 8 September 2016
- 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] How can a Web Based Payment App cancel the payment flow? (#128)
- Re: [w3c/webpayments] How can a Web Based Payment App cancel the payment flow? (#128)
- Re: [w3c/webpayments] Registration: Should we support payee knowing user has payee-controlled payment app? (#112)
- Re: [w3c/webpayments] Registration: Should we support payee knowing user has payee-controlled payment app? (#112)
- Re: [w3c/webpayments] Registration: How is registration information updated? (#111)
- Re: [w3c/webpayments] Registration: How is registration information updated? (#111)
- Minutes [Was: [AGENDA] 8th September 2016]
- Re: Initial draft of "Payment Method Best Practice"
Wednesday, 7 September 2016
- Nick Telford-Reed Interview with David Birch on W3C Web Payments
- Decision regarding HTTP API/Core Messages Publication
- [AGENDA] 8th September 2016
- Initial draft of "Payment Method Best Practice"
- Re: [w3c/webpayments] Respec data update (#178)
- [w3c/webpayments] Respec data update (#178)
Tuesday, 6 September 2016
Saturday, 3 September 2016
Friday, 2 September 2016
- Re: i18n-ISSUE-214: Improper use of languageCode
- Re: i18n-ISSUE-214: Improper use of languageCode
- Re: i18n-ISSUE-214: Improper use of languageCode
- Re: i18n-ISSUE-214: Improper use of languageCode
- Re: i18n-ISSUE-214: Improper use of languageCode
- Re: [w3c/webpayments] small bug fixes (#177)
- [w3c/webpayments] small bug fixes (#177)
- [w3c/webpayments] Add payment method best practice proposal (#176)
- Re: [w3c/webpayments] Add payment method best practice proposal (#176)
- Re: [w3c/webpayments] Overhaul (#175)
- [w3c/webpayments] Overhaul (#175)
- Re: i18n-ISSUE-214: Improper use of languageCode
- Re: i18n-ISSUE-214: Improper use of languageCode
- Re: i18n-ISSUE-214: Improper use of languageCode
Thursday, 1 September 2016
Friday, 2 September 2016
Thursday, 1 September 2016
- [w3c/webpayments] Payment apps moved to its own repo (#174)
- Re: [w3c/webpayments] delete utils (#173)
- [w3c/webpayments] delete utils (#173)
- Minutes [Was: [Agenda] 1 September WPWG teleconference]
- [Minutes] 25 August WPWG teleconference
- Re: i18n-ISSUE-214: Improper use of languageCode
- wpwg-ACTION-30: Work on the distinction between open and proprietary
- Re: i18n-ISSUE-214: Improper use of languageCode
- Re: i18n-ISSUE-212: Prevent the use of currency synonyms
- i18n-ISSUE-212: Prevent the use of currency synonyms
- i18n-ISSUE-214: Improper use of languageCode
- Re: PMI Proposals and Discussion Tomorrow