PMI proposal
[Minutes] 28 July 2016 WPWG teleconference
wpwg-ACTION-24: Work with chairs + team contacts to formalize who is responsible for the activities mentioned at the ftf around tokenized card payment method spec, and payment method spec good practices
wpwg-ACTION-23: Look into what the right practice is if we use urns.
[Agenda] 28 July 2016 WPWG teleconference
WPWG Blog post on July FTF meeting
[Agenda] 27 July Payment Apps task force meeting
[Time-sensitive] Please register WPWG FTF meeting on 19-20 September, and other parts of TPAC by 2 September
No meeting tomorrow (21st July)
Payment Apps Task Force Update
Concerns about Core Messages specification
Re: [WICG/historical-paymentrequest] Web Payments WG relation to this repo (#71)
Re: [WICG/historical-paymentrequest] Payment App Registration: Same Origin is problematic for identifying_url (#66)
[w3c/webpayments] [Payment apps] How can we optimize user experience when there is only one match? (#169)
[w3c/webpayments] [Payment app] Should merchants be able to limit matching to trusted apps? (#168)
- Re: [w3c/webpayments] [Payment app] Should merchants be able to limit matching to trusted apps? (#168)
- Re: [w3c/webpayments] [Payment app] Should merchants be able to limit matching to trusted apps? (#168)
Visa Europe disclosure of patents and exclusion of claims in Web Payments Working Group
Re: [w3c/webpayments] Security and Privacy Self-Review (#61)
POLL - Preferred time for WG calls going forward
ACTION REQUIRED: Payment Method Identifiers
Comments on HTTP API before publishing FPWD
NO meeting tomorrow
Three new first public drafts: Overview, Core Messages, HTTP API
ReSpec and messed up characters in the ToC jump at F2F
[w3c/webpayments] How should the group update documents in 'TR' space? (#167)
- Re: [w3c/webpayments] How should the group update documents in 'TR' space? (#167)
- Re: [w3c/webpayments] How should the group update documents in 'TR' space? (#167)
- Re: [w3c/webpayments] How should the group update documents in 'TR' space? (#167)
- Re: [w3c/webpayments] How should the group update documents in 'TR' space? (#167)
- Re: [w3c/webpayments] How should the group update documents in 'TR' space? (#167)
Web Payments Overview published
WPWG - No Meeting - 14 July
[Minutes] London FTF meeting (7-8 July 2016)
Encrypting basic card data
- Re: Encrypting basic card data
- RE: Encrypting basic card data
[w3c/webpayments] [Payment Apps] What portion of the PaymentRequest is sent to the payment app? (#166)
- Re: [w3c/webpayments] [Payment Apps] What portion of the PaymentRequest is sent to the payment app? (#166)
- Re: [w3c/webpayments] [Payment Apps] What portion of the PaymentRequest is sent to the payment app? (#166)
[w3c/webpayments] [Payment App] Should the payment app registration be for Browsers only or also for other types of User Agents (#165)
- Re: [w3c/webpayments] [Payment App] Should the payment app registration be for Browsers only or also for other types of User Agents (#165)
- Re: [w3c/webpayments] [Payment App] Should the payment app registration be for Browsers only or also for other types of User Agents (#165)
- Re: [w3c/webpayments] [Payment App] Should the payment app registration be for Browsers only or also for other types of User Agents (#165)
- Re: [w3c/webpayments] [Payment App] Should the payment app registration be for Browsers only or also for other types of User Agents (#165)
[w3c/webpayments] [Payment App] How is Native App integration code supplied? (#164)
- Re: [w3c/webpayments] [Payment App] How is Native App integration code supplied? (#164)
- Re: [w3c/webpayments] [Payment App] How is Native App integration code supplied? (#164)
- Re: [w3c/webpayments] [Payment App] How is Native App integration code supplied? (#164)
- Re: [w3c/webpayments] [Payment App] How is Native App integration code supplied? (#164)
- Re: [w3c/webpayments] [Payment App] How is Native App integration code supplied? (#164)
[w3c/webpayments] [Payment App] PROPOSAL: Payment Apps are javascript code that use event listeners to get the PaymentRequest (#163)
- Re: [w3c/webpayments] [Payment App] PROPOSAL: Payment Apps are javascript code that use event listeners to get the PaymentRequest (#163)
- Re: [w3c/webpayments] [Payment App] PROPOSAL: Payment Apps are javascript code that use event listeners to get the PaymentRequest (#163)
[w3c/webpayments] [Payment Apps] What is the process for rendering the payment app UI (#162)
- Re: [w3c/webpayments] [Payment Apps] What is the process for rendering the payment app UI (#162)
- Re: [w3c/webpayments] [Payment Apps] What is the process for rendering the payment app UI (#162)
[w3c/webpayments] [Payment Apps] Display may be subject to user and local policy (consider UA making security decisions etc) (#161)
- Re: [w3c/webpayments] [Payment Apps] Display may be subject to user and local policy (consider UA making security decisions etc) (#161)
- Re: [w3c/webpayments] [Payment Apps] Display may be subject to user and local policy (consider UA making security decisions etc) (#161)
[w3c/webpayments] [Payment Apps] Should we allow payment providers to issue queries about their installed payment apps (match on origin) (#160)
- Re: [w3c/webpayments] [Payment Apps] Should we allow payment providers to issue queries about their installed payment apps (match on origin) (#160)
- Re: [w3c/webpayments] [Payment Apps] Should we allow payment providers to issue queries about their installed payment apps (match on origin) (#160)
[w3c/webpayments] [Payment Request] Should we allow a "polling" mechanism for websites to not invoke the API if there are no enabled methods (#159)
- Re: [w3c/webpayments] [Payment Request] Should we allow a "polling" mechanism for websites to not invoke the API if there are no enabled methods (#159)
- Re: [w3c/webpayments] [Payment Request] Should we allow a "polling" mechanism for websites to not invoke the API if there are no enabled methods (#159)
- Re: [w3c/webpayments] [Payment Request] Should we allow a "polling" mechanism for websites to not invoke the API if there are no enabled methods (#159)
- Re: [w3c/webpayments] [Payment Request] Should we allow a "polling" mechanism for websites to not invoke the API if there are no enabled methods (#159)
- Re: [w3c/webpayments] [Payment Request] Should we allow a "polling" mechanism for websites to not invoke the API if there are no enabled methods (#159)
- Re: [w3c/webpayments] [Payment Request] Should we allow a "polling" mechanism for websites to not invoke the API if there are no enabled methods (#159)
- Re: [w3c/webpayments] [Payment Request] Should we allow a "polling" mechanism for websites to not invoke the API if there are no enabled methods (#159)
- Re: [w3c/webpayments] [Payment Request] Should we allow a "polling" mechanism for websites to not invoke the API if there are no enabled methods (#159)
- Re: [w3c/webpayments] [Payment Request] Should we allow a "polling" mechanism for websites to not invoke the API if there are no enabled methods (#159)
- Re: [w3c/webpayments] [Payment Request] Should we allow a "polling" mechanism for websites to not invoke the API if there are no enabled methods (#159)
- Re: [w3c/webpayments] [Payment Request] Should we allow a "polling" mechanism for websites to not invoke the API if there are no enabled methods (#159)
- Re: [w3c/webpayments] [Payment Request] Should we allow a "polling" mechanism for websites to not invoke the API if there are no enabled methods (#159)
- Re: [w3c/webpayments] [Payment Request] Should we allow a "polling" mechanism for websites to not invoke the API if there are no enabled methods (#159)
- Re: [w3c/webpayments] [Payment Request] Should we allow a "polling" mechanism for websites to not invoke the API if there are no enabled methods (#159)
- Re: [w3c/webpayments] [Payment Request] Should we allow a "polling" mechanism for websites to not invoke the API if there are no enabled methods (#159)
- Re: [w3c/webpayments] [Payment Request] Should we allow a "polling" mechanism for websites to not invoke the API if there are no enabled methods (#159)
- Re: [w3c/webpayments] [Payment Request] Should we allow a "polling" mechanism for websites to not invoke the API if there are no enabled methods (#159)
- Re: [w3c/webpayments] [Payment Request] Should we allow a "polling" mechanism for websites to not invoke the API if there are no enabled methods (#159)
- Re: [w3c/webpayments] [Payment Request] Should we allow a "polling" mechanism for websites to not invoke the API if there are no enabled methods (#159)
- Re: [w3c/webpayments] [Payment Request] Should we allow a "polling" mechanism for websites to not invoke the API if there are no enabled methods (#159)
[w3c/webpayments] [Payment Apps] Split out enabled and supported methods (#158)
- Re: [w3c/webpayments] [Payment Apps] Split out enabled and supported methods (#158)
- Re: [w3c/webpayments] [Payment Apps] Split out enabled and supported methods (#158)
- Re: [w3c/webpayments] [Payment Apps] Split out enabled and supported methods (#158)
Group Photo from Face-to-Face
Security and Privacy Considerations
- Re: Security and Privacy Considerations
- Re: Security and Privacy Considerations
- Re: Security and Privacy Considerations
wpwg-ACTION-22: Try to get a security review within bpce
wpwg-ACTION-21: Try to get a security review organized within worldpay
ISO 4217 proposal to improve support for digital currencies
wpwg-ACTION-20: Work on concrete spec language around currency codes
W3C WPWG: Dinner for tonight
[w3c/webpayments] [Payment Apps] “Security Error” on different origins (#157)
[w3c/webpayments] [Payment Apps] Extending invocation of payment apps with other techniques than HTTP (#156)
- Re: [w3c/webpayments] [Payment Apps] Extending invocation of payment apps with other techniques than HTTP (#156)
- Re: [w3c/webpayments] [Payment Apps] Extending invocation of payment apps with other techniques than HTTP (#156)
- Re: [w3c/webpayments] [Payment Apps] Extending invocation of payment apps with other techniques than HTTP (#156)
- Re: [w3c/webpayments] [Payment Apps] Extending invocation of payment apps with other techniques than HTTP (#156)
- Re: [w3c/webpayments] [Payment Apps] Extending invocation of payment apps with other techniques than HTTP (#156)
- Re: [w3c/webpayments] [Payment Apps] Extending invocation of payment apps with other techniques than HTTP (#156)
- Re: [w3c/webpayments] [Payment Apps] Extending invocation of payment apps with other techniques than HTTP (#156)
- Re: [w3c/webpayments] [Payment Apps] Extending invocation of payment apps with other techniques than HTTP (#156)
- Re: [w3c/webpayments] [Payment Apps] Extending invocation of payment apps with other techniques than HTTP (#156)
- Re: [w3c/webpayments] [Payment Apps] Extending invocation of payment apps with other techniques than HTTP (#156)
- Re: [w3c/webpayments] [Payment Apps] Extending invocation of payment apps with other techniques than HTTP (#156)
- Re: [w3c/webpayments] [Payment Apps] Extending invocation of payment apps with other techniques than HTTP (#156)
- Re: [w3c/webpayments] [Payment Apps] Extending invocation of payment apps with other techniques than HTTP (#156)
[w3c/webpayments] What should be the user experience when an app is recommended for two methods? (#155)
Face to face notes
Thoughts on Native Payments
Updated (TR) drafts of Payment Request API and Payment Method Identifiers
Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130)
ANSI X9.122 Secure Customer Authentication for Internet Payments
- Re: ANSI X9.122 Secure Customer Authentication for Internet Payments
- Re: ANSI X9.122 Secure Customer Authentication for Internet Payments
Presentation on Web Payments Core Messages and HTTP API
Web Payments Architecture Summary?
- Re: Web Payments Architecture Summary?
- Re: Web Payments Architecture Summary?
- Re: Web Payments Architecture Summary?
[w3c/webpayments] Minor fix to register also (#154)
[w3c/webpayments] Add reference to origin and fix a mistake in the registration API (#153)
Payment Apps Proposal
Security Review of 3 WPWG WDs (using W3C TAG checklist)
RE: New Web Payments Architecture document proposal
Re: [w3c/webpayments] Registration: Should payment instrument details be included? (#142)
[w3c/webpayments] Editorial walk-through (#152)
- Re: [w3c/webpayments] Editorial walk-through (#152)
- Re: [w3c/webpayments] Editorial walk-through (#152)
- Re: [w3c/webpayments] Editorial walk-through (#152)